*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff900c551bcf0, 0, fffff9600036260d, 0}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d )
Followup: MachineOwner
What other programs? Try it and see.. As for the video's I'm unsure, check for malware using this app:
https://www.malwarebytes.org/
I certainly can and use Malwarebytes Pro myself. You should ok watching videos and the like..
Hi,
win32.sys can appear if a hardware issue is present like bad RAM. Can you post the actual dump file?
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff900c551bcf0, 0, fffff9600036260d, 0}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d )
Followup: MachineOwner
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff900c551bcf0, 0, fffff9600036260d, 0} Could not read faulting driver name Probably caused by : win32k.sys ( win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d ) Followup: MachineOwner
You still need to update your bios and of course the service pack too... win32k.sys as I already stated can pop up if there's a hardware failure or a driver is incorrect or the bios needs updating...
Try running this scan too:
Link Removed
Shouldn't matter...
Just follow the advice shown in the webpage above and try a test. I know there's a long one that runs for around 4hrs but it's up to you which one you run. All your doing is seeing if the hardrive passes the tests. If you get a fail on any of them then you know you have a possibly failing drive.
Hmm... I guess your using the Asus bios app to update yes? If your not already try right clicking the application and running it as administrator.
Thats good.. Did you try the above suggestion?
Excellent, well done. Let me know how things go..