New computer restarting randomly

[Lateralusxxx]

I just built this setup after christmas:

Intel core 2 duo e6400
elitegroup p965T-a Mobo
1gbx2 g.skill ddr2 800 ram
gigabyte 7600gt vid card
250sata HDD
BFG 650w PSU atx v2.0

It crashes at random times during games or high use. I can play civ 4 fine until i get to the point to where there are many units on the map and a lot of stuff is going on, then it just restarts. if i run prime 95 benchmark it restarts after the second or third test. If i take one stick of ram out leaving a single stick in, it does better but still crashes. I have the latest bios, the latest drivers etc. fresh windows install. I had an older PSU so i just bought another cause the old one wasnt atx 2.0... that didnt help.... i dont know whats going on here. I dont think its my ram, i ran memtest86 for 8 hours and there were 0 errors.


Updates:
my old PSU maybe, but i just got a new PSU that was recommended and i dont think its heat either... all temps seem fine. every once and a while it shows a blue screen.

I went to 'manage' when i right clicked "my computer" and went to the system event viewer and i was getting a 'Save Dump' error.
Source: Save Dump
Event ID: 1001
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000004, 0x000000ff, 0x00000000, 0x00000004). A dump was saved in: C:\WINDOWS\Minidump\Mini123106-01.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

This is so annoying

i tried doing Civ4 at lower settings, it ran for a while then crashed, my computer is restarting, not shutting down if that makes any difference, then i get the save dump message again, with some other stuff in the events log.

help!!!!!

 

[sieistganzfett]

I like to blame "the motherboard" but you should really use MS's windows debugging tool. http://www.microsoft.com/whdc/devtools/debugging/default.mspx use that to open up the minidump file, you probably have a lot of dumpfiles by now, check them all and see if there is a relationship, etc.

Most of the time installed Windows Debugger, and using it to check the dump file will tell why windows crashed. after installing run !analyze -v and lmv commands to find out what did it.
**** after dbg_x86_6.6.07.5.exe installed, open windbg, set FILE|symbol file path to click "reload" box, then ok.
SRV*c:\local cache*http://msdl.microsoft.com/download/symbols

**** then file|open crash dump and run the commands

!analyze -v will tell you the error, click the link on the drive
under Debugging Details:
DEFAULT_BUCKET_ID -tells the general category of the failure
IMAGE_NAME -tells what driver is at fault, like if DRIVER_FAULT
click on the driver highlighted under MODULE_NAME it tells info like path to that module

lmv -tells loaded modules in detail, then click edit|find for that driver listed under IMAGE_NAME


****IF
*if driver at fault is ntoskrl.exe (windows core) or win32.sys (driver most responsible for the GUI layer on windows),it is PROBABLY NOT WINDOWS needing to be reinstalled, it is PROBABLY some third-party device driver that called it.
*if the driver at fault is an antivirus driver, it is PROBABLY NOT the anti virus needing to be reinstalled.
*

 

[Lateralusxxx]

i hope its the mother board cause im sending it back soon anyways and getting and asus 975x board. this board sucks even if its not the prob

EDIT: Is there anyway to make sure my mobo is messed up and not something else if its not software/driver issues?

 

[Lateralusxxx]

I ran it with just the !analyze -v command cause i couldnt figure out how to do much more. and it said 'Probably caused by' several different things but ntoskrl.exe and win32.sys showed up several times.

EDIT: here are some examples.
BugCheck 23, {e0100, aa731a20, aa73171c, 80591684}
Probably caused by : Fastfat.SYS ( Fastfat!FatFlushFat+e6 )

BugCheck 1000000A, {810004, ff, 1, 804dccf5}
Probably caused by : ntoskrnl.exe ( nt!KiTimerListExpire+2f )

BugCheck 100000D1, {2ee0, 2, 0, b802823c}
Probably caused by : RtkHDAud.sys ( RtkHDAud+5a23c )

BugCheck 1000008E, {c000001d, 8056e0ff, b4d74c30, 0}
Probably caused by : ntoskrnl.exe ( nt!NtQueryInformationProcess+e01 )

BugCheck 10000050, {b34e2e83, 0, b34e2e83, 0}
*** WARNING: Unable to verify timestamp for Ntfs.sys
Could not read faulting driver name
*** WARNING: Unable to verify timestamp for hal.dll
Probably caused by : memory_corruption ( nt!MiRemoveNode+17d )

 

[sieistganzfett]

your blue screens are bombing out on windows itself, your Fresh install was an install of win xp on a cleanly formated HD, and you updated the drivers for everything from the manufacturers websites, are you running anti virus on it?(try disabling it) did you overclock anything? if not, then your BIOS is at the defaults for everything, and you didnt overclock the video card either, your ram is running at the right spec (its passing memtest for 8 hours.) My only guess left would be the motherboard then since its near 0% chance its the cpu. it could be that windows needs to be reinstalled due to corruption that occured, but running anything cpu/chipset intense like prime95 actually causes a blue screen??? (have you disabled the "automatically restart" for window's startup and recovery option under the system properties to start seeing blue screens or have you disabled the auto restart but the pc just restarts not showing a blue screen anyways?) which test is it of the torture test that errors on just a few itterations of the test, usually prime95 would give a message in it's window about 'x' being off when it expected a value > or < 'n'.

 

[John]

Prime crashing means your rig is not stable!

Try adjusting the memory timings and voltages. What are your temps?

 

[Lateralusxxx]

no anti virus, no OCing what so ever, ram is running at spec times etc etc.... i get blue screens 20% of the time but mostly just a blank screen restart. is the auto restart a bios setting or a windows setting?

prime 95 makes it crash, 3dmark06 does not, half life 2 episode 1 doesnt crash but civ 4 does. 1g of ram is more stable than 2 gigs.

 

[imported_fixit]

Try increasing your virtual memory.

 

[sieistganzfett]

the auto restart on error is an option in windows xp and 2000. right click "my computer" left click "properties" on the menu that shows up, the "system properties" window shows up, under the "advanced" tab there is a button for "settings" located in the "start up and recovery" section of the tab. when your open up those settings you can uncheck "automatically restart" under the system failure section.

from the additional info you gave, such as blank screen restart.1g of ram is more stable than 2 gigs.no OCing what so ever, ram is running at spec times and it passes memtest! i would bet $$$ that it's a faulty motherboard.

 

[Lateralusxxx]

alright, good to know cause its only a matter of days till my asus 975x board gets here

 

[bamacre]

You certainly don't need a beefier power supply, LOL. Good grief, 650W to power a 7600 GT and an E6400.

 

[Lateralusxxx]

i got a new one to be future proof....