I've gone around looking for forums that provide fast and clear answers to the members. I decided to register here and give it a shot.

My computer is in critical condition.

Intel P4 2.6Ghz
Intel 865GBF Integrated Motherboard
1024MB Kingston PC3200 400Mhz (2x512)
80GB HD
RetailStar 465W PS
Windows XP Home
ATI Radeon 9550 256MB AGP 8x
Creative SoundBlaster Live! 24-Bit

I've been getting numerous BSOD errors. They include:

DRIVER_IRQL_NOT_LESS_OR_EQUAL
IRQL_NOT_LESS_OR_EQUAL

I solved those two when I downgraded my video drivers from 6.4 to 6.1 Catalyst. Haven't gotten them anymore.

However, I've been getting these:

PAGE_FAULT_IN_NONPAGED_AREA
PFN_LIST_CORRUPT
PFN_FILE_CORRUPT
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
BAD_POOL_CALLER

These problems started about a month ago when my 4-month old Antec 350W's fans both stopped spinning. I then bought the RetailStar 465W which I now have and a day after that, upgraded my memory with another stick of 512MB. Then came the problems.

Even a repair installation of Windows XP didn't help.
Today I ran Memtest and it found 88 errors with my memory. The test ended with a PAGE_FAULT BSOD. I then tested the new slot alone - no errors. Then I tested the old one by itself and once again, no errors. Then I tested them both together, but this time in single channel mode since they were both set on dual channel. This time there were no errors and I was able to play a few games. Performance was normal.

However, after finishing up after an hour of Star Wars Battlefront II, I received the 0x0000007E STOP message. After debugging the dump, I found out it is SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M.

After leaving my computer on desktop for a few minutes, I came back only to see a PAGE_FAULT BSOD. I now decided to download the debugging tools and get to the bottom of these errors.

I have txt files for about 5 dumps, first one is the latest PAGE_FAULT and I got it exactly an hour ago. I don't know if it matters, but today after I changed the memory slots, the computer makes a short beep everytime it's turned on.

Here are the dumps, I do hope someone has the time to analyze them:


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


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sat Apr 29 18:12:37.312 2006 (GMT-4)
System Uptime: 0 days 3:35:35.900
Loading Kernel Symbols
.................................................. .................................................. ......................
Loading User Symbols
Loading unloaded module list
.........................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {86fed2c4, 1, 8054b280, 0}


Could not read faulting driver name
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1e8 )

Followup: Pool_corruption
---------

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: 86fed2c4, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 8054b280, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: 86fed2c4

FAULTING_IP:
nt!ExDeferredFreePool+1e8
8054b280 894204 mov [edx+0x4],eax

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 80523f44 to 8053331e

STACK_TEXT:
f7d5aaa0 80523f44 00000050 86fed2c4 00000001 nt!KeBugCheckEx+0x1b
f7d5aaec 804e1718 00000001 86fed2c4 00000000 nt!MmAccessFault+0x6f5
f7d5aaec 8054b280 00000001 86fed2c4 00000000 nt!KiTrap0E+0xcc
f7d5abb8 8054b31e e132e228 00000000 e141fa40 nt!ExDeferredFreePool+0x1e8
f7d5abf8 8058be4b e141fa40 863d0da0 00000000 nt!ExFreePoolWithTag+0x489
f7d5ac10 805953e9 e141fa40 863d0da0 866005b0 nt!CmpFreePostBlock+0x5d
f7d5ac48 8057a2ae 866005b0 862c6418 c0000005 nt!CmNotifyRunDown+0xdc
f7d5acf0 8058314f c0000005 f7d5ad4c 804e60e9 nt!PspExitThread+0x44d
f7d5acfc 804e60e9 862c6418 f7d5ad48 f7d5ad3c nt!PsExitSpecialApc+0x22
f7d5ad4c 804de855 00000001 00000000 f7d5ad64 nt!KiDeliverApc+0x1af
f7d5ad4c 7c90eb94 00000001 00000000 f7d5ad64 nt!KiServiceExit+0x58
WARNING: Frame IP not in any known module. Following frames may be wrong.
0069ffb4 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!ExDeferredFreePool+1e8
8054b280 894204 mov [edx+0x4],eax

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 3

