Random BSOD's on Windows 7 x64

After some google'ing, it would seem that some ati gfx drivers are a cause but on my dumps i dont see anyhink from ati only svchost.exe and some others. can anyone confirm this?
much appreciated.

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\Smungle\031312-18049-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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a11000 PsLoadedModuleList = 0xfffff800`02c4ee50
Debug session time: Mon Mar 12 16:40:00.714 2012 (UTC - 6:00)
System Uptime: 0 days 0:23:07.056
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002d5e7c3, fffff88006a04e30, 0}

Probably caused by : ntkrnlmp.exe ( nt!HvpGetCellPaged+53 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002d5e7c3, Address of the instruction which caused the bugcheck
Arg3: fffff88006a04e30, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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!HvpGetCellPaged+53
fffff800`02d5e7c3 f0480fbaa92806000000 lock bts qword ptr [rcx+628h],0

CONTEXT:  fffff88006a04e30 -- (.cxr 0xfffff88006a04e30)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=000000000063c5e0 rsi=00000000000005e0 rdi=0000000000000000
rip=fffff80002d5e7c3 rsp=fffff88006a05810 rbp=fffff88006a05ca0
 r8=fffff8a000bb8780  r9=000000000000ffff r10=fffffa80066e7080
r11=fffffa800b630b60 r12=0000000000000003 r13=000000000000003c
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!HvpGetCellPaged+0x53:
fffff800`02d5e7c3 f0480fbaa92806000000 lock bts qword ptr [rcx+628h],0 ds:002b:00000000`00000628=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  mscorsvw.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002d5d70a to fffff80002d5e7c3

STACK_TEXT:  
fffff880`06a05810 fffff800`02d5d70a : 00000000`00000000 fffff8a0`00aea010 fffff8a0`00bb8780 00000000`ffffffff : nt!HvpGetCellPaged+0x53
fffff880`06a05870 fffff800`02d5bfc6 : fffff8a0`02e38130 fffff880`06a05b60 fffff880`06a059a0 fffff880`06a059a8 : nt!CmpFindValueByNameFromCache+0xea
fffff880`06a05940 fffff800`02d5b753 : fffff880`06a05c00 fffff880`06a05b60 fffffa80`00000002 00000000`002adbc0 : nt!CmQueryValueKey+0x136
fffff880`06a05a20 fffff800`02a82153 : fffffa80`0b630b60 00000000`0016de38 00000000`00000002 00000000`002adbc0 : nt!NtQueryValueKey+0x381
fffff880`06a05bb0 00000000`77c0feca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0016de18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c0feca


FOLLOWUP_IP: 
nt!HvpGetCellPaged+53
fffff800`02d5e7c3 f0480fbaa92806000000 lock bts qword ptr [rcx+628h],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!HvpGetCellPaged+53

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

STACK_COMMAND:  .cxr 0xfffff88006a04e30 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!HvpGetCellPaged+53

BUCKET_ID:  X64_0x3B_nt!HvpGetCellPaged+53

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

Loading Dump File [D:\Kingston\BSODDmpFiles\Smungle\031212-15880-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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a0b000 PsLoadedModuleList = 0xfffff800`02c48e50
Debug session time: Mon Mar 12 14:34:33.994 2012 (UTC - 6:00)
System Uptime: 0 days 0:38:46.337
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88007721748, fffff88007720fa0, fffff88001315166}

Probably caused by : Ntfs.sys ( Ntfs!NtfsCheckAttributeRecord+25a )

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

2: 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: fffff88007721748
Arg3: fffff88007720fa0
Arg4: fffff88001315166

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


