Jephree, I think I found something.

When I selected to restart my computer, as soon as the desktop icons and everything except for the background disappeared, I caught a glimpse of a Windows error! One of those little error boxes that pop up when something (not the error reporting one). I just saw it and noticed it had an "Ok" option, that's it.

Then, I went to BIOS. Noticed that basically all the options except for SDRAM RAS Active and Bus speed were at the lowest settings. Bus speed was set at Auto and SDRAM was at 5. I decided not to change anything since it wouldn't really matter

But, I've noticed that everytime my computer makes a save dump after a BSOD, there has always been something in EventVwr called "redbook", ID10. The redbooks happen a few times in the logs but always after BSODs too. Before April 29th, there would be 3 consequent redbooks after a save dump in the logs. Now only 1 appears everytime a BSOD happens.

This is what it says:

This drive has not been shown to support digital audio playback.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I've also had some errors called "W32Time". On April 29th, I saw that 2 of these same errors happened at the exact same second. This is what they say:

Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time.windows.com,0x1'. NtpClient will try the DNS lookup again in 15 minutes. The error was: A socket operation was attempted to an unreachable host. (0x80072751)

I hope all this helps somehow

Event ID: 10
Source redbook
Type Information
Description This drive has not been shown to support digital audio playback.
Comments Anne Jan Elsinga (Last update 3/23/2004):
This also happens with some emulation software for CD-ROM drivers, like Daemontools.

Rickey Carter (Last update 11/17/2003):
This error usually appears when a drive does not support digital audio playback. Make sure appropriate settings are used in you CDROM and DVD player configuration so that digital audio playback is not selected.


http://www.eventid.net/display.asp?e...edbook&phase=1

I think I found out what happened.
The digital cable between the motherboard and the dvd drive was not present
and hence I received that log entry in the event viewer.


http://www.thennews.com/c/21/Redbook...20id%2010).php


W32Time errors are common and usually benign. I have somewhere in my links the reset procedure and will dig it up. This is just an inability of your computer to connect to a time server.

Ok

However, the redbook messages stopped coming in trios after I unchecked digital audio from my DVD-ROM settings.

Where are my manners...

Thank you Jephree, for once again looking up information for me. I'd be more than willing to buy the new video card but is it a smart choice considering the fact that all my errors are memory-based?

if W32Time service stops working correctly, it can be fixed and reset to
default values by entering the following commands from start | run cmd and then in the order shown:


C:\NET STOP W32TIME


C:\W32TM /UNREGISTER


C:\W32TM /REGISTER


C:\W32TM /REDISCOVER


C:\NET START W32TIME


C:\W32TM /CONFIG /UPDATE

If all of this started with that new stick of RAM I would try to test that. Perhaps it is just bad.

Do you have another computer that you could test that stick in? Just to try and isolate the problem.

No problem about manners Think Fast Work Fast Get the job done ~wolf

C:\NET STOP W32TIME


C:\W32TM /UNREGISTER - Access is denied. (0x80070005)


C:\W32TM /REGISTER


C:\W32TM /REDISCOVER - command unknown


C:\NET START W32TIME


C:\W32TM /CONFIG /UPDATE - updated successfully

Thanks I hope that helps that.

*Sigh* The good news is, I was able to play Star Wars Battlefront II for 1 full minute!!!

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000fe (0x00000005, 0x8660a0e0, 0x808624d2, 0x8609f790). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

And the oh-so glorious bug check:



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


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Missing image name, possible corrupt data.
*** WARNING: Unable to verify timestamp for Unknown_Module_0396b474
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0396b474
Debugger can not determine kernel base address
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: Tue May 2 12:39:58.968 2006 (GMT-4)
System Uptime: 0 days 042.574
Missing image name, possible corrupt data.
*** WARNING: Unable to verify timestamp for Unknown_Module_0396b474
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0396b474
Debugger can not determine kernel base address
Loading Kernel Symbols
Missing image name, possible corrupt data.
.Unable to read KLDR_DATA_TABLE_ENTRY at 0c3c9400 - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {5, 8660a0e0, 808624d2, 8609f790}

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

Probably caused by : Unknown_Image

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

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

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000005, USB Bugcheck Code:
Arg2: 8660a0e0
Arg3: 808624d2
Arg4: 8609f790

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

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


DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xFE