FOLLOWUP_NAME: Pool_corruption

SYMBOL_NAME: nt!ExDeferredFreePool+1e8

MODULE_NAME: Pool_Corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x50_W_nt!ExDeferredFreePool+1e8

BUCKET_ID: 0x50_W_nt!ExDeferredFreePool+1e8

Followup: Pool_corruption
---------


Here is the SYSTEM EXCEPTION one:


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


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sat Apr 29 14:35:39.968 2006 (GMT-4)
System Uptime: 0 days 0:49:42.550
Loading Kernel Symbols
.................................................. .................................................. .......................
Loading User Symbols
Loading unloaded module list
...........
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8054b339, f7cf2868, f7cf2564}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+fd )

Followup: Pool_corruption
---------

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 8054b339, The address that the exception occurred at
Arg3: f7cf2868, Exception Record Address
Arg4: f7cf2564, Context Record Address

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!ExDeferredFreePool+fd
8054b339 8913 mov [ebx],edx

EXCEPTION_RECORD: f7cf2868 -- (.exr fffffffff7cf2868)
Cannot read Exception record @ f7cf2868

CONTEXT: f7cf2564 -- (.cxr fffffffff7cf2564)
Unable to read context, Win32 error 30

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 8054b31e to 8054b339

STACK_TEXT:
f7cf2970 8054b31e e116fc00 f7cf2aa8 8000000b nt!ExDeferredFreePool+0xfd
f7cf29b0 805761cd e536cc00 00000000 f7cf2a2c nt!ExFreePoolWithTag+0x489
f7cf29d4 80575f39 00000000 00000000 00000000 nt!RtlpInheritAcl+0x76
f7cf2ab0 80576216 00000000 e1f5f008 f7cf2b08 nt!RtlpNewSecurityObject+0x485
f7cf2adc 805766b9 00000000 00000000 f7cf2b08 nt!SeAssignSecurity+0x4f
f7cf2b0c 805766ff f7cf2c20 00000000 866045b0 nt!ObAssignSecurity+0x35
f7cf2bf4 8057af5c 866045b0 f7cf2c20 00000000 nt!ObInsertObject+0x4da
f7cf2d4c 8057bdd8 f7cf2db4 001f03ff 00000000 nt!PspCreateThread+0x618
f7cf2d80 f7692bd8 f7cf2db4 001f03ff 00000000 nt!PsCreateSystemThread+0x33
f7cf2dac 8057be15 00001274 00000000 00000000 NDIS!ndisWorkerThread+0x4b
f7cf2ddc 804fa4da f7692b85 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!ExDeferredFreePool+fd
8054b339 8913 mov [ebx],edx

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: Pool_corruption

SYMBOL_NAME: nt!ExDeferredFreePool+fd

MODULE_NAME: Pool_Corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x7E_nt!ExDeferredFreePool+fd

BUCKET_ID: 0x7E_nt!ExDeferredFreePool+fd

Followup: Pool_corruption---------



This dump came after Memtest found errors in RAM:


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


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:


"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results. Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to load image nt, Win32 error 2
Unable to add module at 00000000
Debugger can not determine kernel base address
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sat Apr 29 01:42:54.812 2006 (GMT-4)
System Uptime: 0 days 0:00:21.375


"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results. Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to load image nt, Win32 error 2
Unable to add module at 00000000
Debugger can not determine kernel base address
Loading Kernel Symbols

Loading User Symbols
Loading unloaded module list
..................................................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ec4c33cf, 1, 855e8bfc, 0}

***** Debugger could not find nt in module list, module list might be corrupt.

Probably caused by : Unknown_Image ( Unknown_Module_a27fa059>+f5c4a86 )

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

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: ec4c33cf, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 855e8bfc, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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

***** Debugger could not find nt in module list, module list might be corrupt.


WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
ec4c33cf

FAULTING_IP:
+ffffffff855e8bfc
855e8bfc ad lodsd

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from b1dbeadf to 8053331e

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
855e8a68 b1dbeadf ccdb8da5 376cec6f f0b2bdd0 0x8053331e
855e8a84 b6c4ce3c e6c2a28c e0794253 874f11af <Unloaded_Unknown_Module_a27fa059>+0xf5c4a86
855e8a88 e6c2a28c e0794253 874f11af 9bd2cc8a <Unloaded_Unknown_Module_a27fa059>+0x14452de3
855e8a8c e0794253 874f11af 9bd2cc8a 7fa37bff <Unloaded_Unknown_Module_d722b45e>+0xf9fee2e
855e8a90 874f11af 9bd2cc8a 7fa37bff db72f2c5 <Unloaded_Unknown_Module_d722b45e>+0x9568df5
855e8a94 9bd2cc8a 7fa37bff db72f2c5 edb48cc3 0x874f11af
855e8a98 7fa37bff db72f2c5 edb48cc3 2cdabdd5 <Unloaded_Unknown_Module_91e1ab74>+0x9f12116
855e8a9c db72f2c5 edb48cc3 2cdabdd5 cbfb24e3 <Unloaded_Unknown_Module_4daf1cf1>+0x31f45f0e
855e8aa0 edb48cc3 2cdabdd5 cbfb24e3 058917a6 <Unloaded_Unknown_Module_d722b45e>+0x4503e67
855e8aa4 2cdabdd5 cbfb24e3 058917a6 e9c9604d <Unloaded_Unknown_Module_9143def9>+0x5c70adca
855e8aa8 cbfb24e3 058917a6 e9c9604d 4dd53f6a <Unloaded_Unknown_Module_27c61c75>+0x514a160
855e8aac 058917a6 e9c9604d 4dd53f6a efa1e5f3 <Unloaded_Unknown_Module_a27fa059>+0x297b848a
855e8ab0 e9c9604d 4dd53f6a efa1e5f3 0fa3e363 <Unloaded_Unknown_Module_030b6329>+0x27db47d
855e8ab4 4dd53f6a efa1e5f3 0fa3e363 f8426b86 <Unloaded_Unknown_Module_d722b45e>+0x12a6abef
855e8ab8 efa1e5f3 0fa3e363 f8426b86 9f43ba43 <Unloaded_Unknown_Module_4daf1cf1>+0x262279
855e8abc 0fa3e363 f8426b86 9f43ba43 9e345cf8 <Unloaded_Unknown_Module_9143def9>+0x5e5e06fa
855e8ac0 f8426b86 9f43ba43 9e345cf8 d35c78a9 <Unloaded_Unknown_Module_030b6329>+0xc98803a
855e8ac4 9f43ba43 9e345cf8 d35c78a9 f9902d52 <Unloaded_Unknown_Module_9143def9>+0x66fe8c8d
855e8ac8 9e345cf8 d35c78a9 f9902d52 353b75e9 <Unloaded_Unknown_Module_91e1ab74>+0xd620ecf
855e8acc d35c78a9 f9902d52 353b75e9 f64da8ba <Unloaded_Unknown_Module_91e1ab74>+0xc52b184
855e8ad0 f9902d52 353b75e9 f64da8ba b7ad3153 <Unloaded_Unknown_Module_a27fa059>+0x30dcd850
855e8ad4 353b75e9 f64da8ba b7ad3153 36fefefe <Unloaded_Unknown_Module_9143def9>+0x684c4e59
855e8ad8 f64da8ba b7ad3153 36fefefe 8cfccbf7 <Unloaded_Unknown_Module_27c61c75>+0xd755974
855e8adc b7ad3153 36fefefe 8cfccbf7 86acfcfc <Unloaded_Unknown_Module_9143def9>+0x6509c9c1
855e8ae0 36fefefe 8cfccbf7 86acfcfc c05d8a55 <Unloaded_Unknown_Module_a27fa059>+0x152d90fa
855e8ae4 8cfccbf7 86acfcfc c05d8a55 7a957022 <Unloaded_Unknown_Module_27c61c75>+0xf38e289
855e8ae8 86acfcfc c05d8a55 7a957022 7aa0bb49 0x8cfccbf7
855e8aec c05d8a55 7a957022 7aa0bb49 e4d3254f 0x86acfcfc
855e8af0 7a957022 7aa0bb49 e4d3254f 24c5bf24 <Unloaded_Unknown_Module_a27fa059>+0x1ddde9fc
855e8af4 7aa0bb49 e4d3254f 24c5bf24 7e0de208 <Unloaded_Unknown_Module_4daf1cf1>+0x2ce65331
855e8af8 e4d3254f 24c5bf24 7e0de208 b86c4999 <Unloaded_Unknown_Module_4daf1cf1>+0x2cf19e58
855e8afc 24c5bf24 7e0de208 b86c4999 28ab22b6 <Unloaded_Unknown_Module_d722b45e>+0xdb070f1
855e8b00 7e0de208 b86c4999 28ab22b6 d1d30ab3 <Unloaded_Unknown_Module_030b6329>+0x21ba5bfb
855e8b04 b86c4999 28ab22b6 d1d30ab3 83ed1396 <Unloaded_Unknown_Module_4daf1cf1>+0x305ec517
855e8b08 28ab22b6 d1d30ab3 83ed1396 2fdd9add <Unloaded_Unknown_Module_a27fa059>+0x15eca940
855e8b0c d1d30ab3 83ed1396 2fdd9add 8d9b553a <Unloaded_Unknown_Module_27c61c75>+0xe50641
855e8b10 83ed1396 2fdd9add 8d9b553a 77d04815 <Unloaded_Unknown_Module_a27fa059>+0x2f536a5a
855e8b14 2fdd9add 8d9b553a 77d04815 c57afbdc 0x83ed1396
855e8b18 8d9b553a 77d04815 c57afbdc fb92a146 <Unloaded_Unknown_Module_27c61c75>+0x8177e68
855e8b1c 77d04815 c57afbdc fb92a146 ddc0e190 0x8d9b553a
855e8b20 c57afbdc fb92a146 ddc0e190 aeb8ac2a <Unloaded_Unknown_Module_4daf1cf1>+0x2a212b24
855e8b24 fb92a146 ddc0e190 aeb8ac2a 4a735ff2 <Unloaded_Unknown_Module_a27fa059>+0x22fb5b83
855e8b28 ddc0e190 aeb8ac2a 4a735ff2 17d683c7 0xfb92a146
855e8b2c aeb8ac2a 4a735ff2 17d683c7 fff6bacd <Unloaded_Unknown_Module_d722b45e>+0x69e2d32
855e8b30 4a735ff2 17d683c7 fff6bacd 031bebda <Unloaded_Unknown_Module_a27fa059>+0xc390bd1
855e8b34 17d683c7 fff6bacd 031bebda f4751e1b <Unloaded_Unknown_Module_030b6329>+0x4767fcc9
855e8b38 fff6bacd 031bebda f4751e1b f7fce740 <Unloaded_Unknown_Module_159837dc>+0x23e4beb
855e8b3c 031bebda f4751e1b f7fce740 f8d8b6cc 0xfff6bacd
855e8b40 f4751e1b f7fce740 f8d8b6cc 94e16d66 <Unloaded_Unknown_Module_030b6329>+0x1088b1
855e8b44 f7fce740 f8d8b6cc 94e16d66 71cbee9d <Unloaded_Unknown_Module_9143def9>+0x63313f22
855e8b48 f8d8b6cc 94e16d66 71cbee9d 9289ed5e <Unloaded_Unknown_Module_9143def9>+0x66b90847
855e8b4c 94e16d66 71cbee9d 9289ed5e 8ca7bd7d <Unloaded_Unknown_Module_9143def9>+0x6794d7d3
855e8b50 71cbee9d 9289ed5e 8ca7bd7d c7e6844f <Unloaded_Unknown_Module_91e1ab74>+0x2ffc1f2
855e8b54 9289ed5e 8ca7bd7d c7e6844f 9b950a3e <Unloaded_Unknown_Module_4daf1cf1>+0x241cd1ac
855e8b58 8ca7bd7d c7e6844f 9b950a3e 4dcaedbd <Unloaded_Unknown_Module_91e1ab74>+0xa841ea
855e8b5c c7e6844f 9b950a3e 4dcaedbd eae37dbd 0x8ca7bd7d
855e8b60 9b950a3e 4dcaedbd eae37dbd 73db88c5 <Unloaded_Unknown_Module_a27fa059>+0x2566e3f6
855e8b64 4dcaedbd eae37dbd 73db88c5 3dad2d3e <Unloaded_Unknown_Module_91e1ab74>+0x9b35eca
855e8b68 eae37dbd 73db88c5 3dad2d3e cf79e3c4 <Unloaded_Unknown_Module_4daf1cf1>+0x1bd0cc
855e8b6c 73db88c5 3dad2d3e cf79e3c4 ab661e09 <Unloaded_Unknown_Module_9143def9>+0x599f9ec4
855e8b70 3dad2d3e cf79e3c4 ab661e09 38553aa7 <Unloaded_Unknown_Module_4daf1cf1>+0x262c6bd4
855e8b74 cf79e3c4 ab661e09 38553aa7 50291336 <Unloaded_Unknown_Module_27c61c75>+0x15e710c9
855e8b78 ab661e09 38553aa7 50291336 24183bf7 <Unloaded_Unknown_Module_a27fa059>+0x2cfa436b
855e8b7c 38553aa7 50291336 24183bf7 3089dcf9 <Unloaded_Unknown_Module_a27fa059>+0x8e67db0
855e8b80 50291336 24183bf7 3089dcf9 f513661b <Unloaded_Unknown_Module_27c61c75>+0x108f1e32
855e8b84 24183bf7 3089dcf9 f513661b c47a7220 <Unloaded_Unknown_Module_4daf1cf1>+0x279f645
855e8b88 3089dcf9 f513661b c47a7220 ab6b20f0 <Unloaded_Unknown_Module_030b6329>+0x210cd8ce
855e8b8c f513661b c47a7220 ab6b20f0 c5bc3c68 <Unloaded_Unknown_Module_27c61c75>+0x8c3c084
855e8b90 c47a7220 ab6b20f0 c5bc3c68 be5e21b4 <Unloaded_Unknown_Module_9143def9>+0x63cf8722
855e8b94 ab6b20f0 c5bc3c68 be5e21b4 97b0a441 <Unloaded_Unknown_Module_a27fa059>+0x21fad1c7
855e8b98 c5bc3c68 be5e21b4 97b0a441 4bb32eba <Unloaded_Unknown_Module_a27fa059>+0x8eb8097
855e8b9c be5e21b4 97b0a441 4bb32eba 47c39c92 <Unloaded_Unknown_Module_a27fa059>+0x233c9c0f
855e8ba0 97b0a441 4bb32eba 47c39c92 19fc8534 <Unloaded_Unknown_Module_a27fa059>+0x1bde815b
855e8ba4 4bb32eba 47c39c92 19fc8534 62fe8dfb <Unloaded_Unknown_Module_91e1ab74>+0x5cef8cd
855e8ba8 47c39c92 19fc8534 62fe8dfb 7e514bfd <Unloaded_Unknown_Module_030b6329>+0x48a7cb91


