Restarts, BSOD, Decode, Please Help :(

sliptapg

Distinguished
Jun 17, 2008
34
0
18,530
Alright, here is my situation. I'm trying to debug my PC, with which I am currently struggling with. Here are the important specs:

*AMD Athlon 64 X 2 3800+
*2 x 1 GB OCZ Platinum PC2-6400 Memory (dual channel, REV 2)
*ECS K8M890M-M motherboard
*MSI 7600GT Graphics Card
*Generic Raidmax 420 watt PS

Under normal, "surfing the net" work loads, the system is completely stable. However, after about 10 minutes or so of heavy gameplay the system completely restarts. Interestingly enough, there are no signs that would allude to a problem. For example, my last test, Call of Duty 5 was running perfectly smooth with no artifacts or anything prior to restarting.

My first guess was to try memory. In my bios, I originally had everything set to auto. So, i changed the timings to 4-4-4-15 @ 1.9V, as recommended by the OCZ website. After that, I ran MemTest86+, and it ran for an hour and a half completely stable, with no errors. Next, I updated the BIOS to the newest version.

My first instinct after memory was overheating, but I don't believe thats the case. It idles at 40 deg celcius. It isn't overclocked at all. I have 2 case fans (rear and side) plus a drive bay fan running. Also, I clean my case regular of dust.

Anyway, I next changed the setting so that windows doesn't restart immediately after BSOD. This didn't make a difference until after I changed my memory settings (first time it actually gave me a BSOD). Here is the error message:

IRQL_NOT_LESS_OR_EQUAL
STOP:0X0000000A (0x00000147,0X0000001C,0X00000000,0X805444DE)

I don't know how to decode STOP/BSOD messages :??:

I'm wondering if it still isn't my memory. I might try raising the voltage again, to see if that will help. COD5 seemed to last a minute or two longer when I changed it last.

Anyway, any help or suggestions would be great. I've been working on this for hours and I'm not quite sure what to try next. I'm hoping the BSOD error message will lead me in the right direction. Thanks for your help!
 
Oh, here is a little more info that might help. This is my mess around PC, but the install of XP is pretty clean (i believe it's XP PRO OEM). Anyway, I've looked through the device manager and haven't found anything out of the ordinary, either.
 
To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool

Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.
Try disabling memory caching (Shadow) in the BIOS.
Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.
Make sure the latest Service Pack is installed.
If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination.
For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only. Also, check each IDE device for the proper master/subordinate/stand-alone setting. Try removing all IDE devices except for hard disks.

http://support.microsoft.com/kb/314063
 
Alright, so I ran a debug on my crash dump files... here is the most recent one:
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000143, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 805444de, address which referenced memory

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


READ_ADDRESS: 00000143

CURRENT_IRQL: 1c

FAULTING_IP:
nt!VfBuildMdlFromScatterGatherList+1ce
805444de 3b992c010000 cmp ebx,dword ptr [ecx+12Ch]

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from baa19c46 to 805444de

STACK_TEXT:
bacd3cc0 baa19c46 badb0d00 00000002 b9ef960f nt!VfBuildMdlFromScatterGatherList+0x1ce
bacd3d50 80544fab 00000000 0000000e fffdffff processr!AcpiC1Idle+0x12
bacd3d6c 00134428 00000100 00400000 00001841 nt!WmiTraceFastEvent+0x15
WARNING: Frame IP not in any known module. Following frames may be wrong.
bacd3d70 00000000 00400000 00001841 179bc1ef 0x134428


STACK_COMMAND: kb

FOLLOWUP_IP:
processr!AcpiC1Idle+12
baa19c46 6a00 push 0

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: processr!AcpiC1Idle+12

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: processr

IMAGE_NAME: processr.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107b32

FAILURE_BUCKET_ID: 0xA_processr!AcpiC1Idle+12

BUCKET_ID: 0xA_processr!AcpiC1Idle+12

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


The first bebug was for a random fan program which I had just installed. However, the last parameter (805444de) remained the same for both crashes.
 
Alright, I guess I solved the problem. I have been running COD5 all day now, with not problems. Here are the steps I've taken:

*Updated Motherboard BIOS
*Updated Nvidia Drivers
*Took of side of case (more airflow potential)
*Increased memory voltage (1.8v default to 1.95v) to accommodate the aggressive memory and timings.
*Replaced processr.sys file (mentioned in BSOD) with a newer file I found on my HDD.
*Unchecked all starting programs in msconfig.

My guess is that the problem was a result of the memory voltage, and bumping the voltage up to it's proper place helped prevent some sort of under voltage pre-measure (which results in a reboot).

Anyway, I hope that someone reads this and it helps to solve their problem.