1.    28 May 2017 #1
    Join Date : May 2017
    Posts : 4
    Windows 10 Pro

    Frequent BSOD


    I believe the problem is with Qualcomm Atheros AR5BWB222 Wireless internet adapter. I've uninstalled/updated and downdated the driver but no go. BSOD seems to happen at periods of inactivity, when I might step away for a couple minutes. I recently switched to Kernel Dump but have been unable to get the proper symbols into WinDbg (Probably caused by : ntoskrnl.wrong.symbols.exe) I'm currently working on understanding how to use WinDbg but would appreciate anything you might be able to gather from the minidumps.

    EDIT:
    ************* Symbol Loading Error Summary **************
    Module name Error
    ntkrnlmp - This error is unknown: 0x400. Please contact the debugger team to report this error. (Mail: windbgfb@microsoft.com)
    Last edited by jerlands; 28 May 2017 at 12:57.
      My ComputerSystem Spec
  2.    28 May 2017 #2
    Join Date : May 2017
    Posts : 4
    Windows 10 Pro
    Thread Starter

    Quote Originally Posted by zbook View Post

    >click win + r keys and type winver

    >View the windows version and build and post in the forum
    Attachment 137142

    >Did you have any bsod after the computer was placed in clean boot?
    >All non-Microsoft applications unchecked and all task manager start up items disabled
    Haven't checked yet

    >Are you doing any over clocking or is any drive in raid configuration?
    No

    >Please repeat the mem test so that you can confirm that there were at least 8 runs
    >Which chkdsk command was checked? chkdsk only or chkdsk /x /f /r?
    >Please run overnight chkdsk /x/f /r if it has not already been run
    Will do tonight
    >>completed chkdsk /x /f /r

    >Verify that you have performed and following troubleshooting steps and if any were not completed please repeat >and post resulsts:

    >1) chkdsk /x /f /r and it found nor fixed any problems?

    >get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl >timecreated, message | out-file Desktop\CHKDSKResults.txt
    I ran this in powershell but it errors with "missing argument" and searching for it in Event Viewer didn't yield any results.

    >2) memtest64+ was ran for at least 8 runs and found no problems

    >Memtest86+ - Advanced Memory Diagnostic Tool
    I've run Windows Memory Diagnostic Tool (no errors) but will follow up.
    >>memtest86+ from PassMark ran and completed without errors.

    >3) sfc /scannow reported no integrity violations
    Yes- no violations

    >4) dism /online /cleanup-image /restorehealth displayed that it completed successfully
    I'm going to run this asap.. forgot about it.
    >>ran restorehealth but likely should have first run checkhealth

    >Run HD tune on your drive: http://www.hdtune.com/
    Will follow up
    >>Health is OK and no damaged blocks

    >Are your files backed up?
    Yes

    >Create a bootable windows 10 iso: Download Windows 10
    Yes


    I've been perusing driver related issues but will do further inspection of hardware.

    Thanks...
    Last edited by jerlands; 30 May 2017 at 10:03. Reason: additional info
      My ComputerSystem Spec
  3.    30 May 2017 #3
    Join Date : May 2017
    Posts : 4
    Windows 10 Pro
    Thread Starter

    I ran Memtest86+ USB provided from PassMark because my optical drive seems to have failed and the USB version from memtest.org I had issues with. The test ran 5.6 hours with no errors.

    This device is a laptop (Acer Aspire V3-772g) and my cpu and graphics chip run a little hot (approaching 70C) at times. I've planned to clean the fan but have delayed this really for no good reason. I'll try and get around to it soon. I don't think this is a factor as I've had BSOD early after boot and entering Windows.
      My ComputerSystem Spec
  4.    30 May 2017 #4
    Join Date : Jan 2017
    Karlsruhe
    Posts : 729
    Windows 10 Pro

    Hi there. I just analysed the last 5 bsod dumps. There are no drivers to blame and we have different bugcheck codes there. The cause for this could be hardware related. These are the last two dumps:
    Code:
    0x000000D1:    DRIVER_IRQL_NOT_LESS_OR_EQUAL (28.05.2017 18:43:47) [Windows 10] 
     
    CAUSED BY:     ntoskrnl    
     
    PROCESS:       ntoskrnl.wrong.symbols.exe 
     
    Usual causes:  Device driver 
     
     
    ============================================================================================================== 
     
     
    0x00000019:    BAD_POOL_HEADER (28.05.2017 05:25:13) [Windows 10] 
     
    CAUSED BY:     ntoskrnl    
     
    PROCESS:       ntoskrnl.wrong.symbols.exe 
     
    Usual causes:  Device driver

    Its says that "device drivers" are the usual cause for codes like this. I think theres really a 50:50 chance for driver/hardware.

    1. I saw you have done a few things like memtest. Did u run it at least 8 passes?

    2. You can try to remove Malwarebytes and BitDefender for testing and using Windows Defender instead.

    3. Theres a newer BIOS version for your Notebook available: Product support

    4. There are a bunch of errors in eventlog which show that the INTEL GPU driver crashed:
    Code:
    2017-04-29T07 54:09.313  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-04-29T09 10:44.509  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-02T09 57:41.517  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-02T11 26:29.818  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-02T11 41:18.245  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-05T17 01:11.897  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-06T17 41:31.954  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-09T10 05:07.850  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-09T16 54:07.766  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-10T11 01:39.700  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-12T17 04:57.996  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-13T10 16:12.518  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-17T17 50:39.019  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-20T10 38:26.312  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-22T23 59:41.648  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-23T15 28:34.462  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-25T19 52:37.173  Display driver igfx stopped responding and has successfully recovered.: .

    Try to update the INTEL GPU driver or roll back to a previous version.
      My ComputerSystem Spec
  5.    30 May 2017 #5
    Join Date : May 2017
    Posts : 4
    Windows 10 Pro
    Thread Starter

    Quote Originally Posted by BSODHunter View Post
    Hi there. I just analysed the last 5 bsod dumps. There are no drivers to blame and we have different bugcheck codes there. The cause for this could be hardware related. These are the last two dumps:
    Code:
    0x000000D1:    DRIVER_IRQL_NOT_LESS_OR_EQUAL (28.05.2017 18:43:47) [Windows 10] 
     
    CAUSED BY:     ntoskrnl    
     
    PROCESS:       ntoskrnl.wrong.symbols.exe 
     
    Usual causes:  Device driver 
     
     
    ============================================================================================================== 
     
     
    0x00000019:    BAD_POOL_HEADER (28.05.2017 05:25:13) [Windows 10] 
     
    CAUSED BY:     ntoskrnl    
     
    PROCESS:       ntoskrnl.wrong.symbols.exe 
     
    Usual causes:  Device driver

    Its says that "device drivers" are the usual cause for codes like this. I think theres really a 50:50 chance for driver/hardware.

    1. I saw you have done a few things like memtest. Did u run it at least 8 passes?

    2. You can try to remove Malwarebytes and BitDefender for testing and using Windows Defender instead.

    3. Theres a newer BIOS version for your Notebook available: Product support

    4. There are a bunch of errors in eventlog which show that the INTEL GPU driver crashed:
    Code:
    2017-04-29T07 54:09.313  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-04-29T09 10:44.509  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-02T09 57:41.517  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-02T11 26:29.818  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-02T11 41:18.245  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-05T17 01:11.897  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-06T17 41:31.954  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-09T10 05:07.850  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-09T16 54:07.766  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-10T11 01:39.700  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-12T17 04:57.996  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-13T10 16:12.518  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-17T17 50:39.019  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-20T10 38:26.312  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-22T23 59:41.648  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-23T15 28:34.462  Display driver igfx stopped responding and has successfully recovered.: .  
    2017-05-25T19 52:37.173  Display driver igfx stopped responding and has successfully recovered.: .
    Try to update the INTEL GPU driver or roll back to a previous version.

    1. I saw you have done a few things like memtest. Did u run it at least 8 passes?
    >>I'm not certain. I quickly set it up last night then this morning quickly requested the results be written but I can't find them. I'll start it later to see what the default is set for. I was thinking it was 8 passes. I'm using PassMark's USB version due to issues I was having with memtest.org's USB version.

    2. You can try to remove Malwarebytes and BitDefender for testing and using Windows Defender instead.
    >> I contacted Malwarebytes and they notified me of conflicts with my Atheros Qualcomm driver. I disabled Malwarebytes but still got BSOD. As for BitDefender.. I also disabled it but in that period of time received no BSOD so it's not cleared yet. I was hoping to get something specific from my attempts at WinDbg before longer periods without my virus protection. I still need to get the correct symbol loaded and am hoping to hear back from the WinDbg team.

    3. Theres a newer BIOS version for your Notebook available: Product support
    >>I've just downloaded and will probably install very shortly.

    4. There are a bunch of errors in eventlog which show that the INTEL GPU driver crashed:
    Try to update the INTEL GPU driver or roll back to a previous version.

    >>I've gone forward and backward with this. It's a screwy driver (specific to Acer config) that controls timing between Intel 4600 and Geforce 760M. I have elevated CPU/GPU temps and have planned to open it up, remove and clean the fan then also replace thermal paste but haven't gotten to it yet. I suspected maybe this but then have had BSOD early after boot. I understand how the sum of this mess might be the problem but still was looking to see if something specific can be deduced. I've run "bluescreen" on the minidumps and got same results. I want to peruse WinDbg but the symbol issue needs to be resolved.

    Thanks for the help and pointers.
      My ComputerSystem Spec
  6.    04 Jul 2017 #6
    Join Date : Jan 2017
    Karlsruhe
    Posts : 729
    Windows 10 Pro

    Is there any news or did you fix the problem?
      My ComputerSystem Spec

 


