Various BSODs starting beginning of december on Acer laptop

mikee286 · 14 Dec 2018

The first bsod I got was on the 10th IRQL_NOT_LESS_OR_EQUAL bsod pink color at boot up.

The second one I got was KMODE_EXCEPTION_NOT_HANDLED bsod ndis.sys wdiwifi.sys wdiwifi.sys+b5ba fffff800`f28e0000 fffff800`f29ac000 0x000cc000 0xd0815a78 11/6/2080

And today I got another BSOD while the computer was idling while I was away at work. This is what WhoCrashed says about today's BSOD

On Fri 12/14/2018 11:08:34 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\121418-8000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801492FDC39, 0xFFFFE500640EED50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

For some reason windows is deleting BSOD dump files and only hanging onto one. This is my setting for how to handle memory dumps .
Attachment 217328

Of course here is my dm collector file it will probably only reflect the most recent bsod

zbook · 14 Dec 2018

Hi mikee286,

Welcome to the Ten Forums BSOD forum.

There are two log collectors: DM and BETA
Please run the BETA log collector and post a zip into this thread.

BSOD - Posting Instructions - Windows 10 Forums
https://www.tenforums.com/attachment...-v2-beta15.zip
(extract all > open)

Open file explorer > this PC > C: > in the right upper corner search for: C:\windows\memory.dmp > if the file size is < 1.5 GB then zip and post a share link into the thread (one drive, drop box, or google drive)

mikee286 · 14 Dec 2018

drive link to dump

https://drive.google.com/file/d/1V-3...ew?usp=sharing

new dm file attached

zbook · 14 Dec 2018

1) The Microsoft symbol server has not yet been upgraded and the debugging cannot be performed at this time.
It is unknown when it will be up and running.

2) There is information in the logs about possible misbehaving drivers.
So this will be trial and error without the windbg debugging.

3) The RAM modules have different SKU.
When was each of the RAM modules installed?

4) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 | Tutorials

5) The BIOS: Version/Date Insyde Corp. V1.25, 3/3/2017
Upgrade the BIOS: 1.25 > 1.27
Product support

6) Identify the software related to: EyeoGmbH.AdblockPlus
Report the software into the thread.
Uninstall the software during the troubleshooting.
It can be reinstalled after one week of stability (no BSOD)

7) Uninstall Kaspersky AV using the applicable uninstall tool:
Removal tool for Kaspersky Lab applications (kavremover)

8) Kaspersky AV can be reinstalled after one week of computer stability (no BSOD)

9) Make sure Windows defender is on.

10) Uninstall and install: Qcamain10x64.sys
Qualcomm Atheros QCA9377 Wireless Network Adapter

Product support

Updating a driver. - Microsoft Community

Code:

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff801492fdc39, ffffe500640eed50, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

Code:

12/11/2018 2:20 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1e
P2: ffffffffc0000005
P3: fffff800ec2582fa
P4: 0
P5: ffffffffffffffff
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121018-6593-01.dmp
\\?\C:\WINDOWS\TEMP\WER-15328-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER76F5.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7705.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7724.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7744.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_ba9b7361b7a3c165ef08a195a3e4562d4f941ce_00000000_cab_03287743

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6a4dc0cf-dab9-47bf-a9ec-5508a743b896
Report Status: 4
Hashed bucket: 
Cab Guid: 0
12/14/2018 10:58 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 3b
P2: c0000005
P3: fffff801492fdc39
P4: ffffe500640eed50
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121418-8000-01.dmp
\\?\C:\WINDOWS\TEMP\WER-16187-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7157.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7177.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7196.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER71A6.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_d8ce5d8b2bcc9f3dc780c3a1d5a1ec7a928c63e5_00000000_cab_032071b5

Analysis symbol: 
Rechecking for solution: 0
Report Id: d7f5ba3c-56c2-4d63-9396-faa86fe65793
Report Status: 4
Hashed bucket: 
Cab Guid: 0
12/11/2018 1:05 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: a
P2: ffffda9ff3821bb8
P3: 2
P4: 0
P5: fffff8002183df44
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121018-11718-01.dmp
\\?\C:\WINDOWS\TEMP\WER-20125-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9E05.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9E25.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9E34.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9E54.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_72f23fe4b8bfc08ca37a51326becd2bd766d749c_00000000_cab_03349e62

