New
#11
Sorry about that.
Interestingly, the memory dumps blame NTFS.sys. Please do the following free tests:
andCHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.
Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"
CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.
Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)
Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
- - The most common drivers are listed on this page: Driver ReferenceHow To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:
Summary of the BSOD's:Code:agrsm64.sys Mon Nov 10 10:01:35 2008 - Agere Systems Soft Modem - http://www.carrona.org/dvrref.html#agrsm64.sys pcouffin.sys Tue Dec 05 09:39:30 2006 - low level access layer for CD devices. A part of many different CD/DVD burning programs - http://www.carrona.org/dvrref.html#pcouffin.sys
Code:Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sat Mar 13 12:48:24.984 2010 (GMT-4) System Uptime: 0 days 12:17:32.862 BugCheck 50, {fffff8a1292f94e8, 0, fffff8800121e2bd, 5} Probably caused by : Ntfs.sys ( Ntfs!memmove+2d ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: wmplayer.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sat Mar 13 14:41:02.992 2010 (GMT-4) System Uptime: 0 days 1:18:58.083 BugCheck 50, {fffff8a1111831a8, 0, fffff8800120d2bd, 5} Probably caused by : Ntfs.sys ( Ntfs!memmove+2d ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: wmplayer.exe
Log Name: Application
Source: Microsoft-Windows-Winlogon
Date: 2/18/2010 12:05:59 PM
Event ID: 6000
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: JBsPowerPc
Description:
The winlogon notification subscriber <SessionEnv> was unavailable to handle a notification event.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Winlogon" Guid="{DBE9B383-7CF3-4331-91CC-A3CB16A3B538}" EventSourceName="Wlclntfy" />
<EventID Qualifiers="32768">6000</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-02-18T18:05:59.000000000Z" />
<EventRecordID>2703</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>JBsPowerPc</Computer>
<Security />
</System>
<EventData>
<Data>SessionEnv</Data>
<Binary>D9060000</Binary>
</EventData>
</Event>
Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 3/17/2010 9:02:33 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: JBsPowerPc
Description:
Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 5)...
329728 file records processed.
File verification completed.
380 large file records processed.
0 bad file records processed.
4 EA records processed.
132 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)...
446942 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 5)...
329728 file SDs/SIDs processed.
Cleaning up 43 unused index entries from index $SII of file 0x9.
Cleaning up 43 unused index entries from index $SDH of file 0x9.
Cleaning up 43 unused security descriptors.
Security descriptor verification completed.
58608 data files processed.
CHKDSK is verifying Usn Journal...
35084856 USN bytes processed.
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
329712 files processed.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
157426531 free clusters processed.
Free space verification is complete.
Windows has checked the file system and found no problems.
961399807 KB total disk space.
331063496 KB in 270574 files.
168512 KB in 58609 indexes.
0 KB in bad sectors.
461671 KB in use by the system.
65536 KB occupied by the log file.
629706128 KB available on disk.
4096 bytes in each allocation unit.
240349951 total allocation units on disk.
157426532 allocation units available on disk.
Internal Info:
00 08 05 00 e5 05 05 00 02 45 09 00 00 00 00 00 .........E......
0b 18 00 00 84 00 00 00 00 00 00 00 00 00 00 00 ................
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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-03-17T14:02:33.000000000Z" />
<EventRecordID>5315</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>JBsPowerPc</Computer>
<Security />
</System>
<EventData>
<Data>
Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 5)...
329728 file records processed.
File verification completed.
380 large file records processed.
0 bad file records processed.
4 EA records processed.
132 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)...
446942 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 5)...
329728 file SDs/SIDs processed.
Cleaning up 43 unused index entries from index $SII of file 0x9.
Cleaning up 43 unused index entries from index $SDH of file 0x9.
Cleaning up 43 unused security descriptors.
Security descriptor verification completed.
58608 data files processed.
CHKDSK is verifying Usn Journal...
35084856 USN bytes processed.
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
329712 files processed.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
157426531 free clusters processed.
Free space verification is complete.
Windows has checked the file system and found no problems.
961399807 KB total disk space.
331063496 KB in 270574 files.
168512 KB in 58609 indexes.
0 KB in bad sectors.
461671 KB in use by the system.
65536 KB occupied by the log file.
629706128 KB available on disk.
4096 bytes in each allocation unit.
240349951 total allocation units on disk.
157426532 allocation units available on disk.
Internal Info:
00 08 05 00 e5 05 05 00 02 45 09 00 00 00 00 00 .........E......
0b 18 00 00 84 00 00 00 00 00 00 00 00 00 00 00 ................
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.
</Data>
</EventData>
</Event>
I used Driver Genius Pro 9 to ensure all drivers are updated.
Managed to still get a blue screen dump.
How can I check the external hard drive i have hooked up to see if there are any errors?
Check the external drive using a utility from the drive manufacturer's website (they're free).
The dump file still blames NTFS.sys
The most likely cause of this is hardware - have you run the H/W Diagnostics that I requested in my first post? If so, what were the results?
Ran both H/W test and CHKDSK tests. Everything came back negative. Scanning and fixing disk errors on external HD drive at the moment
Ok I ran the HW checks on external drive and it found errors but fixed them. However i continued to get BS dumps. I unplugged the external HD and for about 5 days, I have not had any problems. What do you suggest doing in terms of the info on the HD and the problem I'm having when its connected to the PC?
Have you run hardware checks on all of the hard drives?
If you have problems when the drive is plugged in - and don't have them when it's not - the solution is to not use that drive.
Also, check the connection with another drive - just to be sure it's not the connection itself that's causing the problem.