Similar Threads
Thread Forum
Solved Frequent BSOD memory_management
Hello I've been suffering with BSOD since I built my system a year ago and have never been able to solve. Please could someone offer some advice? I've been running driver verifier for 48hours. I'm not overclocking I have run memtest...
BSOD Crashes and Debugging
Frequent BSOD
Hello guys. In the past few months my PC has been constantly having a BSOD, usually 2 times a week or so (more frequently in the last few days). Most of the times it happens right after booting the OS, with WHEA_UNCORRECTABLE_ERROR. One time I...
BSOD Crashes and Debugging
Infrequent BSOD becoming more frequent
I see now I posted this in the wrong area of the forums. SORRY! If someone could move this to the BSOD section I would appreciate it. I built this PC three, maybe four, months ago now and haven't had many issues with it after initial troubleshoot...
BSOD Crashes and Debugging
Frequent BSOD, please help
Hello, so recently I've been getting a BSOD stating "CRITICAL_STRUCTURE_CORRUPTION win32kfull.sys". It happens randomly but its quite often. It might happen 1-2 times per hour or 1-2 per day. I don't know what to do anymore, I did all kinds of...
BSOD Crashes and Debugging
Frequent BSOD Wdf01000.sys
I've been getting BSODs when leaving my computer idle. Not running anything intensive. From looking at the minidump file I can't find much other than it's probably because of the Wdf01000.sys driver. Hopefully you can get all of the information...
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 16:18.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums