BSOD when mounting to docking station


  1. Posts : 27
    Virginia
       #1

    BSOD when mounting to docking station


    Good morning,

    User came in to weird error today - they think it might have been "LogMeIn". They started to get BSODs when placing the laptop, Lenovo T450s, onto docking station. Anything obvious in dumps? I uninstalled/reinstalled LogMeIn as a first step.

    Thanks!
      My Computer


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

    Hi Jimstigator.

    Please make it sure that your SSD is having the latest firmware.
    How to Upgrade Intel SSD Firmware | StorageReview.com - Storage Reviews

    If not, update it.

    In either case, report us back. We have to decide our next course of actions depending on the situation.

    _________________________________________
    Code:
    BugCheck F4, {3, fffffa800c974b30, fffffa800c974e10, fffff800035cce30}
    
    ----- ETW minidump data unavailable-----
    Probably caused by : csrss.exe
    
    Followup: MachineOwner
    ---------
    Code:
    BugCheck 1A, {41284, fffff900c64db001, 35e, fffff90000812000}
    
    Probably caused by : cdd.dll ( cdd!CddFreeShadowSysMem+6b )
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 27
    Virginia
    Thread Starter
       #3

    User still experiencing crashes. Always from cold start. Realized it has nothing to do with the docking station. I checked and the SSD firmware is up-to-date.

    Anything in the new logs?

    Thanks!
    Jim
      My Computer


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

    The docking was nothing but a coincidence.

    The new dumps are giving a hint of memory corruption. It may be a failing physical RAM, or it may be any driver passing bad info to the memory. The dumps are not very clear about the probable causes. So let us check for both the possibilities.

    Test your RAM modules for possible errors.Run memtest86+ for at least 8 consecutive passes.

    If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

    If it does not show any error, enable Driver Verifier to monitor the drivers.Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip



    Let us know the results, with the subsequent crash dumps, if any.
    ____________________________________
    Code:
    BugCheck 50, {fffff93fc0144c40, 0, fffff96000043d3f, 5}
    
    
    Could not read faulting driver name
    Probably caused by : win32k.sys ( win32k!vGetVerticalGSet+6f )
    
    Followup: MachineOwner
    ---------
    Code:
    BugCheck 3B, {c0000005, fffff9600007c67e, fffff880067fb340, 0}
    
    Probably caused by : win32k.sys ( win32k!PUBLIC_PFTOBJ::pPFFGet+6e )
    
    Followup: MachineOwner
    ---------
      My Computer


  5. Posts : 27
    Virginia
    Thread Starter
       #5

    I started the test and its nothing but red lines within a few seconds. This mean the physical RAM is bad and I need to warranty? Laptop is only a few weeks old...

    Thanks!
    Jim
      My Computer


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

    Jimstigator said:
    Laptop is only a few weeks old...

    Thanks!
    Jim
    Send it back asking for a replacement.
      My Computer


  7. Posts : 27
    Virginia
    Thread Starter
       #7

    Arc said:
    Jimstigator said:
    Laptop is only a few weeks old...

    Thanks!
    Jim
    Send it back asking for a replacement.
    Yeah... instead they offered me a back ordered RAM card since I'm outside the 21 day window by like 8 days. I've had to cannibalize one of my other new laptops to get a functioning card.

    Thanks for the help though, at least I know the issue.

    -Jim
      My Computer


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

    Let us know how the computer works with the replacement RAM.
      My Computer


  9. Posts : 27
    Virginia
    Thread Starter
       #9

    Arc said:
    Let us know how the computer works with the replacement RAM.
    All memory tests passed. So far, boots like a champ. Time will tell but it looks like a bad memory stick.

    Thanks again for all the help Arc. This place is an absolute gem.
    -Jim
      My Computer


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

    Welcome. For any further BSOD issue, give us a shout.
      My Computer


 

  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 21:21.
Find Us