STACK_COMMAND: kb

FOLLOWUP_IP:
Unknown_Module_a27fa059>+f5c4a86
b1dbeadf ?? ???

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Unknown_Module_a27fa059>+f5c4a86

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CORRUPT_MODULELIST

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


This is PFN_LIST_CORRUPT:


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


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Thu Apr 27 15:42:03.859 2006 (GMT-4)
System Uptime: 0 days 3:36:03.437
Loading Kernel Symbols
.................................................. .................................................. .........................
Loading User Symbols
Loading unloaded module list
..............
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 0, 0, 0}

Probably caused by : memory_corruption ( nt!MiDeleteValidAddress+123 )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 00000000, page frame number
Arg3: 00000000, current page state
Arg4: 00000000, 0

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


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x4E

LAST_CONTROL_TRANSFER: from 80520aa3 to 8053331e

STACK_TEXT:
a8337bd4 80520aa3 0000004e 00000099 00000000 nt!KeBugCheckEx+0x1b
a8337c08 80582baa 0453b201 85b68850 003ffffc nt!MiDeleteValidAddress+0x123
a8337c28 80501117 85b68850 85b68988 85b68850 nt!MiDeleteAddressesInWorkingSet+0x65
a8337c60 80582e8e 00b68850 85b8e020 85b8e268 nt!MmCleanProcessAddressSpace+0x18f
a8337d08 8057a46a 0000002a 85b8e020 00000000 nt!PspExitThread+0x680
a8337d28 80582d13 85b8e020 0000002a a8337d64 nt!PspTerminateThreadByPointer+0x52
a8337d54 804de7ec 00000000 0000002a 0012fec8 nt!NtTerminateProcess+0x118
a8337d54 7c90eb94 00000000 0000002a 0012fec8 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012fec8 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiDeleteValidAddress+123
80520aa3 00ff add bh,bh

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!MiDeleteValidAddress+123

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x4E_nt!MiDeleteValidAddress+123

