HP Pavilion Laptop BSOD

Page 1 of 2 12 LastLast

  1. Posts : 13
    Windows 7 Home Premium
       #1

    HP Pavilion Laptop BSOD


    I have a HP HP Pavilion DV6 laptop running Windows 7 Home Premium x64 OEM version pre-installed with an Intel Core 2 Duo T6600 @ 2.2 GHz· ATI Mobility Radeon HD 4650 with 8GB RAM

    I have been getting random BSOD's lately and would appreciate any assistance that you can provide.


    The separate dmp file is for BSOD the occurred right after I created this message.

    ·
    Last edited by apccpa; 25 Jul 2015 at 22:43. Reason: Attach new dmp file
      My Computer


  2. Posts : 2,781
    Windows 10 Pro x64
       #2

    Hey there!
    Code:
    BugCheck 1E, {ffffffffc0000005, fffff8800aea7570, 0, 0}
    
    Probably caused by : nwifi.sys ( nwifi!Dot11AllocateSendPacket+58 )
    Code:
    BugCheck 1A, {41287, 9, 0, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+41a95 )
    Code:
    BugCheck 4E, {7, 1cf48a, 13, 0}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31 )
    Code:
    BugCheck 18, {0, fffffa800c448990, 2, fffffffffffffff0}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+487a1 )
    Code:
    BugCheck 1E, {ffffffffc0000005, fffff880084a4d60, 0, 0}
    
    Probably caused by : tcpip.sys ( tcpip! ?? ::FNODOBFM::`string'+3254d )
    Code:
    BugCheck D1, {13e61, 2, 1, fffff88002509190}
    
    Probably caused by : NETIO.SYS ( NETIO!FeNotifyFilter+3f )
    Code:
    BugCheck A, {2100000101, 2, 1, fffff80002eb8f36}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+126 )
    Code:
    BugCheck 3B, {c0000005, fffff80002eb9002, fffff88008086e50, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
    Code:
    BugCheck 24, {1904fb, fffff88003bb0588, fffff88003bafde0, fffff80002e59d22}
    
    Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteScb+ff )
    Code:
    BugCheck A, {0, 2, 0, fffff80002ed3661}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+171 )
    Code:
    BugCheck 1E, {ffffffffc000001d, fffff800031b1560, 0, 2400}
    
    Probably caused by : ntkrnlmp.exe ( nt!ApphelpCacheSendMessage+1e4 )
    Code:
    BugCheck 50, {fffffa806788ef44, 1, fffff88004d51e97, 5}
    
    
    Could not read faulting driver name
    Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProfilePerformanceTick+6ff )
    Code:
    BugCheck FE, {6, fffffa800a7a7058, 43787254, 0}
    
    Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_AssertSig+25 )
    Run sfc /scannow and chkdsk /r.
    Install the latest updates from Windows Update.

    Do the exact same steps for chkdsk /r but instead of typing in sfc /scannow type chkdsk /r.

    SFC /SCANNOW Command - System File Checker

    If that dosen't work then your only hope is to wipe the drive and re-install Windows since there is an 0x24 and a whole bunch of BSODs.
      My Computer


  3. Posts : 13
    Windows 7 Home Premium
    Thread Starter
       #3

    Thank you.

    I was wondering. If I have disk problems and I am able to repair them but not able to fully repair Windows 7, would an upgrade install of Windows 7 over itself, or a Windows 10 upgrade install potentially fix the windows problem? I may copy everything to a new disk before doing the upgrade.
      My Computer


  4. Posts : 2,781
    Windows 10 Pro x64
       #4

    Before wiping the drive run SeaTools if your boot drive is an SSD don't run it. SeaTools for DOS and Windows - How to Use

    It will check if your HDD is failing.
      My Computer


  5. Posts : 13
    Windows 7 Home Premium
    Thread Starter
       #5

    Scannow Log


    Thanks Laith,

    Chkdsk /r didn't find any disk errors.

    I ran sfc /scannow and got a message that it found corrupt files but could not fix all the errors.

    Attached is the log.
      My Computer


  6. Posts : 2,781
    Windows 10 Pro x64
       #6

    Have you installed the latest updates from Windows Update?
      My Computer


  7. Posts : 13
    Windows 7 Home Premium
    Thread Starter
       #7

    Updates


    Sorry, forgot to mention updates.

    Yes, it is updated. I always keep it up to date.
      My Computer


  8. Posts : 2,781
    Windows 10 Pro x64
       #8

    Install the latest DirectX drivers, if that dosen't work then your best bet is to re-install Windows as there is an 0x24 code in the dumps.
      My Computer


  9. Posts : 13
    Windows 7 Home Premium
    Thread Starter
       #9

    Directx


    It should have the latest direct x driver but will update.

    Would a Windows 10 upgrade possibly fix this?

    What does 0x24 mean?
      My Computer


  10. Posts : 2,781
    Windows 10 Pro x64
       #10

    It will probably fix it.
    An 0x24 is an NTFS_FILE_SYSTEM, it is usually and HDD failure or an corrupted install of Windows.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 15:24.
Find Us