BSODs (0xA,0x8E,0x23...)

I'm getting BSOD's as written in the title.
My system has these specs:

Motherboard: VI7 (VIA PT800-8237)

CPU: Intel Pentium 4 3.0GHz (Hyper Threading)

Harddrives:
WDC WD400BB-00FRA0 = Western Digital 40Gb
WDC WD800BB-00JHA0 = Western Digital 80Gb

CD/DVD Drives:
PIONEER DVD-RW DVR-109
SAMSUNG CD-R/RW SW-252B

Legend 512mb Ram (Previously Kingmax 512mb)

ABIT Siluro Geforce FX5200

AC'97 Soundcard (On Board)

PSU: PT-A400w (ATX P4 Power Supply)

Windows XP Professional SP2
Kernel Version: 5.1.2600.2622

To fix this problem I have tried to:
Disable Onboard Audio and Lan
Change Ram, as you can see I use to have Kingmax
Used Different hard drive
Changed OS, Windows 2000
Used, different drivers for Audio, motherboard,Graphics Card, Lan.

I'm stumped with figuring out what the cause of this is, I'm at the stage of thinking its the CPU and Motherboard out of guessing.

Dumps are below

 

Dump1

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 73, {1, c000017d, 1, bb603bb8}

Probably caused by : ntkrnlmp.exe ( nt!CmpInitializeHiveList+2b1 )

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

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

CONFIG_LIST_FAILED (73)
Indicates that one of the core system hives cannot be linked in the
registry tree. The hive is valid, it was loaded OK. Examine the 2nd
bugcheck argument to see why the hive could not be linked in the
registry tree.
This can be either SAM, SECURITY, SOFTWARE or DEFAULT. One common reason
for this to happen is if you are out of disk space on the system drive
(in which case param 2 is 0xC000017D - STATUS_NO_LOG_SPACE) or an attempt
to allocate pool has failed (in which case param 2 is 0xC000009A -
STATUS_INSUFFICIENT_RESOURCES). Other status codes must be individually
investigated.
Arguments:
Arg1: 00000001, 1
Arg2: c000017d, Indicates the NT status code that tripped Windows into
thinking that it had failed to load the hive.
Arg3: 00000001, Index of hive in hivelist
Arg4: bb603bb8, Pointer to UNICODE_STRING containing filename of hive

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


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x73

LAST_CONTROL_TRANSFER: from 8061577e to 805371aa

STACK_TEXT:
bb603b74 8061577e 00000073 00000001 c000017d nt!KeBugCheckEx+0x1b
bb603cc4 805b5c1e 805ae425 bb603cdc 805b5c67 nt!CmpInitializeHiveList+0x2b1
bb603cd0 805b5c67 00000000 bb603ce8 804dd99f nt!CmpCmdInit+0x53
bb603cdc 804dd99f 00000000 bb603d64 804e39c3 nt!NtInitializeRegistry+0xba
bb603cdc 804e39c3 00000000 bb603d64 804e39c3 nt!KiFastCallEntry+0xfc
bb603d58 804dd99f 00000000 0015fecc 7c90eb94 nt!ZwInitializeRegistry+0x11
bb603d58 7c90eb94 00000000 0015fecc 7c90eb94 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0015fecc 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!CmpInitializeHiveList+2b1
8061577e cc int 3

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!CmpInitializeHiveList+2b1

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

FAILURE_BUCKET_ID: 0x73_nt!CmpInitializeHiveList+2b1

BUCKET_ID: 0x73_nt!CmpInitializeHiveList+2b1

Followup: MachineOwner
_____________________________________________________


*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {87, 2, 1, 80500c32}

Probably caused by : memory_corruption ( nt!MiRestoreTransitionPte+a5 )

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

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

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


WRITE_ADDRESS: 00000087

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRestoreTransitionPte+a5
80500c32 ff4910 dec dword ptr [ecx+0x10]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 80500d31 to 80500c32

