bsod While gaming. Many different errors.

[Ragazzacane]

I've had 0x0000007f and 0x0000008e with a few other errors.
Os is windows 7 ultimate and I have service pack 1.

 

[Ragazzacane]

I've had irql less then zero
page fault in non page area
irql gt zero at system services
I have no idea what they mean though.

 

[Tank997]

Ultimate Nvidia Driver Guide for Uninstalling and Installing driversets

 

[Ragazzacane]

I have 'crossfireX'd Radeon HD 4800 cards. Would this Nvidia guide still help me?

 

[writhziden]

Probably not. Just because they occur while gaming does not mean it is a graphics card or graphics card driver problem...


Security Software:

ccsvchst.exe	c:\program files\norton security suite\engine\5.2.0.13\ccsvchst.exe	740	8	1024	10240	4/1/2012 4:57 AM	10.1.1.16	126.96 KB (130,008 bytes)	2/8/2012 3:13 AM
ccsvchst.exe	c:\program files\norton security suite\engine\5.2.0.13\ccsvchst.exe	3276	8	1024	10240	4/1/2012 5:00 AM	10.1.1.16	126.96 KB (130,008 bytes)	2/8/2012 3:13 AM
sascore.exe	c:\program files\superantispyware\sascore.exe	1848	8	200	1380	4/1/2012 4:57 AM	1.0.0.1066	113.88 KB (116,608 bytes)	7/15/2010 7:08 PM
superantispyware.exe	c:\program files\superantispyware\superantispyware.exe	5140	8	200	1380	4/1/2012 5:07 AM	5.0.0.1146	3.72 MB (3,905,920 bytes)	5/26/2009 10:05 AM

Possible out of date drivers (going as far back as 1996!??!):

[COLOR="Red"][B]giveio	8be32000	8be32680	Wed Apr 03 20:33:25 1996 (316334f5)	00003355		giveio.sys[/B][/COLOR]
SENTINEL	adbb0000	adbc4c00	Thu Feb 01 04:38:53 2007 (45c1d14d)	0002591a		SENTINEL.SYS
asusgsb	a0ddf000	a0de2b80	Thu Sep 27 07:14:15 2007 (46fbaca7)	0000f2a0		asusgsb.sys
ATKDispLowFilter	99792000	99799900	Tue May 13 21:02:50 2008 (482a565a)	00007dbc		ATKDispLowFilter.sys
lirsgt	adbf4000	adbf8880	Tue Jun 17 08:41:11 2008 (4857cd07)	00007356		lirsgt.sys
[COLOR="red"][B]Rt86win7	a0cf7000	a0d1c000	Thu Feb 26 02:04:22 2009 (49a65b16)	00022867		Rt86win7.sys[/B][/COLOR]
AtiPcie	8bbef000	8bbf7000	Tue May 05 09:00:16 2009 (4a005480)	00012ec4		AtiPcie.sys
LHidFilt	a1db9000	a1dc0080	Wed Jun 17 10:49:04 2009 (4a391e80)	000167ac		LHidFilt.Sys
LMouFilt	a1dc1000	a1dc8800	Wed Jun 17 10:49:08 2009 (4a391e84)	0000d1d5		LMouFilt.Sys

giveio.sys: ADC Analyzer/SwiftForth/Disspy - ?SpeedFan? Remove this software; we can provide you with a modern replacement if you ask.
SENTINEL.SYS
asusgsb.sys
ATKDispLowFilter.sys
lirsgt.sys
Rt86win7.sys
AtiPcie.sys
LHidFilt.Sys
LMouFilt.Sys
Only worry about the drivers listed in red in the code. The others are not deal breakers.

