New
#1
BSOD while playing Deus Ex:Mankind Divided on SSD
Original post is here...
All disks marked "dirty" after game crash
BlueScreenView seems to point towards ntoskrnl.exe.
Thank you.
Original post is here...
All disks marked "dirty" after game crash
BlueScreenView seems to point towards ntoskrnl.exe.
Thank you.
There isn't anything obvious in the first few .dmp's I looked at.
Please do the following:
Run Driver Verifier for 24 hours, or the occurrence of the next crash, whichever is earlier:
Driver Verifier - Enable and Disable in Windows 10
Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.
I was able to force a BSOD. I have attached the dump files here.
I was checking my Event Viewer and made the changes in this thread, post #7, rebooted and got the BSOD during boot before the splash screen (asking for password) was displayed. I reset and got it again so I powered down and then up and it booted normally. The error was in BrUsbSlb.sys. I have a Brother Printer and the ink is currently low after heavy printing yesterday. I have seen the Brother Status display applet give errors before, just not a BSOD. This problem all started before I was low on ink. this may just have accelerated the original problem.
I have not run the game that started all this because I didn't know if you wanted me to do that. I can if it will help.
The BSOD's could be due to several issues - we'll just tackle them as they appear in the .dmp files.
Those Brother drivers are definately outdated....update them, then run Driver Verifier again.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C9, {24c, fffff80d03f90bb8, ffffaf8c39981010, 103} *** WARNING: Unable to verify timestamp for BrSerIb.sys *** ERROR: Module load completed but symbols could not be loaded for BrSerIb.sys *** ERROR: Module load completed but symbols could not be loaded for BrUsbSIb.sys *** WARNING: Unable to verify timestamp for usbfilter.sys *** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys Probably caused by : BrSerIb.sys Followup: MachineOwner --------- 7: kd> lmvm brSerIb Browse full module list start end module name fffff80d`03fa0000 fffff80d`03feb000 BrSerIb T (no symbols) Loaded symbol image file: BrSerIb.sys Image path: \SystemRoot\system32\DRIVERS\BrSerIb.sys Image name: BrSerIb.sys Browse all global symbols functions data Timestamp: Tue Jan 22 16:01:55 2008 (479578C3) CheckSum: 0004B454 ImageSize: 0004B000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 7: kd> lmvm BrUsbSIb Browse full module list start end module name fffff80d`03f90000 fffff80d`03f93c00 BrUsbSIb (no symbols) Loaded symbol image file: BrUsbSIb.sys Image path: \SystemRoot\system32\DRIVERS\BrUsbSIb.sys Image name: BrUsbSIb.sys Browse all global symbols functions data Timestamp: Tue Jan 22 16:01:51 2008 (479578BF) CheckSum: 00006F17 ImageSize: 00003C00 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Software Download | Brother
Is the date of the drivers the "Timestamp"?
If it is then I am confused.
The dates on both files in \Windows\system32\drivers is different from that.
Yes it is. Here it is again, extracted from the drivers file you included in your .zip file:
Im not sure whats going on with your Explorer, but the .dmp and driver file dates match.Code:BrSerIb Brother MFC Serial Int Brother MFC Serial Int Kernel Manual Running OK TRUE FALSE 45,056 24,576 0 1/22/2008 12:01:55 AM C:\Windows\system32\DRIVERS\BrSerIb.sys 8,192 BrUsbSIb Brother MFC Serial USB Brother MFC Serial USB Kernel Manual Running OK TRUE FALSE 0 10,368 0 1/22/2008 12:01:51 AM C:\Windows\system32\DRIVERS\BrUsbSIb.sys 1,280
I uninstalled the drivers and re-installed them.
I have attached the listings.
I will reinstate the Driver Verifier and attempt another crash.
Shouldn't take longer than a couple of days.