locked
Blue Screen Appear in my HP ProBook 4530s. RRS feed

  • Question

  • Hi,

    I have HP ProBook 4530s Laptop and i buy it before 5 months. I have faced an error two times (i.e. Blue screen error, you can see the image of that error in this link http://worshipcity.files.wordpress.com/2008/04/blue-screen-2.jpg).

    This error occurs when i was normally using my laptop and it doesn't occur start-up of laptop.

    I only receive this error 2 times only but i am worried if it cause any serious problem for me.

    Kindly guide me what to do?

    Thanks

    Regards

    MOEEN

    Saturday, January 21, 2012 5:55 PM

Answers

  • Hi,
     
    Here is a starting point for blue screen troubleshooting,
     
     
    For 0xA IRQL_NOT_LESS_OR_EQUAL,
     
     
    If you would like help with the analysis, please upload the dump files
    (typically in c:\windows\minidump) to skydrive and post a link,
     
     

    -- Mike Burr
    Interesting Reading on Technology and Finance
    • Marked as answer by Niki Han Monday, January 30, 2012 3:18 AM
    Saturday, January 21, 2012 11:06 PM
  • Bug Check Code 0xA:  http://msdn.microsoft.com/en-us/library/windows/hardware/ff560129(v=vs.85).aspx

    This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

    Please use Microsoft Skydrive to upload dump files (c:\windows\minidump). Once done, post a link here.

    If you want to debug dump files by yourself, refer to that: http://support.microsoft.com/kb/315263

    You can also contact Microsoft CSS for assistance.



    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.  

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    • Marked as answer by Niki Han Monday, January 30, 2012 3:18 AM
    Tuesday, January 24, 2012 8:48 PM

All replies

  • Hi,
     
    Here is a starting point for blue screen troubleshooting,
     
     
    For 0xA IRQL_NOT_LESS_OR_EQUAL,
     
     
    If you would like help with the analysis, please upload the dump files
    (typically in c:\windows\minidump) to skydrive and post a link,
     
     

    -- Mike Burr
    Interesting Reading on Technology and Finance
    • Marked as answer by Niki Han Monday, January 30, 2012 3:18 AM
    Saturday, January 21, 2012 11:06 PM
  • Bug Check Code 0xA:  http://msdn.microsoft.com/en-us/library/windows/hardware/ff560129(v=vs.85).aspx

    This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

    Please use Microsoft Skydrive to upload dump files (c:\windows\minidump). Once done, post a link here.

    If you want to debug dump files by yourself, refer to that: http://support.microsoft.com/kb/315263

    You can also contact Microsoft CSS for assistance.



    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.  

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    • Marked as answer by Niki Han Monday, January 30, 2012 3:18 AM
    Tuesday, January 24, 2012 8:48 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
    ---------
    Sunday, March 18, 2012 6:20 PM