• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Uncatchable BSOD with KMODE_EXCEPTION_NOT_HANDLED


Nakushimo

New Member
Posts
1
#1
Hi.
I've bought new PC:

Motherboard: MSI Z97 GAMING 5 LGA 1150
CPU: INTEL Core i7 4790 with Cooler Master "Hyper 212 Evo RR-212E-20PK-R2"
GPU: MSI Geforce GTX 970, GTX 970 GAMING 4G, 4Гб
RAM: CRUCIAL CT102464BA160B DDR3 - 2x8Гб 1600
SSD: 128ГБ 2.5" Plextor "M6S" (SATA III)
HDD: Seagate "ST2000DM001" (SATA III)
ATX FRACTAL DESIGN Core 3500, (FD-CA-CORE-3500-BL) with AEROCOOL Strike-X 600
DVD-RW SAMSUNG SH-224DB/BEBE

I've got BSOD without showing it (even when this option enabled) in random time. Try to plug-off SDD, HDD, video, Ram in different variations. Even try to install windows on HDD without SSD.

I've got the latest versions of BIOS, SSD-firmware and drivers for motherboard and GPU. PC without any OC settings

That's .dmp file View attachment 120914-7500-01.zip and its analyze by windbg

Code:
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       [URL]http://msdl.microsoft.com/download/symbols[/URL]
Symbol search path is: [URL]http://msdl.microsoft.com/download/symbols[/URL]
Executable search path is: 
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17031.amd64fre.winblue_gdr.140221-1952
Machine Name:
Kernel base = 0xfffff800`b660f000 PsLoadedModuleList = 0xfffff800`b68d92d0
Debug session time: Mon Dec  8 12:44:09.862 2014 (UTC - 8:00)
System Uptime: 0 days 0:47:15.527
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..................................................  ............
..................................................  ..............
...................
Loading User Symbols
Loading unloaded module list
......
**************************************************  *****************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
**************************************************  *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff800b67649e2, 0, ff6be010}

Probably caused by : ntkrnlmp.exe ( nt!KiInterruptDispatchLBControl+2f2 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800b67649e2, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 00000000ff6be010, Parameter 1 of the exception

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


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800b6963138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 00000000ff6be010 

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!KiInterruptDispatchLBControl+2f2
fffff800`b67649e2 48cf            iretq

EXCEPTION_PARAMETER2:  00000000ff6be010

BUGCHECK_STR:  0x1E_c0000005_R

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

DPC_STACK_BASE:  FFFFD001DAF31FB0

TRAP_FRAME:  ffffd001daf2aaa0 -- (.trap 0xffffd001daf2aaa0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000069a1d5233 rbx=0000000000000000 rcx=0000000000000002
rdx=000000000001a686 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800b67649e2 rsp=ffffd001daf2ac38 rbp=0000000000000000
 r8=000000000001a686  r9=fffff800b68f7f80 r10=0000000000000000
r11=ffffd001daf2a900 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na pe nc
nt!KiInterruptDispatchLBControl+0x2f2:
fffff800`b67649e2 48cf            iretq
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800b67add47 to fffff800b6762fa0

STACK_TEXT:  
ffffd001`daf2a1c8 fffff800`b67add47 : 00000000`0000001e ffffffff`c0000005 fffff800`b67649e2 00000000`00000000 : nt!KeBugCheckEx
ffffd001`daf2a1d0 fffff800`b676ebc2 : 00000000`00000001  00000000`00000002 00000000`000015b6 00000000`00000000 : nt! ??  ::FNODOBFM::`string'+0x3a897
ffffd001`daf2a8c0 fffff800`b676d314 : 00000000`00000000  ffffd001`daf00180 ffffbd3f`ac4cdf00 ffffd001`daf2aaa0 :  nt!KiExceptionDispatch+0xc2
ffffd001`daf2aaa0 fffff800`b67649e2 : fffff800`b6766ac2  00000000`00000010 00000000`00000286 ffffd001`daf2ac60 :  nt!KiPageFault+0x214
ffffd001`daf2ac38 00000000`00000000 : 00000000`00000000  00000000`00000000 00000000`00000000 00000000`00000000 :  nt!KiInterruptDispatchLBControl+0x2f2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiInterruptDispatchLBControl+2f2
fffff800`b67649e2 48cf            iretq

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!KiInterruptDispatchLBControl+2f2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  53085af2

IMAGE_VERSION:  6.3.9600.17031

BUCKET_ID_FUNC_OFFSET:  2f2

FAILURE_BUCKET_ID:  0x1E_c0000005_R_nt!KiInterruptDispatchLBControl

BUCKET_ID:  0x1E_c0000005_R_nt!KiInterruptDispatchLBControl

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1e_c0000005_r_nt!kiinterruptdispatchlbcontrol

FAILURE_ID_HASH:  {4c0f3d22-2ec4-769a-54c4-2bc89b721961}

Followup: MachineOwner
---------
 
Last edited:

My Computer

System One

  • OS
    Windows 8.1