Analysis symbol: 
Rechecking for solution: 0
Report Id: cceaf647-05e6-4553-8792-f183203dc7cf
Report Status: 4
Hashed bucket: 
Cab Guid: 0

Code:

12/11/2018 2:22 AM	Windows Error Reporting	Fault bucket 0x1E_c0000005_R_Qcamain10x64!__adf_nbuf_free, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 4a1f84ca-899d-4182-b98c-1d894ed5b390

Problem signature:
P1: 1e
P2: ffffffffc0000005
P3: fffff800ec2582fa
P4: 0
P5: ffffffffffffffff
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121018-6593-01.dmp
\\?\C:\WINDOWS\TEMP\WER-15328-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER76F5.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7705.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7724.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7744.tmp.txt
\\?\C:\Windows\Temp\WERC890.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_ba9b7361b7a3c165ef08a195a3e4562d4f941ce_00000000_cab_26a637fe

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6a4dc0cf-dab9-47bf-a9ec-5508a743b896
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0

Code:

Name	[00000005] Qualcomm Atheros QCA9377 Wireless Network Adapter
Adapter Type	Ethernet 802.3
Product Type	Qualcomm Atheros QCA9377 Wireless Network Adapter
Installed	Yes
PNP Device ID	PCI\VEN_168C&DEV_0042&SUBSYS_08A611AD&REV_31\4&20D2006&0&00EA
Last Reset	12/14/2018 4:57 PM
Index	5
Service Name	Qcamain10x64
IP Address	172.19.141.200, fe80::c19a:92a1:5d53:2d70
IP Subnet	255.255.255.0, 64
Default IP Gateway	172.19.141.1
DHCP Enabled	Yes
DHCP Server	172.19.141.1
DHCP Lease Expires	12/15/2018 12:57 AM
DHCP Lease Obtained	12/14/2018 4:57 PM
MAC Address	‪CC:B0:DA:71:7D:5B‬
Memory Address	0xB4200000-0xB43FFFFF
IRQ Channel	IRQ 4294967287
Driver	c:\windows\system32\drivers\qcamain10x64.sys (12.0.0.722, 2.25 MB (2,360,048 bytes), 8/29/2018 3:43 AM)

Code:

qcamain10x64	Qualcomm Atheros Extensible Wireless LAN 11AC device driver	c:\windows\system32\drivers\qcamain10x64.sys	Kernel Driver	Yes	Manual	Running	OK	Normal	No	Yes

mikee286 · 14 Dec 2018

zbook said:

3) The RAM modules have different SKU.
When was each of the RAM modules installed?

There is a 8gb module that came with the computer is made by kingston and I added a crucial 8gb stick back in november
Crucial 8GB Single DDR4 2400 MT/S (PC4-19200) SR x8 SODIMM 260-Pin Memory - CT8G4SFS824A at Amazon.com

This was recommended by the scanner provided on the crucial website as compatible with this computer. Also stated as compatible by amazon's part verifier tool. I ran memtest86 overnight because my thought was it was ram related but the cam came back clean. The only thing is I used a newer version of memtest 8.0 and it did 4 passes and declared everything fine as apposed to the old versions that ran indefinitely

zbook · 14 Dec 2018

For DDR4 we use Memtest86 version 8.0 for 8 or more passes.
RAM modules can pass Memtest and still produce BSOD.

The scanners test compatibility for the computer's motherboard.
The scanners do not test RAM module compatibilty (different SKU)
Computer manufactures can install different SKU at the time of sale as the module compatibility was tested.
End users do not have the tools for testing and it is recommended to always use matching pairs (matching SKU).

So if there are BSOD after the above steps the plan will be to test the RAM for 8 or more passes.
And possibly evaluate computer stability / instability with just one RAM module.

Code:

