Windows Rebooting Itself

[Jafo]

Ever since Friday my computer has decided it wants to restart itself at random times. I see the "Blue Screen" with some error message that you don't have time to read and it starts to reboot but never does until I load bios default setting. Once the default settings are loaded I can boot into Windows and everything is ok until it decides to do it again. My computer might run all day with no problems or it might run 30 min. I did see once that I had a disc error when it shutdown and tried to restart if that helps.

[halutzparilla]

right click MY Computer > then click Properties > Select Advanced > Click Settings under
Startup and Recovery > under System Failure > Uncheck automatically restart

that should give you ample time to read the BSOD error message ... if that error happens again....

[Yellowhello]

Your PC might be overheating. Is it overclocked at all? You might want to open it up and check for dust, if you haven't in a while.

[Jafo]

Originally Posted by yellowhello

Your PC might be overheating. Is it overclocked at all? You might want to open it up and check for dust, if you haven't in a while.

Right as I was trying to respond it restarted again, but I had read the previous response and I had the chance to uncheck auto restart so I had the chance to read everything this time. It said to uninstall either hardware or software that I might have recently installed.

Things I've installed the last 2 weeks. Do any of these jump as possible problems?

Microsoft intellipoint (keyboard software)
Logitech setpoint (mouse software)
Logitech mouse (hardware)
Asus Probe II (software after problem started)
3dmark05 (software after problem started)


It is not overclocked and I have recently cleaned it out, so there shouldn't be any overheating. I use Asus Probe II to check CPU temps and the highest I've seen is 51 after gaming for an hour and idle is around 42.

[Tyreal]

Did it display an error code? The codes are usually very cryptic but you can search them online to see whats wrong.

Those temps are high but are fine. I wouldn't worry about them.

[Jafo]

Originally Posted by Tyreal

Did it display an error code? The codes are usually very cryptic but you can search them online to see whats wrong.

Those temps are high but are fine. I wouldn't worry about them.

It did, unfortunately I didn't write the code down. It was a stop [some long number] error code. I'll have to wait for the next shutdown.

[Tyreal]

Alright. Let us know when it happens again.

[screwballl]

Write down the entire stop error number AND the strange message like IRQL_NOT_LESS_OR_EQUAL and from there you should be able to lookup the last 0x0164654 whatever number and narrow down the problem.
My suggestion is either the Asus probe or the Microsoft point software. I have had problems with both of those myself.

[Yellowhello]

Yeah, I've had problems with ASUS Probe also. I had it running fine on my last build, but on this build (the one in my sig) it didn't work at all. That's why I use CoreTemps now...

[Stewie]

Similar issue with similar system here. I built the system this spring, and it's worked flawlessly until August...

I've been getting the "blue screen" on occasion, and then an immediate reboot. Can happen back to back, or days/weeks apart.

The error is a WINDOWS STOP ERROR, caused by a "DEVICE DRIVER".

This has been happening for months now, and I haven't made any changes to the system that could cause this.

When I download my email, anything with a large attachment arrives corrupted and unreadable. Sometimes when surfing, a web page will appear oddly formatted, and pictures appear scrambled. If I report the 'serious error' to Microsoft's analysis team, the error report is 'corrupted' about 30% of the time.

I ran MEMTEST on the RAM first thing with no errors.
I ran Western Digital's diagnostic on the HDD's, and everything appears fine (suspected a buffer ram problem).
I replaced the power supply with a cooler master 500W unit (the fan in the old unit was making noise anyway).
I have an excellent UPS, so I doubt I've suffered a power spike.

The problem persists.

I'm really leaning towards bad RAM...is it possible that memtest didn't catch a RAM problem? I ran it for 12 hrs. Perhaps a bad capacitor on the MOBO?

Any suggestions or comments from the experts? I was waiting to read a resolution to the problems listed above, but nothing has been posted, so here I am... I don't want to re-install the sytem until I exhaust all of my options.

Thanks in advance,

-Stewie