• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

COD4 Blue Screen of Death! Please Help!

S

SylEm

Senior member
About an hour into the game I'm getting BSOD. Here's the BSOD info I could get:

Product
Windows

Problem
Shut down unexpectedly

Date
1/9/2009 4:13 PM

Status
Report Sent

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033

Files that help describe the problem (some files may no longer be available)
Mini010909-02.dmp
sysdata.xml
Version.txt

Extra information about the problem
BCCode: a3
BCP1: 00000002
BCP2: 00090181
BCP3: 85AD6A78
BCP4: 850EBA60
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1
Server information: 60bcedbc-06fe-44cc-a517-63c66fbda155


Please help me if you know what to do. Thanks!
 
Originally posted by: SylEm
About an hour into the game I'm getting BSOD. Here's the BSOD info I could get:

Product
Windows

Problem
Shut down unexpectedly

Date
1/9/2009 4:13 PM

Status
Report Sent

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033

Files that help describe the problem (some files may no longer be available)
Mini010909-02.dmp
sysdata.xml
Version.txt

Extra information about the problem
BCCode: a3
BCP1: 00000002
BCP2: 00090181
BCP3: 85AD6A78
BCP4: 850EBA60
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1
Server information: 60bcedbc-06fe-44cc-a517-63c66fbda155


Please help me if you know what to do. Thanks!
Click to expand...



Read my website's BSOD section and let us know the results. Post here.
 
thanks will do. Does your info on the site work for Vista though? Briefly reading your instructions it sounds like its XP based.
 

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


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

Symbol search path is: SRV*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x82012000 PsLoadedModuleList = 0x82129c70
Debug session time: Sat Jan 3 20:50:00.589 2009 (GMT-8)
System Uptime: 1 days 2:22:28.764
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 877f9020, b2000040, 800}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, MCA_ASSERT
Arg2: 877f9020, Address of WHEA_ERROR_RECORD structure
Arg3: b2000040, High 32 bits of MCi_STATUS MSR for the MCA bank that had
the error
Arg4: 00000800, Low 32 bits of MCi_STATUS MSR for the MCA bank that had
the error

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


WHEA_ERROR_RECORD: !errrec ffffffff877f9020

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 1b

STACK_TEXT:
805d8488 823d18b5 00000124 00000000 877f9020 nt!KeBugCheckEx+0x1e
805d84dc 820d2928 877f9020 85a44008 85a44008 hal!HalBugCheckSystem+0xe1
805d8508 823d17c9 85a44008 00000000 805d8544 nt!WheaReportHwError+0x1d0
805d8518 823d1ea7 00000003 85a44008 00000000 hal!HalpReportMachineCheck+0x31
805d8544 823cd99f 805d3130 004c006c 00000000 hal!HalpMcaExceptionHandler+0xf7
805d8544 00000000 805d3130 004c006c 00000000 hal!HalpMcaExceptionHandlerWrapper+0x77


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x124_GenuineIntel

BUCKET_ID: 0x124_GenuineIntel

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


I hope this is what you wanted and I did it right =). Let me know what you think. There were a lot of DMP files in there, I took the one I figured was the latest one.
 
I'd suggest debugging the last 5 or 10, but based on this you have a hardware problem. A quick call to Dell or whoever your vendor is, your explanation of this (and your sending the dump to them) should get you a new machine. You can hit F1 in the debugger, then in the helpfile hit Debugging Techniques / Bug Checks (Blue Screens) / Bug Check Code Reference and find error 124 (it's wayyyy down the list) and you'll see this.
 
This is a custom build machine, so no manufactuer to contact. This is also the other one that is the newest:


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


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

Symbol search path is: SRV*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x82011000 PsLoadedModuleList = 0x82128c70
Debug session time: Fri Jan 9 16:10:42.029 2009 (GMT-8)
System Uptime: 0 days 0:50:03.076
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A3, {2, 90181, 85ad6a78, 850eba60}

Probably caused by : CLASSPNP.SYS ( CLASSPNP!SubmitTransferPacket+106 )

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

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

ACPI_DRIVER_INTERNAL (a3)
The ACPI Driver detected an internal inconsistency. The inconsistency is
so severe that continuing to run would cause serious problems.
The ACPI driver calls this when the state is so inconsistent that proceeding
would actually be dangerous. The problem may or may not be a BIOS issue, but
there is no way to tell.
Arguments:
Arg1: 00000002
Arg2: 00090181
Arg3: 85ad6a78
Arg4: 850eba60

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


CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA3

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 8269095b to 820de0e3

