Random BSOD's want to figure this out once and for all

obidon · Mar 14, 2012

Basically they just come up at random. I don't even know anymore. It's probably some hardware thing, I'm thinking maybe my graphics card or hard drive.

But anyway I finally decided that I should try to figure this out since I just want an overall stable system.

I've done the jcgriff2 report thing. But before I post it as an attachment I just have one question. There's a lot of info in the report; will it contain any Personally Identifiable Information?

I just want to get this figured out before I go around publicly posting my system info on the internet. Although I do appreciate the help from everyone who will be diagnosing my system errors I just like to take caution. You can never be too sure you know?

Thanks for replies

DMHolt57 · Mar 14, 2012

No personal information is included in the jcgriff report, only machine specific data which will show us what your problem is.

obidon · Mar 15, 2012

Blah only one response to my inquiry. Very well then.

Guess I'll have to take your word for it.

Attached the files below. Thanks for your help

obidon · Mar 16, 2012

Can someone please help me try to get my blue screens worked out?

Sorry I didn't give a very good description but they are so random I have nothing else to say really except I think it might be my graphics card.

Any responses will be very appreciated as I really want a stable system. Thank you so much!!

writhziden · Mar 16, 2012

Possible out of date driver:

Code:

Lycosa	fffff880`0836f000	fffff880`08373980	Fri Jan 18 01:51:42 2008 (4790689e)	0000e99d		Lycosa.sys

Update the above driver and see if it helps before proceeding with the rest...

Code:

