Sign in with
Sign up | Sign in
Your question

IMAGE_NAME: ntkrnlmp.exe causing BSOD on Win 7 x64

Last response: in Overclocking
Share
February 11, 2013 3:23:32 PM

Greetings friends,

I have searched the forum for a response to my annoying issue, but I did not found a post that fits exactly to my case, then I decided to post my problem, hoping to get your appreciated help.

I am getting BSOD in Win 7 x64 frequently in a random time. I was overclocking my machine with the preset values that my MoBo has for "best performance" (My PC specs are below) and I was getting this Minidump after BSODs:

Quote:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Gamer\Desktop\020113-27019-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02c03000 PsLoadedModuleList = 0xfffff800`02e47670
Debug session time: Fri Feb 1 21:12:19.479 2013 (UTC - 5:00)
System Uptime: 0 days 0:32:17.681
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8009ea5028, be200000, 21136}

Probably caused by : GenuineIntel

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8009ea5028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000021136, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

STACK_TEXT:
fffff880`033dfa58 fffff800`031fda3b : 00000000`00000124 00000000`00000000 fffffa80`09ea5028 00000000`be200000 : nt!KeBugCheckEx
fffff880`033dfa60 fffff800`02d8fb13 : 00000000`00000001 fffffa80`09f7fea0 00000000`00000000 fffffa80`09f7fef0 : hal!HalBugCheckSystem+0x1e3
fffff880`033dfaa0 fffff800`031fd700 : 00000000`00000728 fffffa80`09f7fea0 fffff880`033dfe30 fffff880`033dfe00 : nt!WheaReportHwError+0x263
fffff880`033dfb00 fffff800`031fd052 : fffffa80`09f7fea0 fffff880`033dfe30 fffffa80`09f7fea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`033dfc50 fffff800`031fcf0d : 00000000`00000004 00000000`00000001 fffff880`033dfeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`033dfc90 fffff800`031f0e88 : fffffa80`006f5460 00000000`000251c2 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`033dfcc0 fffff800`02c808ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`033dfcf0 fffff800`02c80713 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`033dfe30 fffff800`02c9280b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`03755990 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiUnlinkPageFromLockedList+0x21b


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

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


I read a lot about possible issues due to the preset overclocking settings of my MoBo, then I set them manually and without demanding too much of my processor (Overclocked from 3.4Ghz to 3.8Ghz).

The system seems to be a little more steady as it BSODs less frequently. What calls my attention is that, since then, the Minidump info changed, what makes me doubt about the issue being in the overclocking, this is the new Minidump I am getting:

Quote:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Gamer\Desktop\021113-12277-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02e05000 PsLoadedModuleList = 0xfffff800`03049670
Debug session time: Mon Feb 11 07:57:23.857 2013 (UTC - 5:00)
System Uptime: 0 days 0:34:28.669
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050033, 406f8, fffff80002e89314}

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

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

2: 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: 0000000080050033
Arg3: 00000000000406f8
Arg4: fffff80002e89314

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80002e83569 to fffff80002e83fc0

STACK_TEXT:
fffff880`0336bce8 fffff800`02e83569 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
fffff880`0336bcf0 fffff800`02e81a32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0336be30 fffff800`02e89314 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`03718000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeferredReadyThread+0x14


STACK_COMMAND: kb

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

FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

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


Ok, this is my PC's info:

Quote:
OS: Windows 7 Professional 64-bit Service Pack (OEM Dell)
CPU: Intel Core i5 3570K @3.40Ghz (Overclocked to 3.8Ghz)
Network device: TP Link 150Mbps Wireless N Adapter (Via PCI)
RAM: 2 modules Corsair of 4GB each DDR3 @1600Mhz in dual chanel slots of the MoBo
MoBo: Asus P8Z77-V LX
Video card: AMD Radeon HD 7850 2GB DDR5, PCIe
HDD: Toshiba DT01ACA100 1TB
Audio device: Realtek High Definition Audio
Power supply: Thermaltake 600W


It is good to mention, I already mounted again the Win (with the same disc I used before), updated ALL drivers and updated BIOS. I also run stress tests with the Asus app and with Prime95. All Memory, HDD, CPU tests passed, except for one while running Prime; the Minidump is just like the second one posted above but with: PROCESS_NAME: prime95.exe

I usually use this PC for gaming. Funny thing is that it only BSODd once while playing, most BSODs come while doing any other thing (I haven't found a pattern).

I am really disappointed and exhausted of struggling with this issues, I have been dealing with it for almost a month and now I come to you, so any help you can provide, will be very very much appreciated.

THANK YOU.

PS: I apologize if I missed any rule of the forum. I will fix it for the next time.
a c 125 K Overclocking
February 12, 2013 9:43:42 AM

Hi,

The First BSOD was a 0x124 which usually points to not enough Vcore

The second one is less clear but usually relates to overclocking, increase the vcore slightly and re-run Prime95, monitor the CPU temps though!.
February 12, 2013 12:20:28 PM

Thanks omgitzfatal!

I am not very knowledgeable about OC, that's why I am using auto Voltages. I will read a little about manipulating VCore and try your suggestion. If you know about any "OC for dummies" link, I will appreciate if you can share it.

Thank you again.
Related resources
a c 125 K Overclocking
February 12, 2013 12:27:09 PM

wkwk said:
Thanks omgitzfatal!

I am not very knowledgeable about OC, that's why I am using auto Voltages. I will read a little about manipulating VCore and try your suggestion. If you know about any "OC for dummies" link, I will appreciate if you can share it.

Thank you again.


No problem, here's a fairly easy guide to follow, though if you get stuck just let us know :) 

http://club.myce.com/f184/easy-overclocking-guide-intel...
February 13, 2013 3:19:47 PM

Guys, yesterday night I followed the guide omgitzfatal suggested. I made some stress tests which were successful. Today, as usual, I turned my PC on to access it from work; when I got to the office (1.5 hours later), immediately accessed it and my surprise is that it BSODd and the Minidump is exactly the same as the first one in my first post. What calls my attention is that the system was doing nothing as I turned it on and left to work. Checking the last Minidumps, all were generated around 8 am (approx 30 to 60 mins after turned on). Funny thing is that it only BSODs at that time and the rest of the day, I work with it without problems. Now I am more confused, any help will be much appreciated.

Thank you,
a c 125 K Overclocking
February 13, 2013 3:30:21 PM

wkwk said:
Guys, yesterday night I followed the guide omgitzfatal suggested. I made some stress tests which were successful. Today, as usual, I turned my PC on to access it from work; when I got to the office (1.5 hours later), immediately accessed it and my surprise is that it BSODd and the Minidump is exactly the same as the first one in my first post. What calls my attention is that the system was doing nothing as I turned it on and left to work. Checking the last Minidumps, all were generated around 8 am (approx 30 to 60 mins after turned on). Funny thing is that it only BSODs at that time and the rest of the day, I work with it without problems. Now I am more confused, any help will be much appreciated.

Thank you,


Hey,

What O/C settings did you use and how long did you stress test for?
February 13, 2013 4:09:50 PM

Thanks for your response omg,

I used this:

AI overclock tuner: Manual
BCLK: 100.0
Asus multicore enhancement: Enabled
Turbo ratio: Manual
Ratio sync control: enabled
1-4 core ratio limit: 43
Internal PLL overvoltage: enabled
CPU bus speed. Dram speed ratio mode: Auto
CPU voltage: Offset mode
offset mode sign: +
CPU offset voltage: 0.025
CPU ratio: auto
EIS: enabled
Turbo mode: enabled
CPU C1, C3, C6: enabled
Package C state support: enabled

I run the tests for about 4 hours (Prime95). Temps max I am getting is 70C. Max VCore is 1.208.

What do you think?

Thank you
a c 125 K Overclocking
February 13, 2013 4:18:00 PM

I think it's an issue with the CPU clock and voltage dropping when idle, I reckon if you disable the C states and EIS and set a fixed voltage (rather than an offset) of 1.208V it will be stable.
Though it is just a theory based on my experience of overclocking and what I've read about before.

A small bump in Vcore would most likely solve it aswell (given that we know the BSOD code 0x124 almost always points to not enough Vcore).

Your temps and voltage are good, 4 hours prime isn't bad, but I'd recommend longer if you can (12 hours +).
February 13, 2013 4:26:44 PM

omg, I apologize, I meant the second Minidump posted. so its a code 0x7f. I would like to use an offset OC; do you come up with something more that don't imply to set a 24/7?

BTW, when idle, the CPU is going to 1.6Ghz and 0.98 Vcore.
a c 125 K Overclocking
February 13, 2013 5:12:15 PM

wkwk said:
omg, I apologize, I meant the second Minidump posted. so its a code 0x7f. I would like to use an offset OC; do you come up with something more that don't imply to set a 24/7?

BTW, when idle, the CPU is going to 1.6Ghz and 0.98 Vcore.

Ah ok fair enough :) 

What did you set your RAM to?

If I were you I'd up the voltage by one notch and stability test again using prime and Intel burn test.

Your idle clock and voltage is fine, though what I meant before was the transition from load to idle states can sometimes cause instability.
February 13, 2013 5:24:26 PM

Thank you,

I set the RAM at 1600Mhz (stock).

by "I'd up the voltage by one notch" you mean the Vcore? or the Voffset?. I am "Controlling" the offset, the Vcore is set to auto, but if you suggest, I can set manually the Vcore too.

Thank you
a c 125 K Overclocking
February 13, 2013 5:28:07 PM

Ah ok then thats fine, just make sure your RAM timings and voltage are set correctly aswell.

If your using offset then up the offset voltage slightly

:) 

Let us know how you get on
February 13, 2013 5:31:04 PM

Sure, I'll test and let you know.

BTW, I really appreciate what you are doing to help me out. Not so many people are so dedicate, patient and professional like you. THANK YOU.

I'll come back with news soon.
a c 125 K Overclocking
February 13, 2013 5:36:59 PM

wkwk said:
Sure, I'll test and let you know.

BTW, I really appreciate what you are doing to help me out. Not so many people are so dedicate, patient and professional like you. THANK YOU.

I'll come back with news soon.


Thanks for your kind works :)  I help out when I have free time, and it gives me a break from studying A2 maths :wahoo: 

!