Loading Dump File [D:\Kingston\BSODDmpFiles\Ragazzacane\Windows_NT6_BSOD_jcgriff2\040112-34765-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.x86fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0x83608000 PsLoadedModuleList = 0x837514d0
Debug session time: Sun Apr  1 05:50:02.352 2012 (UTC - 6:00)
System Uptime: 0 days 0:07:47.727
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, 8db39750, 0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 8db39750
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 00000000 to 83686692

STACK_TEXT:  
c80b7c18 00000000 00000000 00000000 00000000 nt!KiSwapThread+0x25b


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    83686dd0-83686dd7  8 bytes - nt!KiServiceTable+34
	[ 93 6b 8e 83 80 9b 83 83:18 cd f2 89 00 7e 72 8a ]
    83686de8-83686deb  4 bytes - nt!KiServiceTable+4c (+0x18)
	[ 8c 2b 83 83:c8 73 04 88 ]
    83686df4-83686df7  4 bytes - nt!KiServiceTable+58 (+0x0c)
	[ ce e3 87 83:d0 42 18 87 ]
    83686e48-83686e4b  4 bytes - nt!KiServiceTable+ac (+0x54)
	[ 96 7f 80 83:18 7d 9f 8a ]
    83686ec4-83686ec7  4 bytes - nt!KiServiceTable+128 (+0x7c)
	[ 5a 92 81 83:b8 d2 02 88 ]
    83686ef4-83686eff  12 bytes - nt!KiServiceTable+158 (+0x30)
	[ b9 a8 80 83 36 4e 8e 83:c8 e0 02 88 c8 81 04 88 ]
    83686f1c-83686f1f  4 bytes - nt!KiServiceTable+180 (+0x28)
	[ 10 6d 8b 83:c8 14 d7 86 ]
    83686f58-83686f5b  4 bytes - nt!KiServiceTable+1bc (+0x3c)
	[ 1a a6 83 83:40 93 02 88 ]
    83686fa8-83686fab  4 bytes - nt!KiServiceTable+20c (+0x50)
	[ db 24 6c 83:28 72 04 88 ]
    83686fe0-83686fe3  4 bytes - nt!KiServiceTable+244 (+0x38)
	[ 88 e8 7f 83:d8 76 1d 88 ]
    83686fe8 - nt!KiServiceTable+24c (+0x08)
	[ cc:20 ]
    83686fea-83686feb  2 bytes - nt!KiServiceTable+24e (+0x02)
	[ 88 83:ec 8a ]
55 errors : !nt (83686dd0-83686feb)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

Followup: memory_corruption
---------

Usually means hardware conflicts are occurring. Can also be due to antivirus/firewall software being corrupted or out of date. Make sure you have the latest version of your security software. Even if you have the latest version, uninstall the software and re-install it in case the version running on your system is corrupt. For properly uninstalling Norton, use the Norton Removal Tool


If the steps to fix the antivirus/firewall software do not resolve the crashes:

• If you are overclocking any hardware, please stop.
  
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing a CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[Ragazzacane]

round 2

I tried fixing the driver issues by deleting the ones mentioned and reinstalling Norton.
Also, it seems that I can not attach an HTML file.

 

[writhziden]

Loading Dump File [D:\Kingston\BSODDmpFiles\Ragazzacane\Windows_NT6_BSOD_jcgriff2\040712-30328-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.x86fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0x8383b000 PsLoadedModuleList = 0x839844d0
Debug session time: Sat Apr  7 21:57:19.792 2012 (UTC - 6:00)
System Uptime: 0 days 2:26:09.152
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8c65382d, b84bbca4, 0}

Probably caused by : Ntfs.sys ( Ntfs!NtfsStorageDriverCallout+14 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8c65382d, The address that the exception occurred at
Arg3: b84bbca4, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
Ntfs!NtfsStorageDriverCallout+14
8c65382d 89460c          mov     dword ptr [esi+0Ch],eax

TRAP_FRAME:  b84bbca4 -- (.trap 0xffffffffb84bbca4)
ErrCode = 00000002
eax=a26bb206 ebx=86482bb8 ecx=00000000 edx=8be875b8 esi=bcf5d7b8 edi=b84bbd28
eip=8c65382d esp=b84bbd18 ebp=b84bbd1c iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
Ntfs!NtfsStorageDriverCallout+0x14:
8c65382d 89460c          mov     dword ptr [esi+0Ch],eax ds:0023:bcf5d7c4=00000000
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 838ba7ba to 8c65382d

STACK_TEXT:  
b84bbd1c 838ba7ba bcf5d7b8 00000000 ffffffff Ntfs!NtfsStorageDriverCallout+0x14
b84bbd1c 838ba8b1 bcf5d7b8 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x15a
bcf5d728 838c47a7 bcf5d7b8 8c653819 b84bc000 nt!KiSwitchKernelStackAndCallout+0x31
bcf5d79c 8c653800 8c653819 bcf5d7b8 00000000 nt!KeExpandKernelStackAndCalloutEx+0x29d
bcf5d7c8 8c645b83 87160520 8be875b8 86f72598 Ntfs!NtfsCallStorageDriver+0x2d
bcf5d80c 8c6456f7 bcf5da20 87160520 8be875b8 Ntfs!NtfsMultipleAsync+0x4d
bcf5d93c 8c649720 bcf5da20 8be875b8 a197f0f8 Ntfs!NtfsNonCachedIo+0x413
bcf5da10 8c64acf7 bcf5da20 8be875b8 00c8070a Ntfs!NtfsCommonRead+0x1148
bcf5db54 838725be 871d9020 8be875b8 8be875b8 Ntfs!NtfsFsdRead+0x279
bcf5db6c 8c4ab20c 88864138 8be875b8 00000000 nt!IofCallDriver+0x63
bcf5db90 8c4ab3cb bcf5dbb0 88864138 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
bcf5dbc8 838725be 88864138 8be875b8 8be875b8 fltmgr!FltpDispatch+0xc5
bcf5dbe0 838ffa1e 864301a8 86482bb8 86430178 nt!IofCallDriver+0x63
bcf5dbfc 838e25d0 8c0a4c48 86482bb8 864301b0 nt!IoPageRead+0x1f5
bcf5dc94 838cbf44 86e9e220 00a9929c 86430179 nt!MiIssueHardFault+0x28c
bcf5dd1c 8387c478 00000000 00a9929c 00000001 nt!MmAccessFault+0x2c3a
bcf5dd1c 771bf7e4 00000000 00a9929c 00000001 nt!KiTrap0E+0xdc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012e6bc 00000000 00000000 00000000 00000000 0x771bf7e4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Ntfs!NtfsStorageDriverCallout+14
8c65382d 89460c          mov     dword ptr [esi+0Ch],eax

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsStorageDriverCallout+14

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d799527

FAILURE_BUCKET_ID:  0x8E_Ntfs!NtfsStorageDriverCallout+14

BUCKET_ID:  0x8E_Ntfs!NtfsStorageDriverCallout+14

Followup: MachineOwner
---------

The latest crashes are still pointing to hardware.

Continue with the hardware tests.

The above crash also points to hard disk errors (although this can also mean the RAM is causing hard disk file system corruption).

• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run the short and long tests with SeaTools to make sure the hard disk is not faulty.

 

[Ragazzacane]

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 4/8/2012 8:21:07 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: JaredsBalrag
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)...
465920 file records processed.

File verification completed.
490 large file records processed.

0 bad file records processed.

2 EA records processed.

57 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
548380 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
465920 file SDs/SIDs processed.

Cleaning up 1760 unused index entries from index $SII of file 0x9.
Cleaning up 1760 unused index entries from index $SDH of file 0x9.
Cleaning up 1760 unused security descriptors.
Security descriptor verification completed.
41231 data files processed.

CHKDSK is verifying Usn Journal...
33937904 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x8447b07000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x8447b11000 for 0x1000 bytes.
Windows replaced bad clusters in file 58480
of name \Windows\INSTAL~1\35375.msi.
Read failure with status 0xc000009c at offset 0x9102e51000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x9102e5d000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x9102e5e000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x9102e5e000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x9102e5f000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x9102e5f000 for 0x1000 bytes.
Windows replaced bad clusters in file 172861
of name \Users\Jared\Desktop\movies\HALLPA~1.AVI.
Read failure with status 0xc000009c at offset 0x7c2d869000 for 0x2000 bytes.
Read failure with status 0xc000009c at offset 0x7c2d869000 for 0x1000 bytes.
Windows replaced bad clusters in file 280975
of name \Windows\System32\config\SYSTEM~1\AppData\Local\MICROS~1\Windows\TEMPOR~1\Content.IE5\GO1803~1.JS.
465904 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
108860444 free clusters processed.

Free space verification is complete.
Adding 5 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

976657407 KB total disk space.
540411464 KB in 416233 files.
206276 KB in 41232 indexes.
20 KB in bad sectors.
597871 KB in use by the system.
65536 KB occupied by the log file.
435441776 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
108860444 allocation units available on disk.

Internal Info:
00 1c 07 00 03 fb 06 00 8e 36 0d 00 00 00 00 00 .........6......
f7 60 00 00 39 00 00 00 00 00 00 00 00 00 00 00 .`..9...........
b8 60 23 00 50 01 21 00 78 1d 21 00 00 00 21 00 .`#.P.!.x.!...!.

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="2012-04-09T03:21:07.000000000Z" />
<EventRecordID>64986</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>JaredsBalrag</Computer>
<Security />
</System>
<EventData>
<Data>

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)...
465920 file records processed.

