New Desktop built Crashing & BSOD

[rjtehz]

Hi All,

I've just recently built a new desktop with the following specs:

Mobo: Gigabyte 880GA-UD3H
CPU: AMD 955 BE
HDD: Samsung spinpoint 1TB
RAM: 4G Kit ddr3 1600 Patriot-Signature
GPU: 1GB 5770 HIS
Case: Antec 300
PSU: Antec TruePower TP-550

And so far it keeps crashing when I play tf2 and streaming flash vods online.

I've done the following tests on my desktop as well:

- Memtest86+ for 8 hours & it passed 9 tests in total with no errors
- Prime95 for 3 hours and all temps were below 57 degrees
- FurMark test for gfx for 2 hours and gfx temps were constant 62 degrees

I've also upgraded my BIOS and chipset drivers to the latest ones provided by Gigabyte website and also the gfx drivers.

I've managed to get one minidump (attached) from BSOD out of the 5 crashes because sometimes it gets stuck while writing the minidump. But, I've taken photos of the BSOD screens:

Picasa Web Albums - rj - Desktop Crash

Mmm... also my psu makes this high pitch noise when I have my comp turned off, but you can't hear it until you put your ears next to it. However, when I pulled out the power cable it slowly dies and eventually disappears.

This is my first build so it would be great if I could get any professional help!

Cheers.

Edit: Also added System File Collection zip

 

[zigzag3143]

Hi All,

I've just recently built a new desktop with the following specs:

Mobo: Gigabyte 880GA-UD3H
CPU: AMD 955 BE
HDD: Samsung spinpoint 1TB
RAM: 4G Kit ddr3 1600 Patriot-Signature
GPU: 1GB 5770 HIS
Case: Antec 300
PSU: Antec TruePower TP-550

And so far it keeps crashing when I play tf2 and streaming flash vods online.

I've done the following tests on my desktop as well:

- Memtest86+ for 8 hours & it passed 9 tests in total with no errors
- Prime95 for 3 hours and all temps were below 57 degrees
- FurMark test for gfx for 2 hours and gfx temps were constant 62 degrees

I've also upgraded my BIOS and chipset drivers to the latest ones provided by Gigabyte website and also the gfx drivers.

I've managed to get one minidump (attached) from BSOD out of the 5 crashes because sometimes it gets stuck while writing the minidump. But, I've taken photos of the BSOD screens:

Picasa Web Albums - rj - Desktop Crash

Mmm... also my psu makes this high pitch noise when I have my comp turned off, but you can't hear it until you put your ears next to it. However, when I pulled out the power cable it slowly dies and eventually disappears.

This is my first build so it would be great if I could get any professional help!

Cheers.

Edit: Also added System File Collection zip

This is obviously a driver problem and is very common. Unfortunately in this crash it doesnt tell us which one.

Candiddates are : Apple charger, jraid, ultramonutility.sys (which is also old).

I would update all the old drivers, remove the apple charger (USB will charge by itself without it) and is ultramonutility isnt needed remove it

Let us know if you have any more so we can narrow the field


Ken J


