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 dump file debugged... what now?

  • Please log in to reply
1 reply to this topic

#1 Sapheron


  • Members
  • 1 posts
  • Local time:02:46 PM

Posted 13 July 2011 - 03:05 PM

Hello, this is my first post yaaaaaaaaaaaaaaaaaaaaaay!

I am in no way a techie, but I can help myself and have so far figured out how to debug my dump file... I just don't know what to do with the results. I have pasted the file below and would be grateful for help. I googled what viahduaa+2e058 means (that looked like an important line) and understood that it is probably a problem with my HD ADeck driver (right?), however, I wanted to set the scene for whoever deigns to help me.

I had just uninstalled my vlc player (it wasn't taking updates so I thought something was wrong with it and I downloaded and successfully installed it again). I watched a movie on it (equilibrium :thumbup2: fyi) and was then opening another avi file when (dum dum dum) BSOD. I wonder if the newly reinstalled vlc (which hasn't bugged since the problem happened two nights ago) is part of the problem or maybe the file (which I deleted post haste from paranoia).

Below I have posted my system specs and the transcript of the report. Thank you so much for even reading my epistle and endeavoring to assist me.

Microsoft XP Professional 2002 Service Pack 3
AMD processor model unknown
2.71 GHz 896 g of RAM

Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini071211-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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805540c0
Debug session time: Tue Jul 12 00:43:51.468 2011 (UTC - 5:00)
System Uptime: 0 days 1:59:43.031
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
Unable to load image viahduaa.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for viahduaa.sys
*** ERROR: Module load completed but symbols could not be loaded for viahduaa.sys
* *
* Bugcheck Analysis *
* *

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {b8115620, 0, f3cbd058, 0}

Could not read faulting driver name
Probably caused by : viahduaa.sys ( viahduaa+2e058 )

Followup: MachineOwner

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {b8115620, 0, f3cbd058, 0}

Could not read faulting driver name
Probably caused by : viahduaa.sys ( viahduaa+2e058 )

Followup: MachineOwner

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

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.
Arg1: b8115620, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: f3cbd058, If non-zero, the instruction address which referenced the bad memory
Arg4: 00000000, (reserved)

Debugging Details:

Could not read faulting driver name

READ_ADDRESS: b8115620

f3cbd058 ff30 push dword ptr [eax]






LAST_CONTROL_TRANSFER: from 805c62c2 to f3cbd058

WARNING: Stack unwind information not available. Following frames may be wrong.
b7d55dac 805c62c2 b8115620 00000000 00000000 viahduaa+0x2e058
b7d55ddc 80541e82 f3cbd04e b8115620 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


f3cbd058 ff30 push dword ptr [eax]


SYMBOL_NAME: viahduaa+2e058


MODULE_NAME: viahduaa

IMAGE_NAME: viahduaa.sys


FAILURE_BUCKET_ID: 0x50_viahduaa+2e058

BUCKET_ID: 0x50_viahduaa+2e058

Followup: MachineOwner

BC AdBot (Login to Remove)


#2 hamluis



  • Moderator
  • 56,384 posts
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:46 PM

Posted 13 July 2011 - 05:09 PM


Anytime installing/using a program...leads to a BSOD, it's probably a good idea to uninstall it/reinstall it, IMO.


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users