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.

Photo

BSOD


  • Please log in to reply
1 reply to this topic

#1 yankees8223

yankees8223

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:10:07 AM

Posted 07 September 2010 - 11:27 AM

Hello. We have a Dell Latitude laptop computer that has blue screened twice this morning. The user said it happened when he was trying to burn a CD. My initial guess is that it's a bad driver for the CD-ROM or the CD software they have installed is causing it. I made a copy of the minidump files and ran them through Windows Debugger. Below is what I got from the debugger. Any input would be appreciated. Thank you.


BugCheck 1000007E, {c0000005, 804ee125, b2ea4b74, b2ea4870}

Probably caused by : ntkrnlpa.exe ( nt!ExAllocatePoolWithTag+7af )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804ee125, The address that the exception occurred at
Arg3: b2ea4b74, Exception Record Address
Arg4: b2ea4870, Context Record Address

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


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

FAULTING_IP:
nt!IopfCallDriver+2d
804ee125 ff548638 call dword ptr [esi+eax*4+38h]

EXCEPTION_RECORD: b2ea4b74 -- (.exr 0xffffffffb2ea4b74)
ExceptionAddress: 804ee125 (nt!IopfCallDriver+0x0000002d)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000070
Attempt to read from address 00000070

CONTEXT: b2ea4870 -- (.cxr 0xffffffffb2ea4870)
eax=0000000e ebx=00000001 ecx=865395c8 edx=84e0be28 esi=00000000 edi=84e2086d
eip=804ee125 esp=b2ea4c3c ebp=b2ea4c88 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
nt!IopfCallDriver+0x2d:
804ee125 ff548638 call dword ptr [esi+eax*4+38h] ds:0023:00000070=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

PROCESS_NAME: System

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

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: 00000070

READ_ADDRESS: 00000070

FOLLOWUP_IP:
nt!ExAllocatePoolWithTag+7af
805456af eb14 jmp nt!ExAllocatePoolWithTag+0x7c5 (805456c5)

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from 804ee129 to 804ee125

STACK_TEXT:
b2ea4c54 804ee129 8648d018 84e0be28 00000000 nt!IopfCallDriver+0x2d
b2ea4cb8 805456af 00000002 00000000 00000000 nt!IopfCallDriver+0x31
b2ea4dac 805c61e0 84e206e0 00000000 00000000 nt!ExAllocatePoolWithTag+0x7af
b2ea4ddc 80541e02 f742075f 84e206e0 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!ExAllocatePoolWithTag+7af

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlpa.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b7a9cac

STACK_COMMAND: .cxr 0xffffffffb2ea4870 ; kb

FAILURE_BUCKET_ID: 0x7E_nt!ExAllocatePoolWithTag+7af

BUCKET_ID: 0x7E_nt!ExAllocatePoolWithTag+7af

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

BC AdBot (Login to Remove)

 


#2 Sketch71

Sketch71

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:09:07 AM

Posted 07 September 2010 - 11:44 AM

I have seen this issue in the past, It has generally been for me and issue relating to either Intel wired or wireless card drivers or a Multi media card reader drivers. I would make sure they have the most up to date version. Also you said it BSODed twice on you this morning....were you burning a CD when this happened?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Hey look, buddy, I'm an Engineer. That means I solve problems. Not problems like 'what is beauty?', because that would fall within the purview of your conundrums of philosophy. I solve practical problems.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users