Memory Dump

Anubis_rs · June 2003

<div class="IPBDescription">NS causes memory Dump</div> ok when i'm playing NS and a new round starts it causes my system to perform a memory dump and then reboot, it doesn't happen on anyother HL mod or any other game for that matter it only happens on ns, any hepl would be appreciated,i'm running XP Pro

MonsieurEvil · June 2003

YEOW!

If you can get us a copy of your minidump file (it should default to c:\windows\minidump\%today's date%-<i>X</i>.dmp) and zip it, then post it up here, I can offer more assistance. We may need to have you change your default crash dump settings to be more verbose, but let's look at this first.

Anubis_rs · June 2003

Sorry took so long, had to format, but i reinstalled NS and the problems still there. heres the file

Sg1_stinky · June 2003

i got something simulare to this. sometimes when i start the game (i use ASE to connect to servers.but this happen when i start lan games too) the computer reboots and i get a minidump. it does not happen all the time just randomly

I think it might be the same problem as Anubis_rs

minidump fil attached

MonsieurEvil · June 2003

</span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> </td></tr><tr><td id='QUOTE'>kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: f827c7b2, Virtual address for the attempted write.
Arg2: 044a9121, PTE contents.
Arg3: 8053bc40, (reserved)
Arg4: 0000000a, (reserved)

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

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xBE

LAST_CONTROL_TRANSFER: from 000000be to 804fc1bb

STACK_TEXT:
8053bbc0 000000be f827c7b2 044a9121 8053bc40 nt!RtlpStatusTable+0x583

FOLLOWUP_IP:
cmaudio+307b2
f827c7b2 ?? <img src='http://www.unknownworlds.com/forums/html/emoticons/confused.gif' border='0' style='vertical-align:middle' alt='confused.gif'>

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: cmaudio+307b2

MODULE_NAME: cmaudio

IMAGE_NAME: <b>cmaudio.sys</b>

DEBUG_FLR_IMAGE_TIMESTAMP: 3b67e77d

STACK_COMMAND: kb

BUCKET_ID: 0xBE_cmaudio+307b2

Followup: MachineOwner
---------
</td></tr></table><span class='postcolor'>

I bolded the driver that is giving you problems - it is this cmaudio.sys driver file. It is apparently trying to write data to an area of memory that cannot be written to. Can you make sure that you have the most up to date drivers for your sound card?

</span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> </td></tr><tr><td id='QUOTE'>kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
An exception code of 0x80000002 (STATUS_DATATYPE_MISALIGNMENT) indicates
that an unaligned data reference was encountered. The trap frame will
supply additional information.
Arguments:
Arg1: c0000141, The exception code that was not handled
Arg2: 8057d15f, The address that the exception occurred at
Arg3: f3087e44, Trap Frame
Arg4: 00000000

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

EXCEPTION_CODE: (NTSTATUS) 0xc0000141 - The address handle given to the transport was invalid.

FAULTING_IP:
nt!ExpFreeHandleTableEntry+4c
8057d15f ?? <img src='http://www.unknownworlds.com/forums/html/emoticons/confused.gif' border='0' style='vertical-align:middle' alt='confused.gif'>

TRAP_FRAME: f3087e44 -- (.trap fffffffff3087e44)
ESP EDITED! New esp=f30881f4
ErrCode = 00000000
eax=00000001 ebx=fd29a748 ecx=00000400 edx=00000004 esi=00000a36 edi=fd29901c
eip=8057d15f esp=f3087eb8 ebp=f3088220 iopl=0 vif nv up ei pl nz na pe nc
cs=0000 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00080202
nt!ExpFreeHandleTableEntry+4c:
8057d15f ?? <img src='http://www.unknownworlds.com/forums/html/emoticons/confused.gif' border='0' style='vertical-align:middle' alt='confused.gif'>
Resetting default context

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 804fb49e to 8057d15f

STACK_TEXT:
f3088220 804fb49e fd299000 00001001 00000000 nt!ExpFreeHandleTableEntry+0x4c
f3088254 f97d32f7 fd299000 00000001 00000000 nt!MmClaimParameterAdjustUpTime+0x6
f30882a4 f97d207f 816b3000 f3088368 00001001 nv4_mini!dmaRegisterToDevice+0x80
f30882c8 f97cae30 816b3000 f3088368 00001001 nv4_mini!FlushWB+0x38c
f30882f8 f97cacfe 816b3000 00000041 f3088368 nv4_mini!NVPPrescaleAndFlip+0x199
f3088334 f97c9d67 c1d00055 beef0003 beef001e nv4_mini!NVPPrescaleAndFlip+0x67
f3088360 f98b219e 00000000 812a5b38 80f3b590 nv4_mini!NVPEProcessCommand+0xa8
f30883a8 f9afd0c6 816ed320 f30883fc 00000004 nv4_mini!_NULL_IMPORT_DESCRIPTOR <PERF> (nv4_mini+0xfa19e)
f3088438 804e6185 816ed038 80f3b578 00000030 VIDEOPRT!VpInterfaceDefaultReference+0x8
f3088448 bf858fe8 f30885c8 f30885b4 e2dae010 nt!DeleteNodeFromTree+0x6b
f3088478 bf85903e 816ed038 80022000 f3088504 win32k!xxxEmptyClipboard+0x2f
f308849c bf9ab311 816ed038 80022000 f3088504 win32k!xxxEmptyClipboard+0x8e

FOLLOWUP_IP:
nv4_mini!dmaRegisterToDevice+80
f97d32f7 ?? <img src='http://www.unknownworlds.com/forums/html/emoticons/confused.gif' border='0' style='vertical-align:middle' alt='confused.gif'>

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nv4_mini!dmaRegisterToDevice+80

MODULE_NAME: nv4_mini

IMAGE_NAME: <b>nv4_mini.sys</b>

DEBUG_FLR_IMAGE_TIMESTAMP: 3d94e6cb

STACK_COMMAND: .trap fffffffff3087e44 ; kb

BUCKET_ID: 0x8E_nv4_mini!dmaRegisterToDevice+80

Followup: MachineOwner
---------</td></tr></table><span class='postcolor'>

I bolded your problem as well, SQ1. Your PC is barfing on the nvidia video mini driver file. Are you running the latest version of the detonator drivers? If so, perhaps consider going back a version to a more stable certified one.

Anubis_rs · August 2003

my drivers are uptodate and the prob still happens anything else i cuold do

(sorry for the late reply)

MonsieurEvil · August 2003

This is still happening with NS 2.0?

Anubis_rs · August 2003

yep, was hoping it wouldn't but it does

MonsieurEvil · August 2003

ok, before we go any further:

Need all your specs as specified by the tech forum FAQ.
Have you yet tried *completely* uninstalling half-life and reinstalling, then patching, then reinstalling NS?

BigMadSteve · August 2003

Monse, how did you manage to get the minidump file to give you that information? Whenever I open it all i get is seemingly random characters.

Anubis_rs · August 2003

Yep i just uninstalled and reinstalled hl and the probs still there.

heres the specs, in order

Amd 1600 xp 1.4ghz
Leadtek winfast 64mb GF4, C-media onboard sound
Win XP Pro
1024 Open GL
When a round end in NS and just after you select what race you are going to be it causes a memory dump to occure
Nope
Halflife

MonsieurEvil · August 2003

Jay123 - <a href='http://www.microsoft.com/whdc/ddk/debugging/default.mspx' target='_blank'>http://www.microsoft.com/whdc/ddk/debuggin...ng/default.mspx</a>

(be warned - if you get all the symbols too, you are going to be downloading for *awhile*).

Anubis - have you tried completely uninstalling your drivers, then reverting back to the previous detonator drivers? Sometimes the latest and greatest aren't the best idea, depending on your card.

BigMadSteve · August 2003

Thanks. I've had a look at some dump files and it appears to be pointing at my sound and video drivers. I'll try and get Microsoft certified ones and see if that helps.

Memory Dump

Comments