File verification completed.
490 large file records processed.

0 bad file records processed.

2 EA records processed.

57 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
548380 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
465920 file SDs/SIDs processed.

Cleaning up 1760 unused index entries from index $SII of file 0x9.
Cleaning up 1760 unused index entries from index $SDH of file 0x9.
Cleaning up 1760 unused security descriptors.
Security descriptor verification completed.
41231 data files processed.

CHKDSK is verifying Usn Journal...
33937904 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x8447b07000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x8447b11000 for 0x1000 bytes.
Windows replaced bad clusters in file 58480
of name \Windows\INSTAL~1\35375.msi.
Read failure with status 0xc000009c at offset 0x9102e51000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x9102e5d000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x9102e5e000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x9102e5e000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x9102e5f000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x9102e5f000 for 0x1000 bytes.
Windows replaced bad clusters in file 172861
of name \Users\Jared\Desktop\movies\HALLPA~1.AVI.
Read failure with status 0xc000009c at offset 0x7c2d869000 for 0x2000 bytes.
Read failure with status 0xc000009c at offset 0x7c2d869000 for 0x1000 bytes.
Windows replaced bad clusters in file 280975
of name \Windows\System32\config\SYSTEM~1\AppData\Local\MICROS~1\Windows\TEMPOR~1\Content.IE5\GO1803~1.JS.
465904 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
108860444 free clusters processed.

