New
#1
Frequent BSOD and rebooting, memory dump?
Keep getting blue screens of death. I think I may have seen the words "memory dump" at one point during a blue screen.
Thanks in advance for any help you have to give.
Keep getting blue screens of death. I think I may have seen the words "memory dump" at one point during a blue screen.
Thanks in advance for any help you have to give.
Welcome to SevenForums.
- Click on User CP on the top right of this page
- Click on Edit System Spec
- Fill in your computer specs
BugCheck 24 & BugCheck F4
- 1. Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
- 2. Usual causes: None. (But often related to Storage/Hard Drive.)
If you have a SSD, make sure the firmware is up to date.
Upload a screenshot of your hard disk using crystal disk info:
- CrystalDiskInfo - Software - Crystal Dew World
- Screenshots and Files - Upload and Post in Seven Forums
Run Disk Check on your hard disk for file system errors and bad sectors on it:
Test your hard drive:
.nfo file:
- Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.
Summary:
Code:BugCheck 24, {1904fb, fffff8800afd6dd8, fffff8800afd6630, fffff800030f1a30} Probably caused by : memory_corruption ( nt!MmCheckCachedPageStates+3f0 ) ------ BugCheck 24, {1904fb, fffff8800a3bc958, fffff8800a3bc1b0, fffff880012a5f20} Probably caused by : Ntfs.sys ( Ntfs!NtfsOpenExistingPrefixFcb+70 ) ------ BugCheck F4, {3, fffffa8009ffdb30, fffffa8009ffde10, fffff80003381510} ----- ETW minidump data unavailable----- Probably caused by : wininit.exe ------ BugCheck 24, {1904fb, fffff8800c8381b8, fffff8800c837a10, fffff8800123f2b5} Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireExclusiveFcb+65 ) ------ BugCheck 24, {1904fb, fffff880067f4ac8, fffff880067f4320, fffff880012f4f20} Probably caused by : Ntfs.sys ( Ntfs!NtfsOpenExistingPrefixFcb+70 )
Attachment 242115
Attachment 242116
Hmm.. it may seem that there's a problem with my other drive. I tried scanning it and it couldn't complete the scan. (it froze and I had to restart.)
No antivirus?
Run these tools and delete anything they find:
ESET online scanner:
Recommended antivirus program for Windows 7 based on stability compared to others:-
- Microsoft Security Essentials - Free Antivirus for Windows
- Microsoft Security Essentials Download | Free Spyware Protection
- Malwarebytes - The Free version
- Good and Free system security combination.
Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.
Run a full scan with both (separately) once downloaded, installed and updated.
Daemon Tools
Please uninstall DAEMON Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7. Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.
As an alternative, many people recommend the use of Total Mounter or Magic ISO
Free up the start-up, nothing except the antivirus is usually needed.
Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:
- Click on the
- Type CMD on Search
- Left click and Run as Administrator
- Type SFC /scannow
Full tutorial here:
Ran the anti-rootkit. Still scanning my computer, but I uninstalled Daemon Tools and have yet to come across a BSOD, so that might have been the issue. It should be done by tomorrow so I will give you an update then.
So I ran ESET and Malwarebytes each separately, and they detected some suspicious programs and cleaned them off my computer. Then I ran CMD with the sfc /scannow command and came up with this:
Hmm... I can't seem to access it.