Good day, and happy turkey day for us in the USA

I have been lurking around this forum for about a month, and have found many solutions to my issues. I found that this forum is very helpful and kind to all those needing help, so I decided to join up!

My desktop computer is having issues with BSODs, and I am running out of options. It happens randomly and I have no real way of reproducing the error intentionally. The errors are 0x8E (most common), 0x0A, 0x24, and 0x50.

Below is the system information, as well as the dump files and what I have done thus far to correct these issues:

SYSTEM
OS: Windows XP Professional SP3 (32 bit)
Processor: AMD XP 2400+
Motherboard: AOpen AK77-400N, BIOS revision 1.11 (Newer one exists, but will not properly display processor speed or run at 133 FSB!)
PSU: Thermal Take TR2-430W
Memory: 2x1 G-Skill PC3200 DDR400
HD: SEAGATE 120 GB (I think)
Video: Nvidia GeForce 6200 AGP (Downgraded driver to 169 since 180 was thought to be the cause of BSODs)
Audio: Creative Audigy Gamer
LAN: Onboard Ethernet Controller (Realtek 8139)
Disc drive: LG DVD drive and some 3rd party CD-RW drive


DUMP FILES - My comments are in blue

MEMORY DUMP 1


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


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

************************************************** **********
WARNING: Dump file has been truncated. Data may be missing.
************************************************** **********
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
************************************************** ************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
************************************************** ************************
Unable to read PsLoadedModuleList
************************************************** ************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
************************************************** ************************
KdDebuggerData.KernBase < SystemRangeStart
Windows XP Kernel Version 2600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x00000000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Wed Nov 26 16:48:40.415 2008 (GMT-8)
System Uptime: 0 days 0:17:41.000
************************************************** ************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
************************************************** ************************
Unable to read PsLoadedModuleList
************************************************** ************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
************************************************** ************************
KdDebuggerData.KernBase < SystemRangeStart
Loading Kernel Symbols
Unable to read PsLoadedModuleList
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
CS descriptor lookup failed
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get program counter
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 8E, {80000003, 804e3586, b67a6aa8, 0}

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

GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to read selector for PCR for processor 0
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147 Repeats about 60 times
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to read selector for PCR for processor 0
GetContextState failed, 0xD0000147
Unable to read selector for PCR for processor 0
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

GetContextState failed, 0xD0000147 Repeats about 20 more times






Crash file 2


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


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

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sun Nov 23 19:40:22.143 2008 (GMT-8)
System Uptime: 0 days 10:35:54.739
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
...
Loading User Symbols
Loading unloaded module list
............................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf8019ff, b3673d44, 0}

Probably caused by : win32k.sys ( win32k!HMAssignmentLock+a )

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





Crash file 3


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


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

Symbol search path is: SRV*c:\symbols*Symbol information
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 0n2
Unable to add module at 00000000
Debugger can not determine kernel base address
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Wed Nov 26 12:53:41.856 2008 (GMT-8)
System Uptime: 0 days 0:12:49.451

"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 0n2
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 1000008E, {80000003, 804e3586, 80550cfc, 0}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. What is this missing module?
Probably caused by : Unknown_Image ( Unknown_Module_aff474a4>+76242f0 )

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

Crash file 4


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


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

Invalid directory table base value 0x0
Symbol search path is: SRV*c:\symbols*Symbol information
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 0n2
Unable to add module at 00000000
Debugger can not determine kernel base address
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Wed Nov 26 13:05:49.266 2008 (GMT-8)
System Uptime: 0 days 0:11:39.857

"nt" was not found in the image list. NT file again?
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 0n2
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 7E, {80000003, 804e3586, f78e6864, f78e6560}

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

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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





Those are the log files that I can find. What is with the missing NT module? Anyways, here is what I have done to attempt to remedy the BSODs:

1. Replaced AVG Anti-virus with AVAST! Anti-virus
2. Replaced Zone Alarm firewall with Sunbelt firewall
3. Downgraded video drivers (as said in System Information)
4. Updated Windows using Windows Update
5. Ran Memtest86, no errors in any passes
6. Installed Nvidia NV4_loop fix (Courtesy of Nvidia forums, a common problem with WIN XP and Nvidia cards). This cured a few BSOD errors related to the card.
7. Updated onboard Ethernet Controller and motherboard chipset (VIA)

I have been researching this issue for about 3 days and still cannot find an answer. I am pointing the finger at the video card, and sound card. I do know Win32k.SYS is called for by the video card, and I have read that Creative makes the worst drivers for sound cards and users have had some of the same issues .

Can anybody point me in the right direction, or even better give me a link to a magical Windows patch that cures all BSODs (I already have an Ubuntu box, so don't suggest that )? I believe I have hit the end of the road.

UPDATE

Took out Audigy card and am using onboard AC97.
Replaced Nvidia card with ATI Radeon 9200
Ran both sticks in DIMM 0 and 2...BSOD
Rab both sticks on DIMM 1 and 2, BSOD

Ran normal operations on one stick for 6 hours in DIMM 0...no errors
Ran normal operations on other stick for almost 3 hours and in DIMM2...no errors
Ran both sticks, and got a BSOD after 15 mins

So..either the RAM is completely whacky, motherboard is a silent killer, or my processor is on crack.

Any thoughts yet?

How long have you had the RAM? Most of your dump files are corrupt. That's why your getting the missing NT module error. Corrupt dump files usually means hardware, which you've found out is a RAM problem.

I have had my RAM for about 5 days, they were ordered from Newegg.com. I cannot recreate the BSOD at all, but I know it has to be at least one of them. Should I send both of them back and get another two?

UPDATE

Since I ran each memory stick through a memtest with no errors, seperated them on different DIMMS with no BSOD led me to believe it was either the processor or motherboard.

A different processor was used, received BSOD again. Swapped out motherboard with another compatible working one, received NO BSOD errors.

Cause: Motherboard could not run 2 memory sticks at once. I hope this helps out people in the future!

According to the Crucial Ram site the specs on your Aopen motherboard state that each Ram slot can only support a 512 meg stick.

But when I checked the specs at a review site they say each slot can accept a 1 Gig stick of Ram.
That may be due to a bios version upgrade.
I'd check the Aopen site and look at the different bios versions they have and make sure the version you have will indeed handle the 1 Gig sticks.

It did take one 1GB memory stick OK, but when I inserted the other 1GB stick...the system flipped out. I think it was an issue with it utilizing two sticks. Its ok now, I got a Asus a8N-SLI premium...runs solid

Glad to hear all is good.
Asus does make a good board. It's what I usually use.
Have fun!