Free space verification is complete.
Adding 5 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

976657407 KB total disk space.
540411464 KB in 416233 files.
206276 KB in 41232 indexes.
20 KB in bad sectors.
597871 KB in use by the system.
65536 KB occupied by the log file.
435441776 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
108860444 allocation units available on disk.

Internal Info:
00 1c 07 00 03 fb 06 00 8e 36 0d 00 00 00 00 00 .........6......
f7 60 00 00 39 00 00 00 00 00 00 00 00 00 00 00 .`..9...........
b8 60 23 00 50 01 21 00 78 1d 21 00 00 00 21 00 .`#.P.!.x.!...!.

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
</EventData>
</Event>

 

[Ragazzacane]

What do I do if the hard disks 'FAIL' the driver status test? It did btw.

 

[writhziden]

As to your previous post with the disk check results, you will want to run the disk check again with both boxes checked. Appears you had some bad sectors and file system corruption.


For the SeaTools error, see if you get it with the DOS version, as well.

 

[Ragazzacane]

I'm honestly not sure how to use the DOS version. I put it on a CD, but opening it just has the iso file on the CD...

 

[writhziden]

You need to double click the ISO and burn it to CD using the program that opens the ISO file. Windows has a built in system to do so, or you can use a third party program. Many on here use and recommend The Official ImgBurn Website which is free.

 

[Ragazzacane]

Ran the disk check 3 more times.

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 4/11/2012 12:45:06 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: JaredsBalrag
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)...
465920 file records processed.

File verification completed.
489 large file records processed.

0 bad file records processed.

2 EA records processed.

57 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
548606 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
465920 file SDs/SIDs processed.

Cleaning up 18 unused index entries from index $SII of file 0x9.
Cleaning up 18 unused index entries from index $SDH of file 0x9.
Cleaning up 18 unused security descriptors.
Security descriptor verification completed.
41344 data files processed.

CHKDSK is verifying Usn Journal...
34193680 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
465904 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
101128793 free clusters processed.

Free space verification is complete.
Windows has checked the file system and found no problems.

976657407 KB total disk space.
571335692 KB in 422788 files.
208232 KB in 41345 indexes.
20 KB in bad sectors.
598291 KB in use by the system.
65536 KB occupied by the log file.
404515172 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
101128793 allocation units available on disk.

Internal Info:
00 1c 07 00 0f 15 07 00 d7 69 0d 00 00 00 00 00 .........i......
13 61 00 00 39 00 00 00 00 00 00 00 00 00 00 00 .a..9...........
b8 60 39 00 50 01 37 00 78 1d 37 00 00 00 37 00 .`9.P.7.x.7...7.

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="2012-04-11T19:45:06.000000000Z" />
<EventRecordID>65760</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>JaredsBalrag</Computer>
<Security />
</System>
<EventData>
<Data>

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)...
465920 file records processed.

File verification completed.
489 large file records processed.

0 bad file records processed.

2 EA records processed.

57 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
548606 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
465920 file SDs/SIDs processed.

Cleaning up 18 unused index entries from index $SII of file 0x9.
Cleaning up 18 unused index entries from index $SDH of file 0x9.
Cleaning up 18 unused security descriptors.
Security descriptor verification completed.
41344 data files processed.

CHKDSK is verifying Usn Journal...
34193680 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
465904 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
101128793 free clusters processed.

Free space verification is complete.
Windows has checked the file system and found no problems.

976657407 KB total disk space.
571335692 KB in 422788 files.
208232 KB in 41345 indexes.
20 KB in bad sectors.
598291 KB in use by the system.
65536 KB occupied by the log file.
404515172 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
101128793 allocation units available on disk.

Internal Info:
00 1c 07 00 0f 15 07 00 d7 69 0d 00 00 00 00 00 .........i......
13 61 00 00 39 00 00 00 00 00 00 00 00 00 00 00 .a..9...........
b8 60 39 00 50 01 37 00 78 1d 37 00 00 00 37 00 .`9.P.7.x.7...7.

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
</EventData>
</Event>

 

[writhziden]

Looks clean. Any luck getting SeaTools in DOS working?