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

Vista randomly BSOD no reason at all


  • Please log in to reply
No replies to this topic

#1 fritz222

fritz222

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:11:27 AM

Posted 11 August 2011 - 02:37 PM

hello,

Im looking for some help, I have a laptop (HP pavilion dv6000) that crashes randomly and gives a BSOD. There is new hardware installed in the last couple of months so the problem could be there, point is that its a network adapter, kinda needed for an internet connection ^^.

So i followed the guid on this forum for analyzing the BSOD memory dump files and this is my log, I hope somebody can help me.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18327.x86fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0x8280e000 PsLoadedModuleList = 0x82925c70
Debug session time: Wed Aug 10 08:58:19.476 2011 (GMT+2)
System Uptime: 0 days 0:01:24.054
Loading Kernel Symbols
...............................................................
................................................................
.......
Loading User Symbols
....................
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1, {82a16626, 0, fffe, 0}

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: kernel32!pNlsUserInfo                         ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: kernel32!pNlsUserInfo                         ***
***                                                                   ***
*************************************************************************
Probably caused by : ntkrpamp.exe ( nt!NtOpenKey+0 )

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

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

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them.  A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: 82a16626, address of system function (system call)
Arg2: 00000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 0000fffe, Thread->KernelApcDisable
Arg4: 00000000, Previous KernelApcDisable

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: kernel32!pNlsUserInfo                         ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: kernel32!pNlsUserInfo                         ***
***                                                                   ***
*************************************************************************

FAULTING_IP: 
nt!NtOpenKey+0
82a16626 8bff            mov     edi,edi

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1

PROCESS_NAME:  services.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 77bc5ca4 to 82858fe7

STACK_TEXT:  
8d6b4d64 77bc5ca4 badb0d00 00eef270 00000000 nt!KiServiceExit2+0x16e
00eef264 77bc4a40 005a1936 00eef2b8 00080000 ntdll!KiFastSystemCallRet
00eef268 005a1936 00eef2b8 00080000 00eef2d4 ntdll!ZwOpenKey+0xc
00eef2bc 00591b42 00eef2d4 00000238 000000cc services!ScTakeOwnership+0x2a
00eef2f8 0058ac52 000000cc 00eef330 00000000 services!ScRegOpenKeyExW+0x100
00eef56c 0058ac61 000000cc 00577c14 005ac040 services!ScDeleteTree+0xba
00eef7d0 00589809 000000c8 00eef828 00597948 services!ScDeleteTree+0xc9
00eef7dc 00597948 000000bc 000000c8 00eef808 services!ScDeleteRegTree+0x13
00eef828 00597aa8 00000000 00000000 00000000 services!ScDeleteCtrlSetOrphans+0xd9
00eef864 77acd309 00000000 00eef8b0 77ba16c3 services!ScCleanupThread+0x10c
00eef870 77ba16c3 00000000 772dec08 00000000 kernel32!BaseThreadInitThunk+0xe
00eef8b0 77ba1696 0059799c 00000000 00000000 ntdll!__RtlUserThreadStart+0x23
00eef8c8 00000000 0059799c 00000000 00000000 ntdll!_RtlUserThreadStart+0x1b


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nt!NtOpenKey+0
82a16626 8bff            mov     edi,edi

SYMBOL_NAME:  nt!NtOpenKey+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4cb710d6

FAILURE_BUCKET_ID:  0x1_VRF_nt!NtOpenKey+0

BUCKET_ID:  0x1_VRF_nt!NtOpenKey+0

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



BC AdBot (Login to Remove)

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users