BUCKET_ID: 0x4E_nt!MiDeleteValidAddress+123

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



Now this one is interesting. A PAGE_FAULT but also the first dump I found that provided a driver name. The driver name seems to belong to my video card - ati2cqag.dll:


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


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sat Apr 22 16:05:28.750 2006 (GMT-4)
System Uptime: 0 days 0:06:11.334
Loading Kernel Symbols
.................................................. .................................................. ......................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image ati2cqag.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for ati2cqag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati2cqag.dll
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e69f2518, 0, bfa25d60, 2}


Could not read faulting driver name
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
Probably caused by : ati2cqag.dll ( ati2cqag+fd60 )

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

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: e69f2518, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bfa25d60, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)

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


Could not read faulting driver name
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session

READ_ADDRESS: e69f2518

FAULTING_IP:
ati2cqag+fd60
bfa25d60 3b5a0c cmp ebx,[edx+0xc]

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 00000000 to bfa25d60

STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 ati2cqag+0xfd60


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
ati2cqag+fd60
bfa25d60 3b5a0c cmp ebx,[edx+0xc]

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: ati2cqag+fd60

MODULE_NAME: ati2cqag

IMAGE_NAME: ati2cqag.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 43bc8cff

FAILURE_BUCKET_ID: 0x50_ati2cqag+fd60

