Been BSODing five to ten times a month for over a year.

kemical

Windows Forum Admin
Staff member
Premium Supporter
Hmm... Well try removing the original and then re-installing. You never know, a fresh copy may just help?

Also to clear any system corruption you might have (you have been blue screening so it's possible some files have become a little fouled) run these scans:
File scans
Look for command prompt in the start menu, right click on it and choose 'run as administrator'.Type:
sfc /scannow
press enter and await results

In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).

If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.
 

Nes17

Member
Redownloaded the driver and ran the scan.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.228

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
It's fine anyway. If it's only this crashing, not frequently, I'm ok with that.

Thanks again.
 

nmsuk

Windows Forum Admin
Staff member
Premium Supporter
Utorrent is being blamed, are you running the latest network drivers.
 

Nes17

Member
I am running the latest network drivers, yeah.

But my utorrent is a really old version, it's version 2.2.1


Uninstalled it and downloaded a recent version of another program.
 
Last edited:

nmsuk

Windows Forum Admin
Staff member
Premium Supporter
I use qbittorent which after years of uttorrent isn't a bad replacement
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
Sorry bud I've been away building a new pc, let me install the debugger and i'll take a look see
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 139, {0, 0, 0, ffff9f8272b71db0}

Probably caused by : ntkrnlmp.exe ( nt!guard_icall_handler+1b )

Followup:     MachineOwner
---------
Hi,
although it's not exactly obvious what the direct cause is:

Code:
Cannot read Exception record @ 0000000000000000
However it does seem network related.

Code:
PROCESS_NAME:  chrome.exe
Please check for any unwanted extensions and/or that your running the latest version of your Chrome browser. Remove anything like Toolbars and the like.

bwcW10x64.sys Thu Sep 15 09:22:54 2016: Killer Bandwidth Control Filter Driver

The above is taken from your driver stack and shows your driver as being out of date. Please update using the driver found on your motherboard support page:
Support For Z97 GAMING 3 | Motherboard - The world leader in motherboard design | MSI Global


Your bios is also out of date:

BIOS_VERSION: V2.6

BIOS_DATE: 12/24/2014

If your not experience at flashing bios's then I'd say leave it or ask a friend/local PC shop.
Support For Z97 GAMING 3 | Motherboard - The world leader in motherboard design | MSI Global

Post any new dump files.
 

nmsuk

Windows Forum Admin
Staff member
Premium Supporter
Looks like the audio driver is responsible for the dmp from the 12th. PROCESS_NAME: audiodg.exe can you upgrade your sound drivers and let us know how it goes.
 

Nes17

Member
My soundcard already had the latest driver installed for it. I don't use onboard audio, but I just updated the driver for it.
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 0, 0, ffffb402f08518c0}

fffff801360dd388: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!ExpHeapBackedPoolEnabledState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+fdc )

Followup:     MachineOwner
Hi,
as mentioned above the process which failed related to audio and if you recently updated the driver then try rolling back to the previous version.

Your first dump file also mentioned a background process for Nvidia which relates to streaming to Shield devices. This is turned on by default but can be disabled (and also improves a performance slightly).
Disable NVIDIA Streamer Service and other NVIDIA processes - gHacks Tech News

Hopefully the issue is driver based although if the bsod should continue you can try running the driver verifier to see which driver is causing the problem but see how you go and please post any new dump files.
 

Nes17

Member
I haven't recently those drivers.

And shield was off. I don't recall ever turning it on. But I turned off the thing that lets you record your screen.
 

Nes17

Member
I mean I uploaded them now after you've asked me to, but not recently before your asking. It's not that I updated drivers then started getting BSODs, I updated the drivers after the BSODs, updated them today.
 
Top