Unespected BSOD result in crash dump

Hi everyone recently had a crash dump file appear c:\windows\minidump
I am uploading it here.I cannot specify what the cause of this problem may have been.;)



Noob Whisperer
Hello and welcome to the forums.
First make sure your machine is configured properly to facilitate the collection of .dmp files.
Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be
found later.
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
Please read the first post in this sticky thread here How to ask for help with a BSOD problem
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator )
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.

Additionally, if you haven’t already, please take some time and fill out your system specs in your forum profile area http://windows7forums.com/windows-7...you-filling-your-system-specs.html#post235529 .
BugCheck 7A, {4, 0, fffffa8002d46730, 294ec58}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36aa9 )

The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error
Update / upgrade or consider uninstalling or renaming the following old drivers
lmimirr.sys 4/10/2007 Driver Reference Table - lmimirr.sys
LMIRfsDriver.sys 7/14/2008 Driver Reference Table - LMIRfsDriver.sys
RaInfo.sys RaInfo.sys Driver Reference Table - RaInfo.sys
WinRing0x64.sys 7/26/2008
and uninstall Daemon Tools or the Alcohol product using these two drivers
dtsoftbus01.sys 1/13/2012
sptd.sys 8/18/2012
And then get this uninstaller from here DuplexSecure - Downloads run it and click the UNINSTALL button to completely remove sptd.sys.

Then from and elevated command prompt run the native Check Disk utility. Type
chkdsk C: /R
hit enter
answer Yes "Y" when prompted and then reboot and let it run. Check event viewer for results after Check Disk has completed and rebooted your machine.

Finally for some additional peace of mind
Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD from a cold boot after leaving it off for an hour or more.
Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.
See this Guide to using Memtest 86+


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.