Windows 10: BSOD has a different stop code whenever I do a task.

Page 1 of 3 123 LastLast
  1.    03 Dec 2016 #1

    BSOD has a different stop code whenever I do a task.


    I recently bought a 1070 card 4 months ago and installed it. A few weeks later, prior to the new installation of the GPU, windows did an update and few hours prior to that update, I got a BSoD. Afterwords, I soon kept getting random BSoD from either playing a game, doing animations, even watching videos online. Every time I try to figure out how to fix the stop code error, I keep getting a different one. I was hoping someone in the community can help me diagnose which driver is the cause to this.
    BSOD has a different stop code whenever I do a task. Attached Files
      My ComputerSystem Spec

  2.    03 Dec 2016 #2

    In all of the last 5 dumpfiles are references to memory corruption, memory mangement, hardware etc.

    Start with testing your memory.
    Memory Test.
    Please start with diagnosing the system RAM first. You can use the free tool "Memtest86+" to stress test the RAM.

    How to run "Memtest"
    MemTest86+ - Test RAM - Windows 10 Forums
    Make sure you are using the latest version 5.01 - Memtest86+ - Advanced Memory Diagnostic Tool

    You can stop the test even if a single error is found during the test. Otherwise continue the test for 8-10 passes and post a screenshot with next reply. 8 passes is the recommended bare minimum but more passes will give better result.

    If it seems you have no faulty memory, with your next reply please use the posting instruction and upload the Dm.zip.
      My ComputerSystem Spec

  3.    05 Dec 2016 #3

    I managed to run Mem86 on the both my RAM and the slots and had no errors. Unfortunately, the USB could not save the results for some reason. Here are the dump files.
    BSOD has a different stop code whenever I do a task. Attached Files
    Last edited by Darkula; 05 Dec 2016 at 20:56.
      My ComputerSystem Spec

  4.    06 Dec 2016 #4

    You are using razer devices with drivers from 2015, there are mentioning of BSOD on systems with Razer.
    Try updating the drivers or remove/uninstall these devices and see if this stops the BSOD.

    Also you have the ScpVBus Sun May 05 23:31:26 2013 driver, also known for BSODing.
    Driver Description: Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver
    Driver Update Site: XInput Wrapper for DS3 and Play.com USB Dual DS2 Controller

    And a few older driver belonging to some of the Asus Utilities(aka Asus Bloatware) if you use some of these, try updating too the latest versions or uninstall.
      My ComputerSystem Spec

  5.    10 Dec 2016 #5

    I've uninstalled the drivers as you suggested, but the BSoD happened again, this time with the stop code: ATTEMPTED WRITE TO READ-ONLY MEMORY. I've also noticed that the mouse seems to take a long time to respond to a different program whenever I click on something, as well as go forward whenever I backspace on a website or folder.
    BSOD has a different stop code whenever I do a task. Attached Files
      My ComputerSystem Spec

  6.    10 Dec 2016 #6

    The last dumpfiles is not really conclusive
    Code:
       BugCheck BE, {ffff9500395d2208, 8000000001100121, ffffa98016ff0890, a}
    
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : memory_corruption
    Usual causes:* Device driver, Memory

    The razar devices have still drivers from 2015.
    Do you have a other non razer mouse/keyboard to use and test if have your system has a normal respons time.

    Maybe driver verifier can find the problematic driver.
    You can enable "Driver Verifier" according to instructions from the below link.
    Driver Verifier - Enable and Disable in Windows 10 - Windows 10 Tutorials
    "Verifier" is a Microsoft's own tool to stress test third party drivers and find the buggy one. If it detects a violation, a blue screen will be created immediately and the dump will give us the name of offending driver straight forward. After enabling "Verifier" , system will be a bit slow and laggy during to the background verification process. After you got two or more blue screens, please upload the new crash dumps and we will know whether the issue is caused by third party drivers or low level hardware (a verifier enabled dump which blames Windows system files is a clear confirmation of hardware problem).
    "Verifier" should be only used to monitor third party drivers. Selecting Microsoft system drivers is totally unnecessary and doing so may make the system non bootable.
    Additional:
    First read instructions from the below link and set "Windows" to write "Small Memory dumps".
    SetMiniDump
      My ComputerSystem Spec

  7.    11 Dec 2016 #7

    Here are the new dumps after having driver verifier on. Hope I did this correctly.
    BSOD has a different stop code whenever I do a task. Attached Files
      My ComputerSystem Spec

  8.    11 Dec 2016 #8

    Unfortunaly the last dumpfiles are not driver verifier enabled dumpfiles but normal dumpfiles.

    The last one is
    Code:
     BugCheck 4E, {99, 5bda77, 2, 60005f0005f2cf6}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4bc5e )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PFN_LIST_CORRUPT (4e)
    Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc).  If a kernel debugger is
    available get the stack trace.
    Arguments:
    Arg1: 0000000000000099, A PTE or PFN is corrupt
    Arg2: 00000000005bda77, page frame number
    Arg3: 0000000000000002, current page state
    Arg4: 060005f0005f2cf6, 0
    Has your SSD the latest firmware and/or drivers installed.

    Please update these drivers
    asstahci64 Thu Nov 12 08:33:00 2015
    Driver Description: Asmedia 106x SATA Host Controller Driver
    Driver Update Site: ASMedia Technology Inc. 祥碩科技
    or -
    http://alldrivers.****.net/news/asmedia_drivers/1-0-17

    SamsungRapidDiskFltr Fri Sep 04 08:36:11 2015 (55E93BDB)
    SamsungRapidFSFltr Fri Sep 04 08:36:14 2015
    Driver Description: Samsung RAPID Mode Disk Filter driver
    Driver Update Site: Download Center: Download Software, Firmware, Drivers & Manuals | Samsung

    First look on the supportpage of your mobo.

    Next steps
    Test your harddrives
    Run driververifier again.
      My ComputerSystem Spec

  9.    14 Dec 2016 #9

    Sorry for the late reply, work has been busy. Anyways, I ran the driver verifier and came to a stop code called driver verifier IOManager violation. Did I do it incorrectly? Also, I downloaded the latest SATA Host driver and have the latest firmware on my SSD, although the SSD does not have any driver updates to download.
    BSOD has a different stop code whenever I do a task. Attached Files
      My ComputerSystem Spec

  10.    14 Dec 2016 #10

    The driver verifier dump is.
    Code:
       BugCheck C9, {21f, fffff8076de7b174, ffffe60d58094dc0, 0}
    
    Unable to load image ScpVBus.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ScpVBus.sys
    *** ERROR: Module load completed but symbols could not be loaded for ScpVBus.sys
    Probably caused by : ScpVBus.sys ( ScpVBus+b174 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    The IO manager has caught a misbehaving driver.
    Arguments:
    Arg1: 000000000000021f, A driver has not filled out a dispatch routine for a required IRP major function.
    Arg2: fffff8076de7b174, The address in the driver's code where the error was detected.
    Arg3: ffffe60d58094dc0, IRP address.
    Arg4: 0000000000000000
    Timestamp: Sun May 05 23:31:26 2013 (5186CFAE)

    I pointed already in post 4 to this driver
    Also you have the ScpVBus Sun May 05 23:31:26 2013 driver, also known for BSODing.
    Driver Description: Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver
    Driver Update Site: XInput Wrapper for DS3 and Play.com USB Dual DS2 Controller
    If there are no new windows 10 compatible driver remove it.
      My ComputerSystem Spec


 
Page 1 of 3 123 LastLast

Related Threads
Hi all. Starting from yesterday (26Nov), my win10 PC jumped to the blue screen whenever idle for some time. (Not sure if it's relevant though but it never happened when I was actually using it) Stop code is SYSTEM THREAD EXCEPTION NOT HANDLED...
BSOD has popped up a total of 3 times in 2 days, each time was while the laptop was being moved to a different location while browsing in chrome and no other applications running. Today, it showed up twice in a row in the same situation, both only...
Hello guys, My laptop is fairly new only like 3-4 months. last week it started giving me blue screens. started happening more often. Failed:tcpip.sys Stop code:driver_irql_not_less_or_equal. then I did a "reset this pc" with keeping data. it was...
BSOD - Stop Code: DRIVER_POWER_STATE_FAILURE in BSOD Crashes and Debugging
I don't know where to begin. Laptop was working fine again for last week or so after last BSOD issue that Axe0 helpled me with. I re-installed the WAN Wireless driver & Intel Chipset drivers that i was instructed to do and seemed to be working...
Hi there. I've had a number of BSOD in the last week or so. It tends to happen when I've just clicked a link, but it looks like it's happening in the middle of the night as well. Help? Please let me know if there's more information I can provide....
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 12:59.
Find Us