Win7 Debugger location

aloser

Senior member
Nov 20, 2004
511
1
81
Hey guys,
I've had my new computer a little over a year now, and I'm beyond sick of the random reboots.

Specs, just to get that out of the way:
-WESTERN DIGITAL WD10EACS 1TB SATA 7200 RPM 16MB Hard Drive
-MSI P43 Neo3-F Intel P43 Core 2 Extreme/Core 2 Duo/Core 2 Quad Socket 775 1600 MHz PC2-8500 (DDR2-1066) ATX Motherboard
-CORSAIR TWIN2X4096-8500C5D 4GB (2x2GB) PC2-8500 (DDR2-1066) DDR2 Memory
-EVGA 01G-P3-N972-TR Geforce 9800 GT 1GB GDDR3 PCI Express x16 (2.0v) Video Card
-OCZ OCZ600GXSSLI GameXStream 600W Power Supply
-Intel Core 2 Quad Q6600 Quad-Core Processor 2.4GHz, 1066FSB, LGA775, 8MB cache
-Watercooled, temps stay steady around 60

So anyway, ever since I've built it, I've gotten random reboots. At first I attributed it to my Vista 64-bit installation, so I downgraded to 32-bit Vista - same thing. Upgraded to 32-bit Win7 - same thing. All my drivers are updated as far as I can tell. Doesn't matter what I'm doing (playing WoW, Flight Sim X, surfing YouTube, looking at any of the online aerial maps, or anything else) - my computer will randomly either reboot or lock up (also a random choice).

So, I'm wondering where I can look to see what keeps causing this to happen? Thanks!
 

aloser

Senior member
Nov 20, 2004
511
1
81
I've run MemTest86+ several times throughout the year, each with a Passing and 0 errors.

Thanks for the links Jack, I'll try those next. :)
 

aloser

Senior member
Nov 20, 2004
511
1
81
Hmmmmmm... Tried both 32 and 64 bit - maybe I fail at running/reading the results, but I still don't get anything useful. Everything comes up clean; I get a generic "the last reboot was unexpected" message after the computer reboots which is the *most* descriptive thing I've gotten.
 

KeypoX

Diamond Member
Aug 31, 2003
3,655
0
71
there was a thread i saw yesterday, very similar. Someone asked him to run prime. Guy posts back talking about prime only lasted 2 min.

You have water cool and temps are at 60C thats pretty freaking high for idle temps. I would check your overclock settings if your using them.

Also it seems to be a hardware/driver issue. Not os based.
 

aloser

Senior member
Nov 20, 2004
511
1
81
CRAP! :eek: How did I not catch that sooner? My temps are 30, not 60. Anyway, as mentioned already, I figured this is hardware (either a bad part or or faulty driver), but my guess is that the (hdwe) forum would send me to OS to test some stuff to determine exactly what's flaky. Perhaps I could get a friendly Mod to move this for me in case the Hardware guys have any ideas? :)