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

Discus and support Almost Daily ntoskrnl.exe BSOD, Desperately Need Help... in Windows 10 BSOD Crashes and Debugging to solve the problem; As of 11/28/2017 KMS was still present. Discussion in 'Windows 10 BSOD Crashes and Debugging' started by michaelmuliadi, Nov 27, 2017.

  1. zbook New Member

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


    As of 11/28/2017 KMS was still present.
     
    zbook, Nov 28, 2017
    #16

  2. As soon as I restarted after running driver verifier, I got BSOD upon boot up, saying DRIVER VERIFIER IOMANAGER VIOLATION.
     
    michaelmuliadi, Nov 30, 2017
    #17
  3. philc43 Win User
    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.

    Code: 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[/quote] Culprit address:
    Code: 2: kd> u FFFFF8093D6AB174 ScpVBus+0xb174: fffff809`3d6ab174 ?? ??? ^ Memory access error in 'u FFFFF8093D6AB174'[/quote]
     
    philc43, Nov 30, 2017
    #18
  4. Almost Daily ntoskrnl.exe BSOD, Desperately Need Help...

    Phil, thank you so much for all your help *Smile

    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...
     
    michaelmuliadi, Apr 5, 2018
    #19
Thema:

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

Loading...
  1. Almost Daily ntoskrnl.exe BSOD, Desperately Need Help... - Similar Threads - Almost Daily ntoskrnl

  2. Need help with daily BSOD crashes

    in Windows 10 BSOD Crashes and Debugging
    Need help with daily BSOD crashes: I've been having daily BSOD crashes for a few weeks now. I reinstalled my computer a couple of days ago and it started happening again. Also, many of the crashes happen on their own when I'm not even using the computer. I've already tried the following: I replaced my old SSD...
  3. Random BSODs almost daily

    in Windows 10 Gaming
    Random BSODs almost daily: Hey, so randomly when I am gaming, watching YouTube and things like that I will randomly BSOD, with the error in the event viewer A fatal hardware error has occurred. A fatal hardware error has occurred.Reported by component: Processor CoreError Source: Machine Check...
  4. Random BSODs almost daily

    in Windows 10 Software and Apps
    Random BSODs almost daily: Hey, so randomly when I am gaming, watching YouTube and things like that I will randomly BSOD, with the error in the event viewer A fatal hardware error has occurred. A fatal hardware error has occurred.Reported by component: Processor CoreError Source: Machine Check...
  5. Almost daily BSoD appears

    in Windows 10 BSOD Crashes and Debugging
    Almost daily BSoD appears: Hello, I've attached a log file hoping someone would be kind enough to view it and help find a solution to this vexing problem of BSoD. Windows 21h1 Much obliged Thank You Ian 182241
  6. Desperately need help

    in Windows 10 Ask Insider
    Desperately need help: So I was updating some apps here and there on my desktop and when I went to reboot I got this error message thay said "reboot and select proper boot device or insert boot media in selected boot device and press a key". Now, I've been trying to access the bios but since I had...
  7. BSOD ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe: My computer has crashed a few times often when i play games. I bought more ram because i thought that it was the issue but it didn't help. It did work a few days but then the crashes came back. After that i fixed the BSOD´s by lowering the graphics and the resolution on the...
  8. BSOD PAGE_FAULT_IN_NONPAGED_AREA ntoskrnl - Need help

    in Windows 10 BSOD Crashes and Debugging
    BSOD PAGE_FAULT_IN_NONPAGED_AREA ntoskrnl - Need help: I posted below the dmp file that I opened via WinDbg (from MS Store). https://pastebin.com/Qfzxr8hQ https://answers.microsoft.com/en-us/windows/forum/all/bsod-pagefaultinnonpagedarea-ntoskrnl-need-help/c5234bdf-714d-4944-b5a9-6645b82cefb7
  9. BSOD ntoskrnl..exe+1b35e0

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe+1b35e0: Help. Getting 4-5 of these a day. Running latest Windows 10 Pro, Xibo signboard, Docker with Xibo server. Always the same 'Caused By Address'. Put in new memory, ran memory test, no errors, all drivers up to date. Change disk type to AHCA, made sure windows driver was...
  10. Getting BSOD with ntoskrnl, need help.

    in Windows 10 BSOD Crashes and Debugging
    Getting BSOD with ntoskrnl, need help.: *edit: updated BIOS to new version 1.3. Just came up on MSI website.* *edit: system information attached* I think this is the dumpfile on onedrive. This is from the latest 3. WhoCrashed analysis and link to minidump. April 14. This was probably caused by the...
Tags: