New
#81
This crash might be hard to track down, because a list_entry has been corrupted. Again we need to determine of any driver is causing trouble
WarningPlease make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.
Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.
Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.
If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.
NoteYour system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
Yes I did although it was a little difficult.
The cause is again a driver from Killer Bandwidth control
Code:0: kd> lmvm bwcW10x64start end module name fffff801`05dc0000 fffff801`06120000 bwcW10x64 T (no symbols) Loaded symbol image file: bwcW10x64.sys Image path: \SystemRoot\system32\DRIVERS\bwcW10x64.sys Image name: bwcW10x64.sys Timestamp: Thu Jul 30 19:11:32 2015 (55BA5AC4) CheckSum: 00025F35 ImageSize: 00360000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4