EXCEPTION_RECORD:  fffff88007721748 -- (.exr 0xfffff88007721748)
ExceptionAddress: fffff88001315166 (Ntfs!NtfsCheckAttributeRecord+0x000000000000025a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000002
Attempt to read from address 0000000000000002

CONTEXT:  fffff88007720fa0 -- (.cxr 0xfffff88007720fa0)
rax=fffff880077219f8 rbx=fffff980149af980 rcx=fffff880077219f9
rdx=000001000d28dfd1 rsi=0000000000000003 rdi=fffff980149af9c8
rip=fffff88001315166 rsp=fffff88007721980 rbp=fffff980149af9ca
 r8=0000000000000000  r9=0000000000000001 r10=0000000000000400
r11=fffff880077219f8 r12=0000000000000000 r13=0000000000000003
r14=0000000000000001 r15=fffff980149af9d0
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
Ntfs!NtfsCheckAttributeRecord+0x25a:
fffff880`01315166 0fb6442eff      movzx   eax,byte ptr [rsi+rbp-1] ds:002b:fffff980`149af9cc=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

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:  0000000000000002

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb30e0
 0000000000000002 

FOLLOWUP_IP: 
Ntfs!NtfsCheckAttributeRecord+25a
fffff880`01315166 0fb6442eff      movzx   eax,byte ptr [rsi+rbp-1]

FAULTING_IP: 
Ntfs!NtfsCheckAttributeRecord+25a
fffff880`01315166 0fb6442eff      movzx   eax,byte ptr [rsi+rbp-1]

BUGCHECK_STR:  0x24

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff880013157b5 to fffff88001315166

STACK_TEXT:  
fffff880`07721980 fffff880`013157b5 : fffffa80`0711a180 00000000`00000001 00000000`00000000 00000000`00000030 : Ntfs!NtfsCheckAttributeRecord+0x25a
fffff880`077219f0 fffff880`0130b4dc : fffff880`07721f50 fffffa80`0711a180 fffff8a0`02c31018 00000000`00000701 : Ntfs!NtfsReadMftRecord+0x344
fffff880`07721aa0 fffff880`01345648 : 00000000`00000000 00000000`00000000 fffff8a0`0806fbc0 00000000`00000000 : Ntfs!NtfsLookupInFileRecord+0x6c
fffff880`07721b30 fffff880`01333168 : fffff880`07721f50 fffff8a0`0806fa90 fffff880`013338e4 fffff880`07721c80 : Ntfs!NtfsWalkUpTree+0x10c
fffff880`07721c60 fffff880`0138b650 : 00000000`00000000 fffff880`07721d78 00000000`00000000 fffff880`07721d01 : Ntfs!NtfsBuildNormalizedNameWithTxfIsolation+0x60
fffff880`07721cd0 fffff880`012ce1f9 : 00000000`00000000 00000000`000000fc fffff8a0`0806fbc0 fffff8a0`0806fe10 : Ntfs!NtfsBuildNormalizedNameWithSystemSpecialCases+0x240
fffff880`07721d30 fffff880`012ebe11 : fffff880`07721f50 fffff8a0`0806fbc0 fffff880`07721f50 fffff8a0`0806fb00 : Ntfs! ?? ::NNGAKEGL::`string'+0x150e8
fffff880`07721dd0 fffff880`012ec906 : fffff880`07721f50 fffffa80`08f1dc10 00000000`000000f8 fffffa80`000000fc : Ntfs!NtfsCommonQueryInformation+0x621
fffff880`07721eb0 fffff880`012ecea4 : fffff880`07721f50 fffffa80`08f1dc10 fffffa80`08f1dc10 fffffa80`08f1dc10 : Ntfs!NtfsFsdDispatchSwitch+0x106
fffff880`07721f30 fffff880`010f682c : fffffa80`0785de58 fffffa80`06bb6010 00000000`000000fc fffff880`02f64180 : Ntfs!NtfsFsdDispatchWait+0x14
fffff880`07722120 fffff880`010f65b0 : fffffa80`06bb6010 00000000`00000000 fffffa80`0711a030 fffffa80`08156740 : fltmgr!FltpQueryInformationFile+0xfc
fffff880`07722190 fffff880`010f652d : 00000000`0000000c 00000000`00000000 fffffa80`06bb6010 fffff880`01303079 : fltmgr!FltpGetFileName+0x70
fffff880`077221e0 fffff880`010f6200 : fffff880`077222b0 fffff800`02aa9e28 fffff880`07722308 00000000`00000000 : fltmgr!FltpGetOpenedFileName+0x1d
fffff880`07722210 fffff880`010f62c7 : fffffa80`0711a000 fffff800`02a721b5 fffff880`00000036 00000000`00000000 : fltmgr!FltpCallOpenedFileNameHandler+0x20
fffff880`07722250 fffff880`010f613e : fffffa80`06bb6010 fffff880`010f47ec 00000000`00000000 00000000`00000000 : fltmgr!FltpGetNormalizedFileNameWorker+0x27
fffff880`07722290 fffff880`010d754b : fffffa80`0757b100 00000000`00000000 fffffa80`06ebca00 fffff880`07723000 : fltmgr!FltpCreateFileNameInformation+0xee
fffff880`077222f0 fffff880`010e2ad4 : 00000000`00008000 fffffa80`06ebca00 00000000`00000000 00000000`00000401 : fltmgr!FltpGetFileNameInformation+0x26b
fffff880`07722370 fffff880`0112636b : fffffa80`06bb6010 fffff8a0`08449790 00000000`00000001 fffff880`077224a0 : fltmgr!FltGetFileNameInformation+0x184
fffff880`07722400 fffff880`01124bdb : fffff100`022445c6 00000000`00000001 00000000`00000000 00000000`000d75ed : fileinfo!FIStreamGetInfo+0x11f
fffff880`07722480 fffff880`010d5242 : 00000000`00000000 fffff8a0`08449790 fffffa80`06d56fb0 00000000`00000000 : fileinfo!FIPostCreateCallback+0x1c7
fffff880`07722510 fffff880`010d438b : fffffa80`0711a030 fffffa80`067e3f00 fffffa80`081575b0 fffffa80`081577d0 : fltmgr!FltpPerformPostCallbacks+0x392
fffff880`077225e0 fffff880`010f32b9 : fffffa80`06d56c10 fffffa80`0785d800 fffffa80`06d56c00 fffffa80`076ffa30 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x39b
fffff880`07722670 fffff800`02d7d477 : 00000000`00000004 fffff800`02da1080 fffffa80`08c59010 00000000`00000000 : fltmgr!FltpCreate+0x2a9
fffff880`07722720 fffff800`02d7350f : fffffa80`076ffa30 00000000`00000000 fffffa80`067df910 fffffa80`0711a101 : nt!IopParseDevice+0x5a7
fffff880`077228b0 fffff800`02d78876 : fffffa80`067df910 fffff880`07722a30 fffff8a0`00000040 fffffa80`067284b0 : nt!ObpLookupObjectName+0x32f
fffff880`077229b0 fffff800`02d7f587 : 00000000`000007ff 00000000`00000001 fffffa80`0943b601 00000000`00000180 : nt!ObOpenObjectByName+0x306
fffff880`07722a80 fffff800`02d982a4 : 00000000`011be890 fffff8a0`00100080 fffff8a0`078ec640 00000000`011be8b0 : nt!IopCreateFile+0x2b7
fffff880`07722b20 fffff800`02a7c153 : fffffa80`08b82b30 00000000`00000001 fffffa80`08db4b60 fffff800`02d90094 : nt!NtOpenFile+0x58
fffff880`07722bb0 00000000`774b01ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`011be858 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774b01ea


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsCheckAttributeRecord+25a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

STACK_COMMAND:  .cxr 0xfffff88007720fa0 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCheckAttributeRecord+25a

BUCKET_ID:  X64_0x24_Ntfs!NtfsCheckAttributeRecord+25a

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

Loading Dump File [D:\Kingston\BSODDmpFiles\Smungle\031212-19125-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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a62000 PsLoadedModuleList = 0xfffff800`02c9fe50
Debug session time: Mon Mar 12 12:31:46.294 2012 (UTC - 6:00)
System Uptime: 0 days 0:16:46.262
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa7fa85371a0, 2, 0, fffff88003d98bed}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_TxCsqRemoveIrp+29 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa7fa85371a0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88003d98bed, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0a0e0
 fffffa7fa85371a0 

CURRENT_IRQL:  2

FAULTING_IP: 
USBPORT!USBPORT_TxCsqRemoveIrp+29
fffff880`03d98bed 8b16            mov     edx,dword ptr [rsi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002f1ba10 -- (.trap 0xfffff88002f1ba10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002f1bbc8 rbx=0000000000000000 rcx=fffffa8008537480
rdx=fffffa8006ba8480 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003d98bed rsp=fffff88002f1bba0 rbp=fffffa800a7d1210
 r8=000000004f444648  r9=0000000000000000 r10=fffffa80085371a0
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
USBPORT!USBPORT_TxCsqRemoveIrp+0x29:
fffff880`03d98bed 8b16            mov     edx,dword ptr [rsi] ds:0001:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ad3469 to fffff80002ad3f00

STACK_TEXT:  
fffff880`02f1b8c8 fffff800`02ad3469 : 00000000`0000000a fffffa7f`a85371a0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f1b8d0 fffff800`02ad20e0 : fffffa80`06879c50 fffffa80`06ba8480 fffffa80`06879dc0 fffffa80`085386a0 : nt!KiBugCheckDispatch+0x69
fffff880`02f1ba10 fffff880`03d98bed : fffffa80`085371a0 fffff880`03d9a54a fffffa80`08537ea8 00000000`00000002 : nt!KiPageFault+0x260
fffff880`02f1bba0 fffff800`02b65685 : 00000000`00000000 fffffa80`0a7d1210 fffffa80`06ba8480 fffffa80`08537480 : USBPORT!USBPORT_TxCsqRemoveIrp+0x29
fffff880`02f1bbd0 fffff880`03d9c8d8 : fffffa80`0a7d1002 fffffa80`0a7d1010 00000000`ffffffff fffffa80`08537ea8 : nt!IoCsqRemoveIrp+0x45
fffff880`02f1bc00 fffff880`03d9a64f : fffffa80`08537ea8 fffffa80`085371a0 fffffa80`08538040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x1c8
fffff880`02f1bc60 fffff880`03d8bf89 : fffffa80`08537050 00000000`00000000 fffffa80`08537e02 fffffa80`08537ea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02f1bca0 fffff800`02adf5dc : fffff880`009ec180 fffffa80`08537ea8 fffffa80`08537ec0 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02f1bcd0 fffff800`02adc6fa : fffff880`009ec180 fffff880`009f6fc0 00000000`00000000 fffff880`03d8bdb0 : nt!KiRetireDpcList+0x1bc
fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBPORT!USBPORT_TxCsqRemoveIrp+29
fffff880`03d98bed 8b16            mov     edx,dword ptr [rsi]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  USBPORT!USBPORT_TxCsqRemoveIrp+29

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc07

FAILURE_BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_TxCsqRemoveIrp+29

BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_TxCsqRemoveIrp+29

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

1. Points to hardware as the likely cause. Could also be hard disk corruption... Windows file corruption... Drivers... Graphics card drivers...
2. Typical causes are hard disk errors, Memory problems... Corrupted hard disk file system... Drivers... corrupted SCSI or IDE Drivers...
3. Caused by a USB device or the ports themselves.

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 by doing your normal routine after each step 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 can do your normal routine for a few weeks without a crash, and your crashes are usually more frequent than that, then the problem is likely solved.

• 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
  
  
• Go through the steps in HD Diagnostic
  
  
• 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. 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 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.
  
  
• 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.
  
  
• Start with USB Driver - General Fix for Problems to resolve the USB issues. Also, USB ports can sometimes enter a safe power state to protect the system from power surges due to USB devices. To reset the USB ports to a nominal power state, use a hard reset to resolve hardware and software issues which works for all computers, not just HP Pavilions (minus the HP driver update step).
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. Run Driver Verifier and in step 3, only select Standard settings. Do not select the other two settings in the red boxes.
  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

Thank your for your reply. I will follow steps accordingly and will post back.

Smungle said:

Code:

Windows has made corrections to the file system.

Does the chkdsk check out ok?

At present i am running verifier with the settings ZigZag posted previously. Im going to run it for a week to make sure.

But all normal atm so i cannot thank you enough for your time.
Will keep you posted.[/B]

Disk check should be run again until you receive the message Windows has checked the file system and found no problems


Beyond that, just keep doing what you normally do to cause crashes (or do your normal routine if crashes are random). Verifier should pick up any driver problems if they are the cause of the crashes.

I did just that because i was not sure if it completed ok. (takes a long time) yup says no problems found.

Could chkdsk cause BSoD?

They were quite random so will keep doing as i do and see.

Thank you again.

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

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

CHKDSK is verifying files (stage 1 of 5)...
272896 file records processed. File verification completed.
321 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)...
336034 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
272896 file SDs/SIDs processed. Cleaning up 4 unused index entries from index $SII of file 0x9.
Cleaning up 4 unused index entries from index $SDH of file 0x9.
Cleaning up 4 unused security descriptors.
Security descriptor verification completed.
31570 data files processed. CHKDSK is verifying Usn Journal...
35138752 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
272880 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
233607734 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

976657407 KB total disk space.
41758776 KB in 99145 files.
63608 KB in 31571 indexes.
0 KB in bad sectors.
404087 KB in use by the system.
65536 KB occupied by the log file.
934430936 KB available on disk.

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

Internal Info:
00 2a 04 00 a7 fe 01 00 ab b8 03 00 00 00 00 00 .*..............
12 01 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 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Data corruption can cause blue screen crashes. It will also eventually lead to event viewer errors:

The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on...

where the ellipse is in place to signify which hard disk has file system corruption.

writhziden;1848026[QUOTE said:

The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on...

where the ellipse is in place to signify which hard disk has file system corruption.

Sorry but im a bit confused on this?

It is an example of what can happen to Windows if file system corrections do not take place through running disk check. Windows will start complaining that the disk is corrupt and unusable.

Your disk check fixed file system errors, so you are no longer at risk of getting such a message in your Event Viewer logs.

Fabulous! I will keep running for a week (in verifier) and see if its cured. Thank you for your time so far it doesn't go unappreciated.