Code:
BugCheck F7, {8f05c6bbaac49, f05c6bbaac49, ffff0fa3944553b6, 0}
This bugcheck indicates a driver stack buffer overflow which is mainly caused by malicious code trying to corrupt the system
So how does it do this?
Well It overwrites a functions return address (which when the function returns the code in the return address will be executed) on the callstack in order to execute malicious code located in the return address.
Now I'm not too familiar with this but the first and second parameters are buffer security checks, now the second parameter is the address that should have been return and the first parameter is the actual address being returned to.
Notice the flipped bit?
Doesn't really sound like a malicious attack to be honest but rather a driver causing a problem.
I believe this means a flipped bit which looks like has happened.
I can't find anything on the raw stack apart from an I/O completion which could mean anything.
Can you update your network driver?
We might need to enable Driver Verifier.
What is Driver Verifier?
Driver Verifier is a driver monitoring program built into Windows from Windows 2000 and later.
Depending on the settings Driver Verifier stresses the driver selected and tries to force them to crash which causes a BSOD.
How to enable Driver Verifier:
Go to Start
Type in verifier.exe
Click on Create customer settings (for code developers)
Select Standard settings and IRP Logging
Then hit next
Click Select driver names from a list
Select all drivers not created by Microsoft, Macrovision or Unknown
Finally click finish then reboot your computer
What happens if it finds something?
When Driver Verifier finds a violation with a driver it bugchecks the system hopefully with the driver responsible identified.
How long should I run it for?
Normally around 24 hours, if it finds nothing by then chances are it's not a driver issue.
Do I need to do anything in particular when running Driver Verifier?
No, just do what you normally do when the system crashes to help maximize the chances of a crash.
