Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


BSOD: "Memory_Management", infomation posted

  • Please log in to reply
2 replies to this topic

#1 PixarIsWin


  • Members
  • 9 posts
  • Gender:Male
  • Location:IN SPACE...THE FINAL FRONTIER (Toronto actually)
  • Local time:06:05 PM

Posted 09 February 2010 - 04:41 PM

Here is the info that http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/
required me to post

I've been having BSODS for quite a while now (and it's 1 month old PC, on my old PC there weren't any problems)
Basically I have a new HDD, and my old HDD is a slave under it. The BSODS happen when I'm not doing anything (idle on desktop screen), when I'm playing Warcraft 3, and when I'm just Instant Messaging.

if you can help fix this problem I will be very glad and thankful!

Microsoft Windows Debugger Version 6.11.0001.404 X86
Copyright Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini020910-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are 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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090804-1435
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Feb 9 16:20:15.437 2010 (GMT-5)
System Uptime: 0 days 4:31:24.109
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
Unable to load image RtkHDAud.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RtkHDAud.sys
*** ERROR: Module load completed but symbols could not be loaded for RtkHDAud.sys
* *
* Bugcheck Analysis *
* *

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, a8e945cb, a7a8b70c, 0}

Probably caused by : RtkHDAud.sys ( RtkHDAud+745cb )

Followup: MachineOwner

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

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
Arg1: c0000005, The exception code that was not handled
Arg2: a8e945cb, The address that the exception occurred at
Arg3: a7a8b70c, Trap Frame
Arg4: 00000000

Debugging Details:

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

a8e945cb 8990ac000000 mov dword ptr [eax+0ACh],edx

TRAP_FRAME: a7a8b70c -- (.trap 0xffffffffa7a8b70c)
ErrCode = 00000002
eax=00000000 ebx=a7a8b9ec ecx=89788678 edx=00000001 esi=8a41f728 edi=89788bc4
eip=a8e945cb esp=a7a8b780 ebp=a7a8b784 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
a8e945cb 8990ac000000 mov dword ptr [eax+0ACh],edx ds:0023:000000ac=????????
Resetting default scope




PROCESS_NAME: war3.exe

LAST_CONTROL_TRANSFER: from a8e4f2ef to a8e945cb

WARNING: Stack unwind information not available. Following frames may be wrong.
a7a8b784 a8e4f2ef 00000000 898ebd80 8a41f728 RtkHDAud+0x745cb
a7a8b9e0 a8e0e97d a8e0e872 00000000 a8e0e97d RtkHDAud+0x2f2ef
a7a8ba04 a8e0e9cf 8a48c4f0 898ebd80 e16d7094 portcls!PcDispatchProperty+0x130
a7a8ba2c b9610f5c 00000004 8a446ba8 8a446ba0 portcls!PropertyItemPropertyHandler+0x2b
a7a8ba90 b9610ed9 8a48c4f0 0000000c e16d7094 ks!KspPropertyHandler+0x616
a7a8bab4 a8e0c6a9 8a48c4f0 0000000c e16d7008 ks!KsPropertyHandler+0x19
a7a8bac8 a8e1970f 8a48c4f0 0000000c e16d7008 portcls!PcHandlePropertyWithTable+0x1b
a7a8bb00 a8e0c74d 898ebd00 8a42e030 8a48c4f0 portcls!CPortPinWaveCyclic::DeviceIoControl+0x1e5
a7a8bb1c b9610f1f 8a42e030 8a48c4f0 a7a8bb44 portcls!DispatchDeviceIoControl+0x49
a7a8bb2c a8e0c8c0 8a42e030 8a48c4f0 8a42e0e8 ks!KsDispatchIrp+0x126
a7a8bb44 a8e0c881 8a42e030 8a48c4f0 a7a8bb78 portcls!KsoDispatchIrp+0x43
a7a8bb54 a9258100 8a42e030 8a48c4f0 00000000 portcls!PcDispatchIrp+0x5f
a7a8bb78 804ef19f 8a42e030 00000004 8a48c4f0 RtkHDAud+0x438100
a7a8bb88 a8921774 e2f05898 00000000 8a48c4f0 nt!IopfCallDriver+0x31
a7a8bbd8 a89242a2 8a48c4f0 8a446ba8 e1ab7910 sysaudio!ForwardIrpNode+0x1b2
a7a8bc30 b9610f95 89cc4750 8a48c4f0 a7a8bc64 sysaudio!CPinInstance::PinDispatchIoControl+0x153
a7a8bc40 804ef19f 89cc4750 8a48c4f0 806e6410 ks!DispatchDeviceIoControl+0x28
a7a8bc50 8057f982 8a48c638 89baa500 8a48c4f0 nt!IopfCallDriver+0x31
a7a8bc64 805807f7 89cc4750 8a48c4f0 89baa500 nt!IopSynchronousServiceTail+0x70
a7a8bd00 80579274 00004784 00004228 00000000 nt!IopXxxControlFile+0x5c5
a7a8bd34 8054162c 00004784 00004228 00000000 nt!NtDeviceIoControlFile+0x2a
a7a8bd34 7c90e514 00004784 00004228 00000000 nt!KiFastCallEntry+0xfc
0012f13c 00000000 00000000 00000000 00000000 0x7c90e514


a8e945cb 8990ac000000 mov dword ptr [eax+0ACh],edx








BUCKET_ID: 0x8E_RtkHDAud+745cb

Followup: MachineOwner

BC AdBot (Login to Remove)


#2 hamluis



  • Moderator
  • 56,562 posts
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:05 PM

Posted 09 February 2010 - 06:03 PM

That info indicates a problem with your Realtek HD Audio drivers.

I suggest that you uninstall them (via Device Manager), then reboot and reinstall same properly.


#3 PixarIsWin

  • Topic Starter

  • Members
  • 9 posts
  • Gender:Male
  • Location:IN SPACE...THE FINAL FRONTIER (Toronto actually)
  • Local time:06:05 PM

Posted 09 February 2010 - 07:21 PM

hopefully there are no more errors :D

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users