Solved System crash, BSOD's on new HTPC build

[Lutfij]

Hey there everyone, I've been a long time lurker on seven forums, and have used the info on your theads to get my google chrome working when win7 first came out.

However, this time, I've decided to Move out of Tom's hardware threads and post here for a conclusive answer.

I have put together a build some time back since july, its been giving me BSOD's. This only happens when i ahve a portable USB HDD connected to the USB port - whether front panel or back panel header, I still get a BSOD. I did a fresh install of Win7 x64 with the latest device drivers from Intels and Realtek's site.

System specs;
Intel i3-2100 @ stock
ECS H67H2-M Black deluxe mobo
4GB (2x2GB)Twinmos DDR3 1333MHz (dunno the voltages since the sticker doesn't say anything apart from CL9) but I'm assuming its 1.5V +/- .075V
1x 250GB Seagate(formerly maxtor HDD) OS
1x 2TB Samsung HDD for movies and media drive
LiteOn DVD +/-RW
Thermaltake Toughpower 600W PSU

The PSU and 250GB HDD were hand downs from me to this rig..my pals.

Now everytime I connect the portable USB HDD to the port, I can run a movie from the device but after a while, it gives a BSOD. When running a movie from the desktops HDD, there is no such hickup.

Now;
With all this digging I've learn't that
1| BSOD's can happen from a grounding issue
2| BSOD's can happen with a driver failure(or badly written drivers)
3| BSOD's can happen due to heat issues
4| BSOD's can happen from a faulty hardware
5| BSOD's can happen from USB devices as well

But i want to get to the bottom of this problem. Otherwise I can't get back to what I'm supposed to be doing... I'm one of those people who needs to solve the vcurrent problem then move on to other things.

I'm sorry for the long post, but this BSOD thingy is getting to my.

hope these files help, lemme know if you need anything else or what else i can do from here on.


Is Windows 7 . . .
- x64
- installed after connecting the parts
- retail
- What is the age of system (hardware) - 2 months
- What is the age of OS installation (have you re-installed the OS?) - 2 months - yes multiple times.

Thanks!

 

[panais]

Hey there everyone, I've been a long time lurker on seven forums, and have used the info on your theads to get my google chrome working when win7 first came out.

However, this time, I've decided to Move out of Tom's hardware threads and post here for a conclusive answer.

I have put together a build some time back since july, its been giving me BSOD's. This only happens when i ahve a portable USB HDD connected to the USB port - whether front panel or back panel header, I still get a BSOD. I did a fresh install of Win7 x64 with the latest device drivers from Intels and Realtek's site.

System specs;
Intel i3-2100 @ stock
ECS H67H2-M Black deluxe mobo
4GB Twinmos DDR3 1333MHz (dunno the voltages since the sticker doesn't say anything apart from CL9) but I'm assuming its 1.5V +/- .075V
1x 250GB Seagate(formerly maxtor HDD) OS
1x 2TB Samsung HDD for movies and media drive
LiteOn DVD +/-RW
Thermaltake Toughpower 600W PSU

The PSU and 250GB HDD were hand downs from me to this rig..my pals.

Now everytime I connect the portable USB HDD to the port, I can run a movie from the device but after a while, it gives a BSOD. When running a movie from the desktops HDD, there is no such hickup.

Now;
With all this digging I've learn't that
1| BSOD's can happen from a grounding issue
2| BSOD's can happen with a driver failure(or badly written drivers)
3| BSOD's can happen due to heat issues
4| BSOD's can happen from a faulty hardware
5| BSOD's can happen from USB devices as well

But i want to get to the bottom of this problem. Otherwise I can't get back to what I'm supposed to be doing... I'm one of those people who needs to solve the vcurrent problem then move on to other things.

I'm sorry for the long post, but this BSOD thingy is getting to my.

hope these files help, lemme know if you need anything else or what else i can do from here on.

Thanks!

Hi Lutfij welcome to SF

Please upload here you minidumps by following these steps,

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[Lutfij]

here ya go just ran the report and my eyes caught on the USB driver fail. Tell me what you guys think of the report.

Edit; just experienced a BSOD without any HDD connected tot eh HTPC. We were browsing the net rrying to get an update for teh 47" tv. Then the screen went black and then BSOD.

running memtest 86+ and out for some tea.

* thank you for the welcome!

 

[Lutfij]

Update;
I ran memtest86+ 4.2 for 5 straight passes was about to go through pass 6 until i canceled at test # 7(when it was at 90%), didn't pick up any errors.

I go into windows and then the mayhem started again.
I reinstalled the inf installer from intels site.

No anti-virus is installed. BTW, Intel RST was installed after I did a clean install. Uninstalled it and it keeps BSOD'ing while i connect a portable HDD via USB.

 

[panais]

bump!!!

Upload the new bsod file.

 

[Lutfij]

the new bsod files; the pic on your right is the message i get when i try to transfer data(preferably large files - ~120GB) and the process halts for a while and then displays the message.

the pic on the left is the error message I've been getting from the get-go of this BSOD problem - about 2 months ago.

HTPC system specs again;
Intel i3-2100 @ stock
ECS H67H2-M Black deluxe
Twinmos 4GB (2x2GB) DDR3 1333MHz 9-9-9-24(no matter what voltage i set it to I can't get the BSOD off my back)
1x 250GB Maxtor HDD - OS
1x 2TB Samsung media Drive
Liteon DVD+/- RW drive
thermaltake toughpower 600W PSU
used HDMI for conencting to the Phillips 47" tv - model # 47pfl7409s/98

but brought the rig to my place and ran it off the DVI port connected to my Samsung P2250 monitor (still BSOD'd)

Edit; just did a BSOD, with no USB HDD connected, only my keyboard, mouse, internet via RJ-45 and the monitor same BSOD error code at the bottom of page.

 

[yowanvista]

CRITICAL_OBJECT_TERMINATION (f4)
The CRITICAL_OBJECT_TERMINATION bug check has a value of 0x000000F4. This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

Meaning that something such as malware, some unstable programs or bad hardware may be the cause
Run a scan of Malwarebytes and http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Also run http://www.seagate.com/www/en-us/support/downloads/seatoolshttp://www.seagate.com/ww/v/index.j...toid=480bd20cacdec010VgnVCM100000dd04090aRCRD

Note that this BSOD is mainly caused by a bad Hard Drive, a RMA would be required

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8007c4c950, fffffa8007c4cc30, fffff80002d7f240}

Probably caused by : csrss.exe

******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8007c4c950, Terminating object
Arg3: fffffa8007c4cc30, Process image file name
Arg4: fffff80002d7f240, Explanatory message (ascii)

Debugging Details:
------------------


PROCESS_OBJECT: fffffa8007c4c950

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`035d60a8 fffff800`02e02142 : 00000000`000000f4 00000000`00000003 fffffa80`07c4c950 fffffa80`07c4cc30 : nt!KeBugCheckEx
fffff880`035d60b0 fffff800`02dae269 : ffffffff`ffffffff fffffa80`07cd3b60 fffffa80`07c4c950 fffffa80`07c4c950 : nt!PspCatchCriticalBreak+0x92
fffff880`035d60f0 fffff800`02d32c74 : ffffffff`ffffffff 00000000`00000001 fffffa80`07c4c950 fffff6fb`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17a06
fffff880`035d6140 fffff800`02a76153 : fffffa80`07c4c950 fffff800`c0000006 fffffa80`07cd3b60 fffff880`035d6b38 : nt!NtTerminateProcess+0xf4
fffff880`035d61c0 fffff800`02a726f0 : fffff800`02ab6ada fffff880`035d6b38 fffff880`035d6890 fffff880`035d6be0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`035d6358 fffff800`02ab6ada : fffff880`035d6b38 fffff880`035d6890 fffff880`035d6be0 00000000`00781a00 : nt!KiServiceLinkage
fffff880`035d6360 fffff800`02a76542 : fffff880`035d6b38 00000000`000116e4 fffff880`035d6be0 00000000`007814d8 : nt! ?? ::FNODOBFM::`string'+0x4619d
fffff880`035d6a00 fffff800`02a750ba : 00000000`00000000 00000000`000116e4 00000000`00000001 00000000`00000004 : nt!KiExceptionDispatch+0xc2
fffff880`035d6be0 00000000`76da548f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00781420 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76da548f


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

Followup: MachineOwner
---------

 

[Lutfij]

thank you for the reply yowanvista!

Note that this BSOD is mainly caused by a bad Hard Drive, a RMA would be required

I've contacted the retailer and have arranged to send the motherboard to them and diagnose the problem. I've done alot of troubleshooting from my end but even a fresh install of win7 64 bit leaves no rrom for errors. So conclusion, anywhere between 5mins after boot up to an hour - I get a BSOD regardless of using a portable USB HDD or whichever sata HDD i use.

The other identical machine that is used as an office rig, also has the same specs;
Intel i3-2100 @ stock
ECS H67H2-M Black mobo
Twinmos 4GB (2x 2GB) DDR3 1333MHz
320GB Samsung HD320GJ
xfx 450W PSU
Liteon DVD+/-RW

and i just got off the phone with him, he mentioned that the time he runs his rig between startup and shutdown is 6~8hrs.

RMA would be needed, first i need to send it to them and wait for a reply.

I'll keep everyone here posted if my problem is solved.

 

[jcgriff2]

Hi -

HDD failure would be on my list as well. Event Viewer logs show Windows Search constantly crashing; registry corruption is occurring as well -

[FONT=lucida console]{Registry Hive Recovered} Registry hive (file):[/FONT]
[FONT=lucida console] '\SystemRoot\System32\Config\SOFTWARE' was corrupted and it has been recovered.[/FONT]
 
[FONT=lucida console]  Some data might have been lost.[/FONT]

I realize you reinstalled Windows 7 just 2 days ago, but I see -0- Windows Updates. You're running build 7600 (no SP1), so you're missing well over 100 Windows Updates. Installing SP1 will reduce that number considerably.

Windows Updates - www.update.microsoft.com

I see driver installs coming from drive f:, but would advise that you check Entron's support site -- it appears there are updated USB 3.0 drivers available.

From the BSOD dumps -

[FONT=lucida console]EtronHub3.sys   Mon [COLOR=red]Oct 25[/COLOR] 03:08:24 [COLOR=red]2010[/COLOR] (4CC52CE8)[/FONT]

I downloaded the Entron driver update -

[FONT=lucida console][COLOR=red]12/05/2010[/COLOR]  18:10            38,656 EtronHUB3.SYS[/FONT]
[FONT=lucida console]12/05/2010  18:42             8,611 etronxhci.cat[/FONT]
[FONT=lucida console]12/05/2010  18:06             4,646 EtronXHCI.INF[/FONT]
[FONT=lucida console]12/05/2010  18:09            62,720 EtronXHCI.SYS[/FONT]

Driver Updates --> Etron Technology Inc.

How was Windows 7 installed? From DVD, USB or other... possibly an image?
I found wimmount.sys = WIM FS (Windows Imaging File System) Filter driver -

From Microsoft TechNet -
- Mount and Modify an Image
- How ImageX Works


From the dumps -

[FONT=lucida console]FAILURE_BUCKET_ID:  X64_0xF4_[COLOR=red]C0000005[/COLOR]_IMAGE_wininit.exe[/FONT]
[FONT=lucida console]FAILURE_BUCKET_ID:  X64_0xF4_[COLOR=red]IOERR[/COLOR]_IMAGE_csrss.exe[/FONT]
[FONT=lucida console]FAILURE_BUCKET_ID:  X64_0xF4_[COLOR=red]IOERR[/COLOR]_IMAGE_csrss.exe[/FONT]

Exception 0xc0000005 = memory access violation

The CSRSS I/O error could be from the installation source or caused by hardware failure during OS installation. HDD &/or RAM are possibilities.


Regards. . .

jcgriff2

`



BSOD SUMMARY

[FONT=lucida console]Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\080911-16848-01.dmp][/FONT]
[FONT=lucida console]Built by: 7600.16385.amd64fre.win7_rtm.090713-1255[/FONT]
[FONT=lucida console]Debug session time: Mon Aug  8 18:14:13.725 2011 (GMT-4)[/FONT]
[FONT=lucida console]System Uptime: 0 days 0:05:24.020[/FONT]
[FONT=lucida console]BugCheck F4, {3, fffffa8007b56b30, fffffa8007b56e10, fffff80002f8d240}[/FONT]
[FONT=lucida console]Probably caused by : csrss.exe[/FONT]
[FONT=lucida console]PROCESS_NAME:  csrss.exe[/FONT]
[FONT=lucida console]BUGCHECK_STR:  0xF4_IOERR[/FONT]
[FONT=lucida console]DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT[/FONT]
[FONT=lucida console]FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe[/FONT]
[FONT=lucida console]Bugcheck code 000000F4[/FONT]
[FONT=lucida console]Arguments 00000000`00000003 fffffa80`07b56b30 fffffa80`07b56e10 fffff800`02f8d240[/FONT]
[FONT=lucida console]¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]
[FONT=lucida console]Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\080911-21356-01.dmp][/FONT]
[FONT=lucida console]Built by: 7600.16385.amd64fre.win7_rtm.090713-1255[/FONT]
[FONT=lucida console]Debug session time: Mon Aug  8 12:28:14.711 2011 (GMT-4)[/FONT]
[FONT=lucida console]System Uptime: 0 days 0:41:49.007[/FONT]
[FONT=lucida console]BugCheck F4, {3, fffffa8007c4c950, fffffa8007c4cc30, fffff80002d7f240}[/FONT]
[FONT=lucida console]Probably caused by : csrss.exe[/FONT]
[FONT=lucida console]PROCESS_NAME:  csrss.exe[/FONT]
[FONT=lucida console]BUGCHECK_STR:  0xF4_IOERR[/FONT]
[FONT=lucida console]DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT[/FONT]
[FONT=lucida console]FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe[/FONT]
[FONT=lucida console]Bugcheck code 000000F4[/FONT]
[FONT=lucida console]Arguments 00000000`00000003 fffffa80`07c4c950 fffffa80`07c4cc30 fffff800`02d7f240[/FONT]
[FONT=lucida console]¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]
[FONT=lucida console]Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\080811-16426-01.dmp][/FONT]
[FONT=lucida console]Built by: 7600.16385.amd64fre.win7_rtm.090713-1255[/FONT]
[FONT=lucida console]Debug session time: Sun Aug  7 14:29:23.102 2011 (GMT-4)[/FONT]
[FONT=lucida console]System Uptime: 0 days 0:08:58.023[/FONT]
[FONT=lucida console]BugCheck F4, {3, fffffa8007c86b30, fffffa8007c86e10, fffff80002dc5240}[/FONT]
[FONT=lucida console]Probably caused by : wininit.exe[/FONT]
[FONT=lucida console]PROCESS_NAME:  wininit.exe[/FONT]
[FONT=lucida console]BUGCHECK_STR:  0xF4_C0000005[/FONT]
[FONT=lucida console]DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT[/FONT]
[FONT=lucida console]FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_wininit.exe[/FONT]
[FONT=lucida console]Bugcheck code 000000F4[/FONT]
[FONT=lucida console]Arguments 00000000`00000003 fffffa80`07c86b30 fffffa80`07c86e10 fffff800`02dc5240[/FONT]
[FONT=lucida console]¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]
 