STACK_TEXT:
f8960af4 80500d31 81dbf920 ffffffff 81f98368 nt!MiRestoreTransitionPte+0xa5
f8960b0c 80500a36 81dbf8e8 804fb22b e2a3b940 nt!MiRemovePageFromList+0xd5
f8960b14 804fb22b e2a3b940 8bfe1cc6 00000000 nt!MiRemoveAnyPage+0x56
f8960b44 804fae8a 00010000 e2a3b940 81dbf978 nt!MiResolveMappedFileFault+0x3d2
f8960b74 804e9a5f 00000000 cfad0000 c033eb40 nt!MiResolveProtoPteFault+0x122
f8960bf0 804ec48a 00000000 cfad0000 c033eb40 nt!MiDispatchFault+0x13b
f8960c40 804f842b 00000000 cfad0000 00000000 nt!MmAccessFault+0x5bc
f8960c80 80506221 cfad0000 00000000 80556d18 nt!MmCheckCachedPageState+0x461
f8960d2c 80505fc2 823c6200 80561b40 823c9da8 nt!CcPerformReadAhead+0x1f1
f8960d74 804e47fe 823c6200 00000000 823c9da8 nt!CcWorkerThread+0x147
f8960dac 8057dfed 823c6200 00000000 00000000 nt!ExpWorkerThread+0x100
f8960ddc 804fa477 804e4729 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!MiRestoreTransitionPte+a5
80500c32 ff4910 dec dword ptr [ecx+0x10]

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!MiRestoreTransitionPte+a5

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 41108004

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_W_nt!MiRestoreTransitionPte+a5

BUCKET_ID: 0xA_W_nt!MiRestoreTransitionPte+a5

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

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {a1280000, 0, b4f34e46, 0}


Could not read faulting driver name
Probably caused by : kmixer.sys ( kmixer!SuperCopy+a6 )

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: a1280000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: b4f34e46, 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: a1280000

FAULTING_IP:
kmixer!SuperCopy+a6
b4f34e46 0f6f16 movq mm2,qword ptr [esi]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from b4f2718e to b4f34e46

STACK_TEXT:
b50e3ccc b4f2718e 00000002 000001b9 000001b9 kmixer!SuperCopy+0xa6
b50e3d50 b4f15df0 81ed5880 81de3318 00000000 kmixer!MixOneBuff+0x62e
b50e3d84 b4f161fd 81de3318 00000000 00000000 kmixer!MxWorker+0x1c0
b50e3dac 80574128 81ed5880 00000000 00000000 kmixer!MxPrivateWorkerThread+0xad
b50e3ddc 804efc81 b4f16150 81ed5880 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
kmixer!SuperCopy+a6
b4f34e46 0f6f16 movq mm2,qword ptr [esi]

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: kmixer!SuperCopy+a6

MODULE_NAME: kmixer

IMAGE_NAME: kmixer.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107d32

FAILURE_BUCKET_ID: 0x50_kmixer!SuperCopy+a6

BUCKET_ID: 0x50_kmixer!SuperCopy+a6

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

_________________________________________________

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 23, {e0100, ba0c98c0, ba0c95bc, 8057da37}

Probably caused by : Fastfat.sys ( Fastfat!FatReadDirectoryFile+92 )

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

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

FAT_FILE_SYSTEM (23)
If you see FatExceptionFilter 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: 000e0100
Arg2: ba0c98c0
Arg3: ba0c95bc
Arg4: 8057da37

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


EXCEPTION_RECORD: ba0c98c0 -- (.exr ffffffffba0c98c0)
ExceptionAddress: 8057da37 (nt!CcMapData+0x000000ef)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: c5780000
Attempt to read from address c5780000

CONTEXT: ba0c95bc -- (.cxr ffffffffba0c95bc)
eax=0000000f ebx=0000000e ecx=c5780000 edx=00000000 esi=81dcb720 edi=00000000
eip=8057da37 esp=ba0c9988 ebp=ba0c99d4 iopl=0 nv up ei ng nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293
nt!CcMapData+0xef:
8057da37 8a0c0a mov cl,[edx+ecx] ds:0023:c5780000=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

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

READ_ADDRESS: c5780000

BUGCHECK_STR: 0x23

