Windows 10: 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.

:)

 

[BSOD] SYSTEM_SERVICE_EXCEPTION 00000000`c0000096 ntoskrnl.exe

Hi, I get random BSOD usually saying SYSTEM_SERVICE_EXCEPTION and in bluescreenviewer it says that ntoskrnl.exe is the problem. I get this BSOD almost everyday. Can anyone help me I can attach the dump file if possible.

Dropbox - ntoskrnl.exeSYSTEM_SERVICE_EXCEPTION dump.txt

 

Memory Management BSOD almost everyday

Josh

Please upload no more than three copies
of your dump files that were created during the last 14 days as shared files to your OneDrive with a link here.




Dump files are usually found at c:\windows\minidump. You may need to change your settings in Windows to be able to see the files. To show hidden files select the keyboard shortcut
Win+S, type File Explorer Options in the Search box and click Folder Options in the drop down menu. Select View, Advanced Settings and verify that the box before "Show hidden files and folders" is checked and
"Hide protected operating system files" is unchecked. You may need to scroll down to see the second item. You should also make certain that the box before "Hide extensions for known file types" is not checked.



What is your computer make and model? If not a branded computer what is your motherboard make and model?



Please download and run Driver View and upload a copy of the report it produces to your OneDrive. To get a report on all drivers select Edit, Select All followed by File, Save Selected Items. Text file format please, HTML files are less easy
to work with.

DriverView: Loaded Windows Drivers List



Please provide a copy of your System Information file. To access your System Information file select the keyboard shortcut
Win+R, type msinfo32 and press the ENTER
key. Select File, Export and give the file a name noting where it is located.
Files in the txt file format are preferred. Do not place the cursor within the body of the report before exporting the file. The system creates a new System Information file each time system information
is accessed. You need to allow a minute or two for the file to be fully populated before exporting a copy. Please upload the file to your OneDrive, share with everyone and post a link here.



For help with OneDrive see paragraph 9.3:

gerrys template

 

Start with uninstalling MSI afterburner.

 

Ok, I uninstalled it, but I had it installed for a long time with no problems.

 

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.

 

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

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

Code: ******************************************************************************* * * * 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 * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 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. Arguments: 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 0000000000000f38 CURRENT_IRQL: 8 FAULTING_IP: nvlddmkm+65b1 fffff80a`091665b1 488b88380f0000 mov rcx,qword ptr [rax+0F38h] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: AV PROCESS_NAME: System ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre DPC_STACK_BASE: FFFFF8014AD54FB0 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 nvlddmkm+0x65b1: fffff80a`091665b1 488b88380f0000 mov rcx,qword ptr [rax+0F38h] ds:00000000`00000f38=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80148fe4de9 to fffff80148fd9cc0 STACK_TEXT: 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 STACK_COMMAND: kb FOLLOWUP_IP: nvlddmkm+65b1 fffff80a`091665b1 488b88380f0000 mov rcx,qword ptr [rax+0F38h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nvlddmkm+65b1 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 57209fba FAILURE_BUCKET_ID: AV_nvlddmkm+65b1 BUCKET_ID: AV_nvlddmkm+65b1 ANALYSIS_SOURCE: KM 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[/quote] This is the Nvidia driver for your GPU.
It could be corrupted, uninstall with DDU and reinstall

The dumpfile from may 7 blames.
Code: ******************************************************************************* * * * 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.[/quote] This is the driver for your xboxcontroller but seems also the latest version (march 2016)

The dumpfile from may 6 blames

Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c000001d, fffff802803ce736, ffff9c014488be70, 0} Probably caused by : ntkrnlmp.exe ( nt!NtQueryFullAttributesFile+1e6 ) BUGCHECK_STR: 0x3B PROCESS_NAME: MSIDDRService.[/quote] 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.

 

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.

 

As posted in my reply " These older drivers are on your system.( based on dumpfile of may 8)", because there are no newer dumpfiles.

 

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.

 

Hi ViPMorphiik,

Welcome to the 10forums *Smile

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.

 

Please note that you're running the Technical Preview version, the problem of the crashes may very well be due to a bug in the TP version although that may be difficult to say for sure.

Is Speedfan updated & the drivers from Logitech as @lifetec asked? If it is please remove Speedfan to remove the outdated drivers.
Please download the audio drivers of Realtek from MSI
Support For Z97M GAMING | MSI Global | Motherboard - The world leader in motherboard design 64

Please remove / disable items from the startup in taskmanager
These programs could interfere with the boot process giving you trouble and increase the boot time.



Warning Programs that claim to update your drivers install either the wrong or corrupted drivers.
If you have installed any driver with Driver Booster 3, please remove them as it may cause trouble.
An easy way to get rid of the installed drivers is using a restore point prior the use of this program.