Computer Hope
Microsoft => Microsoft Windows => Windows Vista and 7 => Topic started by: moeenhappy on March 18, 2012, 12:04:40 PM
-
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
---------
-
Just a quick heads up...
You Posted this 5 times...4 times in the wrong spot...i deleted the others.
That's not how Forums work...be patient and someone will be along shortly.
patio.
Moderator.
-
Sorry for posting so much!!
-
Instead of the bugcheck Post the entire BSOD including the gibberish...
Include as much info on the PC as you can...
-
Hi,
Here is more complete details. BSOD.txt
==================================================
Dump File : 031812-17362-01.dmp
Crash Time : 3/18/2012 2:21:49 PM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`0013e5f1
Parameter 3 : 00000000`00000001
Parameter 4 : 00000000`00000000
Caused By Driver : afd.sys
Caused By Address : afd.sys+411a9
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\031812-17362-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 262,144
==================================================
==================================================
Dump File : 022312-20545-01.dmp
Crash Time : 2/23/2012 10:39:21 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`0126dea9
Parameter 3 : fffff880`03c5cb00
Parameter 4 : 00000000`00000000
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address :
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\022312-20545-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 262,144
==================================================
==================================================
Dump File : 022112-23462-01.dmp
Crash Time : 2/21/2012 7:04:15 AM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`00138fb7
Parameter 3 : 00000000`00000001
Parameter 4 : 00000000`00000000
Caused By Driver : bckd.sys
Caused By Address : bckd.sys+107d
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\022112-23462-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 262,144
==================================================
==================================================
Dump File : 012112-19874-01.dmp
Crash Time : 1/21/2012 6:03:17 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`00e09ea9
Parameter 3 : fffff880`0bd6fb00
Parameter 4 : 00000000`00000000
Caused By Driver : tdx.sys
Caused By Address : tdx.sys+9ea9
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\012112-19874-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 262,144
==================================================
==================================================
Dump File : 112011-24507-01.dmp
Crash Time : 11/20/2011 9:44:18 PM
Bug Check String : RESOURCE_NOT_OWNED
Bug Check Code : 0x000000e3
Parameter 1 : fffff800`0306d9a0
Parameter 2 : fffffa80`03cd0b60
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\112011-24507-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 266,288
==================================================
==================================================
Dump File : 091011-41979-01.dmp
Crash Time : 9/10/2011 6:29:48 AM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x1000009f
Parameter 1 : 00000000`00000004
Parameter 2 : 00000000`00000258
Parameter 3 : fffffa80`03ceb040
Parameter 4 : fffff800`00b9c4d0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7647a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+7647a
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\091011-41979-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 466,888
==================================================
-
...Include as much info on the PC as you can...
I have the same one bought about the same time. Not on it now.
I don't recognize anything in the BSOD. At least, it's still under warranty.
-
What would I post more?
Kindly guide me
-
Please read this first (http://www.computerhope.com/forum/index.php/topic,86050.0.html)
List as much about your computer as possible. This includes operating system (what version of Windows you are using), service packs, computer make/model, RAM, hard drive, sound and video cards, current adware/spyware/virus programs being used on a regular basis, do you have a "real" Windows CD, etc.
Use this to get all info post screenshot. http://www.hwinfo.com/download64.html
This is my hardware summary, yours should be the same, except for the RAM.
Post the Sensor Summary, too. Need to see if temps are normal. All should be about 40-45C, hard drive about 30-35C.
Fan speed will not be displayed. It is controlled in a proprietary manner which HWInfo is unable to support.
[year+ old attachment deleted by admin]
-
Hi Commando,
In response of your reply i am attaching the files for review.
Thnx
[year+ old attachment deleted by admin]
-
From MSDN:
See Here... (http://msdn.microsoft.com/en-us/library/windows/hardware/ff559014%28v=vs.85%29.aspx)
-
Hi
I can't understand the link.
Would you guide me what to do
Thnx
-
These actions might prevent an error like this from happening again:
1. Download and install updates and device drivers for your computer from Windows Update.
2. Scan your computer for computer viruses.
3. Check your hard disk for errors.
-
when i checked my windows update ON then it start update my window but it failed to finish it every time
-
when i checked my windows update ON then it start update my window but it failed to finish it every time
Turn off your anti-virus app and try it again...it may be interrupting it.
NOTE: It also may need to restart itself in the updates...turn off all programs running in the background.
Do NOT interrupt it...even if it appears to have stalled....in fact i wouldn't even use the PC while it's updating.
-
Hi,
windows update occur only when i shut down my computer the it automatically start update so i think antivirus was off at that time.
will i update all my drivers? from where i find a software that updates all my drivers?
kindly tell me how to update all of them
-
Use the Driver CD that shipped with the Probook...or visit the HP site and choose your Model # and windows version...
DLoad them to the desktop and double clik each one to install...
PS the Anti-Virus has to be shut off manually by you...it doesn't do it by itself.
-
Many thnx for your reply.
In hp there are so many drivers available.
which driver u recommend me to install? graphics, bios etc?
-
Everything for your specific Model # PC...Chipset drivers should go 1st.
-
Hi,
windows update occur only when i shut down my computer the it automatically start update so i think antivirus was off at that time.
will i update all my drivers? from where i find a software that updates all my drivers?
kindly tell me how to update all of them
That's normal. Updates are downloaded but many times are not installed until you shutdown the computer. Big warning on screen: "Do Not Turn Off Computer while Updates are Being Installed".
BTW, there is a BIOS update F0A, 7/18/2011, you have F09. There is also an F0B, do not do this one, it alters the BIOS security which maybe good for a company but not for an individual.
Rather than download all the drivers manually, HP has an Update service similar to Microsoft. Look for HP PC Tuneup on your ProBook. I'm not on the laptop now, so can't tell you exactly where it is.
Patio, BTW, HP does not provide any CD's or written docs with the ProBook. It's a business machine.
-
Gotcha Commando...
Thanx much for the heads up...
-
Hi Commando,
Have u seen the images which i have posted regarding sensor and pc information.
what they shows?
-
All sensor info looks normal.
-
Thanx
So what i do else for this blue screen problem???
-
You could reinstall Windows by going back to the "as shipped" configuration. There is a "F" selection on power-up.
Here is the HP support link: http://h10025.www1.hp.com/ewfrf/wc/product?cc=us&dlc=en&lc=en&product=5060881&query=probook%204530s%20xu015ut&
See your HP Support Assistant on the laptop desktop.
http://h71036.www7.hp.com/hho/us/en/pclc/articles/hp-support-assistant.html?lang=en&cc=us
BTW, our machines aren't exactly the same, there are many different 4530s configurations.
My complete part number is: 4530s-XU015UT#ABA
I'm working on another machine right now.
-
what is this F selection?
i cant fully understand ur reply
-
You could reinstall Windows by going back to the "as shipped" configuration. There is a "F" selection on power-up.
I think Computer_Commando means pressing the right function keys to access the recovery partition.