BUCKET_ID: 0x50_ati2cqag+fd60

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


Please, I cannot afford to buy another computer and I am praying this will not go out of commission. Please save my baby!

Just a quick question: Are the 2 sticks of RAM identical? Speed and brand?

If not: do you have any similar problems when you only use one stick at a time?

Well, these problems only began appearing after my RAM upgrade, but yes both sticks are identical. However, my motherboard has underclocked them by default and provides no options to change their settings.

Both sticks are Kingston ValuRAM 512MB PC3200 400Mhz. My total bus speed is however only 266Mhz whereas I think it should be 400. Their Clock Latency is also 3.0, but Cpuz.exe displays them at 2.0 clocks.

But I did test each of them and found no errors. The only errors I found were when they were both in dual channel mode. 88 errors to be exact, yeesh!

I also previously stated that after moving my RAM to single channel (Slots 1 and 2) I've been hearing a short beep everytime I turn on the computer. On this site, http://www.computerhope.com/beep.htm, the short beep means DRAM Refresh Failure.

But are all those dumps caused by RAM failures even though Memtest claimed they work well?

Decided to edit this post, didn't want to triple-post.

http://www.smartcomputing.com/Editor...4w01.asp&guid=

This site explained couple of good points in determining faulty RAM. I guess I'll remove the new one and keep the older one in DIMM 0.

