Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffcdcb68202480, 0, fffff80365ab7898, 2}
Could not read faulting driver name
Probably caused by : win32kbase.sys ( win32kbase!DirectComposition::CConnection::DiscardPreviousFrames+61 )
Followup: MachineOwner
Hi Zalthoria!
sorry to see your issues have returned.
The dump files you sent were just like the previous sets you had sent. Bugcheck 50, could not read faulting drivers name and Bugcheck D1 blaming the Killer network driver.
Now bugcheck 50 can be brought on by numerous things including faulty hardware, drivers and Anti-Virus apps to name just a few.
Please uninstall AVG AV suite and use the onboard Defender. (to be honest Defender is much improved and probably better than AVG anyway) Defender is much more stable although you can always go back after the testing has stopped.
You have one or two drivers dated 2009 which really is too old for Windows 10. See if you can update the following or if not please remove until testing is over:
MBfilt64.sys Fri Jul 31 04:40:32 2009: Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver). You may have a Creative app for Sound Blaster Cinema 2 so check in your Programs section. There's an updated Realtek driver here:
Support For Z97 GAMING 5 | MSI Global | Motherboard - The world leader in motherboard design pwdrvio.sys Tue Jun 16 02:43:45 2009: MiniTool Partition Wizard, please either update or remove:
http://www.partitionwizard.com/free-partition-manager.html In regards to the killer network driver which was flagged up by the Bugcheck D1 dump files, please download the latest version, released a few days ago:
Killer Networking - Standard Drivers (no Killer features) 64-bit File scans
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. 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.
If the bsod continues then remove all of your RAM apart from one stick.
Use your system as normal. If a bsod occurs make a note of which stick of RAM it is and then pop another stick in the same slot. What your looking for is a stick or sticks which
do not bsod.
If do find a stick or sticks which don't bsod then you know that the other sticks are faulty and need replacing.
The reason I'm asking you to test in this way is because you have already tried Memtest86 and the results were nil. Sometimes however memtest86 can be incorrect (although i think it's simply a case that Memtest86 wasn't run for long enough and would give the correct results if given the time to do so).
I have dealt with a number of users where this turned out to be the case so I know it's definitely possible.
Hope all goes well with the testing and please post back for any advice ect..