I have hand built my computer and have had lots of problems with it since I put it together this summer(mostly random reboots), a few weeks ago I had a major hardware problem and I tracked it down to being bad ram. I have since replaced the ram and it ran beautifully for about 3 days, then I started getting blue screen of death, I have figured out that I only get blue screens when I leave it sitting idle for 10-20 minutes, idle being only programs running are fire wall antivirus background stuff. I can do all my normal work and games on it without issue, and I have noticed that if I leave some music running it doesnt have a problem, I have tested this by letting music run all night for the last few days without issue. But I dont want to have to resort to running off of my external harddrive for long periods of time.

this is the error code I get: OXOOOOOO9L (OXOOOOOOO4, OX805461FO, OXB2OOOOOO, OXOOO7OFOF)

at the blue screen I cant tell if the O are 0 those may all be 0's instead of letter O it has constantly been the same code.

Im running

XP pro
AMD64 3500+ singlecore standard 2.2ghz, but Im overclocking it to 2.4
3gigs kingston pc3200ram
Asus A8N32-sli deluxe motherboard
nvidia 6600 pciexpress video card

 

Did you copy and paste the panic code from the "Your system has recovered from a serious error" screen after it started up, or did you write that down then post? I'd let it do it again, and once it comes up, click more info and copy and paste the exact error code. I have a feeling that these *should* be zeros, not "O"s

 

Could be a few things. Could be an IRQ confilct (rare), Could be a bad install of winders (not uncommon), could be video card drivers. Could be a heat issue. Without having it on the bench, I really wouldn't be able to give an absolute answer.

 

or, we could get the panic code and go from there

 

They absolutely are zeros not "O"s, can't have an O in a hexadecimal number

Have you tried not overclocking it? If you are running an overclocked computer, the first thing to try when it's unstable is to run at the normal clock speed and then figure out what component couldn't handle the speed (RAM, PCI bus cards, processor, northbridge, etc). I'm on an overclocked computer too.. 1.866ghz overclocked to 2.66ghz! I had some issues with my RAM running at this speed, took a lot of tweaking memory timings and even RAM drive strength to get it working stable.

 

with overclocking on it gave me blue screen 20mins, overclocking off bluescreen 40mins. and both times when windows came up again, there was no "windows recovered from a serious error " message to report, just booted up like nothing happened. also both times had the same code forgot to mention the blue screen message says "machine_check_exception" dont know if that makes any difference

Cooling, I have 5X120mm fans , 1x90mm on the cpu, I can run games for hours on end and the system doesnt over heat(dont remember the numbers under stress for cpu and board I havent reinstalled my monitor program yet), so sitting idle I would guess no. I am running a 650w power supply, 2 dvdrw, and 2 hard drives.

how did you work that much out of your cpu kansei?

 

It all depends on the processor architecture.

