- Thread Author
-
- #1
Solution
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80002ee9bad, 0, 30}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2d312 )
Followup: MachineOwner
this bugcheck was generated due to data held in the RAM which was unreadable. Why it was unreadable could be down to a...
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80002ee9bad, 0, 30}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2d312 )
Followup: MachineOwner
this bugcheck was generated due to data held in the RAM which was unreadable. Why it was unreadable could be down to a number of reasons and there are a few causes for this Bugcheck ranging from out of date drivers and bios to hardware issues (usually RAM).
One of your Dump files blamed Norton AV directly and the app itself is a little infamous for causing the odd issue.
I would suggest that you update your drivers and Bios using the Dell support page:
Link Removed
(Although every care is taken to ensure this is your exact download page please make sure)
If you find the issue continues after then post the dump file and depending on what it says it might be worth removing Norton just to see but anyhow try updating first.