Share via

My laptop keeps getting BSOD, tried everything!

Anonymous
2019-09-07T21:39:37+00:00

I bought a windows 10 laptop a year ago, everything worked fine for it for the most part. Then one day something went wrong and it blue screened. I've had multiple bluescreen issues such as memory_management issue, ntsf.sys has failed, corrupted faulty hardware, unhandled exception thread, and a few others.

So i have sent in my laptop, they recommend it needs a new motherboard, so i did that, which was 1000$! and replaced it, the issue still happened. I reformated and did system restore twice! Issue still comes back, once a week it happens!

I have no idea what to do at this point. I have wiped the drive twice, replaced the motherboard, took the computer to a shop and had it scanned, it passed the graphics card and ram test successfully. So i'm out of options now, what else can i do?

I have scanned the hard drives sfc/scan now, virus scanned, malware scanned, everything! The computer has never overheated or anything, but this stupid blue screen issue that happens once a week is driving me crazy, and im sure eventually it will destroy my computer. I'm forced at thiss point to sell it for 1000$, since i bought it for 2500$, and sunk an extra 1000$ into it...If anyone can help me fix this, please let me know.

specs

asus rog GL702VS

32 gigs of ram

i7 processor 7700hq

NVidia GeForce gtx 1070 8gb

2.8 ghz-3.8

windows 10 home

1 terabyte SSD

1 terabyte HD

75hz

Here is the most recent BSOD error it gave me.

==================================================

Dump File : 090619-8921-01.dmp

Crash Time : 9/6/2019 9:01:52 PM

Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Bug Check Code : 0x1000007e

Parameter 1 : ffffffffc0000005 Parameter 2 : fffff80118cd29c3

Parameter 3 : ffff97040658f118 Parameter 4 : ffff97040658e960

Caused By Driver : Ntfs.sys

Caused By Address : Ntfs.sys+12979

File Description : NT File System Driver

Product Name : Microsoft® Windows® Operating System

Company : Microsoft Corporation

File Version : 10.0.18362.1 (WinBuild.160101.0800)

Processor : x64

Crash Address : Ntfs.sys+1329c3

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\Windows\Minidump\090619-8921-01.dmp

Processors Count : 8

Major Version : 15

Minor Version : 18362

Dump File Size : 2,099,796

Dump File Time : 9/6/2019 9:03:14 PM

==================================================

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

22 answers

