Dump Data - bsod, need help thanks

Hi,

First time posted, need help, not sure how to go about analysing the analysis of several minidumps and a memory dump.

I built the troubled system for someone back in august and it is regularly crashing not always BSOD sometimes it just hangs. Anyway I've ran memtest which has found nothing.

The system hangs randomly. Anyway I'm not sure how to read dumps, is there a guide out there or do you just have to be a software dev to get them? Help please, thanks in advance, I've started with the ful memory dump, the8 mini dumps.

[SIZE= "1"]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: 0000005b, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 80677901, address which referenced memory

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


WRITE_ADDRESS: 0000005b

CURRENT_IRQL: 2

FAULTING_IP:
nt!ViFreeMapRegisterFile+1c6
80677901 5f pop edi

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: f78a2e84 -- (.trap fffffffff78a2e84)
ErrCode = 00000002
eax=00000000 ebx=00000000 ecx=08740004 edx=08730003 esi=86701170 edi=86701174
eip=80677901 esp=f78a2ef8 ebp=f78a2f08 iopl=0 vif nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00090246
nt!ViFreeMapRegisterFile+0x1c6:
80677901 5f pop edi
Resetting default scope

LAST_CONTROL_TRANSFER: from 80677901 to 804e0aac

STACK_TEXT:
f78a2e84 80677901 badb0d00 08730003 86701168 nt!KiTrap0E+0x238
f78a2f08 80677d15 86b859f0 00000008 88178f58 nt!ViFreeMapRegisterFile+0x1c6
f78a2f24 baf3df76 86b85af8 86701170 00000008 nt!VfFreeMapRegisters+0x6e
f78a2f5c baf3e6f7 86afaae8 88178f58 f78a2fcb SCSIPORT!SpProcessCompletedRequest+0x172
f78a2fcc 804dcd22 86afaaa4 86afaa30 00000000 SCSIPORT!ScsiPortCompletionDpc+0x2b5
f78a2ff4 804dc88d f78c2bdc 00000000 00000000 nt!KiRetireDpcList+0x61
f78a2ff8 f78c2bdc 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
WARNING: Frame IP not in any known module. Following frames may be wrong.
804dc88d 00000000 00000009 0081850f bb830000 0xf78c2bdc


STACK_COMMAND: kb

FOLLOWUP_IP:
SCSIPORT!SpProcessCompletedRequest+172
baf3df76 83672c00 and dword ptr [edi+2Ch],0

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: SCSIPORT!SpProcessCompletedRequest+172

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: SCSIPORT

IMAGE_NAME: SCSIPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 41107b4b

FAILURE_BUCKET_ID: 0xA_W_VRF_SCSIPORT!SpProcessCompletedRequest+172

BUCKET_ID: 0xA_W_VRF_SCSIPORT!SpProcessCompletedRequest+172

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: bf986924, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: bf986924, address which referenced memory

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


READ_ADDRESS: bf986924

CURRENT_IRQL: 1c

FAULTING_IP:
win32k!sfac_GetSbitBitmap+2e0
bf986924 ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: csrss.exe

LAST_CONTROL_TRANSFER: from 804dc0e0 to bf986924

FAILED_INSTRUCTION_ADDRESS:
win32k!sfac_GetSbitBitmap+2e0
bf986924 ?? ???

STACK_TEXT:
ba32f164 804dc0e0 ba32f610 ba32f900 ba32f30c win32k!sfac_GetSbitBitmap+0x2e0
ba32f188 804dc0b2 ba32f610 ba32f900 ba32f30c nt!KiIdleLoop+0x19
ba32f18c ba32f610 ba32f900 ba32f30c ba32f224 nt!KiSwapProcess+0x54
WARNING: Frame IP not in any known module. Following frames may be wrong.
ba32f198 ba32f224 bf986924 ba32f908 ba32f610 0xba32f610
ba32f3e4 804dc605 ba32f62c ba32f564 00000000 0xba32f224
ba32f3e8 ba32f62c ba32f564 00000000 00000000 nt!KiFindReadyThread+0x4
ba32f3ec ba32f564 00000000 00000000 867000e4 0xba32f62c
ba32f62c ba32f6f4 ba32f800 00000000 40000000 0xba32f564
ba32f630 ba32f800 00000000 40000000 0000000d 0xba32f6f4
ba32f6f4 86165bb4 00000000 ba32f728 ba32f714 0xba32f800
ba32f6f8 00000000 ba32f728 ba32f714 bf83a1a7 0x86165bb4


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!sfac_GetSbitBitmap+2e0
bf986924 ?? ???

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!sfac_GetSbitBitmap+2e0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 43446a58

FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_win32k!sfac_GetSbitBitmap+2e0

BUCKET_ID: 0xD1_CODE_AV_BAD_IP_win32k!sfac_GetSbitBitmap+2e0

Followup: MachineOwner



1: 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: 7d000034, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 806ffa16, address which referenced memory

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


WRITE_ADDRESS: 7d000034

CURRENT_IRQL: 2

FAULTING_IP:
hal!HalCalculateScatterGatherListSize+80
806ffa16 8711 xchg edx,dword ptr [ecx]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from f741adf2 to 806ffa16

STACK_TEXT:
b9d523f0 f741adf2 7d000000 00000001 00000001 hal!HalCalculateScatterGatherListSize+0x80
b9d5246c f741adc9 866192f0 86f5a100 00000001 Ntfs!NtfsFlushVolume+0xfa
b9d5250c f740e385 866192f0 8659d008 b9d50000 Ntfs!NtfsCommonVolumeOpen+0x341
b9d525e4 804e13d9 86f5a020 8659d008 86f47568 Ntfs!NtfsFsdCreate+0x154
b9d525e4 7e010101 86f5a020 8659d008 86f47568 nt!KiTrap0B+0x10f
WARNING: Frame IP not in any known module. Following frames may be wrong.
b9d52760 b9d527a4 f7481687 86f58a00 8659d008 0x7e010101
b9d52764 f7481687 86f58a00 8659d008 8659d204 0xb9d527a4
b9d527a4 f792871f 86ba9ef8 86f47568 f7a99436 PQV2i+0x8687
b9d528b8 8056c063 86f85900 00000000 86b94868 avg7rsxp+0x171f
b9d52930 8056f2a8 00000000 b9d52970 00000240 nt!CmpQuerySecurityDescriptorInfo+0x1d
b9d52984 8057d2d3 00000000 00000000 56ebec00 nt!ObQueryDeviceMapInformation+0x79
b9d52a00 8057d3a2 b9d52ba4 00100003 b9d52b8c nt!NtReplyPort+0x245
b9d52a5c 8057d3e5 b9d52ba4 00100003 b9d52b8c nt!SeCaptureSecurityQos+0x6f
b9d52a9c 804dd99e b9d52ba4 00100003 b9d52b8c nt!SeFreeCapturedSecurityQos+0xa
b9d52aa4 00100003 b9d52b8c b9d52b84 00000000 nt!ZwQueryEvent+0x13
b9d52ad0 804e3577 badb0d00 b9d52b48 00000001 0x100003
b9d52ad4 badb0d00 b9d52b48 00000001 01fffffe nt!__InterlockedDecrement+0x3
b9d52dac 80574128 f469cad0 00000000 00000000 0xbadb0d00
b9d52ddc 804efc81 806319db f469cad0 00000000 nt!NtQueryInformationFile+0x459
b9d52e10 00000000 00000000 00000000 00000000 nt!MmFlushSection+0x111


STACK_COMMAND: kb

FOLLOWUP_IP:
PQV2i+8687
f7481687 ?? ???

SYMBOL_STACK_INDEX: 7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: PQV2i

IMAGE_NAME: PQV2i.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4108c452

SYMBOL_NAME: PQV2i+8687

FAILURE_BUCKET_ID: 0xA_W_PQV2i+8687

BUCKET_ID: 0xA_W_PQV2i+8687

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




0: 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: 00000002, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f79411c0, address which referenced memory

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


READ_ADDRESS: 00000002

CURRENT_IRQL: 2

