Win7 x64 Random BSOD's, different bugcheck codes

aSmith · 16 Feb 2012

I just reinstalled windows and some basic programs. The radeon driver is the only 3rd party driver running currently.
No crashes yet.

The reason im writing is that after i started the setup for the first time, i left the system unnattended for a while, and when i came back i saw a BSOD. I re-formatted the partition and the second install had no errors however.

The error i got: DRIVER_IRQL_NOT_LESS_OR_EQUAL; usbhci.sys was blamed.
This might have to do something with the fact that i use a usb pendrive (4GB kingmax) to install windows. :)

UPDATE:
Another crash occured.

Crashdump attached!
Culd this mean that i have a faulty hardware, the motherboard perhaps, or one of it's component: the built in lan or audio?
UPDATE 2:
Another dump, sabe bugcheck code. Shuld i install the chipset driver and others or stay with the windows defaults? As for the catalyst driver, im using 12.1 WHQL so i doubt thathas anything to do with this.

aSmith · 19 Feb 2012

Bump!

2 new crashdumps.

writhziden · 19 Feb 2012

Code:


Loading Dump File [F:\Kingston\BSODDmpFiles\aSmith\2crashdums\021912-12604-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a16000 PsLoadedModuleList = 0xfffff800`02c5b670
Debug session time: Sun Feb 19 09:25:55.669 2012 (GMT-7)
System Uptime: 0 days 1:19:09.770
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {b0fbd9f3f, 2, 1, fffff80002a9e355}

Probably caused by : memory_corruption

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000b0fbd9f3f, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002a9e355, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc5100
 0000000b0fbd9f3f 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerExpiration+195
fffff800`02a9e355 008b8c24a800    add     byte ptr [rbx+0A8248Ch],cl

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xA

PROCESS_NAME:  BFBC2Game.exe

TRAP_FRAME:  fffff80000ba2cd0 -- (.trap 0xfffff80000ba2cd0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000040560009 rbx=0000000000000000 rcx=fffff80002c0bd48
rdx=0000000000000056 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a9e355 rsp=fffff80000ba2e60 rbp=000000000004a556
 r8=fffffa80057224c0  r9=00000000000000c2 r10=0000000000000056
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KiTimerExpiration+0x195:
fffff800`02a9e355 008b8c24a800    add     byte ptr [rbx+0A8248Ch],cl ds:00000000`00a8248c=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a921e9 to fffff80002a92c40

STACK_TEXT:  
fffff800`00ba2b88 fffff800`02a921e9 : 00000000`0000000a 0000000b`0fbd9f3f 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00ba2b90 fffff800`02a90e60 : 00000000`00000000 00000000`00000000 fffffa80`03be68a0 0000000b`0f157ab3 : nt!KiBugCheckDispatch+0x69
fffff800`00ba2cd0 fffff800`02a9e355 : 0000000b`0f152c92 fffff800`00ba2e88 00000000`0004a556 fffff800`02c0bd48 : nt!KiPageFault+0x260
fffff800`00ba2e60 fffff800`02a9e167 : fffff800`02c08ec2 fffffa80`0004a556 00000000`00000000 00000000`00000056 : nt!KiTimerExpiration+0x195
fffff800`00ba2f00 fffff800`02a95765 : 00000000`00000000 fffffa80`03be68a0 00000000`00000000 fffff880`02cc6588 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`02a9557c : 00000000`0018ba08 fffff800`03009895 fffff800`0302f3c0 fffff880`078c2c60 : nt!KyRetireDpcList+0x5
fffff880`078c2ba0 fffff800`02ade993 : fffff800`02a8f1a0 fffff800`02a8f20c 00000000`00000001 00000000`23570028 : nt!KiDispatchInterruptContinue
fffff880`078c2bd0 fffff800`02a8f20c : 00000000`00000001 00000000`23570028 fffffa80`05020701 00000000`00000840 : nt!KiDpcInterruptBypass+0x13
fffff880`078c2be0 00000000`75a97dc4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x1fc
00000000`0018b9d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75a97dc4


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
6 errors : !nt (fffff80002a9e343-fffff80002a9e373)
fffff80002a9e340  ff  ff  ff *00  d6  68  07  00  49  8b  40 *00  49  89  47  18 .....h..I.@.I.G.
fffff80002a9e350  f0  49  83 *00  24  00  8b  8c  24  a8  00  00  00  3b  e9  0f .I..$...$....;..
fffff80002a9e360  85  e4  fe *00  ff  41  83  fe  01  76  16 *ff  8d  54  24  28 .....A...v...T$(
fffff80002a9e370  45  8b  ce *00  8b  c5  48  8b  cf  e8  52  00  00  00  45  33 E.....H...R...E3

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

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

Loading Dump File [F:\Kingston\BSODDmpFiles\aSmith\2crashdums\021712-15147-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a52000 PsLoadedModuleList = 0xfffff800`02c97670
Debug session time: Thu Feb 16 14:17:09.710 2012 (GMT-7)
System Uptime: 0 days 0:44:27.240
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffba0002c6bf92, 2, 0, fffff80002adaae9}

Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+189 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffba0002c6bf92, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002adaae9, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d01100
 ffffba0002c6bf92 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiInsertTimerTable+189
fffff800`02adaae9 410fb74002      movzx   eax,word ptr [r8+2]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  BFHeroes.exe

TRAP_FRAME:  fffff80000ba25a0 -- (.trap 0xfffff80000ba25a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000040e11288 rbx=0000000000000000 rcx=fffff80002c44e80
rdx=fffff80002c6bf50 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002adaae9 rsp=fffff80000ba2730 rbp=0000000000000001
 r8=ffffba0002c6bf90  r9=00000000000000e1 r10=fffff80002c44e80
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KiInsertTimerTable+0x189:
fffff800`02adaae9 410fb74002      movzx   eax,word ptr [r8+2] ds:31a0:ffffba00`02c6bf92=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ace1e9 to fffff80002acec40

STACK_TEXT:  
fffff800`00ba2458 fffff800`02ace1e9 : 00000000`0000000a ffffba00`02c6bf92 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba2460 fffff800`02acce60 : ffffffff`ffffffff ffffffff`ffffffff fffff880`009e7180 fffff800`02c6bf50 : nt!KiBugCheckDispatch+0x69
fffff800`00ba25a0 fffff800`02adaae9 : fffffa80`04ea3050 fffffa80`03e0b980 fffffa80`04ea3050 fffffa80`052f4010 : nt!KiPageFault+0x260
fffff800`00ba2730 fffff800`02ad75fa : ffffffff`fffb6c20 fffffa80`04ea3050 00000000`00000000 fffff880`040224b8 : nt!KiInsertTimerTable+0x189
fffff800`00ba2790 fffff800`02ada43d : fffff800`02c6bf50 fffffa80`03e0b168 fffffa80`03e0b168 00000000`00000000 : nt!KiTimerWaitTest+0x15a
fffff800`00ba2810 fffff800`02ada37e : 00000006`35cc9227 fffff800`00ba2e88 00000000`00029bdf fffff800`02c48e68 : nt!KiProcessExpiredTimerList+0x6d
fffff800`00ba2e60 fffff800`02ada167 : fffff800`02c44ec1 fffffa80`00029bdf fffffa80`04ea3d40 00000000`000000df : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`02ad1765 : 00000000`00000000 fffffa80`03c72060 00000000`00000000 fffff880`04002db0 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`02ad157c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`06c81ba0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiInsertTimerTable+189
fffff800`02adaae9 410fb74002      movzx   eax,word ptr [r8+2]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiInsertTimerTable+189

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+189

BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+189

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

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\Kingston\BSODDmpFiles\aSmith\021612-16458-01\021612-16458-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a0c000 PsLoadedModuleList = 0xfffff800`02c51670
Debug session time: Thu Feb 16 06:05:28.016 2012 (GMT-7)
System Uptime: 0 days 1:13:59.530
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002d71764, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!IoRemoveIoCompletion+164 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002d71764, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


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

FAULTING_IP: 
nt!IoRemoveIoCompletion+164
fffff800`02d71764 c3              ret

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbb100
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ad4588 to fffff80002a88c40

STACK_TEXT:  
fffff880`037b10b8 fffff800`02ad4588 : 00000000`0000001e ffffffff`c0000005 fffff800`02d71764 00000000`00000000 : nt!KeBugCheckEx
fffff880`037b10c0 fffff800`02a882c2 : fffff880`037b1898 ffff0080`058889b0 fffff880`037b1940 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`037b1760 fffff800`02a86bca : fffffa80`00000001 fffffa80`058db060 fffffa80`03b2c220 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`037b1940 fffff800`02d71764 : ffff0000`02a74b36 ffff0080`00000001 ffff0080`037b1b68 ffff0080`037b1b88 : nt!KiGeneralProtectionFault+0x10a
fffff880`037b1ad8 ffff0000`02a74b36 : ffff0080`00000001 ffff0080`037b1b68 ffff0080`037b1b88 ffff0000`02da4201 : nt!IoRemoveIoCompletion+0x164
fffff880`037b1ae0 ffff0080`00000001 : ffff0080`037b1b68 ffff0080`037b1b88 ffff0000`02da4201 fffff880`037b1b98 : 0xffff0000`02a74b36
fffff880`037b1ae8 ffff0080`037b1b68 : ffff0080`037b1b88 ffff0000`02da4201 fffff880`037b1b98 fffff880`037b1b01 : 0xffff0080`00000001
fffff880`037b1af0 ffff0080`037b1b88 : ffff0000`02da4201 fffff880`037b1b98 fffff880`037b1b01 00000000`00000000 : 0xffff0080`037b1b68
fffff880`037b1af8 ffff0000`02da4201 : fffff880`037b1b98 fffff880`037b1b01 00000000`00000000 00000000`00341201 : 0xffff0080`037b1b88
fffff880`037b1b00 fffff880`037b1b98 : fffff880`037b1b01 00000000`00000000 00000000`00341201 fffffa80`058889b0 : 0xffff0000`02da4201
fffff880`037b1b08 fffff880`037b1b01 : 00000000`00000000 00000000`00341201 fffffa80`058889b0 00000000`00000000 : 0xfffff880`037b1b98
fffff880`037b1b10 00000000`00000000 : 00000000`00341201 fffffa80`058889b0 00000000`00000000 fffffa80`058412c0 : 0xfffff880`037b1b01


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!IoRemoveIoCompletion+164
fffff800`02d71764 c3              ret

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!IoRemoveIoCompletion+164

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1E_nt!IoRemoveIoCompletion+164

BUCKET_ID:  X64_0x1E_nt!IoRemoveIoCompletion+164

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

Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...
Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...
Possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
Thanks to JMH for helping with my understanding of this crash.

Thanks to Dave76 for help understanding possible causes.

We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

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 Check Disk (chkdsk) - Read Event Viewer Log
Before you say you already ran Memtest86+, let me say that sometimes when memory is failing, it can pass Memtest86+ a few times (after seven passes each time) and then throw errors the next time. Memory is finicky when it is failing if it is not outright bad. That being said, I recommend running it again...

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.
Download and install the appropriate version of HWINFO: HWiNFO32 for 32-bit Windows 7 or HWiNFO64 for 64-bit Windows 7 to check hardware temperatures by running in sensor-only mode. Start logging the temperature through sensor-only mode when the computer first starts, and let it run during stress or until a crash occurs.

Save the CSV file in a place you will remember, and then compress the CSV file to a zip file and upload to here for us to analyze by following the steps in Screenshots and Files - Upload and Post in Seven Forums.
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. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.
Run Hardware - Stress Test With Prime95 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.

aSmith · 20 Feb 2012

Memtest and windows memory diagnostics (advanced mode) gave no errors.
Video memory stress test run without errors. I will run furmark and prime95 next.
I also had a crash, dump attached.

UPDATE 1-2:
Prime95 run without problems or crashes. (worker window attached)
I also uploaded some hwinfo log files and another crashdump.
I will run furmark next for a few hours to see if it crashes.
Furmark run for hours and no error or crash...Temp logs attached.

Here is the chkdsk info:

Code:

Checking file system on C:
The type of the file system is NTFS.
Volume label is System.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  69376 file records processed.                                          File verification completed.
  63 large file records processed.                                      0 bad file records processed.                                        2 EA records processed.                                              44 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  100548 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  69376 file SDs/SIDs processed.                                         Cleaning up 186 unused index entries from index $SII of file 0x9.
Cleaning up 186 unused index entries from index $SDH of file 0x9.
Cleaning up 186 unused security descriptors.
Security descriptor verification completed.
  15587 data files processed.                                            CHKDSK is verifying Usn Journal...
  35369048 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  69360 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  20159957 free clusters processed.                                         Free space verification is complete.
Adding 1 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

 104836095 KB total disk space.
  23982440 KB in 53507 files.
     40560 KB in 15588 indexes.
         4 KB in bad sectors.
    173263 KB in use by the system.
     65536 KB occupied by the log file.
  80639828 KB available on disk.

      4096 bytes in each allocation unit.
  26209023 total allocation units on disk.
  20159957 allocation units available on disk.

Internal Info:
00 0f 01 00 f2 0d 01 00 3f 1e 02 00 00 00 00 00  ........?.......
7f 00 00 00 2c 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  ................

##############################################

Checking file system on E:
The type of the file system is NTFS.
Volume label is Box.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  512 file records processed.                                          File verification completed.
  0 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)...
  578 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  512 file SDs/SIDs processed.                                         Security descriptor verification completed.
  33 data files processed.                                            CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x4f6460000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x4f6463000 for 0x1000 bytes.
