BSOD on Sony Vaio Laptop KMODE_EXCEPTION. Reformatted w/ no luck.


  1. Posts : 1
    Windows 7 X64 Pro
       #1

    BSOD on Sony Vaio Laptop KMODE_EXCEPTION. Reformatted w/ no luck.


    I have a Sony Vaio laptop with Windows 7 64 Bit. Laptop just recently started throwing a BSOD on login. During the login the system is very slow, and then flashed to BSOD and restarts.

    Logged in via Safemode and have ran Memtest (no errors), Western Digital DLG Diagnostics on hard drive (no errors), SpyBot Search and Destroy (Found coupon bar, but thats it), ran CCleaner and cleaned all temp files, cache, prefetch (no change). Uninstalled Symantec Norton, no change.

    After all of this, I reformatted the system to factory, no change, still BSOD on login.

    I have tried removing 1 stick of ram at a time and trying again, no change. Have even went so far as replacing the RAM with ram from a working computer, no change still receiving BSOD.

    Here are the first set of dump files:

    https://dl.dropboxusercontent.com/u/.../DumpFiles.zip

    Then, here are the second set after removing Symantec.

    https://dl.dropboxusercontent.com/u/...DumpFiles2.zip

    I am at my wits end, can anyone help?

    Thanks,
    Jeremiah
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Virus check

    Scan your system with the following:

    Kaspersky TDSSKiller - How to remove malware belonging to the family Rootkit.Win32.TDSS (aka Tidserv, TDSServ, Alureon)

    ESET online scanner - One-time virus scanner free with ESET online scanner

    As well as Windows Defender Offline: How to Use Windows Defender Offline

    Hard Drive/Storage

    Post disk summary using CrystalDiskInfo software: CrystalDiskInfo Standard Edition

    • For how to upload a screenshot or file, read here

    Make a hard drive test from the hard drive manufacturers website: Hard Drive Diagnostic Procedure

    Msinfo32:
    Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter > Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post. Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

    If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "msinfo32 /nfo %USERPROFILE%\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back. Then zip up the .nfo file and upload/attach the .zip file with your next post.

    systeminfo:
    Please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "systeminfo.exe >%USERPROFILE%\Desktop\systeminfo.txt" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the syteminfo.txt file. If you have difficulties with making this work, please post back. Then zip up the .txt file and upload/attach the .zip file with your next post.

    Memtest86+

    Run Memtest86+ for at least 8-10 passes. It may take up to 20 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. How to Test and Diagnose RAM Issues with Memtest86+

       Note
    Pay close attention to part 3 of the tutorial in order to rule the faulty RAM stick out.

       Tip
    Do this test overnight.

    System Temperature

    Ensure that there are no heat issues, For monitoring heat of the system use Speccy or HWMonitor

    Next time you get a BSOD, upload all files.

    BSOD BUGCHECK SUMMARY
    Code:
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sun Jun  2 05:53:02.575 2013 (UTC + 6:00)
    System Uptime: 0 days 0:04:09.167
    BugCheck 1E, {ffffffffc0000005, fffffa8006a0c3ef, 0, 7fffffa003c}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+460da )
    BUGCHECK_STR:  0x1E_c0000005_R
    PROCESS_NAME:  SearchIndexer.
    иииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sun Jun  2 05:47:54.096 2013 (UTC + 6:00)
    System Uptime: 0 days 0:04:20.314
    BugCheck 1E, {ffffffffc0000005, fffffa80068c2610, 0, 7fffffa8000}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+460da )
    BUGCHECK_STR:  0x1E_c0000005_R
    PROCESS_NAME:  taskhost.exe
    иииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sun Jun  2 05:08:39.234 2013 (UTC + 6:00)
    System Uptime: 0 days 0:07:35.826
    BugCheck A, {10000008d, 2, 1, fffff80002c62812}
    Probably caused by : ntkrnlmp.exe ( nt!KeInsertQueueApc+42 )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  csc.exe
    иииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      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 12:32.
Find Us