STACK_TEXT:
8cc889dc 8269095b 000000a3 00000002 00090181 nt!KeBugCheckEx+0x1e
8cc889f8 826985ca 00090181 85ad6a78 850eba60 acpi!_ACPIInternalErrorEx+0x1b
8cc88a18 82693d6c 85ad6a78 8cc88a54 8cc88a44 acpi!ACPIInternalGetDispatchTable+0x3e
8cc88a48 820ccfd3 85ad6a78 850eba60 8565c008 acpi!ACPIDispatchIrp+0x20
8cc88a60 8bfcc74b 86bfe738 8565c008 00001000 nt!IofCallDriver+0x63
8cc88a74 8bfcc15b 85ad6a78 863992c8 8659f7c0 CLASSPNP!SubmitTransferPacket+0x106
8cc88ab4 8bfcbee7 00000000 00bfe738 8649cdd8 CLASSPNP!ServiceTransferRequest+0x224
8cc88adc 8bfcc342 86399210 00000000 86399210 CLASSPNP!ClassReadWrite+0x16a
8cc88af0 820ccfd3 86399210 86bfe738 86bfe89c CLASSPNP!ClassGlobalDispatch+0x20
8cc88b08 8270a116 52b00000 86bfe738 866a21c8 nt!IofCallDriver+0x63
8cc88b1c 8270a151 8649cdd8 86bfe880 8649cd20 partmgr!PmReadWrite+0x111
8cc88b30 820ccfd3 8649cd20 86bfe738 86bfe738 partmgr!PmGlobalDispatch+0x1d
8cc88b48 8b91e6f1 86bfe8c0 866a2110 86bfe738 nt!IofCallDriver+0x63
8cc88b64 820ccfd3 866a2110 86bfe738 86bfe8e4 volmgr!VmReadWrite+0x1b3
8cc88b7c 8bf6ad77 00000001 52b00000 8cc88ba4 nt!IofCallDriver+0x63
8cc88b8c 8bf6b565 866a2ce0 86bfe738 8205021b fvevol!RequestPassThrough+0x3b
8cc88ba4 8bf69b6d 866a2ce0 86bfe738 8bfa6c50 fvevol!FveFilterRead+0x23
8cc88bc8 820ccfd3 866a2c28 86bfe738 00000000 fvevol!FveFilterRundownRead+0x11b
8cc88be0 8bf98864 86bfe8ec 00000000 867a54c8 nt!IofCallDriver+0x63
8cc88c08 8bf99542 867a54c8 86bfe738 00000000 ecache!EcDeviceIoCallLowerDriver+0x1d4
8cc88cd0 820ccfd3 867a5410 86bfe738 86bfe92c ecache!EcDispatchReadWrite+0xc26
8cc88ce8 8bf14033 8cc88d38 85bcd458 855c3030 nt!IofCallDriver+0x63
8cc88d08 820ccfd3 85bcd458 86bfe738 8a113a00 volsnap!VolSnapRead+0x14d
8cc88d20 8be14500 8a113988 8cc88d44 820ca288 nt!IofCallDriver+0x63
8cc88d2c 820ca288 8a113a00 00000000 ffffffff Ntfs!NtfsStorageDriverCallout+0x14
8cc88d2c 820ca381 8a113a00 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x118
8a113998 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31


STACK_COMMAND: kb

FOLLOWUP_IP:
CLASSPNP!SubmitTransferPacket+106
8bfcc74b 5f pop edi

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: CLASSPNP!SubmitTransferPacket+106

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CLASSPNP

IMAGE_NAME: CLASSPNP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 47918f70

FAILURE_BUCKET_ID: 0xA3_CLASSPNP!SubmitTransferPacket+106

BUCKET_ID: 0xA3_CLASSPNP!SubmitTransferPacket+106

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


What hardware needs replacing?
 
Originally posted by: SylEm
This is a custom build machine, so no manufactuer to contact.
Click to expand...

Ouch. Sorry to hear that.

Well, the dump says it could be a BIOS issue, so I'd update the BIOS, confirm you're running the latest of (everything from Microsoft), stop all overclocking and CPU/RAM overvolting, and try again. What did all the other dumps say when you went into the MS dump helpfiles and looked up the error codes?

If it's a bunch of random codes (and so far these are) getting a replacement from the vendor is about the only option; software errors tend to be pretty consistent.
 
do u think it could be my soundcard? I have a sound audigy 2zs platinum card, and apparantly vista doesn't support it. Do you think this could cause these crashes?
 
If you don't have the proper drivers for it, yes, a sound card could easily cause instability within your system. Try running it without the sound card and do what you normally do when you get the crashes.
 
I disabled it, still gettin BSOD's, here's the minidump after I disabled the soundcard:


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


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

Symbol search path is: SRV*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x8203b000 PsLoadedModuleList = 0x82152c70
Debug session time: Tue Jan 13 07:37:45.715 2009 (GMT-8)
System Uptime: 0 days 20:35:08.835
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {60, 1b, 1, 820eec13}

Probably caused by : ntkrpamp.exe ( nt!KiUnwaitThread+d )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000060, memory referenced
Arg2: 0000001b, IRQL
Arg3: 00000001, 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: 820eec13, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82172868
Unable to read MiSystemVaType memory at 82152420
00000060

CURRENT_IRQL: 1b

FAULTING_IP:
nt!KiUnwaitThread+d
820eec13 095660 or dword ptr [esi+60h],edx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: iw3mp.exe

LAST_CONTROL_TRANSFER: from 820eeba9 to 820eec13

STACK_TEXT:
be1fcce4 820eeba9 00000001 00000000 00000000 nt!KiUnwaitThread+0xd
be1fcd0c 822855c0 86b496c8 00000001 00000000 nt!KeSetEvent+0x8b
be1fcd54 82092a1a 00000398 00000000 0fd6ff68 nt!NtSetEvent+0x6f
be1fcd54 76fe9a94 00000398 00000000 0fd6ff68 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0fd6ff68 00000000 00000000 00000000 00000000 0x76fe9a94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiUnwaitThread+d
820eec13 095660 or dword ptr [esi+60h],edx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiUnwaitThread+d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7fa

FAILURE_BUCKET_ID: 0xA_nt!KiUnwaitThread+d

BUCKET_ID: 0xA_nt!KiUnwaitThread+d

Followup: MachineOwner
---------
 
Originally posted by: dclive
Originally posted by: SylEm
This is a custom build machine, so no manufactuer to contact.
Click to expand...

Ouch. Sorry to hear that.

Well, the dump says it could be a BIOS issue, so I'd update the BIOS, confirm you're running the latest of (everything from Microsoft), stop all overclocking and CPU/RAM overvolting, and try again. What did all the other dumps say when you went into the MS dump helpfiles and looked up the error codes?

If it's a bunch of random codes (and so far these are) getting a replacement from the vendor is about the only option; software errors tend to be pretty consistent.
Click to expand...

Did you do what I suggested?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top