LAST_CONTROL_TRANSFER: from bb6dfa8d to 8057da37

STACK_TEXT:
ba0c99d4 bb6dfa8d 82257118 ba0c9a00 00001000 nt!CcMapData+0xef
ba0c9a08 bb6dfd40 81e15230 e1010aa0 00000000 Fastfat!FatReadDirectoryFile+0x92
ba0c9af4 bb6de2e7 81e15230 e1010aa0 e1bb6d08 Fastfat!FatLocateDirent+0x14a
ba0c9c34 bb6df63d 81e15230 824e2e48 ba0c9c88 Fastfat!FatQueryDirectory+0x4e1
ba0c9c44 bb6deb75 81e15230 824e2e48 82230020 Fastfat!FatCommonDirectoryControl+0x3e
ba0c9c88 804e13d9 82230020 824e2e48 806ff428 Fastfat!FatFsdDirectoryControl+0x3e
ba0c9c98 80672145 8228a6b8 82294388 824e2e00 nt!IopfCallDriver+0x31
ba0c9cbc bb6fa459 ba0c9cf8 804e13d9 8228a6b8 nt!IovCallDriver+0xa0
ba0c9cc4 804e13d9 8228a6b8 824e2e48 806ff428 sr!SrPassThrough+0x31
ba0c9cd4 80672145 8288ee58 806ff410 824e2e48 nt!IopfCallDriver+0x31
ba0c9cf8 8056f50b ba0c9d64 01f3f2b8 8057fad8 nt!IovCallDriver+0xa0
ba0c9d0c 8057fb35 8228a6b8 824e2e48 81e8d288 nt!IopSynchronousServiceTail+0x60
ba0c9d30 804dd99f 00000418 00000000 00000000 nt!NtQueryDirectoryFile+0x5d
ba0c9d30 7c90eb94 00000418 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
01f3f590 00000000 00000000 00000000 00000000 0x7c90eb94


FOLLOWUP_IP:
Fastfat!FatReadDirectoryFile+92
bb6dfa8d f6d8 neg al

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Fastfat!FatReadDirectoryFile+92

MODULE_NAME: Fastfat

IMAGE_NAME: Fastfat.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107eb7

STACK_COMMAND: .cxr 0xffffffffba0c95bc ; kb

FAILURE_BUCKET_ID: 0x23_Fastfat!FatReadDirectoryFile+92

BUCKET_ID: 0x23_Fastfat!FatReadDirectoryFile+92

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

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 23, {e0100, bb63f4c4, bb63f1c0, 804ebeb4}

Probably caused by : Fastfat.sys ( Fastfat!FatReadDirectoryFile+92 )

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

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

FAT_FILE_SYSTEM (23)
If you see FatExceptionFilter 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: 000e0100
Arg2: bb63f4c4
Arg3: bb63f1c0
Arg4: 804ebeb4

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


EXCEPTION_RECORD: bb63f4c4 -- (.exr ffffffffbb63f4c4)
ExceptionAddress: 804ebeb4 (nt!CcGetVirtualAddress+0x00000014)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 000000d0
Attempt to read from address 000000d0

CONTEXT: bb63f1c0 -- (.cxr ffffffffbb63f1c0)
eax=00001000 ebx=00000000 ecx=bb63f62c edx=00001000 esi=000000d0 edi=00000001
eip=804ebeb4 esp=bb63f58c ebp=bb63f598 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!CcGetVirtualAddress+0x14:
804ebeb4 8b0e mov ecx,[esi] ds:0023:000000d0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 3

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

READ_ADDRESS: 000000d0

BUGCHECK_STR: 0x23

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from 8057d9f7 to 804ebeb4

