Jump to content

BSOD dmp file

Msuni
By Msuni
in Troubleshooting
 Share
Posted

How often has this BSOD happened so far?
What's your current hardware and OS? (dump says Windows 8 kernel... somehow I doubt that? If so, it might be hardware incompatibility with the OS, especially if you have newer hardware like an 8th gen Intel on Windows 8)

What were you doing with the computer at the time this happened? (gaming? browsing the web? extracting files from a zip/rar/7zip archive? watching a video?)

How much disk space do you have left? That error is also related to low disk space.

As for drivers, where did you get them? Are you 100% they are compatible with your hardware and did you update the BIOS as well?


 

Spoiler 

Windows 8 Kernel Version 17134 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff801`3c08c000 PsLoadedModuleList = 0xfffff801`3c43a170
Debug session time: Sun Sep  9 07:58:35.835 2018 (UTC - 4:00)
System Uptime: 0 days 1:40:49.577
*******************************************************************************
*                                                                             *
*                        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: ffffffffc0000096, The exception code that was not handled
Arg2: fffff8013c2383b2, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000001, Parameter 1 of the exception

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

FAULTING_IP: 
nt!KiIdleLoop+32
fffff801`3c2383b2 440f22c1        mov     cr8,rcx

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000001

ERROR_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

BUGCHECK_STR:  0x1e_c0000096

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

EXCEPTION_RECORD:  ffff930f1323d2d0 -- (.exr 0xffff930f1323d2d0)
ExceptionAddress: 0000000100000001
   ExceptionCode: 00000000
  ExceptionFlags: 00000100
NumberParameters: 0

LAST_CONTROL_TRANSFER:  from fffff8013c2cd8da to fffff8013c234ca0

CONTEXT:  7400002a0c953d80 -- (.cxr 0x7400002a0c953d80)
Unable to read context, Win32 error 0n30

STACK_TEXT:  
ffffea01`de2ae9d8 fffff801`3c2cd8da : 00000000`0000001e ffffffff`c0000096 fffff801`3c2383b2 00000000`00000000 : nt!KeBugCheckEx
ffffea01`de2ae9e0 fffff801`3c23d54d : fffff801`3c47d000 fffff801`3c08c000 000585cc`00954000 ffff930f`00000009 : nt!KiFatalExceptionHandler+0x22
ffffea01`de2aea20 fffff801`3c1588e6 : ffffea01`de2aeb50 ffffea01`de2af010 00000000`00000000 ffffea01`de2af928 : nt!RtlpExecuteHandlerForException+0xd
ffffea01`de2aea50 fffff801`3c15a243 : ffffea01`de2af928 ffffea01`de2af670 ffffea01`de2af928 ffff930f`164c5700 : nt!RtlDispatchException+0x416
ffffea01`de2af140 fffff801`3c245942 : ffff930f`1323d2d0 00000000`00000000 ffffa600`87c79180 fffff801`3c0e174c : nt!KiDispatchException+0x1f3
ffffea01`de2af7f0 fffff801`3c23f3c6 : ffff930f`1323d2d0 00000000`00000001 ffffea01`de2afb00 00000000`00000001 : nt!KiExceptionDispatch+0xc2
ffffea01`de2af9d0 fffff801`3c2383b2 : ffffffff`00000000 ffffa600`87c79180 ffffa600`87c89300 ffff930f`164c5700 : nt!KiDivideErrorFault+0x2c6
ffffea01`de2afb60 00000000`00000000 : ffffea01`de2b0000 ffffea01`de2a9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x32


FOLLOWUP_IP: 
nt!KiIdleLoop+32
fffff801`3c2383b2 440f22c1        mov     cr8,rcx

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  nt!KiIdleLoop+32

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5b6bc221

STACK_COMMAND:  .cxr 0x7400002a0c953d80 ; kb

FAILURE_BUCKET_ID:  X64_0x1e_c0000096_nt!KiIdleLoop+32

BUCKET_ID:  X64_0x1e_c0000096_nt!KiIdleLoop+32

Followup: MachineOwner
---------
Crash Code Links
View the MSDN page for KMODE_EXCEPTION_NOT_HANDLED
Search Google for KMODE_EXCEPTION_NOT_HANDLED


The more information you give the better, because from the minidump, honestly, I can't tell much other than it seems to have been caused by System, but generally that's because something else crapped itself and bought the system along with it.

CPU: AMD Ryzen 3700x / GPU: Asus Radeon RX 6750XT OC 12GB / RAM: Corsair Vengeance LPX 2x16GB DDR4-3200
MOBO: MSI B450m Gaming Plus / NVME: Corsair MP510 240GB / Case: TT Core v21 / PSU: Seasonic 750W / OS: Bazzite

Link to comment
https://linustechtips.com/topic/970059-bsod-dmp-file/#findComment-11735353
Share on other sites
Link to post
Share on other sites
Posted
  • Author
15 minutes ago, TetraSky said:

How often has this BSOD happened so far?
What's your current hardware and OS? (dump says Windows 8 kernel... somehow I doubt that? If so, it might be hardware incompatibility with the OS, especially if you have newer hardware like an 8th gen Intel on Windows 8)

What were you doing with the computer at the time this happened? (gaming? browsing the web? extracting files from a zip/rar/7zip archive? watching a video?)

How much disk space do you have left? That error is also related to low disk space.

As for drivers, where did you get them? Are you 100% they are compatible with your hardware and did you update the BIOS as well?


 

  Reveal hidden contents 


Windows 8 Kernel Version 17134 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff801`3c08c000 PsLoadedModuleList = 0xfffff801`3c43a170
Debug session time: Sun Sep  9 07:58:35.835 2018 (UTC - 4:00)
System Uptime: 0 days 1:40:49.577
*******************************************************************************
*                                                                             *
*                        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: ffffffffc0000096, The exception code that was not handled
Arg2: fffff8013c2383b2, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000001, Parameter 1 of the exception

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

FAULTING_IP: 
nt!KiIdleLoop+32
fffff801`3c2383b2 440f22c1        mov     cr8,rcx

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000001

ERROR_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

BUGCHECK_STR:  0x1e_c0000096

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

EXCEPTION_RECORD:  ffff930f1323d2d0 -- (.exr 0xffff930f1323d2d0)
ExceptionAddress: 0000000100000001
   ExceptionCode: 00000000
  ExceptionFlags: 00000100
NumberParameters: 0

LAST_CONTROL_TRANSFER:  from fffff8013c2cd8da to fffff8013c234ca0

CONTEXT:  7400002a0c953d80 -- (.cxr 0x7400002a0c953d80)
Unable to read context, Win32 error 0n30

STACK_TEXT:  
ffffea01`de2ae9d8 fffff801`3c2cd8da : 00000000`0000001e ffffffff`c0000096 fffff801`3c2383b2 00000000`00000000 : nt!KeBugCheckEx
ffffea01`de2ae9e0 fffff801`3c23d54d : fffff801`3c47d000 fffff801`3c08c000 000585cc`00954000 ffff930f`00000009 : nt!KiFatalExceptionHandler+0x22
ffffea01`de2aea20 fffff801`3c1588e6 : ffffea01`de2aeb50 ffffea01`de2af010 00000000`00000000 ffffea01`de2af928 : nt!RtlpExecuteHandlerForException+0xd
ffffea01`de2aea50 fffff801`3c15a243 : ffffea01`de2af928 ffffea01`de2af670 ffffea01`de2af928 ffff930f`164c5700 : nt!RtlDispatchException+0x416
ffffea01`de2af140 fffff801`3c245942 : ffff930f`1323d2d0 00000000`00000000 ffffa600`87c79180 fffff801`3c0e174c : nt!KiDispatchException+0x1f3
ffffea01`de2af7f0 fffff801`3c23f3c6 : ffff930f`1323d2d0 00000000`00000001 ffffea01`de2afb00 00000000`00000001 : nt!KiExceptionDispatch+0xc2
ffffea01`de2af9d0 fffff801`3c2383b2 : ffffffff`00000000 ffffa600`87c79180 ffffa600`87c89300 ffff930f`164c5700 : nt!KiDivideErrorFault+0x2c6
ffffea01`de2afb60 00000000`00000000 : ffffea01`de2b0000 ffffea01`de2a9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x32


FOLLOWUP_IP: 
nt!KiIdleLoop+32
fffff801`3c2383b2 440f22c1        mov     cr8,rcx

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  nt!KiIdleLoop+32

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5b6bc221

STACK_COMMAND:  .cxr 0x7400002a0c953d80 ; kb

FAILURE_BUCKET_ID:  X64_0x1e_c0000096_nt!KiIdleLoop+32

BUCKET_ID:  X64_0x1e_c0000096_nt!KiIdleLoop+32

Followup: MachineOwner
---------
Crash Code Links
View the MSDN page for KMODE_EXCEPTION_NOT_HANDLED
Search Google for KMODE_EXCEPTION_NOT_HANDLED


The more information you give the better, because from the minidump, honestly, I can't tell much other than it seems to have been caused by System, but generally that's because something else crapped itself and bought the system along with it.

I have an i7 8700k and Windows 10 home. I have changed the Write Debugging Information from Kernel Memory Dump to Small Memory Dump (256KB) and that seemed to have fixed the problem. *Touch wood*

Link to comment
https://linustechtips.com/topic/970059-bsod-dmp-file/#findComment-11735417
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×