Windows 10: Random BSOD almost everyday

Page 1 of 2 12 LastLast
  1.    08 May 2016 #1

    Random BSOD almost everyday

    Hi, almost for a month now I'm getting random BSOD once a day with no matter what I'm doing (mostly when I watch video or play something). It often happens when I play LOL, but I can still play big games like Witcher 3 or Overwatch and nothing will crash... I had my GPU slightly overclocked for half of a year, but few days ago it started crashing to a grey screen (OC related). So I got rid of overclock and crashes with grey screen dissapeard, but BSOD still happens. I don't know what can cause this BSOD. I didn't do any hardware update.
      My ComputerSystem Spec

  2.    08 May 2016 #2

    Start with uninstalling MSI afterburner.
      My ComputerSystem Spec

  3.    08 May 2016 #3

    lifetec said: View Post
    Start with uninstalling MSI afterburner.
    Ok, I uninstalled it, but I had it installed for a long time with no problems.
      My ComputerSystem Spec

  4.    10 May 2016 #4

    Yeah after about one day of working normally another BSOD appeard. But now I have no log because when BSOD appeard PC immidiately shutted down without time to generate a log. Anyway I updated all drivers and uninstalled some programs so I post a new package of files. I hope someone can help me here.
      My ComputerSystem Spec

  5.    11 May 2016 #5

    It is difficult to analyze without new dumpfiles.
    And you also on a windows insider preview version, do not known what influence this has on your system and BSOD.

    Your latest windows error report form 9 may 2015 is
    Windows Error Reporting:
    +++ WER0 +++:
    Chybný blok , typ 0

    Název události: AppHangB1

    Reakce: Není k dispozici.

    ID souboru CAB: 0

    Podpis problému:

    P1: SBRecon.exe


    P3: 52a1b0e9

    P4: 67c6

    P5: 134217984
    SBrecon.exe is part of soundblaster control panel is this program compatible with windows 10 , have you up to date drivers etc, ?
    Look into this.

    The latest dumpfile of may 8 blames

    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck D1, {f38, 8, 0, fffff80a091665b1}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+65b1 )
    Followup: MachineOwner
    0: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arg1: 0000000000000f38, memory referenced
    Arg2: 0000000000000008, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff80a091665b1, address which referenced memory
    Debugging Details:
    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
    fffff80a`091665b1 488b88380f0000  mov     rcx,qword ptr [rax+0F38h]
    PROCESS_NAME:  System
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre
    TRAP_FRAME:  fffff8014ad4be80 -- (.trap 0xfffff8014ad4be80)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80a091665b1 rsp=fffff8014ad4c010 rbp=fffff8014ad4c110
     r8=0000000000000003  r9=0000000000001e00 r10=fffff80a097d20a8
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    fffff80a`091665b1 488b88380f0000  mov     rcx,qword ptr [rax+0F38h] ds:00000000`00000f38=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80148fe4de9 to fffff80148fd9cc0
    fffff801`4ad4bd38 fffff801`48fe4de9 : 00000000`0000000a 00000000`00000f38 00000000`00000008 00000000`00000000 : nt!KeBugCheckEx
    fffff801`4ad4bd40 fffff801`48fe3407 : ffffe5fd`d1409000 00000000`144c82ce ffff8083`8bcb0410 00000000`00000001 : nt!KiBugCheckDispatch+0x69
    fffff801`4ad4be80 fffff80a`091665b1 : fffff801`4ad4c3c8 fffff801`4ad4c110 fffff801`4ad4c370 00000000`00000000 : nt!KiPageFault+0x247
    fffff801`4ad4c010 fffff801`4ad4c3c8 : fffff801`4ad4c110 fffff801`4ad4c370 00000000`00000000 00000000`203a0000 : nvlddmkm+0x65b1
    fffff801`4ad4c018 fffff801`4ad4c110 : fffff801`4ad4c370 00000000`00000000 00000000`203a0000 00000000`0000bcfd : 0xfffff801`4ad4c3c8
    fffff801`4ad4c020 fffff801`4ad4c370 : 00000000`00000000 00000000`203a0000 00000000`0000bcfd ffff8083`85bba060 : 0xfffff801`4ad4c110
    fffff801`4ad4c028 00000000`00000000 : 00000000`203a0000 00000000`0000bcfd ffff8083`85bba060 fffff801`48fd6350 : 0xfffff801`4ad4c370
    fffff80a`091665b1 488b88380f0000  mov     rcx,qword ptr [rax+0F38h]
    SYMBOL_NAME:  nvlddmkm+65b1
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nvlddmkm
    IMAGE_NAME:  nvlddmkm.sys
    FAILURE_BUCKET_ID:  AV_nvlddmkm+65b1
    BUCKET_ID:  AV_nvlddmkm+65b1
    FAILURE_ID_HASH_STRING:  km:av_nvlddmkm+65b1
    FAILURE_ID_HASH:  {2d3fbf99-f052-d11d-4292-f1cc215b07f2}
    Followup: MachineOwner
    0: kd> lmvm nvlddmkm
    start             end                 module name
    fffff80a`09160000 fffff80a`09daa000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Wed Apr 27 13:17:14 2016 (57209FBA)
        CheckSum:         00C0E5A7
        ImageSize:        00C4A000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    This is the Nvidia driver for your GPU.
    It could be corrupted, uninstall with DDU and reinstall

    The dumpfile from may 7 blames.
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck D1, {c, 2, 1, fffff806f3269725}
    Probably caused by : xusb22.sys ( xusb22!PeriodicWorkManager::WorkItemCallback+65 
    5: kd> lmvm xusb22
    start             end                 module name
    fffff806`f3260000 fffff806`f327f000   xusb22     (pdb symbols)          c:\symbols\XUSB22.pdb\310FA8DA7B70418C938A8B63925E64FB1\XUSB22.pdb
        Loaded symbol image file: xusb22.sys
        Mapped memory image file: c:\symbols\xusb22.sys\56ECEC581f000\xusb22.sys
        Image path: \SystemRoot\System32\drivers\xusb22.sys
        Image name: xusb22.sys
        Timestamp:        Sat Mar 19 07:06:16 2016 (56ECEC58)
        CheckSum:         00019BB5
        ImageSize:        0001F000
        File version:     10.0.14295.1000
        Product version:  10.0.14295.1000
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.0 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     XUSB21
        OriginalFilename: XUSB21.sys
        ProductVersion:   10.0.14295.1000
        FileVersion:      10.0.14295.1000 (rs1_release.160318-1628)
        FileDescription:  Xbox 360 Common Controller for Windows Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    This is the driver for your xboxcontroller but seems also the latest version (march 2016)

    The dumpfile from may 6 blames

    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck 3B, {c000001d, fffff802803ce736, ffff9c014488be70, 0}
    Probably caused by : ntkrnlmp.exe ( nt!NtQueryFullAttributesFile+1e6 )
    The proces during in the dumpfile is the MSI command center utility.
    Did you also uninstall this program?

    These older drivers are on your system.( based on dumpfile of may 8)
    GPCIDrv64 Thu Jul 10 14:58:31 2008
    Driver Description: Gigabyte Easy boost related driver
    Driver Update Site: GIGABYTE - Support - Utility - Graphics Card

    I would uninstall this.

    MBfilt64 Fri Jul 31 05:40:32 2009
    Driver Description: Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver) - Was found in the latest Win8 version available from Realtek on 07Sep2013

    Driver Update Site: Realtek

    NTIOLib_X64 Mon Jan 06 07:15:54 2014 (52CA4A1A)
    fffff80a`0afd0000 fffff80a`0afd7000 NTIOLib_X64_fffff80a0afd0000 Fri Oct 26 03:46:44 2012 (5089EB84)
    fffff80a`0b020000 fffff80a`0b027000 NTIOLib_X64_fffff80a0b020000 Mon Mar 17 11:24:03 2014 (5326CD43)
    fffff80a`0b0f0000 fffff80a`0b0f7000 NTIOLib_X64_fffff80a0b0f0000 Tue Nov 20 09:11:26 2012 (50AB3B2E)
    fffff80a`0b100000 fffff80a`0b107000 NTIOLib_X64_fffff80a0b100000 Thu Oct 25 12:27:58 2012 (5089142E)

    Driver Description: MSI Afterburner driver (known BSOD issues with Windows) Also found to be a part of MSI Live Update 5, MSI Super Charger & MSI Smart Utilities.

    Recently (Nov 2014) there have been numerous instances of this driver in memory dumps. Analysis reveals that they are scattered throughout the filesystem by the installed MSI command utilities. For now I suggest uninstalling them all.

    Driver Update Site: Afterburner - MSI Gaming Series

    RTCore64 Fri Apr 24 09:01:47 2015
    Driver Description: RivaTuner/EVGA Precision/MSI Afterburner (known BSOD issues w/Win7)

    Driver Update Site: RivaTuner

    Also update your Logitech drivers Wingman etc. they are from 2010 and 2012
    Update speedfan to the latest version.

    Maybe this give some clues/ideas to stop the BSODs.
      My ComputerSystem Spec

  6.    11 May 2016 #6

    Ok so I reinstalled my GPU drivers, uninstalled all programs from MSI and Gigabyte (OC Guru 2) and updated realtek drivers. What is strange is I already uninstalled Afterburner and RivaTuner before, but diagnose files are still telling that I have it on my pc? Xbox controller driver I already updated before. So now I must just wait and hope that it won't crash. Anyway thanks for helping me.
      My ComputerSystem Spec

  7.    11 May 2016 #7

    What is strange is I already uninstalled Afterburner and RivaTuner before, but diagnose files are still telling that I have it on my pc
    As posted in my reply " These older drivers are on your system.( based on dumpfile of may 8)", because there are no newer dumpfiles.
      My ComputerSystem Spec

  8.    15 May 2016 #8

    I'm back, yey... After few days of normal working my PC decided to throw at me another BSOD with following message "Driver overran stack buffer". I was watching YT video at a time of crash. And I didn't install any new or previously uninstalled software. I'll attach newest dump.
      My ComputerSystem Spec

  9. axe0's Avatar
    Posts : 13,707
    Windows 10 Pro
       16 May 2016 #9

    Hi ViPMorphiik,

    Welcome to the 10forums :)

    Please upload a new zip generated by the DM Log Collector from the BSOD Posting Instructions in case of relevant data that may be missed.
      My ComputersSystem Spec

  10.    16 May 2016 #10

    Ok, here it is.
      My ComputerSystem Spec

Page 1 of 2 12 LastLast

Related Threads
BSOD at random times doing random things. in BSOD Crashes and Debugging
Hi, I am getting BSODs at random times, while doing different things each time. Been getting them for 5 days trying to narrow down what could be causing it. Searching lead me here. I did the posting instructions. Also did sfc/scannow 2 times that...
I have had to reinstall my wireless printers everyday for the last couple of weeks. I upgraded to Windows 10 in December of 2015. I'll get the message that no driver is installed and that they are not connected to the network. One is an HP...
Hi, i got this computer about 3~ Weeks ago, and have gotten random BSOD's after that. System Information Bellow Intel Core i5-6600K 3.5Ghz @ 3.5 GeForce GTX960 2gb GDDR5, Physx CUDA 1TB Harddisk 7200RPM 8Gb DDR4 2133Mhz Dual Channel, 2x4gb...
Hi, Over the past couple of days I have been having reasonably frequent BSODs. Some have not created a dump file. I cant pinpoint anything in particular but it seems to be pointing to a driver issue but never identifies the driver from what I can...
I made a mistake, I'm a beta tester since the old days, I asked on another forum ( OMG I was accused of not knowing anything because I called the preview beta and not Alpha ect... and even accused of not really beta testing MS OS in the past my...
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 19:33.
Find Us