New
#11
Two days later I start getting BSOD again. Here are the new dump files and updated logs. One of them is a new stop code that I haven't seen before on my system ntfs.sys. The other is one that I have seen very often, ntkrnlmp.exe. Any help would be appreciated. Thanks
I'm starting to think I will need a windows recovery seeing that ntfs file system is causing BSoD..
This time it is showing multiple errors in the last two dumps.
Display driver is failing.
The latest version is the display driver is often problematic. Install the 314.22 WHQL only.Code:fffff880`0786b6e8 fffff880`04ac920dUnable to load image nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x20920d
- Uninstall All nvidia items in Control Panel > Programs and features
- 3D Vision Control Driver
- 3D Vision Driver
- Graphics Driver
- HD Audio Driver
- PhysX
- nvidia Update
(Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).- Now follow Drivers - Clean Left over Files after Uninstalling
- Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
Also some ataport errors ate there.
I see that there is Virtual clone drive installed.Code:fffff880`0786ba58 fffff880`010760c5 ataport!AtaPortCompleteRequest+0x21 fffff880`0786ba18 fffff880`0107f731 ataport!IdeProcessPortNotification+0x30d
No code has to be inserted here.
The SCSI adapter installed by Virtual CloneDrive may cause this error, so it is suggested to uninstall Virtual CloneDrive.
One more thing in this regard ... ataport.sys is always the most vulnerable to malware called rootkit. For a safety reason, scan the system for possible virus infection with the following programs.
and, Ntfs error is there, too.
The C drive is feeling up. It has 11.72 GB free space left. So better to clear some files. Disable Hibernate. It is not anything must for a desktop, and it will salvage some free space there.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* NTFS_FILE_SYSTEM (24) If you see NtfsExceptionFilter on the stack then the 2nd and 3rd parameters are the exception record and context record. Do a .cxr on the 3rd parameter and then kb to obtain a more informative stack trace.
Check your Maxtor 200 GB, too .... do some Disc checks.
- Re-seat the sata and power.
- Run chkdsk /f/r, following the option two of the tutorial Disk Check
- Seatool for dos: SeaTools | Seagate download
Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
Let us know the results.
I uninstalled and cleaned all graphics drivers then ran clean install of 314.22 whql nvidia driver. Uninstalled VirtualCloneDrive and ran the scans provided. Both resulted with no threats. I already had hibernate disabled a long time ago to free up space. Seatools for DOS long test and short DST both passed.
I ran chkdsk /f/r and here are the results:
Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 8/26/2013 4:43:39 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: BMHoff-PC1
Description:
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 5)...
248320 file records processed.
File verification completed.
1903 large file records processed.
0 bad file records processed.
2 EA records processed.
58 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)...
347174 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 5)...
248320 file SDs/SIDs processed.
Cleaning up 1330 unused index entries from index $SII of file 0x9.
Cleaning up 1330 unused index entries from index $SDH of file 0x9.
Cleaning up 1330 unused security descriptors.
CHKDSK is compacting the security descriptor stream
49428 data files processed.
CHKDSK is verifying Usn Journal...
36879288 USN bytes processed.
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
248304 files processed.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
2796939 free clusters processed.
Free space verification is complete.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
61143389 KB total disk space.
49341708 KB in 181562 files.
260008 KB in 49431 indexes.
0 KB in bad sectors.
353913 KB in use by the system.
65536 KB occupied by the log file.
11187760 KB available on disk.
4096 bytes in each allocation unit.
15285847 total allocation units on disk.
2796940 allocation units available on disk.
Internal Info:
00 ca 03 00 58 86 03 00 ea 43 06 00 00 00 00 00 ....X....C......
68 02 00 00 3a 00 00 00 00 00 00 00 00 00 00 00 h...:...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Windows has finished checking your disk.
Please wait while your computer restarts.
Was running fine until today (1 full day without BSOD). I compiled the diagnostic logs again with the new dump file. When it BSOD'ed, as it was booting back, it BSOD again at the windows loading screen before desktop loads but that instance didn't get reported in the dump files. Roughly 45-60 minutes later I get another couple BSOD with different probable causes. I'm starting to see inconsistencies with what the probable cause is in the crash dump records. I used to see probably caused by ntkrnlmp.exe quite consistently but now it's getting to be more random. Will keep you updated if more BSOD occur.
Last edited by BHoffman; 28 Aug 2013 at 07:32.
It appears that you have not followed this part of my post #15.....
Do it as soon as possible.I see that there is Virtual clone drive installed.Code:fffff880`0786ba58 fffff880`010760c5 ataport!AtaPortCompleteRequest+0x21 fffff880`0786ba18 fffff880`0107f731 ataport!IdeProcessPortNotification+0x30d
No code has to be inserted here.
The SCSI adapter installed by Virtual CloneDrive may cause this error, so it is suggested to uninstall Virtual CloneDrive.
One more thing in this regard ... ataport.sys is always the most vulnerable to malware called rootkit. For a safety reason, scan the system for possible virus infection with the following programs.
Also update Realtek network driver. Get it grom Realtek. You are supposed to take the Win7 and WinServer 2008 R2 Auto Installation Program dated 2013/8/1.
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
That's odd that you don't see those actions done because I uninstalled virtual clonedrive through the control panel then ran both tdsskiller and windows defender offline (from boot). Which of these actions is not showing up in logs? Also, I can't re-uninstall virtualclonedrive of course but I will perform the rootkit scans once more just in case. I will run the memory tests tonight as well even though I ran prime95 over a week ago with all passes. Also, here's another BSOD that occurred as I booted up my PC this afternoon.