Constantly getting BAD_POOL_HEADER BSOD on Windows 10

[fairfrozens]

Dumps: https://mega.nz/#!zwMA1JDB!C8HM0VYoWe72jdk1aIHtJqAtrlpZwxQY4ICh7Ho-7ts

Using BlueScreenView, the BSODs were caused by the drivers vmnetbridge.sys and win32kfull.sys. I've tried looking online but I couldn't really pinpoint a cause. Can someone help me out to find the cause please?

Thanks

 

[Slashgeek]

Are you running VMWare Workstation or other virtual machine products? Try disabling the VMWare virtual network device in the Network and Sharing Center. If this does not work, try uninstalling VMWare completely.

 

[johnbl]

ok I think this is a reltek audio driver but it is kind of old.
\SystemRoot\system32\DRIVERS\RtkIOAC60.sys Tue Jan 17 21:51:02 2012
you might go to
http://www.acer.co.id/ac/en/ID/content/drivers/4958;-;Aspire%20TC-605
and get the most current version.


the bugcheck was caused by pool corruption, IE a device driver corrupted kernel memory of another driver.
often these can be found if you:
start cmd.exe as an admin, then run
verifier.exe /standard /all
then reboot.
if windows finds a bad driver it will call a bugcheck and name the driver.
Note: use verifier.exe /reset to turn off verifier.
Also, you might want to create a restore point before you start debugging.

 

[Matt Sweeney]

"start cmd.exe as an admin, then run
verifier.exe /standard /all
then reboot."

I tried this and my computer wouldn't restart. Kept getting "driver verifier iomanager violation". Had to do a full restore.

I'm not ruling out user error--but I know how to open a command prompt and I know how to cut and paste--so I'm not sure what I could have done wrong.

 

[Matt Sweeney]

Windows 10, I should have mentioned.