BSOD HP EliteBook Wake From Sleep

Page 1 of 2 12 LastLast

  1. Posts : 12
    Windows 7 32 bit
       #1

    BSOD HP EliteBook Wake From Sleep


    I've been having a problem with my laptop. I keep getting a BSOD or the screen bugs out like in the picture I attached. Some times it will recover, others it will BSOD, and even wierder it will just shut off shortly after bugging out. If the screen bugs out like that I can sometimes put it to sleep and when it wakes up its fine. I've tried doing a memtest and let it run all night. I didn't see any errors. I've tried reinstalling windows with the same result. I've also noticed it happens when the computer is woken for the first time after its been sitting (cold?). I've also switched hard drives to another known working one.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Apparently it seems to be a huge error with the storage.
    Code:
    3709 errors : !volmgrx (fffff880010e8000-fffff880010e8ffe)
    The disc is Corsair Force CSSD-F120GB2-BRKT 2.5" 120GB SATA II MLC Internal Solid State Drive (SSD).
    Make it sure that the firmware to the SSD is up-to-date. Corsair does it via their forums.

    Post a screenshot of the SSD using CrystalDiskInfo - Software - Crystal Dew World.

    Plus, test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.
    If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

    Let us know the results. How old the computer is? Is it still within warranty?
    Code:
    BugCheck 7A, {fffff6fc40008740, ffffffffc00000c0, 13b4d1860, fffff880010e8000}
    
    GetPointerFromAddress: unable to read from fffff80002cfe278
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : memory_corruption
    
    Followup: memory_corruption
    ---------
      My Computer


  3. Posts : 12
    Windows 7 32 bit
    Thread Starter
       #3

    Just over a year old its just out of warranty, I called them about it before it ended but they were no help. They insisted that it was a problem with windows or a virus. I've reinstalled windows (on a fresh SSD) with a clean disk and haven't restored any of my previous files and it is still doing it.

    I've noticed that it comes after logging in. Meaning when I wake the laptop from sleep its fine, as soon as I type in my password and hit enter it bugs out. What boggles my mind is that I swapped in the SSD for the factory drive and it is having the same problems on both.

    Here is crystal disk:
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    OK, let us know what memtest says.
      My Computer


  5. Posts : 12
    Windows 7 32 bit
    Thread Starter
       #5

    Ran MEMTEST all night with no errors (7 hours 2 passes). I also ran the Microsoft one, which froze the first time (did not show an error however).
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    You need to run memtest for at least 8 passes.
      My Computer


  7. Posts : 12
    Windows 7 32 bit
    Thread Starter
       #7

    Memtest 8 passes no errors. I'm lost to what it could be. I thought for sure it was bad ram.
      My Computer


  8. Posts : 12
    Windows 7 32 bit
    Thread Starter
       #8

    2 BSOD later here is another dump. I got a dialog box when I woke my laptop up that said something along the lines of ".... referenced memory at xxxxxxxxxx and could not find". It BSOD right after it came up so I didn't get a chance to take a picture.
      My Computer


  9. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #9

    ipyro24 said:
    2 BSOD later here is another dump. I got a dialog box when I woke my laptop up that said something along the lines of ".... referenced memory at xxxxxxxxxx and could not find". It BSOD right after it came up so I didn't get a chance to take a picture.
    Because there is no new BSOD after 05/03. :)

    Attachment 309753
      My Computer


  10. Posts : 12
    Windows 7 32 bit
    Thread Starter
       #10

    So I took a ram stick out, still doing it. I was going to switch them out with a different stick and see if it fixes it. Here is another BSOD. I wonder if it shut down before the other ones could dump.
      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 14:06.
Find Us