Hi,
I bought my HP ProBook 4530s Laptop 7 months back. I had received 6 times BLUE SCREEN OF DEATH. I am very worried how to cope with this. I have windows 7 in my Laptop.
I open one of .dmp file that i get today and i am posted it here. Kindly read the errors and guide me what should i do to stop receiving this BLUE SCREEN OF DEATH.
Thanks
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 000000000013e5f1, page frame number
Arg3: 0000000000000001, current share count
Arg4: 0000000000000000, 0
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff80002e4c000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aa44
BUGCHECK_STR: 0x4E_7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002f1ce39 to fffff80002ebc5c0
STACK_TEXT:
fffff880`0a293348 fffff800`02f1ce39 : 00000000`0000004e 00000000`00000007 00000000`0013e5f1 00000000`00000001 : nt+0x705c0
fffff880`0a293350 00000000`0000004e : 00000000`00000007 00000000`0013e5f1 00000000`00000001 00000000`00000000 : nt+0xd0e39
fffff880`0a293358 00000000`00000007 : 00000000`0013e5f1 00000000`00000001 00000000`00000000 fffff880`041501a9 : 0x4e
fffff880`0a293360 00000000`0013e5f1 : 00000000`00000001 00000000`00000000 fffff880`041501a9 fffffa80`03bb1d30 : 0x7
fffff880`0a293368 00000000`00000001 : 00000000`00000000 fffff880`041501a9 fffffa80`03bb1d30 fffff800`02f30dbe : 0x13e5f1
fffff880`0a293370 00000000`00000000 : fffff880`041501a9 fffffa80`03bb1d30 fffff800`02f30dbe 00000000`42646641 : 0x1
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+705c0
fffff800`02ebc5c0 48894c2408 mov qword ptr [rsp+8],rcx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+705c0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------