|reply to devolic |
Have you updated any drivers lately?
You can upload your minidump file to this site and view the details.
When I uploaded your file, here are some quick snippets:
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
Arg1: c0000005, The exception code that was not handled
Arg2: bf9568c8, The address that the exception occurred at
Arg3: aa39fc00, Trap Frame