STACK_TEXT:
bb63f598 8057d9f7 00000000 00001000 00000000 nt!CcGetVirtualAddress+0x14
bb63f600 bb6dfa8d 81e02b60 bb63f62c 00001000 nt!CcMapData+0x8b
bb63f634 bb6dfd40 82113c20 e1496d80 00001000 Fastfat!FatReadDirectoryFile+0x92
bb63f720 bb6e1311 82113c20 e1496d80 bb63f7a0 Fastfat!FatLocateDirent+0x14a
bb63f974 bb6dece0 82113c20 83598e48 82288c30 Fastfat!FatCommonCreate+0xbe4
bb63f9b8 804e13d9 82288c30 83598e48 806ff428 Fastfat!FatFsdCreate+0x52
bb63f9c8 80672145 83598fd0 8228d770 83598e48 nt!IopfCallDriver+0x31
bb63f9ec bb6ff90e 8228d6b8 82231980 8214bb00 nt!IovCallDriver+0xa0
bb63fa38 804e13d9 8228d770 00000002 806ff428 sr!SrCreate+0x1e8
bb63fa48 80672145 83598e58 83598e48 8214bb48 nt!IopfCallDriver+0x31
bb63fa6c 8057ccc7 822328e8 81e179cc bb63fc04 nt!IovCallDriver+0xa0
bb63fb4c 8056c063 82232900 00000000 81e17928 nt!IopParseDevice+0xa58
bb63fbc4 8056f2a8 00000000 bb63fc04 00000040 nt!ObpLookupObjectName+0x53c
bb63fc18 8057d2d3 00000000 00000000 bb57b001 nt!ObOpenObjectByName+0xea
bb63fc94 8057d3a2 008aec48 c0110080 008aebe8 nt!IopCreateFile+0x407
bb63fcf0 8057d3e5 008aec48 c0110080 008aebe8 nt!IoCreateFile+0x8e
bb63fd30 804dd99f 008aec48 c0110080 008aebe8 nt!NtCreateFile+0x30
bb63fd30 7c90eb94 008aec48 c0110080 008aebe8 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
008aec40 00000000 00000000 00000000 00000000 0x7c90eb94


FOLLOWUP_IP:
Fastfat!FatReadDirectoryFile+92
bb6dfa8d f6d8 neg al

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 2

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Fastfat!FatReadDirectoryFile+92

MODULE_NAME: Fastfat

IMAGE_NAME: Fastfat.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107eb7

STACK_COMMAND: .cxr 0xffffffffbb63f1c0 ; kb

FAILURE_BUCKET_ID: 0x23_Fastfat!FatReadDirectoryFile+92

BUCKET_ID: 0x23_Fastfat!FatReadDirectoryFile+92

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

_______________________________________________________________

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {4, 2, 0, 804e7eb5}

Probably caused by : memory_corruption ( nt!MiRemovePageByColor+6a )

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

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


READ_ADDRESS: 00000004

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRemovePageByColor+6a
804e7eb5 8b4804 mov ecx,[eax+0x4]

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 8051a327 to 804e7eb5

STACK_TEXT:
baf0fce8 8051a327 c0300140 c0050d94 81ddb9e0 nt!MiRemovePageByColor+0x6a
baf0fd00 804ea841 14365000 c0050d94 81ddb9e0 nt!MiResolveDemandZeroFault+0xa6
baf0fd4c 804e0944 00000001 14365000 00000001 nt!MmAccessFault+0x8a4
baf0fd4c 7c910c71 00000001 14365000 00000001 nt!KiTrap0E+0xd0
WARNING: Frame IP not in any known module. Following frames may be wrong.
0720f958 00000000 00000000 00000000 00000000 0x7c910c71


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!MiRemovePageByColor+6a
804e7eb5 8b4804 mov ecx,[eax+0x4]

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!MiRemovePageByColor+6a

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiRemovePageByColor+6a

BUCKET_ID: 0xA_nt!MiRemovePageByColor+6a

Followup: MachineOwner
---------
________________________________________________________
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {b4804488, 2, 1, 804e7ed7}

Probably caused by : memory_corruption ( nt!MiRemovePageByColor+8d )

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

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

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


WRITE_ADDRESS: b4804488

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRemovePageByColor+8d
804e7ed7 8954cb08 mov [ebx+ecx*8+0x8],edx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 804e958d to 804e7ed7