[list=1]
[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\obidon\Windows_NT6_BSOD_jcgriff2\031412-22635-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0300f000 PsLoadedModuleList = 0xfffff800`0324be70
Debug session time: Wed Mar 14 12:05:06.290 2012 (UTC - 6:00)
System Uptime: 0 days 0:00:50.272
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff8800318c6e8, fffff8800318bf50, fffff880012d2900}

Probably caused by : Ntfs.sys ( Ntfs! ?? ::NNGAKEGL::`string'+16818 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff8800318c6e8
Arg3: fffff8800318bf50
Arg4: fffff880012d2900

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


EXCEPTION_RECORD:  fffff8800318c6e8 -- (.exr 0xfffff8800318c6e8)
ExceptionAddress: fffff880012d2900 (Ntfs! ?? ::NNGAKEGL::`string'+0x0000000000016818)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800318bf50 -- (.cxr 0xfffff8800318bf50)
rax=fffff8a001cfe5c0 rbx=fffff8800318c9b0 rcx=000000000000122a
rdx=fffff88002f00000 rsi=0002000000000000 rdi=fffffa8005916120
rip=fffff880012d2900 rsp=fffff8800318c920 rbp=fffff800032235a0
 r8=0000000000009150  r9=0000000000000040 r10=fffff8000300f000
r11=fffff8a001cfe5c0 r12=fffff8a001cfe5c0 r13=fffffa800479c180
r14=fffff8800318c9a1 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
Ntfs! ?? ::NNGAKEGL::`string'+0x16818:
fffff880`012d2900 488b8e88000000  mov     rcx,qword ptr [rsi+88h] ds:002b:00020000`00000088=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b60e0
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs! ?? ::NNGAKEGL::`string'+16818
fffff880`012d2900 488b8e88000000  mov     rcx,qword ptr [rsi+88h]

FAULTING_IP: 
Ntfs! ?? ::NNGAKEGL::`string'+16818
fffff880`012d2900 488b8e88000000  mov     rcx,qword ptr [rsi+88h]

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff88001266cfa to fffff880012d2900

STACK_TEXT:  
fffff880`0318c920 fffff880`01266cfa : fffff800`032235a0 fffff880`0318cb01 fffff880`0318c9a1 fffff8a0`01cfe5c0 : Ntfs! ?? ::NNGAKEGL::`string'+0x16818
fffff880`0318c980 fffff880`012ee3dc : fffffa80`05916120 fffffa80`0479c180 fffff8a0`01cfe5c0 fffff8a0`01cfe958 : Ntfs!NtfsTeardownFromLcb+0x1ea
fffff880`0318ca10 fffff880`0126f602 : fffffa80`05916120 fffffa80`05916120 fffff8a0`01cfe5c0 00000000`00000000 : Ntfs!NtfsTeardownStructures+0xcc
fffff880`0318ca90 fffff880`013058f3 : fffffa80`05916120 fffff800`032235a0 fffff8a0`01cfe5c0 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffff880`0318cad0 fffff880`012dfc9f : fffffa80`05916120 fffff8a0`01cfe6f0 fffff8a0`01cfe5c0 fffffa80`0479c180 : Ntfs!NtfsCommonClose+0x353
fffff880`0318cba0 fffff800`0308c6e1 : 00000000`00000000 fffff800`03377400 fffffa80`03705601 fffffa80`00000002 : Ntfs!NtfsFspClose+0x15f
fffff880`0318cc70 fffff800`0331e726 : 00000000`00000000 fffffa80`03705680 00000000`00000080 fffffa80`036da040 : nt!ExpWorkerThread+0x111
fffff880`0318cd00 fffff800`0305dac6 : fffff880`02f63180 fffffa80`03705680 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0318cd40 00000000`00000000 : fffff880`0318d000 fffff880`03187000 fffff880`0318c9b0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs! ?? ::NNGAKEGL::`string'+16818

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d79996d

STACK_COMMAND:  .cxr 0xfffff8800318bf50 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!_??_::NNGAKEGL::_string_+16818

BUCKET_ID:  X64_0x24_Ntfs!_??_::NNGAKEGL::_string_+16818

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

[/list]

Possible causes are Memory problems... Corrupted hard disk file system... Drivers... corrupted SCSI or IDE Drivers...

Thanks to Dave76 for help understanding possible causes.

Event Viewer Errors associated to your crash...

Code:

Event[353]:
  Log Name: System
  Source: Ntfs
  Date: 2012-03-14T12:45:44.757
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: x0bi7
  Description: 
[B][COLOR="Red"]The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume1.[/COLOR][/B]

If you are overclocking any hardware, please stop.
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
I would also recommend following the steps laid out in HD Diagnostic

Update to Service Pack 1 (SP1)

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]

Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

Service Pack 1 Download site

Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH

obidon · Mar 17, 2012

Ok updated the Lycosa driver and haven't had a bluescreen yet. I'll post the chkdsk results once they finish. Thanks for the informative reply.

writhziden · Mar 17, 2012

You're welcome. For any drives that do not give the message:
Windows has checked the file system and found no problems
run the disk checks 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.

obidon · Mar 17, 2012

Here is the chkdsk log found in the Event Viewer log.

Code:

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)...
  562176 file records processed.                                          File verification completed.
  1348 large file records processed.                                      0 bad file records processed.                                        2 EA records processed.                                              101 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  669212 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  562176 file SDs/SIDs processed.                                         Cleaning up 16 unused index entries from index $SII of file 0x9.
Cleaning up 16 unused index entries from index $SDH of file 0x9.
Cleaning up 16 unused security descriptors.
Security descriptor verification completed.
  53519 data files processed.                                            CHKDSK is verifying Usn Journal...
  35082984 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  562160 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  4677735 free clusters processed.                                         Free space verification is complete.
Windows has checked the file system and found no problems.

 312560608 KB total disk space.
 292910592 KB in 471995 files.
    264492 KB in 53520 indexes.
         0 KB in bad sectors.
    674584 KB in use by the system.
     65536 KB occupied by the log file.
  18710940 KB available on disk.

      4096 bytes in each allocation unit.
  78140152 total allocation units on disk.
   4677735 allocation units available on disk.

Internal Info:
00 94 08 00 d6 04 08 00 f0 e1 0e 00 00 00 00 00  ................
c2 15 00 00 65 00 00 00 00 00 00 00 00 00 00 00  ....e...........
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.

writhziden · Mar 17, 2012

How many times did you need to run the disk check to get that message?

How is the system responding after the disk check(s)?

obidon · Mar 18, 2012

writhziden said:
How many times did you need to run the disk check to get that message?

How is the system responding after the disk check(s)?

I only had to run it once, but it took a really long time to complete. I've done check disk before at startup, but I don't think it ever got to cycle through all 5 stages. It usually only did 3 stages before.

Overall the system seems to be fairly stable, no bluescreens since I've updated the Lycosa driver. I really hope it stays that way. Also the reliability history is clear so far today except for one "Video hardware error". I'll let you know if anything else happens.

Also I did a chkdsk on my external Hitachi drive I have connected at the moment. I'll attach the log file of this drive too since it says that some problems were found and fixed.

Code:

Chkdsk was executed in read/write mode.  

Checking file system on F:
Volume label is Hitachi.

CHKDSK is verifying files (stage 1 of 5)...
  146176 file records processed.                                          File verification completed.
  61 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              0 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
The two index entries of length 0x80 and 0x70 are either identical
or appear in the wrong order.
7f 56 01 00 00 00 01 00 80 00 6e 00 00 00 00 00  .V.......n.....
3d 56 01 00 00 00 01 00 88 38 eb 75 d5 bc cc 01  =V......8ëu....
00 98 92 b6 fd 54 ca 01 98 5f eb 75 d5 bc cc 01  ..ýT.._ëu....
88 38 eb 75 d5 bc cc 01 00 20 00 00 00 00 00 00  8ëu..... ......
9c 1e 00 00 00 00 00 00 20 00 00 00 00 00 00 00  ....... .......
16 01 4c 00 44 00 22 00 50 00 61 00 74 00 68 00  ..L.D.".P.a.t.h.
20 00 6f 00 66 00 20 00 44 00 65 00 73 00 74 00   .o.f. .D.e.s.t.
69 00 6e 00 79 00 2e 00 66 00 78 00 70 00 00 00  i.n.y...f.x.p...
70 00 01 00 00 00 01 00 70 00 d6 75 d5 bc cc 01  p.......p..u....
----------------------------------------------------------------------
80 56 01 00 00 00 01 00 70 00 5e 00 00 00 00 00  V......p.^.....
3d 56 01 00 00 00 01 00 ca d4 eb 75 d5 bc cc 01  =V........ëu....
00 98 92 b6 fd 54 ca 01 db fb eb 75 d5 bc cc 01  ..ýT....ëu....
ca d4 eb 75 d5 bc cc 01 00 20 00 00 00 00 00 00  ..ëu..... ......
9c 1e 00 00 00 00 00 00 20 00 00 00 00 00 00 00  ....... .......
0e 01 4c 00 44 00 20 00 50 00 69 00 72 00 61 00  ..L.D. .P.i.r.a.
6e 00 68 00 61 00 2e 00 66 00 78 00 70 00 00 00  n.h.a...f.x.p...
81 56 01 00 00 00 01 00 78 00 66 00 00 00 00 00  V......x.f.....
Sorting index $I30 in file 87613.
Unable to locate the file name attribute of index entry LD"Path of Destiny.fxp
of index $I30 with parent 0x1563d in file 0x1567f.
Deleting index entry LD"Path of Destiny.fxp in index $I30 of file 87613.
  166756 index entries processed.                                         Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.

Recovering orphaned file LD Path of Destiny.fxp (87679) into directory file 87613.

CHKDSK is verifying security descriptors (stage 3 of 5)...
  146176 file SDs/SIDs processed.                                         Cleaning up 87 unused index entries from index $SII of file 0x9.
Cleaning up 87 unused index entries from index $SDH of file 0x9.
Cleaning up 87 unused security descriptors.
Security descriptor verification completed.
  10291 data files processed.                                            CHKDSK is verifying Usn Journal...
  34187632 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x1d31ac9000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ad8000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ba9000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31bad000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31bae000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31c8e000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31c98000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31bae000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31bae000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31c99000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31c99000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31c9a000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31c9a000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31cfb000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d02000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d03000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d03000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d04000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d04000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d65000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d6c000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d6d000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d6d000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d6e000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d6e000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31dcf000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31dd5000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31dd6000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31dd6000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31dd7000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31dd7000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31dd8000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31dd8000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e39000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e3d000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e3e000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e3e000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e3f000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e3f000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e40000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e40000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e41000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e41000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea2000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea4000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea5000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea5000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea6000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea6000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea7000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea7000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea8000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea8000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea9000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea9000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31f8a000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31f8e000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31f8f000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31f8f000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31f90000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31f90000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31f91000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31f91000 for 0x1000 bytes.
Windows replaced bad clusters in file 18723
of name \VMWARE~1\MYVIRT~1\TESTOP~1\WINDOW~1.VME.
  146160 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  3957347 free clusters processed.                                         Free space verification is complete.
Adding 31 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

 195350368 KB total disk space.
 179213184 KB in 132997 files.
     55680 KB in 10292 indexes.
    251992 KB in use by the system.
     65536 KB occupied by the log file.
  15829388 KB available on disk.

      4096 bytes in each allocation unit.
  48837592 total allocation units on disk.
   3957347 allocation units available on disk.

Thanks for the help.

writhziden · Mar 18, 2012

Your external drive was in worse shape, actually. It had some bad clusters that had to be re-mapped. Hard drives come with extra sectors/clusters for this purpose. If bad clusters are found, they are replaced by the extra clusters. If a drive is mechanically failing in such a way that the head is wiping out clusters by physically running into them, eventually the extra clusters end up being used up and the drive stops being able to function properly. This results in a catastrophic hard disk failure.

In your case, it does not appear the drive is failing, but to be sure, you should run the disk check again with both boxes checked and look for the line: Adding XX bad clusters to the Bad Clusters File. Where XX is the number of bad clusters found.

obidon · Mar 26, 2012

Ok well here is the second disk check for my Hitachi drive. This one looks a little bit better.

Code:

Chkdsk was executed in read/write mode.  

Checking file system on F:
Volume label is Hitachi.

CHKDSK is verifying files (stage 1 of 5)...
  146176 file records processed.                                          File verification completed.
  61 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              0 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  166758 index entries processed.                                         Index verification completed.


CHKDSK is verifying security descriptors (stage 3 of 5)...
  146176 file SDs/SIDs processed.                                         Cleaning up 1 unused index entries from index $SII of file 0x9.
Cleaning up 1 unused index entries from index $SDH of file 0x9.
Cleaning up 1 unused security descriptors.
Security descriptor verification completed.
  10292 data files processed.                                            CHKDSK is verifying Usn Journal...
  34188224 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  146160 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  3957342 free clusters processed.                                         Free space verification is complete.
Windows has checked the file system and found no problems.

 195350368 KB total disk space.
 179213204 KB in 132998 files.
     55676 KB in 10293 indexes.
    251996 KB in use by the system.
     65536 KB occupied by the log file.
  15829368 KB available on disk.

      4096 bytes in each allocation unit.
  48837592 total allocation units on disk.
   3957342 allocation units available on disk.

Sorry I took a while to respond, but in the meantime I installed more RAM and a new 1 Terabyte drive. I also moved some data over from my other drives so they have a lot more free space now. Hopefully this should make them a little more stable too.

What else can I do for now to try to make my system more stable?

Thanks for the help and for looking at my logs.

writhziden · Mar 26, 2012

See how things go for now. Report back after a few days of doing your normal routine and let us know how the system is responding. More steps to improve stability may not be necessary if the system is already stable after the steps that have already been done.

obidon · Mar 26, 2012

Well I did have a random BlueScreen yesterday which I think shows that it's still not completely stable. And for some reason I still can't get SP1 to install.

But besides that my HDD's seem to be a little more reliable since they have a lot more free space now. I'm going to do some disk monitoring and diagnosis just to be safe though. Probably using Acronis or WD Utilities and Seatools.

By the way did my jcgriff2 report reveal any other useful information if you can recall?

writhziden · Mar 26, 2012

The only thing that stood out was the hard disk problem of being too corrupt to be usable. Since you cannot get SP1 to install:

Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

obidon · Mar 26, 2012

writhziden said:
The only thing that stood out was the hard disk problem of being too corrupt to be usable. Since you cannot get SP1 to install:

Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

Running the sfc /scannow command from an elevated command prompt works but it never gets to completely finish and make it up to 100%.

It keeps geiving the error "Windows Resource Protection could not perform the requested operation."

Should I keep trying till it makes it up to 100% (which I'm sure will take me probably 50 times or so), or should I run the SFC command in the command prompt at boot using a Windows repair CD?

Or maybe a different technique is recommended?

writhziden · Mar 26, 2012

Try sfc /verifyonly and post back the results.

It needs to be run in an http://www.sevenforums.com/tutorials/783-elevated-command-prompt.html as with the /scannow switch.

obidon · Mar 26, 2012

Ok well I guess it went a lot faster than I thought. I did the command with the /verifyonly switch which completed 100% and then with just the /scannow switch.

For some reason the CBS.log file is only 894 KB right now, but I could've sworn it was around 15 MB before I did the scan. Strange.

Anyway here's the current CBS.log file in its entirety

obidon · Mar 26, 2012

Tried to post it but I guess it was too big. Waited for the server to upload but it timed out several times so I'll just attach it instead.

writhziden · Mar 27, 2012

Code:

2012-03-26 22:04:16, Info                  CSI    00000075 [SR] Verifying 100 (0x0000000000000064) components
2012-03-26 22:04:16, Info                  CSI    00000076 [SR] Beginning Verify and Repair transaction
[COLOR="Red"][B]2012-03-26 22:04:16, Info                  CSI    00000078 [SR] Cannot repair member file [l:20{10}]"IMJPPD.CHM" of Microsoft-Windows-Desktop_Technologies-Text_Input_Services-IME-Japanese-Help, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:17, Info                  CSI    0000007a [SR] Cannot repair member file [l:20{10}]"IMJPPD.CHM" of Microsoft-Windows-Desktop_Technologies-Text_Input_Services-IME-Japanese-Help, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:17, Info                  CSI    0000007b [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"
2012-03-26 22:04:17, Info                  CSI    0000007e [SR] Could not reproject corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMEJP10\HELP"\[l:20{10}]"IMJPPD.CHM"; source file in store is also corrupted[/B][/COLOR]
2012-03-26 22:04:18, Info                  CSI    00000080 [SR] Verify complete

2012-03-26 22:04:23, Info                  CSI    00000095 [SR] Verifying 100 (0x0000000000000064) components
2012-03-26 22:04:23, Info                  CSI    00000096 [SR] Beginning Verify and Repair transaction
[COLOR="Red"][B]2012-03-26 22:04:24, Info                  CSI    00000098 [SR] Cannot repair member file [l:20{10}]"msyhbd.ttf" of Microsoft-Windows-Font-TrueType-MicrosoftYaHeiBold, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch[/B][/COLOR]
2012-03-26 22:04:25, Info                  CSI    00000099 [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[l:20{10}]"msyhbd.ttf" by copying from backup
[COLOR="Red"][B]2012-03-26 22:04:25, Info                  CSI    0000009b [SR] Cannot repair member file [l:20{10}]"msyhbd.ttf" of Microsoft-Windows-Font-TrueType-MicrosoftYaHeiBold, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:25, Info                  CSI    0000009c [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"[/B][/COLOR]
[COLOR="red"][B]2012-03-26 22:04:26, Info                  CSI    0000009f [SR] Could not reproject corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:20{10}]"msyhbd.ttf"; source file in store is also corrupted[/B][/COLOR]
2012-03-26 22:04:27, Info                  CSI    000000a3 [SR] Verify complete

2012-03-26 22:04:27, Info                  CSI    000000a4 [SR] Verifying 100 (0x0000000000000064) components
2012-03-26 22:04:27, Info                  CSI    000000a5 [SR] Beginning Verify and Repair transaction
[COLOR="red"][B]2012-03-26 22:04:29, Info                  CSI    000000a7 [SR] Cannot repair member file [l:16{8}]"msyh.ttf" of Microsoft-Windows-Font-TrueType-MicrosoftYaHei, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:30, Info                  CSI    000000c8 [SR] Cannot repair member file [l:16{8}]"msyh.ttf" of Microsoft-Windows-Font-TrueType-MicrosoftYaHei, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:30, Info                  CSI    000000c9 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"
2012-03-26 22:04:31, Info                  CSI    000000cc [SR] Could not reproject corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:16{8}]"msyh.ttf"; source file in store is also corrupted[/B][/COLOR]
2012-03-26 22:04:32, Info                  CSI    000000ce [SR] Verify complete

2012-03-26 22:04:32, Info                  CSI    000000cf [SR] Verifying 100 (0x0000000000000064) components
2012-03-26 22:04:32, Info                  CSI    000000d0 [SR] Beginning Verify and Repair transaction
[COLOR="Red"][B]2012-03-26 22:04:33, Info                  CSI    000000d2 [SR] Cannot repair member file [l:24{12}]"daunpenh.ttf" of Microsoft-Windows-Font-TrueType-DaunPenh, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:33, Info                  CSI    000000d4 [SR] Cannot repair member file [l:16{8}]"kaiu.ttf" of Microsoft-Windows-Font-TrueType-DFKaiSB, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:36, Info                  CSI    000000d6 [SR] Cannot repair member file [l:16{8}]"kaiu.ttf" of Microsoft-Windows-Font-TrueType-DFKaiSB, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:36, Info                  CSI    000000d7 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"[/B][/COLOR]
2012-03-26 22:04:37, Info                  CSI    000000d8 [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[l:24{12}]"daunpenh.ttf" by copying from backup
2012-03-26 22:04:37, Info                  CSI    000000da [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:24{12}]"daunpenh.ttf" from store
2012-03-26 22:04:37, Info                  CSI    000000dc [SR] Verify complete

2012-03-26 22:04:45, Info                  CSI    000000ef [SR] Verifying 100 (0x0000000000000064) components
2012-03-26 22:04:45, Info                  CSI    000000f0 [SR] Beginning Verify and Repair transaction
[B][COLOR="Red"]2012-03-26 22:04:47, Info                  CSI    000000f2 [SR] Cannot repair member file [l:22{11}]"PINTLGT.IMD" of Microsoft-Windows-IME-Simplified-Chinese-TrigramDictionary, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:48, Info                  CSI    000000f6 [SR] Cannot repair member file [l:22{11}]"PINTLGT.IMD" of Microsoft-Windows-IME-Simplified-Chinese-TrigramDictionary, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:04:48, Info                  CSI    000000f7 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"
2012-03-26 22:04:50, Info                  CSI    000000fa [SR] Could not reproject corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:22{11}]"PINTLGT.IMD"; source file in store is also corrupted[/COLOR][/B]
2012-03-26 22:04:50, Info                  CSI    000000fc [SR] Verify complete

2012-03-26 22:05:01, Info                  CSI    00000121 [SR] Verifying 100 (0x0000000000000064) components
2012-03-26 22:05:01, Info                  CSI    00000122 [SR] Beginning Verify and Repair transaction
[B][COLOR="Red"]2012-03-26 22:05:02, Info                  CSI    00000124 [SR] Cannot repair member file [l:24{12}]"imageres.dll" of Microsoft-Windows-imageres, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:05:05, Info                  CSI    00000125 [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[l:24{12}]"imageres.dll" by copying from backup
2012-03-26 22:05:05, Info                  CSI    00000127 [SR] Cannot repair member file [l:24{12}]"imageres.dll" of Microsoft-Windows-imageres, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-03-26 22:05:05, Info                  CSI    00000128 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"
2012-03-26 22:05:06, Info                  CSI    0000012b [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:24{12}]"imageres.dll"; source file in store is also corrupted[/COLOR][/B]
2012-03-26 22:05:06, Info                  CSI    0000012d [SR] Verify complete

And that was only about 10% of the corruption that is occurring on your system. I strongly advise that you http://www.sevenforums.com/tutorials/3413-repair-install.html Windows 7 ASAP.

Random BSOD's want to figure this out once and for all

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer