I've installed a fresh copy of XP x64 recently but am being constantly interupted by blue screen errors.
I've used driver agent to check for updated drivers, and all (according to this site) are current. there is no pattern to the blue screens. happens with one program open, sometimes no programs (at night). sometimes after 10 minutes, sometimes after several hours.
what virus or firewall program what are you using, what is your system,soundcard,videocard,ram,psu,motherboard.Specks please,
http://aumha.org/a/stop.htm
Message edited by gomerpile on 11-02-2007 at 11:04:02 PM
---------------
WAITING FOR THE NEXT MOMENT TO STRIKE
OS Name Microsoft(R) Windows(R) XP Professional x64 Edition
Version 5.2.3790 Service Pack 2 Build 3790
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name GLHAMD64
System Manufacturer VIAK8T
System Model AWRDACPI
System Type x64-based PC
Processor AMD64 Family 15 Model 15 Stepping 0 AuthenticAMD ~2452 Mhz
BIOS Version/Date Phoenix Technologies, LTD 6.00 PG, 1/19/2005
SMBIOS Version 2.3
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.2.3790.3959 (srv03_sp2_rtm.070216-1710)"
User Name HEDRICK\garyh
Time Zone Pacific Daylight Time
Total Physical Memory 4,095.26 MB
Available Physical Memory 3.09 GB
Total Virtual Memory 5.76 GB
Available Virtual Memory 5.14 GB
Page File Space 2.00 GB
Page File C:\pagefile.sys
Ok read the link I posted there are many things that can cause this, bad memory, incompatiable drivers, try a different sound driver for your card.
What are you doing when this happens, have you noticed if before or after a sound this happens or closing opening an application, or anytime when using a app.
in the run type
eventVwr.msc see if an app is causing this and what app
ok I see there is no pattern so now this say that something in momery my be causing this or a bug of somesort
Message edited by gomerpile on 11-02-2007 at 11:16:09 PM
---------------
WAITING FOR THE NEXT MOMENT TO STRIKE
Also, i was having these problems for a couple of months. i reformatted the drive on the 29th, and started reloading everything a new. looking at the system event log,
10/30 2:05 p.m.:
Source: System error:
Immediately before that:
The Plug and Play operation cannot be completed because a device driver is preventing the device from stopping. The name of the device driver is listed as the vetoing service name below.
Vetoed device: STORAGE\REMOVABLEMEDIA\8&F5F4DBD&0&RM
Vetoing device: STORAGE\RemovableMedia\8&f5f4dbd&0&RM
Vetoing service name: FileSystem\RAW
Veto type 6: PNP_VetoDevice
When Windows attempts to install, upgrade, remove, or reconfigure a device, it queries the driver responsible for that device to confirm that the operation can be performed. If any of these drivers denies permission (query-removal veto), then the computer must be restarted in order to complete the operation.
User Action
Restart your computer.
The time service is now synchronizing the system time with the time source hedcogaserver.hedrick.local (ntp.d|192.168.1.107:123->192.168.1.5:123).
Source W32time
The time service is now synchronizing the system time with the time source hedcodserver.hedrick.local (ntp.d|192.168.1.107:123->192.168.1.6:123).
Source W32time
The time service is now synchronizing the system time with the time source hedcodserver.hedrick.local (ntp.d|192.168.1.107:123->192.168.1.6:123).
Source W32time
The time service is now synchronizing the system time with the time source hedcodserver.hedrick.local (ntp.d|192.168.1.107:123->192.168.1.6:123).
Source W32time
The time service is now synchronizing the system time with the time source hedcodserver.hedrick.local (ntp.d|192.168.1.107:123->192.168.1.6:123).
Source W32time
The time service is now synchronizing the system time with the time source hedcodserver.hedrick.local (ntp.d|192.168.1.107:123->192.168.1.6:123).
Source W32time
The time service is now synchronizing the system time with the time source hedcodserver.hedrick.local (ntp.d|192.168.1.107:123->192.168.1.6:123).
sound card:
Name Creative X-Fi Audio Processor (WDM)
Manufacturer Creative Technology, Ltd.
Status OK
PNP Device ID PCI\VEN_1102&DEV_0005&SUBSYS_00211102&REV_00\3&13C0B0C5&0&50
I/O Port 0x0000B400-0x0000B41F
Memory Address 0xEF000000-0xEF1FFFFF
Memory Address 0xE8000000-0xEBFFFFFF
IRQ Channel IRQ 18
Driver c:\windows\system32\drivers\ctaud2k.sys (5.12.01.1201-2.10.0760, 833.75 KB (853,760 bytes), 8/17/2006 1:18 PM)
Name Realtek AC'97 Audio for VIA (R) Audio Controller
Manufacturer Realtek
Status OK
PNP Device ID PCI\VEN_1106&DEV_3059&SUBSYS_1415147B&REV_60\3&13C0B0C5&0&8D
I/O Port 0x0000E800-0x0000E8FF
IRQ Channel IRQ 22
Driver c:\windows\system32\drivers\alcwdm64.sys (5.10.00.6260 built by: WinDDK, 3.40 MB (3,566,592 bytes), 10/29/2007 11:53 AM)
I think so I'm thinking if anyone has a topof the hat know please help
http://support.microsoft.com/kb/223184 manual set read this ok I'm working on it
ok I'm sick and need to lay down for a bit I'll be back sry flu
Message edited by gomerpile on 11-03-2007 at 12:02:11 AM
---------------
WAITING FOR THE NEXT MOMENT TO STRIKE
sound card:
Name Creative X-Fi Audio Processor (WDM)
Manufacturer Creative Technology, Ltd.
Status OK
PNP Device ID PCI\VEN_1102&DEV_0005&SUBSYS_00211102&REV_00\3&13C0B0C5&0&50
I/O Port 0x0000B400-0x0000B41F
Memory Address 0xEF000000-0xEF1FFFFF
Memory Address 0xE8000000-0xEBFFFFFF
IRQ Channel IRQ 18
Driver c:\windows\system32\drivers\ctaud2k.sys (5.12.01.1201-2.10.0760, 833.75 KB (853,760 bytes), 8/17/2006 1:18 PM)
Name Realtek AC'97 Audio for VIA (R) Audio Controller
Manufacturer Realtek
Status OK
PNP Device ID PCI\VEN_1106&DEV_3059&SUBSYS_1415147B&REV_60\3&13C0B0C5&0&8D
I/O Port 0x0000E800-0x0000E8FF
IRQ Channel IRQ 22
Driver c:\windows\system32\drivers\alcwdm64.sys (5.10.00.6260 built by: WinDDK, 3.40 MB (3,566,592 bytes), 10/29/2007 11:53 AM)
no sounds or anything prior to the crash.
ok I see you have a creative sound card plus you have the realtek
disable onboard sound
uninstal those drivers
that just may fix you
---------------
WAITING FOR THE NEXT MOMENT TO STRIKE
in control panel add and remove programs if not in there then don't worry the disable fixed the remove I hope
try to get speedupmypc by uniblue that is a good program to use to fix errors
that creative the music or what, the drivers are touchy
disable also in bios
Message edited by gomerpile on 11-03-2007 at 12:51:49 AM
---------------
WAITING FOR THE NEXT MOMENT TO STRIKE
Thanks for the help. i disabled the ON Chip Audio in the Bios, deleted the software and disabled the RealTech in the device manager.
it will probably take a day or so to tell if there is another crash. it does make some sense, after reinstalling xp64, it took a day or so to get all the microsoft updates, install drivers. i'm not sure when i loaded the Creative, or the Realtech.
i have been using CrapCleaner for some cleanup duties. went to the Speedupmypc site and downloaded the program, but alas, it does not support 64bit systems.
Looking at the timeservice might have caused the error I'm giving you a snap of my registry entry so you can compare it, maybe change yours to what I have but save your registry entry incase you need to inport it back.HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
Shot at 2007-11-05
By the looks of this code some app or driver is causing the error, however I can not be absolutely sure if its because of failing memory,CPU addressing. Maybe disable synchronizing of time service explained in the link http://support.microsoft.com/kb/223184 about timeservice
http://oca.microsoft.com/en/welcome.aspx Report error
Have you gone into administrative tools and look in the eventlog look under system, upon investigating my log I noticed how timeservice has a warning stating unsynchronized timeservice. If it is reporting an error in there you can go to the proprieties of the error and then click yes and this will bring you to microsoft answers to solve the error.
Message edited by gomerpile on 11-05-2007 at 02:14:14 PM
---------------
WAITING FOR THE NEXT MOMENT TO STRIKE
W32Time service registry values
• AvoidTimeSyncOnWan : REG_DWORD (optional)
Prevents the computer from synchronizing with a computer that is in another site.
0 = the site of the time source is ignored [default]
1 = the computer does not synchronize with a time source that is in a different site
• GetDcBackoffMaxTimes : REG_DWORD (optional)
The maximum number of times to double the backoff interval when successive attempts to find a domain controller do not succeed. An event is logged every time a wait of the maximum length occurs.
0 = the wait between successive attempts is always the minimum and no event is logged
7 = [default]
• GetDcBackoffMinutes : REG_DWORD (optional)
The initial number of minutes to wait before looking for a domain controller if the last attempt did not succeed.
15 = [default]
• LocalNTP : REG_DWORD
Used to start the SNTP server.
0 = do not start the SNTP server unless this computer is a domain controller[default]
1 = always start the SNTP server
• NtpServer : REG_SZ (optional)
NtpServer : REG_SZ (optional) Used to manually configure the time source. Set this to the DNS name or IP address of the NTP server to synchronize from. You can modify this from the command line by using the net time command. Value is blank by default
Note If you enter multiple NTP entries you must separate the entries with a space. For example, if you enter two different IP addresses for two distinct NTP servers, you must separate the entries with a space. Do not use a comma to separate multiple IP addresses or multiple fully qualified domain names (FQDNs).
• Period : REG_DWORD or REG_SZ
Used to control how often the time service synchronizes. If a string value is specified, it must be one of special ones listed below. If you specify the string value by using the numbers (65535 for example), then create the value as a REG_DWORD. If you use the word to specify the string value (BiDaily for example), then the entry should be created as a REG_SZ.
0 = once a day
65535, "BiDaily" = once every 2 days
65534, "Tridaily" = once every 3 days
65533, "Weekly" = once every week (7 days)
65532, "SpecialSkew" = once every 45 minutes until 3 good synchronizations occur, then once every 8 hours (3 per day) [default]
65531, "DailySpecialSkew" = once every 45 minutes until 1 good synchronization occurs, then once every day
freq = freq times per day
• ReliableTimeSource : REG_DWORD (optional)
Used to indicate that this computer has reliable time.
0 = do not mark this computer as having reliable time [default]
1 = mark this computer as having reliable time (this is only useful on a domain controller)
• Type : REG_SZ
Used to control how a computer synchronizes.
Nt5DS = synchronize to domain hierarchy [default]
NTP = synchronize to manually configured source
NoSync = do not synchronize time
The Nt5DS setting may not use a manual configured source.
Note When you join a Microsoft Windows Server 2003-based computer to a domain, the computer may not synchronize its time setting with the time setting of the domain controller if the Automatically synchronize with an Internet time server check box in the Date and Time Properties dialog box is not selected. The default option (NTP) for Windows Server 2003 workgroup computers is disabled if the Automatically synchronize with an Internet time server check box is not selected. When you join the computer to a domain that has this setting, the default synchronization type (Nt5DS) for computers that are joined to a domain is not set and the time service does not synchronize from the domain hierarchy.
The Adj and msSkewPerDay values are used to preserve information about the computer's clock between restarts. Do not manually edit these values. For additional information about the Windows Time service, click the following article number to view the article in the Microsoft Knowledge Base:
224799 (http://support.microsoft.com/kb/224799/) Basic operation of the Windows Time service
should i try to not joine a domain, but make it a workgroup?
Note When you join a Microsoft Windows Server 2003-based computer to a domain, the computer may not synchronize its time setting with the time setting of the domain controller if the Automatically synchronize with an Internet time server check box in the Date and Time Properties dialog box is not selected
to make the last message shorter, my dialoge box for date and time does not have an "automaticly syncronize" spot. i remember this on other operating systems. any idea?
i think you can see, i'm not very good technically.
You have to do that through the registry the key I showed you compair your key to what I have shown. the pic is larger if you click on it then at the bottom
---------------
WAITING FOR THE NEXT MOMENT TO STRIKE