Location     : ChannelA-DIMM0
BankLabel    : BANK 0
Manufacturer : 859B
MemoryType   : DDR4
FormFactor   : SODIMM
Capacity     : 8GB
Speed        : 2133
Serial       : E1312A26
PartNumber   : CT8G4SFS824A.C8FDD1 
ECC          : False
TypeDetail   : {Synchronous}

Location     : ChannelB-DIMM0
BankLabel    : BANK 2
Manufacturer : Kingston
MemoryType   : DDR4
FormFactor   : SODIMM
Capacity     : 8GB
Speed        : 2133
Serial       : AE1FBA04
PartNumber   : ACR24D4S7S8MB-8     
ECC          : False
TypeDetail   : {Synchronous}

mikee286 · 14 Dec 2018

If worst comes to worst how will I know what ram is compatible with that kingston sku of ram. I actually looked for that ram online but couldn't find the exact one. I think it is a sku release specifically for acer. Here is the information for the ram currently in my laptop. The kingston part number ACR24D4s7s8mb-8 leads me to believe this ram module was made specifically for acer so I don't know how I would match it.

Also about the qualcomn wireless driver I looked on acer's site you linked but the drivers are very old there from 2016 whereas mine are from may 2018

Attachment 217344 Attachment 217345 Attachment 217346

zbook · 14 Dec 2018

AFAIK you can use RAM supported by the motherboard in pairs.
Mixing SKU may create an incompatibility issue.
At this time you can troubleshoot the steps in the earlier post.
If there are no further BSOD then the RAM is not an issue.

For the drivers it is always best to install the best tested drivers.
The best tested drivers are on the computer manufacturer's website.
Windows will update all Microsoft drivers and many non-Microsoft drivers.

The most up to date version of Windows can become corrupt.
In a similar fashion the most up to date driver can become corrupt.
Many end users are using computers that have driver support only through Windows 7 or 8 that are using Windows 10.
Again it is best to install the drivers displayed on the computer manufacturers website as they are the best tested drivers and then perform Windows updates.

On occasion there are problems with new drivers and they need to be rolled back.

Install the drivers from Qualcom displayed on the Acer website and then perform windows updates.
Qualcom no longer supports drivers and the drivers may be on the Killer Networks website.
If there are problems the driver can be uninstalled and reinstalled with a different driver version if you are able to find another version.

If you cannot find another driver then change the current driver from qcamain10x64.sys to qcamain10x64.sys.old

mikee286 · 15 Dec 2018

I have done all the things you have said

turned off fast startupuninstalled kasperskyadblock plus removedupdated bios to 1.27

qualcomm atheros drivers updated over windows update after I downgraded to the 2016 versions. I never deliberately upgrade drivers unless I am experiencing issues but that doesn't stop windows update from doing it. I hope windows update finds the best driver for the device.

I guess the next time I see a bluescreen I will take the crucial stick I bought out and see if that fixes the issue. It's really the only thing I have changed on the computer in december. I have installed nothing software wise. The timing seems like too much of a coincidence with the ram upgrade then these issues but none seem to point to the ram directly.

zbook · 15 Dec 2018

This BSOD txt report (WER) on 12/11/2018 is the best data available at this time that implicated the Qualcom driver as the cause of the BSOD.
Ordinarily we run commands on the dump files and were not able to with the problems with Microsoft database.

Code:

12/11/2018 2:22 AM	Windows Error Reporting	Fault bucket 0x1E_c0000005_R_Qcamain10x64!__adf_nbuf_free, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 4a1f84ca-899d-4182-b98c-1d894ed5b390

Problem signature:
P1: 1e
P2: ffffffffc0000005
P3: fffff800ec2582fa
P4: 0
P5: ffffffffffffffff
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\121018-6593-01.dmp
\\?\C:\WINDOWS\TEMP\WER-15328-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER76F5.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7705.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7724.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7744.tmp.txt
\\?\C:\Windows\Temp\WERC890.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_ba9b7361b7a3c165ef08a195a3e4562d4f941ce_00000000_cab_26a637fe

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6a4dc0cf-dab9-47bf-a9ec-5508a743b896
Report Status: 268435456
Hashed bucke