FAULTING_IP:
USBSTOR!RequestListRemove+c
f79411c0 3300 xor eax,dword ptr [eax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: winlogon.exe

LAST_CONTROL_TRANSFER: from f7941291 to f79411c0

STACK_TEXT:
f798ada8 f7941291 86d11fb4 86d11fa4 86d11fa4 USBSTOR!RequestListRemove+0xc
f798adbc f79413c3 86d11fa4 86d5d3c8 86eb6f54 USBSTOR!UsbDequeueIrp+0x25
f798add8 f793fa52 86d11fa4 86eb6e78 86c831f0 USBSTOR!UsbQueueFlush+0x29
f798adf0 804e13d9 86d11ea0 86eb6e78 86d5d3c8 USBSTOR!USBSTOR_Scsi+0x6c
f798adf0 865c37a8 86d11ea0 86eb6e78 86d5d3c8 nt!KiTrap0B+0x10f
WARNING: Frame IP not in any known module. Following frames may be wrong.
f798ae8c 86814030 86d47438 86d7d0ec 00000000 0x865c37a8
f798ae90 86d47438 86d7d0ec 00000000 86d7d000 0x86814030
f798ae94 86d7d0ec 00000000 86d7d000 86d7d028 0x86d47438
f798ae98 00000000 86d7d000 86d7d028 0000000d 0x86d7d0ec


STACK_COMMAND: kb

FOLLOWUP_IP:
USBSTOR!RequestListRemove+c
f79411c0 3300 xor eax,dword ptr [eax]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: USBSTOR!RequestListRemove+c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: USBSTOR

IMAGE_NAME: USBSTOR.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 41107d6c

FAILURE_BUCKET_ID: 0xD1_USBSTOR!RequestListRemove+c

BUCKET_ID: 0xD1_USBSTOR!RequestListRemove+c

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




0: 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: 001902fe
Arg2: b965b530
Arg3: b965b22c
Arg4: f741dddc

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


EXCEPTION_RECORD: b965b530 -- (.exr ffffffffb965b530)
ExceptionAddress: f741dddc (Ntfs!NtfsCommonCreate+0x00001337)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 3e65b788
Attempt to read from address 3e65b788

CONTEXT: b965b22c -- (.cxr ffffffffb965b22c)
eax=b965b990 ebx=b965b988 ecx=00000000 edx=00000000 esi=86bfefdc edi=b965b858
eip=f741dddc esp=b965b5f8 ebp=b965b834 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
Ntfs!NtfsCommonCreate+0x1337:
f741dddc ffb554ffff84 push dword ptr [ebp-7B0000ACh] ss:0010:3e65b788=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: Picasa2.exe

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

READ_ADDRESS: 3e65b788

BUGCHECK_STR: 0x24

LAST_CONTROL_TRANSFER: from f740ff72 to f741dddc

STACK_TEXT:
b965b834 f740ff72 b965b858 86bfee28 b965b988 Ntfs!NtfsCommonCreate+0x1337
b965b9e0 f7496f70 86bfee28 b965bc00 86f3c020 Ntfs!NtfsNetworkOpenCreate+0x8a
b965ba00 f7a9395a 86bfee28 b965bc00 86fcca08 sr!SrFastIoQueryOpen+0x40
WARNING: Stack unwind information not available. Following frames may be wrong.
b965bb04 8056c063 86fd1900 00000000 86bb1f30 avg7rsw+0x95a
b965bb7c 8056f2a8 00000000 b965bbbc 00000040 nt!CmpQuerySecurityDescriptorInfo+0x1d
b965bbd0 80581e21 00000000 00000000 80571e01 nt!ObQueryDeviceMapInformation+0x79
b965bd54 804dd99e 04159520 041594f8 0415954c nt!PspQueryQuotaLimits+0xa
b965bd70 e1f0fb38 bad3fdcc 00000000 00000000 nt!ZwQueryEvent+0x13
b965bd88 00000000 00000000 00000000 00000023 0xe1f0fb38


FOLLOWUP_IP:
Ntfs!NtfsCommonCreate+1337
f741dddc ffb554ffff84 push dword ptr [ebp-7B0000ACh]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107eea

SYMBOL_NAME: Ntfs!NtfsCommonCreate+1337

STACK_COMMAND: .cxr 0xffffffffb965b22c ; kb

FAILURE_BUCKET_ID: 0x24_Ntfs!NtfsCommonCreate+1337

BUCKET_ID: 0x24_Ntfs!NtfsCommonCreate+1337

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


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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 86556958, The pool entry we were looking for within the page.
Arg3: 865569c0, The next pool entry.
Arg4: 0a0d0005, (reserved)

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


BUGCHECK_STR: 0x19_20

POOL_ADDRESS: 86556958

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 80550fc5 to 805371aa

STACK_TEXT:
f79d6d10 80550fc5 00000019 00000020 86556958 nt!MiRemoveUnusedSegments+0x52f
f79d6d60 804e6da6 86556960 00000000 80566b20 nt!MmMakeProtectNotWriteCopy+0x5d
f79d6d8c 8051a610 e266e198 00000000 86fbb020 nt!MiRemovePageByColor+0xd3
f79d6dac 80574128 00000000 00000000 00000000 nt!CcGetVacbMiss+0x11c
f79d6ddc 804efc81 8051a573 00000000 00000000 nt!NtQueryInformationFile+0x459
f79d6e10 00000000 00000000 00000000 00000000 nt!MmFlushSection+0x111


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRemoveUnusedSegments+52f
805371aa 5d pop ebp

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiRemoveUnusedSegments+52f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x19_20_nt!MiRemoveUnusedSegments+52f

BUCKET_ID: 0x19_20_nt!MiRemoveUnusedSegments+52f

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

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

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000005, USB Bugcheck Code:
Arg2: 86dd70e0
Arg3: 11063038
Arg4: 86d0d868

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


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xFE

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from f6f60cc3 to 805371aa

STACK_TEXT:
b9dcf9c4 f6f60cc3 000000fe 00000005 86dd70e0 nt!MiRemoveUnusedSegments+0x52f
b9dcf9e4 f6f6d516 86dd7028 00002fd0 85fb3000 USBPORT!USBPORT_BugCheck+0x2d
b9dcfa20 f78aa05c 05bbe560 86dd79dc 86d0d868 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x126
b9dcfa44 f78a7ded 86dd79dc 85fb3000 b9dcfa74 usbuhci!UhciPollAsyncEndpoint+0x32
b9dcfa54 f6f5a2ba 86dd79dc 86d0d868 804e56fc usbuhci!UhciPollEndpoint+0x1f
b9dcfa74 f6f5b578 026c6f50 804e56fc 86d0d6f0 USBPORT!USBPORT_PollEndpoint+0xe8
b9dcfa9c f6f5e1fa 86dd7028 50457270 86700a78 USBPORT!USBPORT_CoreEndpointWorker+0x2be
b9dcfaf8 f6f5f1f6 00d0d6f0 ffffffff 804e56fc USBPORT!USBPORT_FlushPendingList+0x4c2
b9dcfb28 f6f66198 86cd6278 b9dcfb60 f6f65d5c USBPORT!USBPORT_QueueTransferUrb+0x248
b9dcfb34 f6f65d5c 86dd7028 86700a78 86422dd8 USBPORT!USBPORT_AsyncTransfer+0x30
b9dcfb60 f6f6adfe 86926030 86dd7028 00000090 USBPORT!USBPORT_ProcessURB+0x3f4
b9dcfb80 f6f541e2 86926030 86700a78 86700a78 USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x7e
b9dcfba4 804e13d9 86700b54 86926188 86422dd8 USBPORT!USBPORT_Dispatch+0x148
b9dcfba4 869150e8 86700b54 86926188 86422dd8 nt!KiTrap0B+0x10f
WARNING: Frame IP not in any known module. Following frames may be wrong.
b9dcfc2c 869150e8 00000000 00001000 00000006 0x869150e8
b9dcfc30 00000000 00001000 00000006 804ecd04 0x869150e8


STACK_COMMAND: kb

FOLLOWUP_IP:
usbuhci!UhciPollAsyncEndpoint+32
f78aa05c ?? ???

SYMBOL_STACK_INDEX: 3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbuhci

IMAGE_NAME: usbuhci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107d62

SYMBOL_NAME: usbuhci!UhciPollAsyncEndpoint+32

FAILURE_BUCKET_ID: 0xFE_usbuhci!UhciPollAsyncEndpoint+32

BUCKET_ID: 0xFE_usbuhci!UhciPollAsyncEndpoint+32

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




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

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 00000104, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 805505a1, address which referenced memory

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


BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiDoubleFaultStack+2a21
805505a1 894804 mov dword ptr [eax+4],ecx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: Ad-Aware.exe

LAST_CONTROL_TRANSFER: from f479e26f to 805505a1

STACK_TEXT:
b8939484 f479e26f 00000000 00000001 206b6444 nt!KiDoubleFaultStack+0x2a21
WARNING: Stack unwind information not available. Following frames may be wrong.
b89394d8 f47aeb5f 868510f0 b89394f8 b8939654 VETEFILE+0x726f
b8939548 f47aebf8 868510f0 00000000 b8939654 VETEFILE+0x17b5f
b89395bc f47aebf8 86c10001 000008db b8939654 VETEFILE+0x17bf8
b8939630 f47ab549 00000000 00000001 b8939654 VETEFILE+0x17bf8
b8939658 f47ab491 866c1000 86dd1680 f47a83ea VETEFILE+0x14549
b89396bc f47a810a 00000010 86eca248 86dd1680 VETEFILE+0x14491
b89396e4 f47a62d6 b8939744 86eca248 86dd1680 VETEFILE+0x1110a
b893971c f4797c85 00000000 86eca248 86dd1680 VETEFILE+0xf2d6
b8939774 f47979a1 86eca248 00000000 00028000 VETEFILE+0xc85
b89397b0 f479772b 86eca248 86be8a00 00000000 VETEFILE+0x9a1
b89397e8 f47976b8 86eca248 b89398ac 00000000 VETEFILE+0x72b
b893981c f47975ca 86eca248 b89398ac 00000000 VETEFILE+0x6b8
b89398cc f7909899 85ea0030 f790bf30 f790be78 VETEFILE+0x5ca
b89398f0 f7908a4c 85ea0030 f790bf30 f790be78 VETMONNT+0x2899
b8939940 f7908b72 85ea0030 f790bf30 f790be78 VETMONNT+0x1a4c
b893999c f7908c65 861c9a64 0000003f 00000000 VETMONNT+0x1b72
b89399b0 f7907904 86f3f9e8 861c98b0 b89399e4 VETMONNT+0x1c65
b8939a00 f7901846 86f3f9e8 861c98b0 861c98c0 VETMONNT+0x904
b8939a5c 804e13d9 86d3cee8 861c98b0 861c98b0 VET_FILT+0x2846
b8939a5c 00000000 86d3cee8 861c98b0 861c98b0 nt!KiTrap0B+0x10f
8056ba01 00000000 00000000 00000000 00000000 0x0


STACK_COMMAND: kb

FOLLOWUP_IP:
VETEFILE+726f
f479e26f ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: VETEFILE+726f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: VETEFILE

IMAGE_NAME: VETEFILE.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 44dbeb2a

FAILURE_BUCKET_ID: 0xC5_2_VETEFILE+726f

BUCKET_ID: 0xC5_2_VETEFILE+726f

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




1: 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: 810036f0, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804e9222, address which referenced memory

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


WRITE_ADDRESS: 810036f0

CURRENT_IRQL: 2

FAULTING_IP:
nt!GUID_DOCK_INTERFACE+306
804e9222 897910 mov dword ptr [ecx+10h],edi

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: IEXPLORE.EXE

LAST_CONTROL_TRANSFER: from 804f107f to 804e9222

STACK_TEXT:
b96ba7e4 804f107f 02837fff c000a0e0 85f47020 nt!GUID_DOCK_INTERFACE+0x306
b96ba87c 804f0ff3 ffffffa4 00000001 85f47020 nt!MmCheckCachedPageState+0xcf
b96baca0 80570962 02838000 c000a0dc 22b74867 nt!CcSetDirtyPinnedData+0xe6
b96bad4c 804dd99e ffffffff 0013e03c 0013e040 nt!NtOpenThreadTokenEx+0x16d
b96bad64 7c90eb94 badb0d00 0013e018 00000000 nt!ZwQueryEvent+0x13
WARNING: Frame IP not in any known module. Following frames may be wrong.
b96bad7c 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!GUID_DOCK_INTERFACE+306
804e9222 897910 mov dword ptr [ecx+10h],edi

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

SYMBOL_NAME: nt!GUID_DOCK_INTERFACE+306

FAILURE_BUCKET_ID: 0xA_W_nt!GUID_DOCK_INTERFACE+306

BUCKET_ID: 0xA_W_nt!GUID_DOCK_INTERFACE+306

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

[/SIZE]

 

Hi,

One minidump is crashed with IRQL x'1c' which is timer IRQL and it is symptom of hardware error.

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: 00000002, memory referenced
Arg2: 00000002, IRQL <-- timer IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f79411c0, address which referenced memory



Your windows is crashed randomly (ie difficult bugcheck code and different failing module) and it is also the symptom of hardware error. Probably the ram is bad. Run memtest to stress test the ram.

 

Hi, goldmercury. Welcome to Windows BBS!

Here are couple links to memory testers.

• Windows Memory Diagnostic
  -
• Memtest86

 

hi thanks have treid both of these, had my machine on last night and it was crashing on the microsoft mem tester, however it was not coming up with errors just hanging. The machine has now been off overnight, have just started it back up and is going through mem tester ok.

I also tried to re-install windows last night however that was also crashing on setup this leads me to believe it is not a dodgy driver but hardware related.

Think its either the CPU (one of the first conroe's of the shelf back in august)

Or the mother board however I don't have a spare CPU or mobo to test. Any ideas.