Frequent BSODs,dumps included

Recently I'm getting alot of bsods on my pc (P4 2.6 with HT enabled,512ram 2.5-3-3-6 geil , gygabyte radeon 9600pro , the system is not overclocked in anyway) , mainly IRQL_IS_NOT_LESS_OR_EQUAEL and NON_PAGE_FAULT

*I've ran memtest for a few hours,no errors so far.
*there's no chance of overheating,cpu is usally 40-43 and MB 35-38
*There's also a very low chance of viruses\malware\spyware\etc.

Minidump 1


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


Loading Dump File [C:\WINDOWS\Minidump\Mini122006-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.051019-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Wed Dec 20 19:00:46.562 2006 (GMT+2)
System Uptime: 0 days 1:35:35.134
Loading Kernel Symbols
.....................................................................................................................
Loading unloaded module list
.............
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {124, 1c, 0, 804e1627}

Probably caused by : CLASSPNP.SYS ( CLASSPNP!ClassCompleteRequest+11 )

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

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


READ_ADDRESS: 00000124

CURRENT_IRQL: 1c

FAULTING_IP:
nt!KiUnlinkThread+7
804e1627 8b10 mov edx,[eax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 804e1680 to 804e1627

STACK_TEXT:
80556288 804e1680 82335280 82335288 00000100 nt!KiUnlinkThread+0x7
8055629c 804e177c 00000001 805562b8 00000000 nt!KiUnwaitThread+0x12
805562c8 804e20d7 00000042 81521008 00000000 nt!KiWaitTest+0xab
805562dc 804eb961 82335280 00000001 00000000 nt!KeSetEvent+0x5a
8055630c f8577bf0 8055633c f8577ece 822c0ab8 nt!IopfCompleteRequest+0x189
80556314 f8577ece 822c0ab8 81521008 00000001 CLASSPNP!ClassCompleteRequest+0x11
8055633c 804e18ef 00000000 82262c00 81e24820 CLASSPNP!TransferPktComplete+0x180
8055636c f83926c0 82334ef8 822c40e8 00000000 nt!IopfCompleteRequest+0xa2
80556398 f8392bf6 82262c00 82334ef8 80556413 atapi!IdeProcessCompletedRequest+0x664
80556414 8236447b 822c40a4 822c4030 00000000 atapi!IdePortCompletionDpc+0x204
WARNING: Frame IP not in any known module. Following frames may be wrong.
ffdff980 00000000 f8953000 0025fb82 00000000 0x8236447b


FOLLOWUP_IP:
CLASSPNP!ClassCompleteRequest+11
f8577bf0 5d pop ebp

SYMBOL_STACK_INDEX: 5

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: CLASSPNP!ClassCompleteRequest+11

MODULE_NAME: CLASSPNP

IMAGE_NAME: CLASSPNP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 43446788

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0xA_CLASSPNP!ClassCompleteRequest+11

BUCKET_ID: 0xA_CLASSPNP!ClassCompleteRequest+11

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

 

Minidump 2


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


Loading Dump File [C:\WINDOWS\Minidump\Mini122006-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.051019-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Wed Dec 20 17:24:17.671 2006 (GMT+2)
System Uptime: 0 days 2:44:47.360
Loading Kernel Symbols
.....................................................................................................................
Loading unloaded module list
..................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {9c790420, 0, 804e3061, 0}


Could not read faulting driver name
*** WARNING: Unable to verify timestamp for amon.sys
*** ERROR: Module load completed but symbols could not be loaded for amon.sys
Probably caused by : amon.sys ( amon+2cde )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: 9c790420, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 804e3061, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: 9c790420

FAULTING_IP:
nt!_local_unwind2+3d
804e3061 8b0cb3 mov ecx,[ebx+esi*4]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 804e2f9d to 804e3061

STACK_TEXT:
b84769e8 804e2f9d 82314020 ffffffff b8476a14 nt!_local_unwind2+0x3d
b8476a18 804e13c9 82314020 81707288 b8b3f2b4 nt!_except_handler3+0xd5
b8476a34 804e13c9 81ea2c18 81707288 9d24a000 nt!IopfCallDriver+0x31
b8476a44 804fb06e 00000000 815e35b0 815e35c0 nt!IopfCallDriver+0x31
b8476a58 804fb095 81ea2c18 815e3508 815e35c8 nt!IopPageReadInternal+0xf3
b8476a78 804fadbc 81eb9c98 815e35e8 815e35c8 nt!IoPageRead+0x1b
b8476aec 804e9dc9 0c1698c0 ca28a000 c0328a28 nt!MiDispatchFault+0x280
b8476b40 804f97ca 00000000 ca28a000 00000000 nt!MmAccessFault+0x642
b8476b80 80583afc ca28a000 00000000 b8476cd8 nt!MmCheckCachedPageState+0x476
b8476c10 f82d4e9a fed26518 9d249243 00001000 nt!CcFastCopyRead+0x152
b8476c68 b8af9cde fed26518 b8476cd8 00001000 Ntfs!NtfsCopyReadA+0x1bf
WARNING: Stack unwind information not available. Following frames may be wrong.
b8476c8c b8b00ee0 0022ec50 fed26518 b8476d38 amon+0x2cde
b8476c9c 80581a9e fed26518 b8476cd8 00001000 amon+0x9ee0
b8476d38 804dd98f 00000358 00000000 00000000 nt!NtReadFile+0x2c4
b8476d38 7c90eb94 00000358 00000000 00000000 nt!KiFastCallEntry+0xfc
0022ec78 00000000 00000000 00000000 00000000 0x7c90eb94


FOLLOWUP_IP:
amon+2cde
b8af9cde ?? ???

SYMBOL_STACK_INDEX: b

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: amon+2cde

MODULE_NAME: amon

IMAGE_NAME: amon.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 455c994d

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0x50_amon+2cde

BUCKET_ID: 0x50_amon+2cde

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

 

Minidump 3


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


Loading Dump File [C:\WINDOWS\Minidump\Mini122006-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.051019-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Wed Dec 20 19:07:19.765 2006 (GMT+2)
System Uptime: 0 days 0:05:54.459
Loading Kernel Symbols
....................................................................................................................
Loading unloaded module list
...........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {70, 2, 0, f8014395}

Probably caused by : hidusb.sys ( hidusb!HumReadReport+ed )

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

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


READ_ADDRESS: 00000070

CURRENT_IRQL: 2

FAULTING_IP:
USBPORT!USBPORT_FindUrbInIrpTable+77
f8014395 8b7760 mov esi,[edi+0x60]

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from f801a1f0 to f8014395

STACK_TEXT:
8055605c f801a1f0 8218d028 821dc7f8 820f1650 USBPORT!USBPORT_FindUrbInIrpTable+0x77
805560c4 f801b254 020a0b28 ffffffff 804e56ec USBPORT!USBPORT_FlushPendingList+0x43a
805560f4 f80221f8 820e9e78 8055612c f8021dbc USBPORT!USBPORT_QueueTransferUrb+0x248
80556100 f8021dbc 8218d028 820b2e70 820f1650 USBPORT!USBPORT_AsyncTransfer+0x30
8055612c f8026e60 82008480 8218d028 00000090 USBPORT!USBPORT_ProcessURB+0x3f4
8055614c f8010260 82008480 820b2e70 820b2e70 USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x7e
80556170 804e13c9 820b2f28 820085d8 820f1650 USBPORT!USBPORT_Dispatch+0x148
80556180 f861750a 805561a8 f861b3ef 820b2e70 nt!IopfCallDriver+0x31
80556188 f861b3ef 820b2e70 82008480 820b2e70 usbhub!USBH_PassIrp+0x18
805561a8 f861bc4e 81f4cd50 820b2e70 820f1ba0 usbhub!USBH_PdoUrbFilter+0xbd
805561c4 f86192ee 820f1650 820b2e70 80556208 usbhub!USBH_PdoDispatch+0x202
805561d4 804e13c9 821d8ba8 820b2e70 820f1650 usbhub!USBH_HubDispatch+0x48
805561e4 f7e64e91 820b2e70 81ff7868 81ffe560 nt!IopfCallDriver+0x31
80556208 f7e64567 820f1ba0 820e4cf8 80556227 hidusb!HumReadReport+0xed
80556228 f8677e91 820f1ba0 820b2e70 820b2e70 hidusb!HumInternalIoctl+0x69
8055623c f8679234 820f1ba0 820b2e70 820b2e70 HIDCLASS!HidpCallDriver+0x3f
80556258 f867909c 820f1c6c 81ffe560 805562a3 HIDCLASS!HidpSubmitInterruptRead+0x84
80556290 804e18ef 00000000 820b2e70 000f1c6c HIDCLASS!HidpInterruptReadComplete+0x1d2
805562c0 f8017f63 820b2e70 8209c768 8218d028 nt!IopfCompleteRequest+0xa2
80556328 f8018bd5 820f1650 00000000 8218d7d8 USBPORT!USBPORT_CompleteTransfer+0x373
80556358 f80197d2 026e6f44 8218d0e0 8218d0e0 USBPORT!USBPORT_DoneTransfer+0x137
80556390 f801afc8 8218d028 804e56ec 8218d230 USBPORT!USBPORT_FlushDoneTransferList+0x16c
805563bc f8029023 8218d028 804e56ec 8218d028 USBPORT!USBPORT_DpcWorker+0x224
805563f8 f802919a 8218d028 00000001 80560f00 USBPORT!USBPORT_IsrDpcWorker+0x38f
80556414 821916fb 8218d64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
WARNING: Frame IP not in any known module. Following frames may be wrong.
ffdff980 8218d670 f8953000 00011ea3 00000001 0x821916fb
ffdff984 f8953000 00011ea3 00000001 80556440 0x8218d670
ffdff988 00011ea3 00000001 80556440 00000001 0xf8953000
ffdff98c 00000000 80556440 00000001 00011ea1 0x11ea3


FOLLOWUP_IP:
hidusb!HumReadReport+ed
f7e64e91 8b4d10 mov ecx,[ebp+0x10]

SYMBOL_STACK_INDEX: d

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: hidusb!HumReadReport+ed

MODULE_NAME: hidusb

IMAGE_NAME: hidusb.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3b7d8658

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0xD1_hidusb!HumReadReport+ed

BUCKET_ID: 0xD1_hidusb!HumReadReport+ed

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

 

Minidump 4 (and the last,so far)


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


Loading Dump File [C:\WINDOWS\Minidump\Mini122006-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.051019-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Wed Dec 20 19:11:49.546 2006 (GMT+2)
System Uptime: 0 days 0:03:54.248
Loading Kernel Symbols
...................................................................................................................
Loading unloaded module list
...........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Probably caused by : ntkrnlmp.exe ( nt!KiTrap0E+d0 )

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

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

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

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

LAST_CONTROL_TRANSFER: from 804dc0d0 to 804e2f10

EXCEPTION_RECORD: b873b08c -- (.exr ffffffffb873b08c)
ExceptionAddress: 804e2f10 (nt!_except_handler3+0x00000048)
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000010
NumberParameters: 3
Parameter[0]: 00000000
Parameter[1]: d8205a8c
Parameter[2]: d0000016
Inpage operation failed at d8205a8c, due to I/O error d0000016

STACK_TEXT:
b873abe0 804dc0d0 b873b08c b873eb4c b873ad88 nt!_except_handler3+0x48
b873ac04 804dc0a2 b873b08c b873eb4c b873ad88 nt!ExecuteHandler2+0x26
b873acb4 8050b08b b873b08c b873ad88 d0000016 nt!ExecuteHandler+0x24
b873b070 804de3f3 b873b08c 00000000 b873b0e0 nt!KiDispatchException+0x13e
b873b0d8 804e0a42 b873b16c 804e2f10 badb0d00 nt!CommonDispatchException+0x4d
b873b0d8 804e2f10 b873b16c 804e2f10 badb0d00 nt!KiTrap0E+0x1de
b873b16c 804dc0d0 b873b618 b873eb4c b873b314 nt!_except_handler3+0x48
b873b190 804dc0a2 b873b618 b873eb4c b873b314 nt!ExecuteHandler2+0x26
b873b240 8050b08b b873b618 b873b314 d0000016 nt!ExecuteHandler+0x24
b873b5fc 804de3f3 b873b618 00000000 b873b66c nt!KiDispatchException+0x13e
b873b664 804e0a42 b873b6f8 804e2f10 badb0d00 nt!CommonDispatchException+0x4d
b873b664 804e2f10 b873b6f8 804e2f10 badb0d00 nt!KiTrap0E+0x1de
b873b6f8 804dc0d0 b873bba4 b873eb4c b873b8a0 nt!_except_handler3+0x48
b873b71c 804dc0a2 b873bba4 b873eb4c b873b8a0 nt!ExecuteHandler2+0x26
b873b7cc 8050b08b b873bba4 b873b8a0 d0000016 nt!ExecuteHandler+0x24
b873bb88 804de3f3 b873bba4 00000000 b873bbf8 nt!KiDispatchException+0x13e
b873bbf0 804e0a42 b873bc84 804e2f10 badb0d00 nt!CommonDispatchException+0x4d
b873bbf0 804e2f10 b873bc84 804e2f10 badb0d00 nt!KiTrap0E+0x1de
b873bc84 804dc0d0 b873c130 b873eb4c b873be2c nt!_except_handler3+0x48
b873bca8 804dc0a2 b873c130 b873eb4c b873be2c nt!ExecuteHandler2+0x26
b873bd58 8050b08b b873c130 b873be2c d0000016 nt!ExecuteHandler+0x24
b873c114 804de3f3 b873c130 00000000 b873c184 nt!KiDispatchException+0x13e
b873c17c 804e0a42 b873c210 804e2f10 badb0d00 nt!CommonDispatchException+0x4d
b873c17c 804e2f10 b873c210 804e2f10 badb0d00 nt!KiTrap0E+0x1de
b873c210 804dc0d0 b873c6bc b873eb4c b873c3b8 nt!_except_handler3+0x48
b873c234 804dc0a2 b873c6bc b873eb4c b873c3b8 nt!ExecuteHandler2+0x26
b873c2e4 8050b08b b873c6bc b873c3b8 d0000016 nt!ExecuteHandler+0x24
b873c6a0 804de3f3 b873c6bc 00000000 b873c710 nt!KiDispatchException+0x13e
b873c708 804e0a42 b873c79c 804e2f10 badb0d00 nt!CommonDispatchException+0x4d
b873c708 804e2f10 b873c79c 804e2f10 badb0d00 nt!KiTrap0E+0x1de
b873c79c 804dc0d0 b873cc48 b873eb4c b873c944 nt!_except_handler3+0x48
b873c7c0 804dc0a2 b873cc48 b873eb4c b873c944 nt!ExecuteHandler2+0x26
b873c870 8050b08b b873cc48 b873c944 d0000016 nt!ExecuteHandler+0x24
b873cc2c 804de3f3 b873cc48 00000000 b873cc9c nt!KiDispatchException+0x13e
b873cc94 804e0a42 b873cd28 804e2f10 badb0d00 nt!CommonDispatchException+0x4d
b873cc94 804e2f10 b873cd28 804e2f10 badb0d00 nt!KiTrap0E+0x1de
b873cd28 804dc0d0 b873d1d4 b873eb4c b873ced0 nt!_except_handler3+0x48
b873cd4c 804dc0a2 b873d1d4 b873eb4c b873ced0 nt!ExecuteHandler2+0x26
b873cdfc 8050b08b b873d1d4 b873ced0 d0000016 nt!ExecuteHandler+0x24
b873d1b8 804de3f3 b873d1d4 00000000 b873d228 nt!KiDispatchException+0x13e
b873d220 804e0a42 b873d2b4 804e2f10 badb0d00 nt!CommonDispatchException+0x4d
b873d220 804e2f10 b873d2b4 804e2f10 badb0d00 nt!KiTrap0E+0x1de
b873d2b4 804dc0d0 b873d760 b873eb4c b873d45c nt!_except_handler3+0x48
b873d2d8 804dc0a2 b873d760 b873eb4c b873d45c nt!ExecuteHandler2+0x26
b873d388 8050b08b b873d760 b873d45c d0000016 nt!ExecuteHandler+0x24
b873d744 804de3f3 b873d760 00000000 b873d7b4 nt!KiDispatchException+0x13e
b873d7ac 804e0a42 b873d840 804e2f10 badb0d00 nt!CommonDispatchException+0x4d
b873d7ac 804e2f10 b873d840 804e2f10 badb0d00 nt!KiTrap0E+0x1de
b873d840 804dc0d0 b873dcec b873eb4c b873d9e8 nt!_except_handler3+0x48
b873d864 804dc0a2 b873dcec b873eb4c b873d9e8 nt!ExecuteHandler2+0x26


MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

FOLLOWUP_NAME: MachineOwner

DEBUG_FLR_IMAGE_TIMESTAMP: 4356dee7

FOLLOWUP_IP:
nt!KiTrap0E+d0
804e0934 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+d0

STACK_COMMAND: .trap ffffffffb873ab54 ; kb

FAILURE_BUCKET_ID: TRAP_FRAME_RECURSION

BUCKET_ID: TRAP_FRAME_RECURSION

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

 

Hi,

The first minidump is crashed at IRQL x'1c' which is the clock level IRQL. This is the symptom of faulty ram. The 2nd and 3rd minidump are also related to memory problem. The last system crash is related to bad paging space and it causes windows recovery routines executes recursively. Finally windows ran out of stack and it crashes with bugcheck 7F. Memtest is not 100% accurate as some faulty ram can pass memtest.

Suggestion
1. Run chkdsk /r at safemode and re-allocate paging space
2. Reseat memory module to another memory slot and clean the dust inside the ram slot.
3. If it still crashes, replace the ram.