STACK_TEXT:
f88b6814 804e958d 00000000 00008000 00000000 nt!MiRemovePageByColor+0x8d
f88b6840 806ad2bd 822dc020 00000000 00000044 nt!MmZeroPageThread+0x9f
f88b6dac 80574128 80087000 00000000 00000000 nt!Phase1Initialization+0x1287
f88b6ddc 804efc81 806ae7cb 80087000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!MiRemovePageByColor+8d
804e7ed7 8954cb08 mov [ebx+ecx*8+0x8],edx

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!MiRemovePageByColor+8d

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_W_nt!MiRemovePageByColor+8d

BUCKET_ID: 0xA_W_nt!MiRemovePageByColor+8d

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

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf801fa9, b9fcdc44, 0}

Probably caused by : win32k.sys ( win32k!xxxRealInternalGetMessage+e4 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf801fa9, The address that the exception occurred at
Arg3: b9fcdc44, Trap Frame
Arg4: 00000000

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


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

FAULTING_IP:
win32k!xxxRealInternalGetMessage+e4
bf801fa9 3998f0000000 cmp [eax+0xf0],ebx

TRAP_FRAME: b9fcdc44 -- (.trap ffffffffb9fcdc44)
ErrCode = 00000000
eax=00eceae6 ebx=00000000 ecx=e23ed0a8 edx=00000000 esi=e2531990 edi=e270f418
eip=bf801fa9 esp=b9fcdcb8 ebp=b9fcdce8 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
win32k!xxxRealInternalGetMessage+0xe4:
bf801fa9 3998f0000000 cmp [eax+0xf0],ebx ds:0023:00ecebd6=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from bf80373a to bf801fa9

STACK_TEXT:
b9fcdce8 bf80373a b9fcdd14 00000000 00000000 win32k!xxxRealInternalGetMessage+0xe4
b9fcdd48 804dd99f 01f8ff98 00000000 00000000 win32k!NtUserPeekMessage+0x40
b9fcdd48 7c90eb94 01f8ff98 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
01f8ff44 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
win32k!xxxRealInternalGetMessage+e4
bf801fa9 3998f0000000 cmp [eax+0xf0],ebx

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: win32k!xxxRealInternalGetMessage+e4

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 43446a58

FAILURE_BUCKET_ID: 0x8E_win32k!xxxRealInternalGetMessage+e4

BUCKET_ID: 0x8E_win32k!xxxRealInternalGetMessage+e4

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

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 80576f73, f7e2b298, 0}

Probably caused by : ntkrnlmp.exe ( nt!HvpGetCellMapped+5f )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 80576f73, The address that the exception occurred at
Arg3: f7e2b298, Trap Frame
Arg4: 00000000

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!HvpGetCellMapped+5f
80576f73 8b4304 mov eax,[ebx+0x4]

TRAP_FRAME: f7e2b298 -- (.trap fffffffff7e2b298)
ErrCode = 00000000
eax=00001c17 ebx=00001c17 ecx=820130e0 edx=00000002 esi=e1960b60 edi=00000061
eip=80576f73 esp=f7e2b30c ebp=f7e2b354 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!HvpGetCellMapped+0x5f:
80576f73 8b4304 mov eax,[ebx+0x4] ds:0023:00001c1b=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 805803e2 to 80576f73

STACK_TEXT:
f7e2b354 805803e2 e1960b60 005c0061 cf9d0024 nt!HvpGetCellMapped+0x5f
f7e2b37c 80580062 e1960b60 cf9d0048 f7e2b448 nt!CmpFindNameInList+0x26
f7e2b3f0 8057fff7 e13360e0 f7e2b448 00000001 nt!CmSetValueKey+0xd0
f7e2b484 804dd99f 000005e0 02e08784 00000000 nt!NtSetValueKey+0x228
f7e2b484 7c90eb94 000005e0 02e08784 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
02e0875c 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!HvpGetCellMapped+5f
80576f73 8b4304 mov eax,[ebx+0x4]

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!HvpGetCellMapped+5f

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

FAILURE_BUCKET_ID: 0x8E_nt!HvpGetCellMapped+5f

BUCKET_ID: 0x8E_nt!HvpGetCellMapped+5f

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

 

