Sign in with
Sign up | Sign in
Your question

Windows 7 BSOD

Last response: in Windows 7
Share
September 19, 2010 11:28:05 AM

Hello everyone, I just had a BSOD about an hour ago and I wish to find out what went wrong. This is the first time.

System Specs:

AMD Phenom II X4 955 @ stock, CoolerMaster V8
MSI 790GX-G65
HIS HD4850 i-Cooler
Xigmatek NRP-MC751 750W modular PSU
2x KVR1333-2G @ 1333MHz
Seagate 7200.12 500GB

The BSOD flashed too quickly, didn't have enough time to take down the error message. It doesn't happen often and event viewer is not helping. Anyone who wishes to help, could you PM or add me on Windows Live (add foreverdarkness2002@hotmail.com) so that I could send my dump file over?

Also, I believe it has nothing to do with power issue since that Xigmatek model is pretty solid (of course not as solid compared to brands like Corsair, XFX) and 750W is plenty. So my guess is that it's either the GPU, RAM or the HDD. Please help me pinpoint the error. Thank you.

More about : windows bsod

September 19, 2010 2:50:40 PM

In the early months of using my current build, I had a completely random BSOD while gaming. I didn't worry too much about it, and have never had one since (other than those caused by OC experimentation). I know this sounds irresponsible, but you could just not worry about it unless it happens again.

Otherwise, you need to start asking troubleshooting questions like "What was I doing when the BSOD occurred? Have I made any hardware changes recently? Have I been Overclocking anything? Have I installed new drivers or made and significant software changes recently?" Finally, check your temps for the CPU, GPU, and Mobo. Are you within safe thresholds?
m
0
l
September 19, 2010 3:13:04 PM

Well, it is very weird because it was built last year and I have never encountered BSOD, until today. Besides, the temps are all good and within threshold. At max load with Prime95, CPU goes up to 53C which isn't impressive but safe. Since I am running on auto voltage, I assume that's a reasonable temp.

GPU on the other hand never exceeds 65C, based on HWMonitor max temp result.

I just feel uncomfortable seeing a BSOD since I spent a hefty sum on my current machine. It just makes me feel like I'm back in the old WinME days where BSOD was very common.
m
0
l
Related resources
September 19, 2010 8:39:57 PM

Don't stress too much about it. I know what it's like to spend a lot on hardware and ending up "uncomfortable" or dissapointed. It could have just been a fluke. If it happens again, a little more concern is certainly justifiable. If not, than you still have a great computer that has only given you one BSOD.
m
0
l
September 20, 2010 1:18:02 AM

Thanks for the replies. In the minidump folder, there are 2 logs one dated weeks ago (ain't aware of it, probably wasn't around to see it happen) and the other right after the BSOD yesterday. This isn't looking good.
m
0
l
September 20, 2010 5:47:25 AM

Is anyone able to help analyze the dump file?
m
0
l
September 20, 2010 3:01:45 PM

Hello guys, I managed to open the dump file and analyzed with WinDbg. It has narrowed down to the following process:

ntkrnlmp.exe

Does anyone have any idea?

***Edited***

Here is the full 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: fffff80002c8dec0

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80002cc4ca9 to fffff80002cc5740

STACK_TEXT:
fffff880`02f69ce8 fffff800`02cc4ca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`02f69cf0 fffff800`02cc3172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f69e30 fffff800`02c8dec0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`02f85ed0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`02cc3172 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
---------

m
0
l
September 20, 2010 10:30:03 PM

Google search ntkrnlmp.exe
Apparently, you aren't the only one with this problem.
The first few results immediately associate that name with BSOD's.

Like I said, make sure temps are ok and you might consider updating your video driver. If you use Catalyst, download 10.8 because this forum has been filled with 10.9 problems since it came out. Also, you never said whether or not you overclock. If you do, turn it off for a while.

So have you had any BSODs since the one that prompted this post?
m
0
l
September 21, 2010 12:47:52 AM

Hello CKLayoka,

The temps look OK. Ambient temp is on average around 30C and at idle, CPU is ~36C and on load (Prime95), it's around 52C.

Video card on the other hand rarely exceeds 60C which I find is pretty good. Motherboard/chipset temp is usually around ~28C.

I am using Catalyst 10.2, it's been stable all the time. No, I haven't had any BSODs.

My main concern is this, right now, my parts are still within 1 year store warranty and I am very close to the sales guy, he might be able to do a 1-for-1 exchange on the spot if only I could pin point the exact problem. Once this period has expired, I will need to send back to manufacturers which most of the time, is a hassle.

After digging a bit through Google, I found that it could be CPU related but no one can be sure of it. Can anyone tell me what are the signs of a damaged/dying CPU?
m
0
l
!