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

Common BSOD or not!?


  • Please log in to reply
2 replies to this topic

#1 Sniki

Sniki

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:01:07 PM

Posted 24 December 2010 - 04:41 PM

Hi everyone,
my first post and too bad it's about BSOD..
anyway, am using Win7 for almost a month, so far I got 2 BSOD. the first one was about week after the installation, and I was able to fix the issue (Jraid fault).
yest. I got another one, I tried to shutdown the machine and boom!!! BSOD.

Here's the log:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 83461b86, a0ec1bd4, 0}

Probably caused by : ntkrpamp.exe ( nt!PspExitThread+45b )

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

2: 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.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 83461b86, The address that the exception occurred at
Arg3: a0ec1bd4, 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.

FAULTING_IP:
nt!PspExitThread+45b
83461b86 83bf2001000000 cmp dword ptr [edi+120h],0

TRAP_FRAME: a0ec1bd4 -- (.trap 0xffffffffa0ec1bd4)
ErrCode = 00000000
eax=00000000 ebx=86ed28f8 ecx=86ed28f8 edx=746c6644 esi=00000068 edi=00000000
eip=83461b86 esp=a0ec1c48 ebp=a0ec1cb4 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!PspExitThread+0x45b:
83461b86 83bf2001000000 cmp dword ptr [edi+120h],0 ds:0023:00000120=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: Babylon.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 834961e1 to 83461b86

STACK_TEXT:
a0ec1cb4 834961e1 40010004 893670c0 00000001 nt!PspExitThread+0x45b
a0ec1ccc 832c1133 893670c0 a0ec1cf8 a0ec1d04 nt!PsExitSpecialApc+0x22
a0ec1d1c 8325c504 00000001 00000000 a0ec1d34 nt!KiDeliverApc+0x28b
a0ec1d1c 76ee64f4 00000001 00000000 a0ec1d34 nt!KiServiceExit+0x64
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f71c 00000000 00000000 00000000 00000000 0x76ee64f4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!PspExitThread+45b
83461b86 83bf2001000000 cmp dword ptr [edi+120h],0

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!PspExitThread+45b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac

FAILURE_BUCKET_ID: 0x8E_nt!PspExitThread+45b

BUCKET_ID: 0x8E_nt!PspExitThread+45b

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


The first thing I noticed that Babylon wasn't working anymore after the BSOD, had to reinstall it.
so, what you think guys? it was Babylon fault?

thanks in advance
:)

Attached Files


Edited by Sniki, 24 December 2010 - 04:59 PM.


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,092 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:06:07 AM

Posted 24 December 2010 - 05:18 PM

http://www.sevenforums.com/crashes-debugging/133135-common-bsod-not.html

They seem to have a handle on it, I suggest sticking with them.

Louis

#3 Sniki

Sniki
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:01:07 PM

Posted 24 December 2010 - 05:26 PM

thank you Louis, I will.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users