Sort by: Most helpful
  1. Anonymous
    2019-09-08T21:43:33+00:00

    Who did you pay to fix it last time? It was not really fixed so to my way of thinking it is a continuation of the same issue. Make sure you are speaking to higher management before you accept any denial of service claim. Do you know an attorney who might give a bit of free advice?

    Rob

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2019-09-08T20:32:37+00:00

    No. even make a copy somewhere else so just in case they want to see them you can easily provide them.

    Please let me know what they say.

    Rob

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2019-09-08T07:45:13+00:00

    Should i delete the minidumps now? I will chat with Asus tomorrow and post back what they say.

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2019-09-08T06:50:52+00:00

    2 of the minidumps were corrupt and unreadable. The other 3 all had the same probably cause.

    There were the 3 readable DMP files and all were essentially identical:

    090719-10453-01.dmp - 090719-5390-01.dmp - 090719-5328-01.dmp

    BugCheck C4, {2000, fffff8011da212f4, 0, 696d7741}

    *** WARNING: Unable to verify timestamp for atkwmiacpi64.sys

    *** ERROR: Module load completed but symbols could not be loaded for atkwmiacpi64.sys

    Probably caused by : atkwmiacpi64.sys ( atkwmiacpi64+12f4 )

    atkwmiacpi64.sys dated 7/2/2013 part of ASUS ATK Package - a Power Management application.

    Check with ASUS to see if you can either update that or remove it.

    If you remove it certain things might not work such as possibly the keyboard backlight and other similar. ASUS Support can tell you.

    Try the ASUS Chat or other contacts in the links I provided in a previous reply.


    BTW, I did a full detailed analysis on all 3 minidumps and no other software was even implicated. Though some hardware may still be.

    Here to help,

    Rob


    Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

    Please let us know the results and if you need further assistance. Feedback definitely helps us help all.

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2019-09-07T22:45:03+00:00

    Hi Eminent, I am Rob, an independent and a 14 time and dual award MVP specializing in Windows troubleshooting and Bluescreen analysis. Please remember as independents we are not responsible for the development of Windows or the computer hardware and drivers. If you will work with me I will be here to help until the issue is resolved.

    Nothing there that specifically helps though if we analyze the DMP file in detail we might be able to glean more info from it.

    1. Try removing ALL power. Open case, remove and reseat ALL cards, memory chips, and ALL cables (do not just try to snug) on both ends if they can be reached and on the device ends if not (removing the cables and reseating them helps to eliminate minor corrosion).
    2. Try adding a fan blowing into the case to reduce the chances that heat is involved. Remember that even though the levels are normal a single small component (resistor, capacitor, transistor or so on) could be too sensitive

    Troubleshoot blue screen errors <-- read this link

    http://windows.microsoft.com/en-us/windows-10/t...

    We can analyze the minidumps if you make them available from the OneDrive or other file sharing sites (such as MediaFire). If you have problems uploading the minidumps copy them to the Desktop or the Documents folder and upload them from there.

    One-Drive - Share files and folders and change permissions

    http://windows.microsoft.com/en-us/onedrive/sha...

    Upload photos and files

    http://windows.microsoft.com/en-us/onedrive/add...

    Zip or upload the contents of C:\Windows\minidump

    Use OneDrive to upload collected files

    http://social.technet.microsoft.com/Forums/en-U...

    ====================================================

    Does the system have RAID? If so that is also very suspect.

    This error is usually a driver issue and display adapter (video) driver is the most suspect though it could be others. Antivirus/antispyware/security programs, hardware (heat) and major software issues can also cause the error. When you get to the driver section of the troubleshooter use my generic methods below and then return to the troubleshooter if needed.

    Have you added hardware recently or updated drivers? Be sure to look in Windows Updates to see if any drivers were updated there. Other lessor possibilities include antivirus/anti-spyware/security programs.


    BCCode: 7E 0x0000007E which is also 0x1000007E

    BCCode: 7E 0x00000007E which is also 0x1000007E <-- read this link

    http://www.faultwire.com/solutions-fatal_error/...*1141.html?order=votes

    ==================================================

    1. This is my generic how to for proper driver updates :

    This utility makes it easy to see which versions are loaded : Run DriverView - set VIEW to Hide Microsoft drivers - update those without Dump in their names (and BIOS and chipset drivers).

    DriverView - Free - utility displays the list of all device drivers currently loaded on your system. For each driver in the list, additional useful information is displayed: load address of the driver, description, version, product name, company that created the driver, and more.

    http://www.nirsoft.net/utils/driverview.html

    For Drivers check System Maker as fallbacks and Device Maker's which are the most current. Right Click the Start Button - Device Manager - Display Adapter - write down the make and complete model of your video adapter - double click - Driver's tab - write down the version info. Now click UPdate Driver (this may not do anything as MS is far behind certifying drivers) - then Right Click - Uninstall - REBOOT this will refresh the driver stack.

    Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard if 3rd party with their own software and drivers and any other major device drivers you have.

    Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and then Device Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their latest versions. (Look for BIOS, Chipset, and software updates at System Maker's site while there.)

    Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN - REBOOT after each installation.

    Always check in Device Manager - Drivers tab to be sure the version you are installing actually shows up. This is because some drivers rollback before the latest is installed (sound drivers particularly do this) so install a driver - reboot - check to be sure it is installed and repeat as needed.

    Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER - check manually by model.

    Manually look at manufacturer's sites for drivers - and Device Maker's sites.

    http://pcsupport.about.com/od/driverssupport/ht...

    ====================================================

    1. Memory tests do not catch all errors such as mismatched memory (possible even for sticks that appear to be identical) and when faster memory is placed in system behind slower memory. So it is best to also swap sticks in and out to check for those even if all memory tests fail to show a problem.

    To test RAM check here - let it run 4+ hours or so. <-- best method

    www.memtest.org

    MemTestX86 - Test RAM With

    http://www.tenforums.com/tutorials/14201-memtes...

    For the Windows Memory Diagnostic Tool.

    Type in Cortana's search box -> Windows Memory Diagnostics

    at top of list - click it. in Windows 8/8.1/10 the name is "Windows Memory

    Diagnostic".

    ================================================

    1. After doing ALL the updates you can, and if the issue continues, then run DriverVerifier.

    Driver Verifier can help find some BSOD issues :

    Using Driver Verifier to identify issues with Windows drivers for advanced users

    http://support.microsoft.com/kb/244617

    How To Troubleshoot Driver Problems in Windows Vista or 7. (8/8.1 and 10

    are essentially the same).

    http://www.winvistaclub.com/t79.html

    Using Driver Verifier

    https://msdn.microsoft.com/en-us/library/window...

    WINKEY + X - RUN - type in -> verifier /reset hit enter to disable

    If DriverVerifier creates a minidump upload it and post the link here so we can analyze it.


    Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

    Please let us know the results and if you need further assistance. Feedback definitely helps us help all.

    1 person found this answer helpful.
    0 comments No comments