System crash, BSOD's on new HTPC build

sorry for the double post, I'm inviting Moderators to delte this post,

I edited my previous post, please check :)

I do understand about no-SP1 because of the crashes, but usually 2 initial Windows Updates get through before license validation occurs.

Did you run memtest86+ one stick at a time and alternate the slots?

I would suggest that you rerun the jcgriff2 BSOD app after reinstall or check the Event Viewer yourself (Custom Views, Admin Events) for signs of trouble.

Regards. . .

jcgriff2

`

Lutfij said:

9| installed daemon tools lite to install MS office from an image file....BUT - got this code a while ago.
only happens when i go to install MS office 2007

error 101

Hi -

Bugcheck 0x101 = CPU hang

Intel graphics driver was listed on the stack -

Code:

igdkmd64.sys    Sun Apr 10 14:50:59 2011 (4DA1FC13)

http://sysnative.com/0x1/DriverReference.html#igdkmd64.sys

Info on 0x101 - STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

Daemon Tools may be involved here. Daemon/ Alcohol driver sptd.sys is known to cause BSODs in Windows 7 & Vista.

The BSOD does show setup.exe, likely the MS Office installation you mentioned. I would suggest getting rid of Daemon & installing MS Office via the DVD.

I noticed that your system clock is off by about 7 days. The system files and BSOD have timestamp = 4 August 2011

Set Windows Time - Set the clock

Test CPU - https://www.sevenforums.com/tutorials...t-prime95.html



Windbg Logs
--> http://sysnative.com/bsod2011/jcgrif..._jcgriff2_.txt
--> http://sysnative.com/bsod2011/jcgrif...riff2_.txt.zip

Regards. . .
jcgriff2

`

BSOD SUMMARY

Code:

Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\080411-27627-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Aug  3 23:44:27.626 2011 (GMT-4)
System Uptime: 0 days 0:05:12.548
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  setup.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`03364180 00000000`00000002

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

  

okay then Daemon tools is the next thing to remove from the equation :)

but i also mentioned that my rig is able to shut down when i select shut down from the start menu. after a few seconds the rig powers back up again...would you guys have an answer for this?

thank you very much for all your help so far!

Hi -

That sounds like a restart.

Shut the system down via command line - see if it stays off.

Bring up elevated Admin cmd screen -
START | type cmd.exe | RIGHT-click on cmd.exe above under "Programs" | "Run as Administrator" | paste -

Code:

shutdown /s 

Regards. . .

jcgriff2

`

hey there;

i uninstalled daemon tools lite and also go tried of the imaged MS office 2007 installer

but a new problem persists, every-time i connect the USB HDD, i get an error code 101 and at one point when i connected the USB drive to the USB3.0 ports, i got a screen artifacting.

I also tried shutting down the PC via the shutdown button, no luck - the pc shuts off and from a cold start, the pc powers back up again. I also did what you advised, to shutdown the rig via cmd, administator privilege's and shutdown/s after less than a min, the rig powers down but it boots back up again from a cold start...

I'm at my witts end...and i feel that the board needs to be RMA'd

Please advise.

this problem has been solved by changing;
1st| the HDD which gave me the f4(sounds like a middlefinger BSOD code ) :lol:
2nd| after some feedback with a member on tom's hardware i did some google'ing and came with these answers and the eventual solution to the BSOD when i hooked up a USB HDD.

BSOD codes for overclocking
0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore... H67/P67 increase/decrease Vcore first then qpi/vtt second.
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore
on i7 32nm SB, usually means too little vCore
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

This is taken from XS Forum. A user there posted this. Thought it would help over here.

more in these two links;
BSOD Error codes....

and this

The ULTIMATE Sandy Bridge OC Guide + P67A-UD7 Performance Review - Overclock.net - Overclocking.net

please follow this thread to followup on what had happened.

Hope these help solve anyone else's problems similar to mine :)
Ciao.