Solution
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {48, 2, 1, fffff80002ccffc9}
Probably caused by : memory_corruption ( nt!MiRestoreTransitionPte+109 )
Followup: MachineOwnerthis bugcheck is caused by drivers accessing paged memory at an incorrect address.
Let's first check for corruption. Look in the start menu for command prompt, rightclick and run as admin. Type
sfc /scannow
Press enter and await results.
Ufortunately no driver is mentioned in the dump file although looking over what's installed something popped up straight away:
dtsoftbus01.sys Wed Feb 19 14:43:17 2014: Daemon Tools driver Possible BSOD issues in Win7 please remove.
If the bsod still continues then try removing your AV suite (you can always re-install later).
If that doesn't help then we could try running the driver verifier but first see how you go with the above
Please post any new dump files.
Similar threads
- Featured
- Article
- Featured
- Article
- Solved
Windows 10
Unexpected BSOD resulted in crash dumps
- Solved
Windows 7
Unexpected BSOD results and crash dumps