Analysis

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\091110-16317-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0300b000 PsLoadedModuleList = 0xfffff800`03248e50
Debug session time: Sat Sep 11 00:58:42.060 2010 (GMT-4)
System Uptime: 0 days 1:10:00.340
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff8000308198e}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff8000308198e

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000307aca9 to fffff8000307b740

STACK_TEXT:  
fffff800`04410d28 fffff800`0307aca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`04410d30 fffff800`03079172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`04410e70 fffff800`0308198e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00fff880`03925970 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext_PatchXSave+0x8b


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`03079172 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff8000308198e

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000307aca9 to fffff8000307b740

STACK_TEXT:  
fffff800`04410d28 fffff800`0307aca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`04410d30 fffff800`03079172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`04410e70 fffff800`0308198e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00fff880`03925970 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext_PatchXSave+0x8b


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`03079172 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

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

Old drivers to be updated.

speedfan.sys        fffff880`01900000    fffff880`01907000    0x00007000    0x45168798    9/24/2006 09:26:48                        
LHidFilt.Sys        fffff880`06400000    fffff880`06413000    0x00013000    0x47c7d99b    2/29/2008 06:08:27                        
LMouFilt.Sys        fffff880`0642e000    fffff880`06442000    0x00014000    0x47c7d99f    2/29/2008 06:08:31                        
dne64x.sys        fffff880`04fc7000    fffff880`04ff3000    0x0002c000    0x4918d964    11/10/2008 21:01:24                        
UltraMonUtility.sys        fffff880`047ea000    fffff880`047f3000    0x00009000    0x491cd006    11/13/2008 21:10:30                        
gdrv.sys        fffff880`07773000    fffff880`0777c000    0x00009000    0x49b9d175    3/12/2009 23:22:29                        
AtiPcie.sys        fffff880`019dc000    fffff880`019e4000    0x00008000    0x4a005486    5/5/2009 11:00:22                        
spldr.sys        fffff880`018f8000    fffff880`01900000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
amdxata.sys        fffff880`00e7c000    fffff880`00e87000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59

 

[rjtehz]

m... what is jraid?

Thanks for your reply Zigzag!

 

[Tews]

JMicron Technology Corp. (JRAID) SCSIAdapter is developed by JMICRON Technology Corp. and is used by 15 users of Software Informer.

JMicron Technology

 

[rjtehz]

Ah... ok Thanks Tews!

I'm going to reinstall the OS now actually and then install the latest updated drivers one by one to test out which ones are actually giving me the problems.

I'll update you guys on my findings!

Thanks again!

 

[Tews]

Good luck!

 

[rjtehz]

Ahhh...

Formatted HDD completely and reinstalled Win 7 Pro x64 on it + Chipset drivers + Gfx drivers etc. and it BSOD on me again

It didn't even finish writing the Minidump file it got stuck at 80%.

I've linked a photo of the BSOD & the uploaded latest Health Reports etc.

Picasa Web Albums - rj

Cheers.

Note: I had an external HDD plugged in to reinstall backuped steam games i.e. GTA, tf2, etc. when my desktop BSOD on me.

 

[rjtehz]

Hi again,

After formatting and reinstalling the OS again I did a Prime95 and a FurMark stress test overnight for approx. 6 hours and found my computer shut down when I woke up m... but the fans were still going. When I restarted the desktop it seemed like it was forced shut.

I've captured a health report and also ran "Windows_NT6_BSOD_jcgriff2.exe" and have attached it to this post.

Have been trying to work out whats wrong for the past week any help would be great!!!

This problem is not solved btw

 

[Tews]

Im sorry that you are still having problems.. However a "health report" by its self is really of much use... have you checked c:/windows/minidump for any .dmp files... are you sure that you have enabled minidump files??

 

[rjtehz]

m... yep pretty sure i had it turned on well i just unticked the "restart immediately after crash" and it should produce minidumps but sometimes when it writes a minidump it just hangs at a certain stage e.g. 80%

but i'll try and reproduce the problem and get a minidump to upload here and update ya

thanks!

 

[rjtehz]

Hi again,

It crashed on me again today, but unfortunately it got stuck on 60% again while creating a crash dump on BSOD. I noticed an error in the Event Viewer under the "Subsys-SMSS" source and the error details were:

"The crash dump file could not be created due to a lack of free space on the destination drive. Increasing the amount of free space on the destination drive may help prevent this error."

I've got 800GBs of free space in my HDD m... anyone have any ideas on this?

Cheers,

Rue.

 

[Solarstarshines]

sounds like a hardware failure

 

[rjtehz]

sounds like a hardware failure

yeah i guess m... can't determine which part
cause i brought the parts from different places.

 

[Solarstarshines]

do you have another pc to test the parts on if not you can always run diagnostics on it

If windows can't detect that then you have to one by one sort out each peice of hardware

i also saw you are running a 550watt psu that could give you issues if the power isnt suplied enough a bsod could occur as well when running this new stuff i would recommned 600watt or higher

 

[rjtehz]

do you have another pc to test the parts on if not you can always run diagnostics on it

If windows can't detect that then you have to one by one sort out each peice of hardware

i also saw you are running a 550watt psu that could give you issues if the power isnt suplied enough a bsod could occur as well when running this new stuff i would recommned 600watt or higher

Mmm... nope don't have another PC to test the parts on unfortunately

Shouldn't the 550w psu be sufficient? But, anyways I just brought a new 650w shall test it tonight and hopefully it's the psu

Shall update you guys later thanks for the suggestions solar!

rue

 

[Solarstarshines]

no problem and good luck

 

[youkay1]

This motherboard is fault. me and about 5 others having exactly the same issues - all with a single common factor, the gigabyte 880ga-ud3h

 

[Jonathan_King]

This motherboard is fault. me and about 5 others having exactly the same issues - all with a single common factor, the gigabyte 880ga-ud3h

Hello,

Could you please follow these directions?

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

 

[rjtehz]

Hi Guys!


Sorry for the late response have been kinda busy with work and all. I would just like to come back here and say a BIG THANK YOU TO ALL!

I finally found out what the problem was and now my desktop is working as it should

Culprit: It was the RAM!!! Even though I used Memtest86+ to stress test the RAM for 10++ hours it didn't detect any faulty partitions... But, I did realize that it kept crashing when I streamed Megavideo vods. Thus, allowing me to reproduce the problem easily. So, I took out each piece of hardware and played the vods to single out the culprit. In the end, it was that one stick of faulty RAM that caused the problem for over a bit of 3 weeks.

So I returned the RAM to MSY and they tested it for a few seconds and confirmed that the RAM was faulty and gladly gave me a refund so... I upgraded my RAM to a better brand i.e. Kingston

Thanks for all the help and got to say I love the community support!

Rue

 

[rjtehz]

This motherboard is fault. me and about 5 others having exactly the same issues - all with a single common factor, the gigabyte 880ga-ud3h

Mine is doing pretty well sorry to say >.<"

I guess there are always 1 in 100,000 pieces of hardware that are bound to have some defects. The world is not perfect, but yeah I have to agree with you on that one sometimes the quality of products are just not up to standards these days.

Hope all is good for you now