One thing to consider is that MemTest can also be picking up on CPU or GPU memory errors.

Troubleshooting Memory Errors
Please be aware that not all errors reported by Memtest86 are due to bad memory. The test implicitly tests the CPU, L1 and L2 caches as well as the motherboard. It is impossible for the test to determine what causes the failure to occur. However, most failures will be due to a problem with memory module. When it is not, the only option is to replace parts until the failure is corrected.

http://www.memtest86.com/#trouble

Do you have your latest BIOS?
http://downloadfinder.intel.com/scri...l&submit=Go%21

More board links:
http://www.intel.com/support/motherb...5gbf/index.htm

http://www.intel.com/products/mother...5gbf/index.htm

I also wonder about this underclocking? Are there no settings in the BIOS to set the BUS speed? Perhaps a latter version of the BIOS might help.

I will look thru those dumps when I have more time but if these all coincided with additional RAM that would be my first suspect.

I am often asked about the reliability of errors reported by Mestest86. In the vast majority of cases errors reported by the test are valid. There are some systems that cause Memtest86 to be confused about the size of memory and it will try to test non-existent memory. This will cause a large number of consecutive addresses to be reported as bad and generally there will be many bits in error. If you have a relatively small number of failing addresses and only one or two bits in error you can be certain that the errors are valid. Also intermittent errors are without exception valid. Frequently memory vendors question if Memtest86 supports their particular memory type or a chipset. Memtest86 is designed to work with all memory types and all chipsets. Only support for ECC requires knowledge of the chipset.

This is interesting for me as well. All 88 errors (strangely large number for errors in RAM) were consequent messages stating something about strings disagreeing with each other, for example, 10946 doesn't like 10724 and such. I basically clicked the "Ok" button 88 times in a row. Then there were no more errors until I just got that PAGE_FAULT BSOD, 'tis a beautiful thing.

And no, I haven't found ANY options in the BIOS to change BUS speeds, it's frustrated me quite a bit. I've been told by my friends that "Intel makes great processors but horrible motherboards", heh.

About those board updates, will they be able to "expand" options in the actual BIOS? To tell you the truth, I'm not familiar with installing new drivers in that area.

Also, I'm using my old 512MB at the moment, took out the new one from Slot 2.


Oops, just took a good look at those download instructions. I should probably tell you I don't have a floppy drive on my computer.

Here are the listed revisions to your board's BIOS:

ftp://aiedownload.intel.com/df-suppo...leaseNotes.pdf

You should be able to see your version in the BIOS setup or almost any hardware scan.

DAL has created this one: http://www.d-a-l.com/hardware-scan.php

Your RAM support is listed as:

Memory Four 184-pin DDR SDRAM DIMM sockets
Support for DDR 400, DDR 333, and DDR 266
Support for up to 4 GB of system memory

As such I am not quite drawing the clock issue but I am also being widely distracted this evening ... sorry

Do you notice a difference running only the one stick?

Actually, I am greatly in debt to you for answering me so quickly this evening. I've been watching NHL games and checking this thread at once :P

Not really a difference in running the lone stick, if I were to run Doom 3, I'd probably be getting 15-20fps on high quality as opposed to the 60fps I get with the gig of RAM.

I just wish my upgrade won't turn into a downgrade, $50 for nothing

Thanks for the information, I know everything about my motherboard and the things in my computer

"There is no knowledge that is not power...now someone get these BSODs out of my face!"

:P

Just as a troubleshooting step removing possible problems is a first step. Not to imply that you cannot upgrade. Just maybe the RAM stick might have been faulty? Faulty slot? Faulty combination? etc.

A general listing of your STOP errors can be found here: http://aumha.org/win5/kbestop.htm

As I get time I will look at you dumps in details but that site gives you the headlines.

I am still looking for an online manual for that board as well.