______________________________________________

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {c4, 1c, 0, 804dc2ca}

Probably caused by : ntkrnlmp.exe ( nt!KiFindReadyThread+7c )

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

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

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


READ_ADDRESS: 000000c4

CURRENT_IRQL: 1c

FAULTING_IP:
nt!KiFindReadyThread+7c
804dc2ca 85b824010000 test [eax+0x124],edi

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 804e1bc2 to 804dc2ca

STACK_TEXT:
f866ecd0 804e1bc2 81f23e08 81f23e60 81f23da8 nt!KiFindReadyThread+0x7c
f866ece0 804e1608 f866ed64 0132fbf4 0132fc14 nt!KiSwapThread+0x2a
f866ed0c 8056dbb7 00000001 00000000 f866ed2c nt!KeDelayExecutionThread+0x1c9
f866ed54 804dd99f 00000000 0132fc14 0132fc3c nt!NtDelayExecution+0x87
f866ed54 7c90eb94 00000000 0132fc14 0132fc3c nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0132fc3c 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!KiFindReadyThread+7c
804dc2ca 85b824010000 test [eax+0x124],edi

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiFindReadyThread+7c

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

FAILURE_BUCKET_ID: 0xA_nt!KiFindReadyThread+7c

BUCKET_ID: 0xA_nt!KiFindReadyThread+7c

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

______________________________________________________

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {4, 2, 1, f878750f}

Probably caused by : mouclass.sys ( mouclass!MouseClassDequeueRead+1b )

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

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

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


WRITE_ADDRESS: 00000004

CURRENT_IRQL: 2

FAULTING_IP:
mouclass!MouseClassDequeueRead+1b
f878750f 894a04 mov [edx+0x4],ecx

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from f8787f8a to f878750f

STACK_TEXT:
f88baf48 f8787f8a 8225d0e8 00000000 8216d0d8 mouclass!MouseClassDequeueRead+0x1b
f88baf68 f85a70cb 00000018 81f7c008 81f7c020 mouclass!MouseClassServiceCallback+0x50
f88bafcc 804dcd22 8216d230 0116d020 00000000 i8042prt!I8042MouseIsrDpc+0xf0
f88baff4 804dc88d f88b6784 00000000 00000000 nt!KiRetireDpcList+0x61
f88baff8 f88b6784 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
WARNING: Frame IP not in any known module. Following frames may be wrong.
804dc88d 00000000 00000009 0081850f bb830000 0xf88b6784


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
mouclass!MouseClassDequeueRead+1b
f878750f 894a04 mov [edx+0x4],ecx

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: mouclass!MouseClassDequeueRead+1b

MODULE_NAME: mouclass

IMAGE_NAME: mouclass.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107b08

FAILURE_BUCKET_ID: 0xD1_W_mouclass!MouseClassDequeueRead+1b

BUCKET_ID: 0xD1_W_mouclass!MouseClassDequeueRead+1b

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

And theres more where they came from, the computer produces around 4/5 of them daily.

 

Hardware problem

Hi,

One minidump is crashed with bugcheck 0A at IRQL x'1c' and this is the sign of hardware. One minodump is crashed with nt!MmAccessFault and it is the sign of faulty ram. Your Windows are crashed with different bugcheck code and they are signs of hardware error.


STACK_TEXT:
baf0fce8 8051a327 c0300140 c0050d94 81ddb9e0 nt!MiRemovePageByColor+0x6a
baf0fd00 804ea841 14365000 c0050d94 81ddb9e0 nt!MiResolveDemandZeroFault+0xa6
baf0fd4c 804e0944 00000001 14365000 00000001 nt!MmAccessFault+0x8a4 <-- faulty ram
baf0fd4c 7c910c71 00000001 14365000 00000001 nt!KiTrap0E+0xd0
WARNING: Frame IP not in any known module. Following frames may be wrong.
0720f958 00000000 00000000 00000000 00000000 0x7c910c71

Suggestion
Run memtest to stress test the ram.

 

My old ram was faulty, but is it possible that when I bought new ram, its faulty as well?
Or could there be a motherboard problem?