LAST_CONTROL_TRANSFER: from f6bb8cc3 to 8053331e

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
8055004c f6bb8cc3 000000fe 00000005 8660a0e0 0x8053331e
8055006c f6bc5516 8660a028 00000fd0 85a8c000 0xf6bb8cc3
805500a8 f7bc605c 0528cd00 8660a9dc 8609f790 0xf6bc5516
805500cc f7bc3ded 8660a9dc 85a8c000 805500fc 0xf7bc605c
805500dc f6bb22ba 8660a9dc 8609f790 804e2eb4 0xf7bc3ded
805500fc f6bb3578 026c6f50 8660a0e0 8609f618 0xf6bb22ba
80550124 f6bb6ed0 8660a028 50457270 804e2eb4 0xf6bb3578
80550154 f6bc4fb0 8660a028 804e2eb4 8660a028 0xf6bb6ed0
80550190 f6bc5128 8660a028 00000001 80558e80 0xf6bc4fb0
805501ac 804dbbd4 8660a64c 6b755044 00000000 0xf6bc5128
ffdff980 00000000 f7c7f000 0001d29f 00000000 0x804dbbd4


STACK_COMMAND: kb

FOLLOWUP_IP:
+ffffffff8053331e
8053331e 5d pop ebp

FAULTING_SOURCE_CODE:


FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CORRUPT_MODULELIST

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

Well, after that initial BSOD, I took out the newer module and left the old one in DIMM1. I played Battlefront II for about an hour, but as soon as I began typing here, I got another BSOD, the marvelous return of the IRQL_NOT_LESS_OR_EQUAL messages.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0a04ffe5, 0x00000002, 0x00000000, 0x804e63a1). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

Well, I'll see if I find any drivers in here:


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


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is 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: Tue May 2 13:31:51.296 2006 (GMT-4)
System Uptime: 0 days 0:50:13.881
Loading Kernel Symbols
.................................................. .................................................. .......................
Loading User Symbols
Loading unloaded module list
............
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {a04ffe5, 2, 0, 804e63a1}

Probably caused by : ntoskrnl.exe ( nt!ExpScanGeneralLookasideList+1b )

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

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


READ_ADDRESS: 0a04ffe5

CURRENT_IRQL: 2

FAULTING_IP:
nt!ExpScanGeneralLookasideList+1b
804e63a1 8b56e0 mov edx,[esi-0x20]

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 804e63a1 to 804e187f

STACK_TEXT:
f899eca8 804e63a1 badb0d00 00000002 00000000 nt!KiTrap0E+0x233
f899ed2c 804e63ef 80561870 80561868 804e55fc nt!ExpScanGeneralLookasideList+0x1b
f899ed38 804e55fc 00000000 823c3da8 00000000 nt!ExAdjustLookasideDepth+0x32
f899edac 8057be15 00000000 00000000 00000000 nt!KeBalanceSetManager+0x88
f899eddc 804fa4da 804e557a 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!ExpScanGeneralLookasideList+1b
804e63a1 8b56e0 mov edx,[esi-0x20]

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!ExpScanGeneralLookasideList+1b

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9

FAILURE_BUCKET_ID: 0xA_nt!ExpScanGeneralLookasideList+1b

BUCKET_ID: 0xA_nt!ExpScanGeneralLookasideList+1b

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


ntoskrnl.exe ?

BTW, that basically proves that the new memory isn't the culprit. I have it now in DIMM1 and have the old one out.

Ugh, speed couldn't be worse. I put the old one in Slot 4, the one stick alone is just way too slow for me!

BTW, do you know if these problems will be fixed if I were to buy another 512MB module to replace the old one? Maybe it's just shot.

Well, thanks for your help but you might as well close this thread. My computer is now officially dead. Even with the new stick it crashed, this time showing a PAGE_FAULT_IN_NONPAGED_AREA and for the first time a driver; win32k.sys



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


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
************************************************** ************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
************************************************** ************************
Unable to read PsLoadedModuleList
KdDebuggerDataBlock not available!
KdDebuggerData.KernBase < SystemRangeStart
Windows XP Kernel Version 2600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x00000000 PsLoadedModuleList = 0x8055a420
Debug session time: Tue May 2 15:57:23.046 2006 (GMT-4)
System Uptime: 0 days 0:33:41.652
Unable to read PsLoadedModuleList
KdDebuggerDataBlock not available!
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
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 50, {e3fffc5c, 0, bf80166d, 1}

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

GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Probably caused by : Unknown_Image

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

GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
?: kd> !analyze -v
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
************************************************** *****************************
* *
* 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: e3fffc5c, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf80166d, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)

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

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

GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get MmPageSize (0x0) - probably bad symbols
e3fffc5c

FAULTING_IP:
+ffffffffbf80166d
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
bf80166d ?? ???

MM_INTERNAL_CODE: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

STACK_TEXT:
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CORRUPT_MODULELIST

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

Stupid me, I was already making plans to buy another stick of 512MB tomorrow. Aren't I stupid in thinking this could be fixed? Might as well close it Jephree, if you've seen this and the horde of errors from today that I posted earlier, you'll understand. Thank you for being a friend when I needed one, but I'm going to take out my hard drive, PS, sound card, and CD/DVD and hope that in a few years, I can buy a low-end computer. Just sufficient enough to play Tetris on or create a masterpiece in Paint with.