Go to the System control panel, Advanced tab, then click "settings" in a section on that tab that I think is called "startup and recovery" (I'm doing this from memory, bear with me). In the new window that opens there should be something along the likes of "restart automatically" in case of a system failure. Make it so that it doesn't do that (which IIRC is just unchecking one box).

The next time it gets a blue screen it'll stay, allowing you to write it all down.

It should all be in the event log though. You can get at that by right clicking "my computer" and clicking Manage.

 

I turned off the autoreboot, also went and found the event log the way you said and its what follows(sorry its not in a smaller format),
I looked at the report for both reboots and they both have same ID. An odd thing that happened though,
when it rebooted while overclocking it stayed at the bluescreen I had to hit the reset button,
but nonoverclocking the bluescreen stayed up for a few seconds and then reset itself.


Details
Product: Windows Operating System
ID: 7000
Source: Service Control Manager
Version: 5.0
Symbolic Name: EVENT_SERVICE_START_FAILED
Message: The %1 service failed to start due to the following error:
%2.

Explanation
Service Control Manager (SCM) could not start the specified service, probably because the service is not configured correctly.


User Action
Do one or all of the following:

Review the error information displayed in the message.
Verify that the service password has not expired.
Verify that the service is in the correct location.
Verify that the service is not infected with a virus.
To display the WIN32_EXIT_CODE error that SCM encountered when trying to start the program, at the command prompt, type
sc query service name
The information displayed can help you troubleshoot possible causes for the error.
If the WIN32_EXIT_CODE is zero, then SCM did not attempt to start the service because the error was detected first.



Version: 5.2
Symbolic Name: EVENT_SERVICE_START_FAILED
Message: The %1 service failed to start due to the following error:
%2

Explanation
Service Control Manager (SCM) could not start the specified service, probably because the service is not configured correctly.


User Action
Do one or all of the following:

Review the error information displayed in the message.
Verify that the service password has not expired.
Verify that the service is in the correct location.
Verify that the service is not infected with a virus.
To display the WIN32_EXIT_CODE error that SCM encountered when trying to start the program, at the command prompt, type
sc query service name
The information displayed can help you troubleshoot possible causes for the error.

If the WIN32_EXIT_CODE is zero, then SCM did not attempt to start the service because the error was detected first.

 

SERVICE_START_FAILED messages, while definitely something to look into, aren't what is causing your blue screens.

 

hows this one, I found a "save dump" log just before that error code above, but there isnt one for the first time I got the blue screen just the second time. in the description of it had this "The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009c (0x00000004, 0x805461f0, 0xb2000000, 0x00070f0f). A dump was saved in: C:\WINDOWS\Minidump\Mini110707-01.dmp." so thats the same error code

Details
Product: Windows Operating System
ID: 1001
Source: Save Dump
Version: 5.2
Symbolic Name: EVENT_BUGCHECK_SAVED
Message: The computer has rebooted from a bugcheck. The bugcheck was: %1. A dump was saved in: %2.

Explanation
The computer has restarted from a bugcheck. The event log contains details about the cause of the bugcheck.


User Action
If an error report was generated for this error, you might be able to obtain more information about the error by sending the report to Microsoft for analysis.

What to expect

Microsoft actively analyzes all error reports and prioritizes them based on the number of customers affected by the error signature contained in the report. When a report is submitted, Microsoft will try to determine the cause of the error, categorize it according to the type of issue encountered, and send you relevant information when such information is available. However, because error reports do not always contain enough information to positively identify the source of the issue, Microsoft may might need to collect a number of similar reports from other customers before a pattern is discovered. Although Microsoft might not be able to provide a solution for your particular error at this time, all information submitted is used to further improve the quality and reliability of our products.

 

what about any messages right before or right after that?

if there's something like an IRQ_NOT_LESS_OR_EQUAL or some message like that.. that would be way helpful.

Also most stop errors (nearly all) are hardware related. Have you made sure that all of the drivers you are using are the most appropriate (from the hardware manufacturer and not microsoft), up to date, etc?

 

these are the only 2 that stand out, all the rest I looked at are the system turning on programs after the system rebooted, but the explanations are saying that i restarted it myself which doesnt make sense since Im not doing it.



Details
Product: Windows Operating System
ID: 6009
Source: EventLog
Version: 5.2
Symbolic Name: EVENT_EventLogProductInfo
Message: Microsoft (R) Windows (R) %1 %2 %3 %4.

Explanation
The user restarted or shut down the computer by clicking Start or pressing CTRL+ALT+DELETE, and then clicking Shut Down. The message displays the Windows product information for the computer logging the message, including the product name, version, build number, service pack number, and operating system type.


User Action
No user action is required.



Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_EventLogProductInfo
Message: Microsoft (R) Windows 2000 (R) %1 %2 %3 %4.

Explanation
The user restarted or shut down the computer by clicking Start or pressing CTRL+ALT+DELETE, and then clicking Shut Down. The message displays the Windows product information for the computer logging the message, including the product name, version, build number, service pack number, and operating system type.

Details
Product: Windows Operating System
ID: 6005
Source: EventLog
Version: 5.2
Symbolic Name: EVENT_EventlogStarted
Message: The Event log service was started.

Explanation
This event is written at system startup after the user initiates an expected restart or shutdown by clicking Start or pressing CTRL+ALT+DELETE, and then clicking Shut Down.

If the persistent Time Stamp group policy setting is either enabled or not configured, system information is written to the data section of this event. This information includes the name and version of the Windows Server 2003 operating system and the computer's make and model.

If any of the sources for this information are unavailable, or if their contents are unreadable, their corresponding fields display <unknown>.

 

You using a legit copy of XP? Like Kansei mentioned turn off overclocking all together, remove any extra peripherals and PCI cards, only leave the video card and go from there. If you can completely reinstall the OS and make sure the board BIOS version is correct and current. Reset BIOS to default settings.

You very well may have an actual board problem if it persists but you will only be to tell if you have known working hardware (video card, RAM) a fresh install of Win XP, and the board has the latest BIOS version and device drivers. What power supply are you using, have it tested, if the board is not receiving a constant +5 volt on the good signal it will cause the board to reset. Most builders neglect buying a good power supply, its just as important. Thats actually going to be a difficult one to figure out because that error can be generated by numerous hardware, ram, cpu, L2 cache, software....etc..

Maybe this can help.
http://aumha.org/a/stop.htm

 

antec true power 650w just bought it this summer, legit copy of xp, bios...the one time ive tried to update that ended up somehow screwing with the registry and i had to wipe the comp, so i dont like messin with that. I would be willing to believe its with windows, i did the install on my old set of ram and had nothing but problems doing it immediately had to run nortan windisk stuff. I have since put in this new ram but not reinstalled windows, but if it was related to the ram i dont see why it would have been fine for 3 days then started.

 

BIOS update will never corrupt the registry, its a board firmware update. I would definitely checking the manufacturers site and ensure your running the latest version, its simple to update. As well go to http://www.anandtech.com/ and join the forum, alot of smart members there.