Windows 10: Almost Daily ntoskrnl.exe BSOD, Desperately Need Help... Solved

Page 2 of 2 FirstFirst 12
  1.    28 Nov 2017 #11

    Third Renewed File

    I've restarted my PC, then make a new log.

    Rules and regulations make everything more complicated huh...

    If you still find slightest trace of violations etc, better give up on this, I'll mark this as solved.
    Almost Daily ntoskrnl.exe BSOD, Desperately Need Help... Attached Files
      My ComputerSystem Spec

  2. philc43's Avatar
    Posts : 3,590
    64bit Win 10 Pro ver 1809 Build 17763.1 and W10 Insider Build 18252
       29 Nov 2017 #12

    Many thanks, it looks like everything is now sorted.

    I can see that you have been getting a lot of windows update failures. Please run the troubleshooter for windows update to see if it will fix this problem.

    Click image for larger version. 

Name:	2017-11-29.png 
Views:	1 
Size:	37.5 KB 
ID:	166025

    The bluescreen crash dump file does not reveal which driver is causing the problem - therefore you will need to run a program to try and force the drivers to crash until you find the one that is the problem. The details to do this are in the tutorial listed below. Please follow all the instructions carefully and make a system backup and system recovery disk before you do so because there is a risk you will not be able to get back to a working system.

    Almost Daily ntoskrnl.exe BSOD, Desperately Need Help... Diagnostic Test Almost Daily ntoskrnl.exe BSOD, Desperately Need Help...

    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please read and run driver verifier.

    If you suspect a driver is causing a problem but do not have a clear idea which one it is then Driver Verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or until you have a bluescreen, whichever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset driver verifier from within safe mode, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My ComputersSystem Spec

  3.    29 Nov 2017 #13

    Many thanks, Phil... I've ran Windows Update troubleshooting and it said some errors were fixed. Will try verifier very soon...

    Thanks for the help so far, will report back in.
      My ComputerSystem Spec

  4. Posts : 20,846
    windows 10 professional version 1607 build 14393.969 64 bit
       29 Nov 2017 #14

    As of 11/28/2017 KMS was still present.
      My ComputerSystem Spec

  5.    01 Dec 2017 #15

    Series of BSOD after Driver Verifier

    As soon as I restarted after running driver verifier, I got BSOD upon boot up, saying DRIVER VERIFIER IOMANAGER VIOLATION.
    Almost Daily ntoskrnl.exe BSOD, Desperately Need Help... Attached Files
      My ComputerSystem Spec

  6. philc43's Avatar
    Posts : 3,590
    64bit Win 10 Pro ver 1809 Build 17763.1 and W10 Insider Build 18252
       01 Dec 2017 #16

    OK, so the Driver Verifier has worked and identified a bad driver. It is the Scarlet Crush Productions Scp Dual Shock 3 Virtual Bus Driver (ScpVBus.sys Sun May 5 22:31:26 2013 (5186CFAE))

    See if you can update this from their website.

    Also the iastorA.sys driver was implicated, see if you can update this Intel Rapid Storage Technology driver using the Intel download centre.

    Start memory scan  : 0xffffdf8797107068 ($csp)
    End memory scan    : 0xffffdf8797108000 (Kernel Stack Base)
                   rsp : 0xffffdf8797107068 : 0xfffff8001e02d293 : nt!VerifierBugCheckIfAppropriate+0xdf
    0xffffdf8797107068 : 0xfffff8001e02d293 : nt!VerifierBugCheckIfAppropriate+0xdf
    *** WARNING: Unable to verify timestamp for ScpVBus.sys
    *** ERROR: Module load completed but symbols could not be loaded for ScpVBus.sys
    0xffffdf8797107098 : 0xfffff8001d9a2401 : nt!RtlStringVPrintfWorkerA+0xd
    0xffffdf87971070a8 : 0xfffff8001e03281f : nt!ViErrorFinishReport+0x117
    0xffffdf87971070c8 : 0xfffff8001e082a70 : nt!ViErrorDescriptions
    0xffffdf87971070e8 : 0xfffff8001e01a060 :  !da ""This driver has not filled out a dispatch routine for a required IRP.major funct...""
    0xffffdf8797107108 : 0xfffff8001daf5533 : nt!ViErrorReport1+0x63
    0xffffdf8797107140 : 0x41746972706c7543 :  !da ""CulpritAddress = FFFFF8093D6AB174, Irp = FFFFB908475ACC70..""
    0xffffdf8797107148 : 0x3d20737365726464 :  !da ""ddress = FFFFF8093D6AB174, Irp = FFFFB908475ACC70..""
    0xffffdf8797107150 : 0x3038464646464620 :  !da "" FFFFF8093D6AB174, Irp = FFFFB908475ACC70..""
    0xffffdf8797107158 : 0x3731424136443339 :  !da ""93D6AB174, Irp = FFFFB908475ACC70..""
    0xffffdf8797107160 : 0x3d20707249202c34 :  !da ""4, Irp = FFFFB908475ACC70..""
    0xffffdf8797107168 : 0x3039424646464620 :  !da "" FFFFB908475ACC70..""
    0xffffdf8797107170 : 0x3743434135373438 :  !da "8475ACC70.."
    0xffffdf8797107188 : 0xfffff8001d8a07cb : nt!KeQueryCurrentStackInformation+0x2b
    0xffffdf8797107198 : 0xfffff8001e03fd0b : nt!ViFilterDispatchGeneric+0xbb
    0xffffdf87971071a8 : 0xfffff8001e03dc72 : nt!VfWmiVerifyIrpStackDownward+0x62
    0xffffdf87971071b8 : 0xfffff8001d8a0784 : nt!RtlpGetStackLimits+0x14
    0xffffdf87971071d8 : 0xfffff8001e0322ba : nt!VfMajorVerifyIrpStackDownward+0x82
    0xffffdf87971071f8 : 0xfffff8001e02d062 : nt!IovpExamineIrpStackForwarding+0x8a
    0xffffdf8797107210 : 0xfffff8001e03fd0b : nt!ViFilterDispatchGeneric+0xbb
    0xffffdf8797107238 : 0xfffff8001e02c586 : nt!IovpCallDriver1+0x476
    0xffffdf8797107268 : 0xfffff8001e03fd0b : nt!ViFilterDispatchGeneric+0xbb
    0xffffdf87971072e8 : 0xfffff8001e02d610 : nt!VfBeforeCallDriver+0x13c
    0xffffdf8797107308 : 0xfffff8001e03fd0b : nt!ViFilterDispatchGeneric+0xbb
    0xffffdf8797107318 : 0xfffff8001e021d39 : nt!IovCallDriver+0x251
    0xffffdf8797107338 : 0xfffff8001e02c5fc : nt!IovpCallDriver1+0x4ec
    0xffffdf8797107398 : 0xfffff8001e03fd0b : nt!ViFilterDispatchGeneric+0xbb
    0xffffdf87971073d8 : 0xfffff8001d99fcfa : nt!IopfCallDriver+0x56
    0xffffdf8797107408 : 0xfffff8001e02da69 : nt!VfIrpSendSynchronousIrp+0x109
    0xffffdf8797107418 : 0xfffff8001e021d5d : nt!IovCallDriver+0x275
    0xffffdf8797107438 : 0xfffff8001e02db0d : nt!VfIrpWatermark+0x2d
    0xffffdf8797107498 : 0xfffff8001e02da69 : nt!VfIrpSendSynchronousIrp+0x109
    0xffffdf8797107508 : 0xfffff8001e03dbfa : nt!VfWmiTestStartedPdoStack+0x5a
    0xffffdf87971075a8 : 0xfffff8001e032198 : nt!VfMajorTestStartedPdoStack+0x58
    0xffffdf87971075d8 : 0xfffff8001d99e9e7 : nt!PpvUtilTestStartedPdoStack+0x17
    0xffffdf8797107608 : 0xfffff8001de0d13c : nt!PipProcessStartPhase3+0xb8
    0xffffdf8797107638 : 0xfffff8001db37b48 : nt!DEVPKEY_Device_HardwareConfigurationIndex
    0xffffdf8797107648 : 0xfffff8001dc07e18 : nt!PnpCurrentHardwareConfigurationIndex
    0xffffdf8797107690 : 0xffffe18e577dd0d0 : 0xfffff8001dc014b0 : nt!PiPnpRtlActiveOperations
    0xffffdf87971076a0 : 0xfffff8001de67c60 :  !du "{00000000-0000-0000-FFFF-FFFFFFFFFFFF}"
    0xffffdf87971076a8 : 0xfffff8001ddf76a6 : nt!PipProcessStartPhase2+0x56
    0xffffdf87971076e0 : 0xffffdf87971077f0 : 0xfffff8001db389f8 : nt!KMPnPEvt_SystemStartPnPEnum_Start
    0xffffdf87971076e8 : 0xfffff8001dcf7b2a : nt!PipProcessDevNodeTree+0x3d6
    0xffffdf87971077f0 : 0xfffff8001db389f8 : nt!KMPnPEvt_SystemStartPnPEnum_Start
    0xffffdf8797107808 : 0xfffff8001d8ce206 : nt!EtwWriteEx+0x186
    0xffffdf8797107830 : 0xfffff8001db389f8 : nt!KMPnPEvt_SystemStartPnPEnum_Start
    0xffffdf8797107918 : 0xfffff8001d993b81 : nt!PnpDiagnosticTrace+0x5d
    0xffffdf8797107920 : 0xfffff8001dc98900 : nt!PspHostSiloGlobals+0x3c0
    0xffffdf8797107938 : 0xfffff8001db389f8 : nt!KMPnPEvt_SystemStartPnPEnum_Start
    0xffffdf8797107968 : 0xfffff8001de63445 : nt!PiProcessStartSystemDevices+0x59
    0xffffdf87971079b8 : 0xfffff8001d99e7b4 : nt!PnpDeviceActionWorker+0x474
    0xffffdf87971079e8 : 0xfffff8001d8c31d4 : nt!KeRemovePriQueue+0x1e4
    Unable to load image \SystemRoot\System32\drivers\iaStorA.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for iaStorA.sys
    *** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
    0xffffdf8797107a00 : 0xfffff80936000100 : iaStorA+0x100
    0xffffdf8797107a38 : 0xfffff8001dc989c0 : nt!ExNode0
    0xffffdf8797107a50 : 0xfffff8001dc989c0 : nt!ExNode0
    0xffffdf8797107a70 : 0xfffff8001d99e340 : nt!PnpDeviceActionWorker
    0xffffdf8797107a78 : 0xfffff8001d8c2e05 : nt!ExpWorkerThread+0xf5
    0xffffdf8797107a90 : 0xfffff8001dc00980 : nt!PnpDeviceEnumerationWorkItem
    0xffffdf8797107ab8 : 0xffffb9084169e170 : 0xffffb9084169bdf0 : 0xfffff8001dc07e80 : nt!MiSystemPartition
    0xffffdf8797107b00 : 0xfffff8001d8c2d10 : nt!ExpWorkerThread
    0xffffdf8797107b08 : 0xfffff8001d8aef87 : nt!PspSystemThreadStartup+0x47
    0xffffdf8797107b10 : 0xfffff8001dc9a380 : nt!KiInitialThread
    0xffffdf8797107b50 : 0xfffff8001dc9a380 : nt!KiInitialThread
    0xffffdf8797107b58 : 0xfffff8001d9ef676 : nt!KiStartSystemThread+0x16
    0xffffdf8797107b70 : 0xfffff8001d8aef40 : nt!PspSystemThreadStartup
    Culprit address:
    2: kd> u FFFFF8093D6AB174
    fffff809`3d6ab174 ??              ???
                            ^ Memory access error in 'u FFFFF8093D6AB174'
      My ComputersSystem Spec

  7.    01 Dec 2017 #17

    Phil, thank you so much for all your help :)

    I uninstalled the SCP driver since I don't use controller much for gaming anymore, also I installed latest driver for Intel RST. Hopefully no more BSOD after implementing the actions...

    For now I'll mark this thread as solved, thanks a lot once again...
      My ComputerSystem Spec

Page 2 of 2 FirstFirst 12

Related Threads
Hi. I've researched and attempted as much as I could possibly try, and now have to ask for community assistance. I never had these BSODs until updating to Windows 10. My crash dump files show two regular culprits (majority are the first one): ...
i have done all that windows itself will allow in changing the size and ease of access to make it easier for me to find the cursor on the screen but that did very little to help. I am legally/half blind and have always used something like cursor...
Solved Daily BSOD in BSOD Crashes and Debugging
I had fairly frequent BSOD when running window 7 and never had a resolution in 7forum. Tested memory and stressed drivers. I switched to windows 10 and everything went well for quite a while. I now have very frequent BSOD and it seems to have...
SuperFetch and Prefetch are disabled. Memcheck gives no errors. The computer ran almost 24/7 for ~~10 months before the Win 10 upgrade, not a single BSOD. Since 10, I've gotten 15-20. I've followed all the steps in this article: Windows 10: How...
Daily BSOD in BSOD Crashes and Debugging
Almost daily BSOD after upgrade from Win 8.1 to Win 10. This is a different laptop than my other posts in this forum. ASUS 12 GB - see details in screenshot. Thanks!34300
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 21:59.
Find Us