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.


Need help with my Blue Screen Crashes

  • Please log in to reply
No replies to this topic

#1 Alkaniel


  • Members
  • 1 posts
  • Local time:12:06 PM

Posted 18 October 2010 - 03:53 PM

Here is the information of my crash, any help will be greatly appritiated:

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

Loading Dump File [C:\WINDOWS\Minidump\Mini010101-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 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp1.020828-1920
Machine Name:
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054a130
Debug session time: Mon Jan 1 07:09:30.140 2001 (GMT-4)
System Uptime: 0 days 0:05:36.890
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* *
* Bugcheck Analysis *
* *

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 1c, 1, 804f62e0}

*** WARNING: Unable to verify timestamp for ctaud2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ctaud2k.sys
Probably caused by : ctaud2k.sys ( ctaud2k+551cb )

Followup: MachineOwner

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

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.
Arg1: 00000000, memory referenced
Arg2: 0000001c, 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: 804f62e0, address which referenced memory

Debugging Details:



804f62e0 8939 mov dword ptr [ecx],edi





TRAP_FRAME: f7b0bac0 -- (.trap 0xfffffffff7b0bac0)
ErrCode = 00000002
eax=870f8cd0 ebx=870f8cc8 ecx=00000000 edx=00000000 esi=873ca640 edi=873ca6b0
eip=804f62e0 esp=f7b0bb34 ebp=f7b0bb54 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
804f62e0 8939 mov dword ptr [ecx],edi ds:0023:00000000=????????
Resetting default scope

LOCK_ADDRESS: 805481e0 -- (!locks 805481e0)

Resource @ nt!PiEngineLock (0x805481e0) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.

WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

Lock address : 0x805481e0
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 805331a1 to 804f52af

f7b0baa4 805331a1 0000000a 00000000 0000001c nt!KeBugCheckEx+0x19
f7b0baa4 804f62e0 0000000a 00000000 0000001c nt!KiTrap0E+0x2b5
f7b0bb54 806bb7eb 00000000 00000000 00000000 nt!KeWaitForSingleObject+0x184
f7b0bb74 f64721cb 86c7e488 86c7e3d0 86c7e464 hal!ExAcquireFastMutex+0x2b
WARNING: Stack unwind information not available. Following frames may be wrong.
f7b0bb88 f6472556 86c7e3d0 86c7e3d0 86c7e488 ctaud2k+0x551cb
f7b0bba0 f6471eae 870f8ae0 86c7e3d0 f7b0bbec ctaud2k+0x55556
f7b0bbb0 804eb171 870f8ae0 86c7e3d0 f7b0bc30 ctaud2k+0x54eae
f7b0bbc0 805764fa 873a7ce8 873a7ce8 00000002 nt!IopfCallDriver+0x31
f7b0bbec 8057672f 870f8ae0 f7b0bc0c 00000000 nt!IopSynchronousCall+0xb8
f7b0bc3c 804f2646 873a7ce8 00000002 00000000 nt!IopRemoveDevice+0x89
f7b0bc64 80577f4e e20fe350 0000000a e1ae33a0 nt!IopRemoveLockedDeviceNode+0x15e
f7b0bc7c 80577faf 873a7298 00000002 e1ae33a0 nt!IopDeleteLockedDeviceNode+0x32
f7b0bcb0 8057d7f5 873a7ce8 02ae33a0 00000002 nt!IopDeleteLockedDeviceNodes+0x3d
f7b0bd3c 8057daae f7b0bd74 806bb7f4 e1021f28 nt!PiProcessQueryRemoveAndEject+0x741
f7b0bd54 8057dbd0 f7b0bd74 873ca640 86bbe920 nt!PiProcessTargetDeviceEvent+0x24
f7b0bd7c 80528267 86bbe920 00000000 873ca640 nt!PiWalkDeviceList+0xce
f7b0bdac 805b046c 86bbe920 00000000 00000000 nt!ExpWorkerThread+0xed
f7b0bddc 80534ad6 8052817a 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


f64721cb ?? ???


SYMBOL_NAME: ctaud2k+551cb


MODULE_NAME: ctaud2k

IMAGE_NAME: ctaud2k.sys


FAILURE_BUCKET_ID: 0xA_ctaud2k+551cb

BUCKET_ID: 0xA_ctaud2k+551cb

Followup: MachineOwner

BC AdBot (Login to Remove)


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users