[FONT=lucida console]by [COLOR=navy]jcgriff2     [/COLOR][/FONT]
 
[FONT=lucida console][COLOR=navy]      J. C. Griffith, Microsoft MVP[/COLOR]   [/FONT]
 
[FONT=lucida console]        [URL="https://mvp.support.microsoft.com/profile/Griffith"][COLOR=#000055][U]https://mvp.support.microsoft.com/profile/Griffith[/U][/COLOR][/URL]   [/FONT]
 
[FONT=lucida console]        [URL="http://www.sysnative.com"][COLOR=#000033][U]www.sysnative.com[/U][/COLOR][/URL][/FONT]
 
[FONT=lucida console]        [URL="http://www.jcgriff2.com"][COLOR=#000055][U]www.jcgriff2.com[/U][/COLOR][/URL] [/FONT]
 
[FONT=lucida console]¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨[/FONT]

 

[Lutfij]

the Seagate/maxtor drive was a hand down from me, the samsung is brand new. Will try and repartition the 2TB drive and see where it goes form there.

How was Windows 7 installed?

well I installed win7 from a dvd and was going to run updates, until it crashed. So that should explain why i don't have SP1

The CSRSS I/O error could be from the installation source or caused by hardware failure during OS installation. HDD &/or RAM are possibilities.

okay me capiche but i ran memtest 86+ for 5 passes and went through pass 6 test #7 and then i cancelled as i read on Tom's that if there are any problems on ram dimms, then the first 5 passes will give you a general idea... :/ correct me if I'm wrong.

so now, i've disconnected the 250GB Maxtor HDD and will work on the samsung 2TB drive and install from DVD.

will keep you posted.

Thanks btw!!!

 

[Lutfij]

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

I edited my previous post, please check

 

[jcgriff2]

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]

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

even after I've done a clean install? on all the occasions, I formatted the drives clean...during win os install page

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

i ran the test with both sticks installed on ram slots 2 and 4(the white ones - according to the manual) and no errors.

However, now that you mention it, I had only the 250GB Maxtor/Seagate HDD hooked up while the 2TB samsung was disconnected...and i got a bsod when i was online replying to this thread.

 

[Lutfij]

okay so here's the update;

1| removed Seagate drive
2| restructured the partition on Samsung 2TB Drive
3| installed windows
4| prior to installation, i downloaded drivers, all the latest ones from intel, etron, realtek and compared them to ECS' site for which one was latest.
5| have installed codecs, plugins and even watched movies.
6| installed all updates except for SP1 - that will take some bandwidth, I'll update to SP1 when I'm returning this rig to my pal (provided the problems over)
7| surely enough I don't get BSOD f4 anymore
8| watched a lil bit of tron legacy on the machine
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

I've included the BSOD file and the image of the error code.

Hope these can shine some light :/

P.S; didn't run memtest yet and the voltages for my ram in BIOS are set to default which is 1.562V command rate is also set to default

and I'm having trouble shutting down the rig. If i hit the shut down button in start menu, it either powered down and then restarted or display goes out while the cpu fan, lights and temp (on 80 port) still run.

 

[jcgriff2]

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 -

[font=lucida console]igdkmd64.sys    Sun Apr 10 14:50:59 2011 (4DA1FC13)[/font]

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

Info on 0x101 - http://www.sevenforums.com/crash-lo..._watchdog_timeout-troubleshtg.html#post567135

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 - http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html



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

Regards. . .
jcgriff2

`

BSOD SUMMARY

[font=lucida console]
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

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

  [/font]

 

[Lutfij]

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!

 

[jcgriff2]

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 -

[FONT=Arial][COLOR=black][FONT=Lucida Console][SIZE=3]shutdown /s [/SIZE][/FONT][/COLOR][/FONT]

Regards. . .

jcgriff2

`

 

[Lutfij]

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.

 

[Lutfij]

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.