Share via

BSOD

Anonymous
2017-11-07T07:01:38+00:00

Hi I've Been Having Problems With My Windows 10 Computer And It Has Been Blue Screening Quite Frequently, I Did A Who Crashed Analyze And I Found This:  

On Tue 2017/11/07 8:52:16 AM your computer crashed

crash dump file: C:\WINDOWS\Minidump\110717-20984-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800B2D5CAF7, 0x0, 0xFFFFFFFFFFFFFFFF)

Error: KMODE_EXCEPTION_NOT_HANDLED

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

If Anybody Has A Possible Fix, Please Help.

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

12 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sumit 43,806 Reputation points Volunteer Moderator
    2017-11-07T09:01:34+00:00

    Need dumps. Who crashed is useless software. Either provide the dumps or if you want to self diagnose, then provide the dump stack of the crash in a txt file.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Sumit 43,806 Reputation points Volunteer Moderator
    2017-11-07T09:40:52+00:00

    Not helpful. I guess there is a misunderstanding, I need dump stack from Windows debugger provided you have that up and running.

    Do you have any privacy concerns with sharing dumps? Please note that the dumps do not contain any personal info so it is perfectly safe to share them with us.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-11-07T09:12:26+00:00

    https://anonfile.com/B251S9cbb5/DumpStack.txt

    The DumpStack download that i just uploaded

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-11-07T08:58:42+00:00

    The Who Crashed Analyse:

    On Tue 2017/11/07 8:52:16 AM your computer crashed

    crash dump file: C:\WINDOWS\Minidump\110717-20984-01.dmp

    This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)

    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800B2D5CAF7, 0x0, 0xFFFFFFFFFFFFFFFF)

    Error: KMODE_EXCEPTION_NOT_HANDLED

    file path: C:\WINDOWS\system32\ntoskrnl.exe

    product: Microsoft® Windows® Operating System

    company: Microsoft Corporation

    description: NT Kernel & System

    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.

    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    The OSR Analyse: 

    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: fffff800b2d5caf7, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, 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) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
nt!ExpInterlockedPopEntrySListFault+0
fffff800`b2d5caf7 498b08          mov     rcx,qword ptr [r8]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffffffffffffffff 

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

BUGCHECK_STR:  0x1e_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  H1Z1.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800b2d9014e to fffff800b2d56f90

CONTEXT:  e0750ac70f49f0cb -- (.cxr 0xe0750ac70f49f0cb)
Unable to read context, Win32 error 0n30

STACK_TEXT:  
ffffd681`a74c8828 fffff800`b2d9014e : 00000000`0000001e ffffffff`c0000005 fffff800`b2d5caf7 00000000`00000000 : nt!KeBugCheckEx
ffffd681`a74c8830 fffff800`b2d62202 : 00000000`00000002 00000000`17327890 ffff8844`22000000 ffff8844`22110880 : nt! ?? ::FNODOBFM::`string'+0x29f8e
ffffd681`a74c8f00 fffff800`b2d604bd : ffff8844`00003df0 fffff800`b2c817c6 fffff980`044d27d8 00000000`00000020 : nt!KiExceptionDispatch+0xc2
ffffd681`a74c90e0 fffff800`b2d5caf7 : 00000000`00000031 fffff800`b2c834b4 01000000`00000002 ffffd681`a74c9380 : nt!KiGeneralProtectionFault+0xfd
ffffd681`a74c9270 fffff800`b2c834b4 : 01000000`00000002 ffffd681`a74c9380 00000000`00000020 00000000`00000004 : nt!ExpInterlockedPopEntrySListFault
ffffd681`a74c9280 fffff800`b2c832a0 : fffff800`b2f31380 00000000`00000031 ffffc184`00000002 00000000`00000002 : nt!MiGetFreeOrZeroPage+0x64
ffffd681`a74c9350 fffff800`b2c82e96 : fffff800`b2f31380 00000000`00000000 00000000`00000000 ffffa901`00000000 : nt!MiGetPage+0x80
ffffd681`a74c93d0 fffff800`b2c7f01f : 00000000`00000002 80000000`018f0867 ffffc184`3fc27d00 fffff800`b2c804a3 : nt!MiGetPageChain+0x156
ffffd681`a74c9500 fffff800`b2c80a78 : ffffd681`a74c9670 ffffd681`a74c9650 00000000`00000000 00000000`0a1d2190 : nt!MiCreateSharedZeroPages+0x16f
ffffd681`a74c9600 fffff800`b2c86709 : 00000000`ffffffff ffffffff`00000480 00000000`00000000 ffffd681`00000018 : nt!MiResolveDemandZeroFault+0x258
ffffd681`a74c96f0 fffff800`b2c85870 : ffffd681`a74c99c0 00000000`0a1d3000 ffff8800`00050e98 ffffc184`460b6580 : nt!MiResolveProtoPteFault+0x269
ffffd681`a74c97a0 fffff800`b2c843da : ffffffff`00000480 00000000`00000004 ffffc184`3fc27d00 ffffd681`a74c9a00 : nt!MiDispatchFault+0x3d0
ffffd681`a74c9900 fffff800`b2d605fc : ffffc184`476b2080 ffffd681`a74c9b80 ffffffff`ffff3cb0 ffffc184`460b6080 : nt!MmAccessFault+0x67a
ffffd681`a74c9b00 00007ffa`4e268a8e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c
00000000`7d8df5a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ffa`4e268a8e

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+29f8e
fffff800`b2d9014e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+29f8e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  578998f1

STACK_COMMAND:  .cxr 0xe0750ac70f49f0cb ; kb

FAILURE_BUCKET_ID:  X64_0x1e_c0000005_nt!_??_::FNODOBFM::_string_+29f8e

BUCKET_ID:  X64_0x1e_c0000005_nt!_??_::FNODOBFM::_string_+29f8e

Followup: MachineOwnerHope This Helps.

    Was this answer helpful?

    0 comments
  5. Sumit 43,806 Reputation points Volunteer Moderator
    2017-11-07T08:41:07+00:00

    Was this answer helpful?

    0 comments