BSOD after a few minutes (5 to 55 minutes) with Samsung SSD 840 EVO


  1. Posts : 4
    Microsoft Windows 7 Professional 64bit
       #1

    BSOD after a few minutes (5 to 55 minutes) with Samsung SSD 840 EVO


    Hi.

    I have successfully cloned my existing OS over to the SSD 840 EVO using Samsung magician. My OS boots fine with the SSD 840 EVO but crashes several minutes after startup.

    Crashes can happen from 5 to 50+ minutes after start up. The crashing process happens slowly, starting with the mouse cursor going into busy mode, then the active application freezes, but I can still swap between opened programs, then all other programs freeze, and finally ending with the blue screen. The process takes about 30 secs to go into the BSOD.

    When I allow my computer to reboot on its own, my BIOS will not be able to detect the SSD. However, after I recycle the power to the computer, it will be detected again and will be able to boot into windows, only to crash after a few minutes again.

    I have the latest firmware of the SSD installed.

    I do not have any crashes when I boot from my old HDD.

    I have tried the following but I still got the same results
    -Clean install windows 7 after secure erase
    -Secure erase + clone OS with Samsung magician a few more times
    -Changed SATA cables

    I'm suspecting a faulty SSD, but can't be sure.

    I will greatly appreciate any help! Thanks guys!
      My Computer


  2. Posts : 3,056
    Windows 10
       #2

    Welcome to SF :) .

    A few more dumps would have been nicer to have for better perspective on the issue.
    Regardless, the single bugcheck contains activity with the audio subsystem (portcls & atihdw67)
    with the driver involved is pretty recent.

    That is not inline with your description of the problem, please upload any
    other bugchecks that may exist.
      My Computer


  3. Posts : 7
    Windows 7 64-bit
       #3

    That sounds like my problem, and I also have SSDs. Is your BSOD's error code 0xF4?
      My Computer


  4. Posts : 4
    Microsoft Windows 7 Professional 64bit
    Thread Starter
       #4

    I lost most of the dump files whilst trying clean installs and re-cloning and stuff. I'll go intentionally crash the SSD OS a few more times.

    Meanwhile, I attached some photos of the BSOD with the error code, hopefully it can reveal a little more of my problem.
      My Computer


  5. Posts : 3,056
    Windows 10
       #5

    Thanks for the extra information :) .

    Most of those are 0x7A + a 0xF4, which are usually attributed to storage issues which is inline with your description
    of problem (unfortunately).

    Code:
    STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR
    
    Usual causes:  Memory, Paging file corruption, File system, Hard drive,
    Cabling, Virus infection, Improperly seated cards, BIOS,
    Bad motherboard, Missing Service Pack.
    We will hopefully know more with the dump files themselves, but for now if we take into account
    what is in post #1, it does look like storage is the issue.

    The bugcheck that uploaded was a 0x7E.

    Code:
    STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    
    Usual causes:  Insufficient disk space, Device driver, Video card, BIOS,
    Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service,
    Memory, 3rd party remote control.
    The stack didn't show much, it was an *access violation which basically means a device driver tried
    to access an address that it didn't have access to *(0xc0000005).
    As I said before the drivers involved were portcls & atihdw67, apart of the audio subsystem.
      My Computer


  6. Posts : 4
    Microsoft Windows 7 Professional 64bit
    Thread Starter
       #6

    Hi. I can't seem to get my computer generate a minidump when it crashes. I even did all 3 different options in the link above to configure my OS to log a minidump. I waited for the computer to restart itself after the bsod. But no new minidump in the minidump folder.

    Is there anything else I can try?
      My Computer


  7. Posts : 3,056
    Windows 10
       #7

    That is somewhat inline with the storage related bugchecks you're experiencing .

    Here's what we can try.

    First power cycle the SSD:

    Golden said:
    1. Power off laptop, unplug power lead, and remove battery.
    2. Press and hold down the on/off button for 30 seconds, then release.
    3. Disconnect the SSD.
    4. Press and hold the on/off button for another 30 seconds, then release.
    5. Reconnect SSD, reinsert battery, reconnect power lead.
    6. Reboot as normal.
    I see you have Samsung's Magician software, make sure the SSD is running the latest firmware.

    Test the HDD.

       Warning
    The Following Method Should NOT Be Performed On An SSD!

    Testing the HDD:

    1. Perform a Disk Check | Disk Check
    2. Then Post the results following | THIS METHOD
    3. Download SeaTools for DOS if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
    4. If SeaTools for Windows is unable to recognize your HDD visit HDDdiag and follow the instructions.

    If SeaTools For DOS does not recognize the drive;
    Boot into the BIOS using the *Fxkey.
    Look for an entry called SATA Mode (or something similar), it should be set to IDE / AHCI.
    It's probably set to AHCI which is why SeaTools doesn't recognize them in the DOS environment.
    Set it to IDE then save and exit usually by pressing the F10 key.
    Now boot into SeaTools and it should detect the drives.
    Start the Long Test and let it run.
    Upon completion don't try to boot into Windows as it will only result in a BSOD, go back into the BIOS
    and change the SATA setting back to what it was in the first place.




    The AMD sound device is now in an error state in the Device Manager, most commonly due to corrupt
    drivers / registry.

    Code:
    Name    AMD High Definition Audio Device
    Manufacturer    Advanced Micro Devices
    Status    Error
    Uninstall the driver from the device manager.

    1. Start menu type: devmgmt.msc (Hit enter).
    2. Find the AMD sound device, right click and select Uninstall.
    3. Reboot.
    4. Find updates and install (mainly the chipset and storage driver), please specify whether it found any and if so which ones were installed. - AMD Auto-Detect -



    Post back with the results :) .
      My Computer


  8. Posts : 4
    Microsoft Windows 7 Professional 64bit
    Thread Starter
       #8

    Sorry for being out for so long. I tried the power cycle. Nothing changed same crash. Just curious, how will a power cycle help in such a case?

    "Test the HDD" doesn't apply for me because I'm only having trouble with my SSD right?

    I fixed my audio driver too. Looks like its a faulty SSD? Any other possibilities?
      My Computer

  9.    #9

    For the SSD:

    writhziden said:
    If you have an SSD, make sure the following are up to date:
    • SSD firmware
    • BIOS Version
    • Chipset Drivers
    • Hard disk controller drivers/SATA drivers
    • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
      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 20:24.
Find Us