Windows replaced bad clusters in file 63
of name \WINDOW~1\BETON\BACKUP~1\6CC35A~2.VHD.
  496 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  123204231 free clusters processed.                                         Free space verification is complete.
Adding 1 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

 520190975 KB total disk space.
  27291576 KB in 194 files.
       128 KB in 35 indexes.
         4 KB in bad sectors.
     82339 KB in use by the system.
     65536 KB occupied by the log file.
 492816928 KB available on disk.

      4096 bytes in each allocation unit.
 130047743 total allocation units on disk.
 123204232 allocation units available on disk.

Internal Info:
00 02 00 00 f0 00 00 00 ab 01 00 00 00 00 00 00  ................
3a 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 00 00 00 00  ................

aSmith · 22 Feb 2012

Another crash. What shuld i do?
Culd a clean install with the x86 version of windows 7 help?
I it's a hardware problem i will need some help to narrow it down.

(crashdump attached!)

writhziden · 22 Feb 2012

Let's see if your RAM is configured properly. Then we can move on to other troubleshooting steps.

Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

Also, go into your BIOS and post all Voltages (CPU, RAM, NB, IMC, etc.) and all RAM settings (timings, frequency, etc.)

Thanks to Dave76 for help learning RAM Stability

aSmith · 22 Feb 2012

CPU-Z stuff and another crashdump attached.

BIOS
Memory
- SPD: Auto
- Memory frequency: 800Mhz
- Timings: 5-5-5-18

Adv. timings
- ACT to ACT (tRRD): 3
- Rank write to READ: 3
- Write to precharge delay: 6
- Refresh to ACT delay: 42
- read to precharge delay: 3
- Static tRead value: 7
- Static tRead phase adjust: 29

System voltage control: Auto
- All on normal
- Normal CPU Vcore: 1.22500V

writhziden · 22 Feb 2012

Memory looks good. You should run the disk check again. For any drives that do not give the message:
"Windows has checked the file system and found no problems"
run disk check again with both boxes checked. In other words, if it says:
"Windows has made corrections to the file system"
after running the disk check, run the disk check again.

aSmith · 22 Feb 2012

Windows has checked the file system and found no problems. - On all drives.

I also had another crash, and one right aftar that when i tried to reboot.
Both had blue screen errors and it said minidump was made but i found none..
One was memory_management error the other one driver_irql or something :)

writhziden · 22 Feb 2012

Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.