stormflora
Well-known member
- Jun 26, 2019
- 54
Very well then. I will disable Driver Verifier and enable Debug Mode now. I will post back once something happens.
Been having trouble with the IRQL_NOT_LESS_OR_EQUAL BSOD for many months now
- Thread starter stormflora
- Start date
stormflora
Well-known member
- Jun 26, 2019
- 54
Hi everyone, just popping in to give a small status report. So far, after updating W10 to the latest possible version (with all additional updates), I haven't been getting the IRQL BSOD after playing gaming sessions for several hours on end, after several days of gaming. I have been very pleased by this! Perhaps my version of W10 really was broken in some way.
Just last night though, I experienced a WHEA_UNCORRECTABLE_ERROR BSOD, but I think I might know why it happened. I was trying to play a game, and it crashed (just a normal one), so I promptly tried to reload it. The game loads a lot of resources all at once, so when it was happening, I heard my CPU fans ramp up to maximum, and then I (stupidly) tried to do some other stuff on the side, and it gave me this BSOD, claiming it was caused by hal.dll and ntoskrnl.exe. My suspicion is that the CPU suddenly ramped up past T-Max and triggered the CPU's failsafe and forced a BSOD, but I'm not 100% sure about that. Could it have happened because of the CPU overheating like this? It's my first time experiencing it, and I'm not sure if I want to deliberately try recreating it because it's quite rare.
(Note: This particular game is the only one that ever causes my fans to ramp up to an audible full (70C+), and I was playing it for a lengthy amount of time prior to its initial crash. The game's been known to be poorly optimized.)
Thanks everyone for all the help so far!!!! I left Driver Verifier on indefinitely ever since then as a means to catch detailed BSODs (instead of debug mode, because it seems to interfere with some programs).
Just last night though, I experienced a WHEA_UNCORRECTABLE_ERROR BSOD, but I think I might know why it happened. I was trying to play a game, and it crashed (just a normal one), so I promptly tried to reload it. The game loads a lot of resources all at once, so when it was happening, I heard my CPU fans ramp up to maximum, and then I (stupidly) tried to do some other stuff on the side, and it gave me this BSOD, claiming it was caused by hal.dll and ntoskrnl.exe. My suspicion is that the CPU suddenly ramped up past T-Max and triggered the CPU's failsafe and forced a BSOD, but I'm not 100% sure about that. Could it have happened because of the CPU overheating like this? It's my first time experiencing it, and I'm not sure if I want to deliberately try recreating it because it's quite rare.
(Note: This particular game is the only one that ever causes my fans to ramp up to an audible full (70C+), and I was playing it for a lengthy amount of time prior to its initial crash. The game's been known to be poorly optimized.)
Thanks everyone for all the help so far!!!! I left Driver Verifier on indefinitely ever since then as a means to catch detailed BSODs (instead of debug mode, because it seems to interfere with some programs).
Last edited:
stormflora
Well-known member
- Jun 26, 2019
- 54
Hi Patrick. I'm guessing you want the minidump for the WHEA BSOD, correct? If so, I have attached it.
I've yet to experience an IRQL BSOD ever since updating Windows, so that is already a major improvement. The WHEA BSOD might've been caused by unrelated reasons.
Of course, I cannot be certain whether this issue has been solved yet, but I have confidence that my computer is healthier now. I will continue to leave Verifier enabled to catch any other BSODs I encounter down the line.
stormflora
Well-known member
- Jun 26, 2019
- 54
Hi Patrick, it's me again. I have already disabled Driver Verifier since the last time I postd here.
So since the time I posted that minidump, I didn't experience any BSoDs until yesterday.
Yesterday, I had a BSoD during ordinary operation (I wasn't gaming), and it was for KMODE_EXCEPTION_NOT_HANDLED.
I didn't have Driver Verifier enabled, but BlueScreenView pointed to a driver called e1d68x64.sys, which I found on the Internet to be Intel's Ethernet Driver, so I updated that.
However, just now, I had another BSoD called SYSTEM_SERVICE_EXCEPTION, which happened while I was trying to load a game.
WhoCrashed claims that this particular BSoD was likely caused by fltmgr.sys, which seems to be "Microsoft Filesystem Filter Manager".
I've included both minidumps for your analysis. In the meanwhile, I did a sfc /scannow check, and it did find corrupt files, but it wasn't able to fix them. I'm not sure how to get it to do so.
Ultimately, although I've seemingly rectified my initial problems, other problems keep rising. I'm not sure what's going on. Is W10 really that buggy?
I'm a bit late to this thread but I've just had a look at these recent minidumps.
1. Going back to the 0x124 WHEA BSOD I can see that the CPU was reporting an internal timer error. If this was a one off I might be inclined to ignore it and in any case we would need to see a few more of these types of errors to begin to build up a picture of what is happening.
2. The KMODE exception 0x1e BSOD showed two possible drivers were implicated these were e1d68x64.sys which you already found out and also nvlddmkm.sys which is the graphics driver.
The full memory stack from the time of the crash is shown below:
3. The System Exception BSOD (0x3B) also showed the graphics driver but not the network driver:
Based on these results I would suggest you update the graphics driver as well. The best way to do this is by uninstalling the nVidia driver with a utility called Display Driver Uninstaller DDU and then reinstalling just the graphics driver and PhysX driver required for gaming.
Hope this helps.
1. Going back to the 0x124 WHEA BSOD I can see that the CPU was reporting an internal timer error. If this was a one off I might be inclined to ignore it and in any case we would need to see a few more of these types of errors to begin to build up a picture of what is happening.
2. The KMODE exception 0x1e BSOD showed two possible drivers were implicated these were e1d68x64.sys which you already found out and also nvlddmkm.sys which is the graphics driver.
The full memory stack from the time of the crash is shown below:
Code:
Start memory scan : 0xffff818b40a8e4c8 ($csp)
End memory scan : 0xffff818b40a90000 (Kernel Stack Base)
rsp : 0xffff818b40a8e4c8 : 0xfffff8075b2a382e : nt!KiFatalExceptionHandler+0x22
0xffff818b40a8e4c8 : 0xfffff8075b2a382e : nt!KiFatalExceptionHandler+0x22
0xffff818b40a8e4e0 : 0xfffff8075bab37ce : hal!KeQueryPerformanceCounter+0xe
0xffff818b40a8e4f0 : 0xfffff8075bab37c0 : hal!KeQueryPerformanceCounter
0xffff818b40a8e508 : 0xfffff8075b1c560f : nt!RtlpExecuteHandlerForException+0xf
0xffff818b40a8e510 : 0xfffff8075b50c000 : "nt!Ports (nt+0x50c000)"
0xffff818b40a8e518 : 0xfffff8075b000000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor (nt+0x0)"
0xffff818b40a8e530 : 0xffff818b40a8eb00 : 0xfffff8075b1c0388 : nt!KiIdleLoop+0x48
0xffff818b40a8e538 : 0xfffff8075b0ca765 : nt!RtlDispatchException+0x4a5
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_37ec54c19854e219\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\e1d68x64.inf_amd64_9b64147bed2d44a1\e1d68x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e1d68x64.sys
0xffff818b40a8e5d8 : 0xfffff8075e715001 : NETIO!PplGenericFreeFunction+0x21
0xffff818b40a8e6a8 : 0xfffff8075b047f75 : nt!KiExitDispatcher+0x105
0xffff818b40a8e708 : 0xfffff8075b047a63 : nt!KeSetEvent+0xb3
0xffff818b40a8e908 : 0xfffff8075ea918fe : fwpkclnt!FwpsNetBufferListRetrieveContext0+0x4e
0xffff818b40a8e918 : 0xfffff8075bab4e0a : hal!HalBuildScatterGatherListV2+0x21a
0xffff818b40a8e928 : 0xffff898001be19f0 : !da "ee966&token=AC4w5Vhn46n9XaCylmd16TvDAiwirdQ-iw%3A1564864118601&includes_info_par..."
0xffff818b40a8e968 : 0xfffff8075e591d4c : ndis!PplGenericAllocateFunction+0x1c
0xffff818b40a8e9a8 : 0xfffff8075e58ee89 : ndis!NdisMAllocateNetBufferSGList+0x249
0xffff818b40a8e9b8 : 0xfffff8075b07313d : nt!KeQueryCurrentStackInformationEx+0x6d
0xffff818b40a8e9f8 : 0xfffff8075b0ce5f4 : nt!RtlGetExtendedContextLength2+0x3c
0xffff818b40a8ea08 : 0xfffff8075b1256e0 : nt!RtlpGetStackLimitsEx+0x14
0xffff818b40a8ea38 : 0xfffff8075b0ca3bc : nt!RtlDispatchException+0xfc
0xffff818b40a8ea90 : 0xfffff8075b000000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor (nt+0x0)"
0xffff818b40a8ea98 : 0xfffff8075b2a380c : nt!KiFatalExceptionHandler
0xffff818b40a8eaf0 : 0xfffff8075b52313c : "nt!Ports (nt+0x52313c)"
0xffff818b40a8eb00 : 0xfffff8075b1c0388 : nt!KiIdleLoop+0x48
0xffff818b40a8eb08 : 0xfffff8075b000000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor (nt+0x0)"
0xffff818b40a8eb10 : 0xfffff8075b52313c : "nt!Ports (nt+0x52313c)"
0xffff818b40a8eb30 : 0xfffff8075b2a380c : nt!KiFatalExceptionHandler
0xffff818b40a8eb68 : 0xfffff8075b021115 : nt!PoIdle+0x55
0xffff818b40a8eb70 : 0xfffff8075bab386b : hal!KeQueryPerformanceCounter+0xab
0xffff818b40a8eb78 : 0xfffff8075bab2000 : "hal!HalpTimerDpcRoutine (hal+0x0)"
0xffff818b40a8eb80 : 0xfffff8075bb23060 : "hal!XmCmosAddress (hal+0x71060)"
0xffff818b40a8eb88 : 0xfffff8075b000000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor (nt+0x0)"
0xffff818b40a8eb90 : 0xfffff8075b50d830 : "nt!Ports (nt+0x50d830)"
0xffff818b40a8eb98 : 0xfffff8075b000000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor (nt+0x0)"
0xffff818b40a8eba0 : 0xfffff8075b50d800 : "nt!Ports (nt+0x50d800)"
0xffff818b40a8eba8 : 0xfffff8075b000000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor (nt+0x0)"
0xffff818b40a8ebb0 : 0xfffff8075b52313c : "nt!Ports (nt+0x52313c)"
0xffff818b40a8ec48 : 0xfffff8075b0cf076 : nt!KdTrap+0x22
0xffff818b40a8ec88 : 0xfffff8075b0cecfe : nt!KiDispatchException+0x16e
0xffff818b40a8ed88 : 0xfffff8075bab37c0 : hal!KeQueryPerformanceCounter
0xffff818b40a8edb8 : 0xfffff8075bab37ce : hal!KeQueryPerformanceCounter+0xe
0xffff818b40a8ede8 : 0xfffff8075b047f75 : nt!KiExitDispatcher+0x105
0xffff818b40a8ee48 : 0xfffff8075b047a63 : nt!KeSetEvent+0xb3
0xffff818b40a8ef68 : 0xfffff8075bab3848 : hal!KeQueryPerformanceCounter+0x88
0xffff818b40a8ef78 : 0xfffff8075d17146e : partmgr!PmUpdateIoPower+0x13e
0xffff818b40a8f028 : 0xfffff8075b046b67 : nt!IofCompleteRequest+0x17
0xffff818b40a8f058 : 0xfffff8075b0477a3 : nt!IopfCompleteRequest+0xc23
0xffff818b40a8f0b8 : 0xfffff8075ee175df : CLASSPNP!ClasspWriteIOResultEvent+0x7f
0xffff818b40a8f0d8 : 0xfffff8075b03d365 : nt!KiCancelTimer+0x155
0xffff818b40a8f118 : 0xfffff8075b0ce5f4 : nt!RtlGetExtendedContextLength2+0x3c
0xffff818b40a8f158 : 0xfffff8075b0ce4ed : nt!RtlGetExtendedContextLength+0x2d
0xffff818b40a8f168 : 0xfffff8075b046b67 : nt!IofCompleteRequest+0x17
0xffff818b40a8f338 : 0xfffff8075b1ce69d : nt!KiExceptionDispatch+0x11d
0xffff818b40a8f438 : 0xfffff8075b069ffe : nt!PopFxIdleWorkerTail+0xd6
0xffff818b40a8f488 : 0xfffff8075bab37ce : hal!KeQueryPerformanceCounter+0xe
0xffff818b40a8f4a0 : 0xfffff8075bab37c0 : hal!KeQueryPerformanceCounter
0xffff818b40a8f4d8 : 0xfffff8075b1be905 : nt!KiInterruptDispatchNoLockNoEtw+0x85
0xffff818b40a8f4e0 : 0x0000000000000000 : Trap @ ffff818b40a8f4e0
0xffff818b40a8f510 : 0xfffff807735ed3b0 : intelppm!C1Idle
0xffff818b40a8f518 : 0xfffff8075b1c78df : nt!KxDebugTrapOrFault+0x3df
0xffff818b40a8f520 : 0x0000000000000000 : Trap @ ffff818b40a8f520
0xffff818b40a8f538 : 0xfffff807735e1400 : intelppm!AcpiCStateIdleExecute
0xffff818b40a8f578 : 0xfffff8075bab37c0 : hal!KeQueryPerformanceCounter
0xffff818b40a8f610 : 0xffff898ffb3faad0 : 0xfffff807735e1180 : intelppm!PerfReadWrappingCounter
0xffff818b40a8f628 : 0xfffff8075b0233cf : nt!PpmUpdatePerformanceFeedback+0x14f
0xffff818b40a8f648 : 0xfffff807735e4332 : intelppm!C1Halt+0x2
0xffff818b40a8f688 : 0xfffff8075bab37ce : hal!KeQueryPerformanceCounter+0xe
0xffff818b40a8f6d8 : 0xfffff8075b021d9b : nt!PpmIdleExecuteTransition+0x7cb
0xffff818b40a8f808 : 0xfffff8075b0226ac : nt!PpmIdlePrepare+0x45c
0xffff818b40a8f9b8 : 0xfffff8075b000000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor (nt+0x0)"
0xffff818b40a8f9f8 : 0xfffff8075b02142e : nt!PoIdle+0x36e
0xffff818b40a8fb58 : 0xfffff8075b1c0388 : nt!KiIdleLoop+0x483. The System Exception BSOD (0x3B) also showed the graphics driver but not the network driver:
Code:
Start memory scan : 0xffffc70336566218 ($csp)
End memory scan : 0xffffc70336568000 (Kernel Stack Base)
rsp : 0xffffc70336566218 : 0xfffff8035a9ce569 : nt!KiBugCheckDispatch+0x69
0xffffc70336566218 : 0xfffff8035a9ce569 : nt!KiBugCheckDispatch+0x69
0xffffc70336566230 : 0xfffff8035a835590 : nt!ObFastReferenceObject+0x10
0xffffc703365662f0 : 0xfffff8035a835590 : nt!ObFastReferenceObject+0x10
0xffffc703365662f8 : 0xfffff8035a91c28b : nt!KeCheckStackAndTargetAddress+0x2b
0xffffc70336566338 : 0xfffff8035a9cdf95 : nt!KiSystemServiceCopyEnd+0x25
0xffffc70336566350 : 0xfffff8035ad239dc : "nt!Ports (nt+0x5239dc)"
0xffffc70336566358 : 0xfffff8035a9cd9bc : nt!KiSystemServiceHandler+0x7c
0xffffc70336566370 : 0xfffff8035ad3e610 : "nt!Ports (nt+0x53e610)"
0xffffc70336566388 : 0xfffff8035ae43308 : nt!NtWriteFile+0x458
0xffffc70336566398 : 0xfffff8035a9c560f : nt!RtlpExecuteHandlerForException+0xf
0xffffc703365663a0 : 0xfffff8035ad0c000 : "nt!Ports (nt+0x50c000)"
0xffffc703365663a8 : 0xfffff8035a800000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor (nt+0x0)"
0xffffc703365663c0 : 0xffffc70336566990 : 0xfffff8035a9cdf95 : nt!KiSystemServiceCopyEnd+0x25
0xffffc703365663c8 : 0xfffff8035a8ca765 : nt!RtlDispatchException+0x4a5
0xffffc70336566408 : 0xfffff8035a847a63 : nt!KeSetEvent+0xb3
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_37ec54c19854e219\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
0xffffc70336566498 : 0xfffff8035eb1c4d8 : FLTMGR!FltpFsControlCompletion+0x18
0xffffc703365664c8 : 0xfffff8035a846c99 : nt!IopfCompleteRequest+0x119
0xffffc70336566558 : 0xfffff8035a9c326f : nt!KiIpiInterrupt+0x34f
0xffffc70336566578 : 0xfffff8035a7602cb : hal!HalPerformEndOfInterrupt+0x1b
0xffffc70336566590 : 0xfffff8035ad8c400 : nt!KiInitialThread
0xffffc703365665a8 : 0xfffff8035a9be444 : nt!KiInterruptDispatch+0xc4
0xffffc70336566738 : 0xfffff8035ae59fd5 : nt!PspGetContextThreadInternal+0x135
0xffffc70336566748 : 0xfffff803601a0000 : "Ntfs!NtfsProtectClusters (Ntfs+0x0)"
0xffffc70336566778 : 0xfffff8036029c5c6 : Ntfs!NtfsFsdDispatchSwitch+0x586
0xffffc70336566848 : 0xfffff8035a87313d : nt!KeQueryCurrentStackInformationEx+0x6d
0xffffc70336566888 : 0xfffff8035a8ce5f4 : nt!RtlGetExtendedContextLength2+0x3c
0xffffc70336566898 : 0xfffff8035a9256e0 : nt!RtlpGetStackLimitsEx+0x14
0xffffc703365668c8 : 0xfffff8035a8ca3bc : nt!RtlDispatchException+0xfc
0xffffc703365668f8 : 0xfffff8035aebffba : nt!RtlpWow64CtxFromAmd64+0x18e
0xffffc70336566908 : 0xfffff8035aebfc36 : nt!RtlpWriteExtendedContext+0x96
0xffffc70336566920 : 0xfffff8035a800000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor (nt+0x0)"
0xffffc70336566928 : 0xfffff8035a9cd940 : nt!KiSystemServiceHandler
0xffffc70336566980 : 0xfffff8035ad239dc : "nt!Ports (nt+0x5239dc)"
0xffffc70336566990 : 0xfffff8035a9cdf95 : nt!KiSystemServiceCopyEnd+0x25
0xffffc70336566998 : 0xfffff8035a800000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor (nt+0x0)"
0xffffc703365669a0 : 0xfffff8035ad239dc : "nt!Ports (nt+0x5239dc)"
0xffffc703365669c0 : 0xfffff8035a9cd940 : nt!KiSystemServiceHandler
0xffffc703365669f8 : 0xfffff8035a835580 : nt!ObFastReferenceObject
0xffffc70336566a00 : 0xfffff8037303debe : Npfs!NpCommonWrite+0x2be
0xffffc70336566a08 : 0xfffff8035a800000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor (nt+0x0)"
0xffffc70336566a10 : 0xfffff8035ad0e9f4 : "nt!Ports (nt+0x50e9f4)"
0xffffc70336566a18 : 0xfffff8035a800000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor (nt+0x0)"
0xffffc70336566a20 : 0xfffff8035ad3a7e8 : "nt!Ports (nt+0x53a7e8)"
0xffffc70336566a28 : 0xfffff80373030000 : "Npfs!NpCancelDataQueueIrp (Npfs+0x0)"
0xffffc70336566a30 : 0xfffff80373036348 : "Npfs!NpAliases (Npfs+0x6348)"
0xffffc70336566a38 : 0xfffff80373030000 : "Npfs!NpCancelDataQueueIrp (Npfs+0x0)"
0xffffc70336566a40 : 0xfffff80373036390 : "Npfs!NpAliases (Npfs+0x6390)"
0xffffc70336566a48 : 0xfffff80373030000 : "Npfs!NpCancelDataQueueIrp (Npfs+0x0)"
0xffffc70336566a50 : 0xfffff80373036354 : "Npfs!NpAliases (Npfs+0x6354)"
0xffffc70336566a58 : 0xfffff8035eb10000 : "FLTMGR!FltpDequeueThrottledWorkItem (FLTMGR+0x0)"
0xffffc70336566a60 : 0xfffff8035eb3c4d4 : "FLTMGR!FltpVerifierCodeSectionHandle (FLTMGR+0x2c4d4)"
0xffffc70336566a68 : 0xfffff8035eb10000 : "FLTMGR!FltpDequeueThrottledWorkItem (FLTMGR+0x0)"
0xffffc70336566a70 : 0xfffff8035eb3df50 : "FLTMGR!FltpVerifierCodeSectionHandle (FLTMGR+0x2df50)"
0xffffc70336566a78 : 0xfffff8035a800000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor (nt+0x0)"
0xffffc70336566a80 : 0xfffff8035ad3e610 : "nt!Ports (nt+0x53e610)"
0xffffc70336566a88 : 0xfffff8035a800000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor (nt+0x0)"
0xffffc70336566a90 : 0xfffff8035ad239dc : "nt!Ports (nt+0x5239dc)"
0xffffc70336566ac8 : 0xfffff8035a835591 : nt!ObFastReferenceObject+0x11
0xffffc70336566ad8 : 0xfffff8035a8cf076 : nt!KdTrap+0x22
0xffffc70336566b18 : 0xfffff8035a8cecfe : nt!KiDispatchException+0x16e
0xffffc70336566c18 : 0xfffff8035add0d40 : nt!SeCreateClientSecurity
0xffffc70336566c48 : 0xfffff8035a835590 : nt!ObFastReferenceObject+0x10
0xffffc70336566c98 : 0xfffff8035a9c326f : nt!KiIpiInterrupt+0x34f
0xffffc70336566cb8 : 0xfffff8035a7602cb : hal!HalPerformEndOfInterrupt+0x1b
0xffffc70336566cd0 : 0xfffff8035ad8c400 : nt!KiInitialThread
0xffffc70336566ce8 : 0xfffff8035a9be444 : nt!KiInterruptDispatch+0xc4
0xffffc70336566e38 : 0xfffff8035a9c3a1f : nt!SwapContext+0x1af
0xffffc70336566e78 : 0xfffff8035a9c3596 : nt!KiSwapContext+0x76
0xffffc70336566ea8 : 0xfffff8035a87962f : nt!SepMandatoryIntegrityCheck+0x2df
0xffffc70336566f28 : 0xfffff8035a83d365 : nt!KiCancelTimer+0x155
0xffffc70336566f78 : 0x3333333333333333 : !da "33333333"
0xffffc70336566fa8 : 0xfffff8035a8ce5f4 : nt!RtlGetExtendedContextLength2+0x3c
0xffffc70336566fb8 : 0xfffff8035a83b96b : nt!KiSwapThread+0x57b
0xffffc70336566fe8 : 0xfffff8035a8ce4ed : nt!RtlGetExtendedContextLength+0x2d
0xffffc70336566ff8 : 0xfffff8035a8ed70d : nt!RtlpHpLfhSubsegmentFreeBlock+0x31d
0xffffc703365671c8 : 0xfffff8035a9ce69d : nt!KiExceptionDispatch+0x11d
0xffffc703365672a0 : 0xfffff8035a800000 : "nt!SeConvertSecurityDescriptorToStringSecurityDescriptor (nt+0x0)"
0xffffc703365672a8 : 0xfffff8035a833196 : nt!RtlpHpLfhSlotAllocate+0x126
0xffffc70336567318 : 0xfffff8035a835590 : nt!ObFastReferenceObject+0x10
0xffffc703365673a8 : 0xfffff8035a9ca87f : nt!KiPageFault+0x43f
0xffffc703365673b0 : 0x0000003400000000 : Trap @ ffffc703365673b0
0xffffc70336567408 : 0xfffff8035add0d40 : nt!SeCreateClientSecurity
0xffffc70336567518 : 0xfffff8035a835590 : nt!ObFastReferenceObject+0x10
0xffffc70336567548 : 0xfffff8035ab6a06d : nt!ExAllocatePoolWithTag+0x5d
0xffffc70336567578 : 0xfffff8035add0dd1 : nt!SeCreateClientSecurity+0x91
0xffffc70336567598 : 0xfffff8035a829a20 : nt!ExAllocatePoolWithQuotaTag+0x60
0xffffc70336567618 : 0xfffff8037303d8a7 : Npfs!NpAddDataQueueEntry+0x1e7
0xffffc70336567688 : 0xfffff8037303de19 : Npfs!NpCommonWrite+0x219
0xffffc70336567718 : 0xfffff8037303daa4 : Npfs!NpFastWrite+0x74
0xffffc70336567778 : 0xfffff8035eb15f78 : FLTMGR!FltpPerformFastIoCall+0x198
0xffffc703365677d8 : 0xfffff8035eb4c64c : FLTMGR!FltpFastIoWrite+0x1dc
0xffffc70336567878 : 0xfffff8035eb4c470 : FLTMGR!FltpFastIoWrite
0xffffc70336567888 : 0xfffff8035ae43308 : nt!NtWriteFile+0x458
0xffffc70336567940 : 0xfffff8035eb4c470 : FLTMGR!FltpFastIoWrite
0xffffc70336567988 : 0xfffff8035a9cdf95 : nt!KiSystemServiceCopyEnd+0x25
0xffffc703365679f8 : 0xfffff8035a9cdf95 : nt!KiSystemServiceCopyEnd+0x25
0xffffc70336567a00 : 0xffff810e99384080 : Trap @ ffffc70336567a00Based on these results I would suggest you update the graphics driver as well. The best way to do this is by uninstalling the nVidia driver with a utility called Display Driver Uninstaller DDU and then reinstalling just the graphics driver and PhysX driver required for gaming.
Hope this helps.
That is a Machine Check Exception - definite unknown hardware failure.
Machine-check exception - Wikipedia
stormflora
Well-known member
- Jun 26, 2019
- 54
Hi philc43, thank you for your reply!
1) I haven't experienced any WHEA BSOD since then, so it may have been a one-off, as you say. I will post a dump if I experience it again.
2) So the graphics driver might be at fault again? That's disappointing to hear; I thought I already dealt with that issue with the graphics driver update a while back, which seems to have completely stopped the IRQL BSODs. (I haven't experienced the IRQL BSOD for several months now, just these random one-offs.)
3) So the graphics driver might still be experiencing trouble then. I already updated it once before (as mentioned above), but sure, I will try updating it once again. I will still keep this current driver on hand in case the newer driver is less stable.
Again, thank you very much for your assistance. I'm glad to see that the issue is being narrowed down. It means that the rest of my PC's probably fine. I will update my graphics driver now, and drop by again if I get any other BSODs later on.
I am curious though: Is there a chance that it's just my GPU turning faulty and is in need of replacement, or is it strictly the graphics drivers and not the card itself?
1) I haven't experienced any WHEA BSOD since then, so it may have been a one-off, as you say. I will post a dump if I experience it again.
2) So the graphics driver might be at fault again? That's disappointing to hear; I thought I already dealt with that issue with the graphics driver update a while back, which seems to have completely stopped the IRQL BSODs. (I haven't experienced the IRQL BSOD for several months now, just these random one-offs.)
3) So the graphics driver might still be experiencing trouble then. I already updated it once before (as mentioned above), but sure, I will try updating it once again. I will still keep this current driver on hand in case the newer driver is less stable.
Again, thank you very much for your assistance. I'm glad to see that the issue is being narrowed down. It means that the rest of my PC's probably fine. I will update my graphics driver now, and drop by again if I get any other BSODs later on.
I am curious though: Is there a chance that it's just my GPU turning faulty and is in need of replacement, or is it strictly the graphics drivers and not the card itself?
Last edited:
stormflora
Well-known member
- Jun 26, 2019
- 54
Hi, just popping in again to report another BSOD I encountered just now during gaming, specifically while loading a save file. I just recalled that several of my past BSODs had to do with loading as well, in a few games. I'm not sure if that's just a coincidence though. I have attached the minidump file. Thank you all very much
WhoCrashed reported that this BSOD was caused by hardware.sys, which really isn't that helpful. Can somebody identify whether it is yet again my graphics driver?
WhoCrashed reported that this BSOD was caused by hardware.sys, which really isn't that helpful. Can somebody identify whether it is yet again my graphics driver?
Hi. . .
Could you please re-zip the dump, upload it and attach to your next post?
I am getting error messages when trying to open the zip file and therefore cannot process it.
Thank you.
Regards. . .
jcgriff2
Could you please re-zip the dump, upload it and attach to your next post?
I am getting error messages when trying to open the zip file and therefore cannot process it.
Thank you.
Regards. . .
jcgriff2
There is no sign of this latest BSOD having anything to do with the graphics card, but it may well be hardware related.
I'd try updating the BIOS for the motherboard first, even though you are against doing this. The latest version is 1105 and may address these issues.
I'd try updating the BIOS for the motherboard first, even though you are against doing this. The latest version is 1105 and may address these issues.
Code:
Version 1105
2019/07/018.32 MBytes
PRIME Z390-A BIOs 1105
Improved DRAM compatibility.
Improved system performance.
Updated ME version to Ver.12.0.39
Updated microcode for Security.I managed to get the file opened by using 7-Zip.
stormflora
Well-known member
- Jun 26, 2019
- 54
I see, very well. I will do so now; hopefully nothing goes drastically wrong like it did last time. I will be back if anything comes up.
From Post #1 -
Just curious. . . Did a BSOD Analyst on a forum actually tell you that your BSOD was caused by ntkrnlmp.exe?
I ask because if so, he did you a real disservice as ntkrnlmp.exe is the Windows kernel and often shows up (along with ntoskrnl.exe and 2 others) as the probable cause because the real cause can't be determined. The real cause could be a driver, but it also could be unknown hardware failure.
Basically, ntkrnlmp.exe shows up as the probable cause as a default of sorts. It can never be the actual, sole cause of a BSOD.
This graphic may help with the different kernel names.
Here are the 4 Kernel image filenames -
https://en.wikipedia.org/wiki/Ntkrnlmp.exe
ntoskrnl.exe - Wikipedia
Regards. . .
jcgriff2
.
Just curious. . . Did a BSOD Analyst on a forum actually tell you that your BSOD was caused by ntkrnlmp.exe?
I ask because if so, he did you a real disservice as ntkrnlmp.exe is the Windows kernel and often shows up (along with ntoskrnl.exe and 2 others) as the probable cause because the real cause can't be determined. The real cause could be a driver, but it also could be unknown hardware failure.
Basically, ntkrnlmp.exe shows up as the probable cause as a default of sorts. It can never be the actual, sole cause of a BSOD.
This graphic may help with the different kernel names.
Here are the 4 Kernel image filenames -
| Filename | Supports SMP | Supports PAE |
|---|---|---|
| ntoskrnl.exe | No | No |
| ntkrnlmp.exe | Yes | No |
| ntkrnlpa.exe | No | Yes |
| ntkrpamp.exe | Yes | Yes |
https://en.wikipedia.org/wiki/Ntkrnlmp.exe
ntoskrnl.exe - Wikipedia
Regards. . .
jcgriff2
.
stormflora
Well-known member
- Jun 26, 2019
- 54
I initially asked on the Microsoft Support forums, and it was what somebody told me back then. Over the months, I have noticed (on BlueScreenView) that as you say, that particular file is not the culprit itself. It's more like an interface of sorts, which is linked to another culprit. I continued asking for help, but as you'd expect, the people on Microsoft Support aren't the most reliable people to count on, so ultimately I sought help elsewhere. That's how I stumbled upon this forum. And I'm glad that this forum has been very helpful so far with all of the expert help I'm receiving.
Over the months, I've been updating things based on advice I've received (mostly from here) and my own research on the BSODs (with BlueScreenView and WhoCrashed). And as a result, the BSODs I've been experiencing have been changing (positively, I think). Initially, it was always the IRQL BSOD, but after a (successfully stable) graphics driver update and an OS update to W10 Build 1903, I haven't experienced that one since. I have experienced other BSODs instead, most of which have been found to still be graphics related, but not always. The BSODs themselves almost always occur during gaming though; that's the one pattern I've noticed.
On a side note, the BIOS update went through successfully. I will continue to monitor and submit any minidumps if I encounter BSODs from this point on.
Well, I am very glad that you stumbled on to Sysnative however you accomplished it! 
Please always send ALL dumps to us even if you have run them through BlueScreenView and/or WhoCrashed and determined that there appears to be nothing special about them as we exclusively use Microsoft's Windbg kernel memory dump debugger which does a much more thorough analysis than BlueScreenView or WhoCrashed does. Plus, Windbg gives us the option to run some additional commands against the mini-dump.
John
p.s. Glad that the BIOS update went well.
Please always send ALL dumps to us even if you have run them through BlueScreenView and/or WhoCrashed and determined that there appears to be nothing special about them as we exclusively use Microsoft's Windbg kernel memory dump debugger which does a much more thorough analysis than BlueScreenView or WhoCrashed does. Plus, Windbg gives us the option to run some additional commands against the mini-dump.
John
p.s. Glad that the BIOS update went well.
stormflora
Well-known member
- Jun 26, 2019
- 54
@jcgriff2 After the Microsoft forums failed me, I just searched around Google and eventually found this forum. It didn't take me long to realize that this was the place to be for professional BSOD analysis and assistance. I am very glad I found this place, and very thankful.
For the most part, I have indeed been submitting all of the dumps for the BSODs I experience, here. BSV and WC offer an overall picture for what might be the problem, but I am aware that they're simply rough guidelines. I want to get this problem fixed for good, and I need all the help I can get.
Again, thank you very much, and I will be back again with a dump file if I experience another BSOD.
For the most part, I have indeed been submitting all of the dumps for the BSODs I experience, here. BSV and WC offer an overall picture for what might be the problem, but I am aware that they're simply rough guidelines. I want to get this problem fixed for good, and I need all the help I can get.
Again, thank you very much, and I will be back again with a dump file if I experience another BSOD.
stormflora
Well-known member
- Jun 26, 2019
- 54
Okay, so I tried gaming again just now for about 2-3 hours or so, my CPU cooler fan suddenly ramped up and I experienced a pretty severe BSOD.
First, my PC hit a BSOD with the error "UNEXPECTED_KERNEL_MODE_TRAP", and then restarted.
Then on the login screen, just as I was about to type in my password, it immediately gave another BSOD, "SYSTEM_SERVICE_EXCEPTION" and restarted again.
Then after it restarted that time, after I logged in, about five seconds later, I got hit with the dreaded "IRQL_NOT_LESS_OR_EQUAL" BSOD.
That's three BSODs in a row!! This is actually pretty serious, and I'm genuinely concerned if it's because of a bad BIOS update.
First, my PC hit a BSOD with the error "UNEXPECTED_KERNEL_MODE_TRAP", and then restarted.
Then on the login screen, just as I was about to type in my password, it immediately gave another BSOD, "SYSTEM_SERVICE_EXCEPTION" and restarted again.
Then after it restarted that time, after I logged in, about five seconds later, I got hit with the dreaded "IRQL_NOT_LESS_OR_EQUAL" BSOD.
That's three BSODs in a row!! This is actually pretty serious, and I'm genuinely concerned if it's because of a bad BIOS update.
Has Sysnative Forums helped you? Please consider donating to help us support the site!