blue screen stopcode wdiwifi.sys

[Michele_88]

HI Guys, My problem is this, I bought this new laptop 4 days ago, is an Acer predator Helios 300.
Once on i started to download the window updates straight away and there was one of 4gb that took long time but at the end my system ended up with a blue screen.
I restarted my laptop I checked for update again and I installed everything normally.
The problem now is that sometimes even if I'm not using the laptop I have a blue screen with '' stop code: kmode exception not handled" and the process is wdiwifi.sys.
I tried a window repair and this is the log file :
Startup Repair diagnosis and repair log
---------------------------
Last successful boot time: ‎8/‎1/‎2017 1:17:32 AM (GMT)
Number of repair attempts: 1

Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\Windows
AutoChk Run = 0
Number of root causes = 1

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 15 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 312 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 63 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 15 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Boot status test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Root cause found:
---------------------------
Boot status indicates that the OS booted successfully.

It does not say the problem and I don't understand if it's a software or hardware problem.

Thx for any answer that I will get .

 

[Colif]

wdiwifi.sys = WDI Driver Framework Driver

that 4gb update was a new version of windows 10. It looks like it broke itself on install, I would suggest trying this: https://answers.microsoft.com/en-us/insider/wiki/insider_wintp-insider_install/how-to-perform-a-repair-upgrade-using-the-windows/35160fbe-9352-4e70-9887-f40096ec3085

 

[Michele_88]

What about if I download window 10 creators update and try to get the last version with it?

 

[Colif]

What about if I download window 10 creators update and try to get the last version with it?

If you aren't on creators edition now, you can update to it and it might fix this. I figured the 4gb patch you got already is the Creators Edition, so running the repair is likely the best approach

right click start button
choose run...
type winver

Creators edition is version 1703, what number you have will tell you which solution to choose. If before 1703, run the update. if you on 1703, try the repair

Of course, you can also try this but it may not fix it all:
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, DISM cleans image files, re run SFC if it failed to fix all files and restart PC


the pages from solvusoft all say the same things for BSOD and generally include installing extra software you don't need.

 

[Michele_88]

Thx Manish but I already tried something like that, Colif at moment I'm sitting on version 1607 build 14393.1480 so I think that I will tray the creators update.

 

[Colif]

Strange it didn't update you to current build. I would have thought it make sense to jump to 1703 instead of installing an older build.

Your idea is a smart one. Might help to download the Windows 10 media creation tool (2nd button on page) and use it to make a win 10 installer on USB, and then once USB made, put it in PC, open file explorer and navigate to USB and run setup. this will update PC

Only suggest USB as if the update doesn't work, you won't have to download all the files again as they on USB

 

[Michele_88]

Ok I will try
Thanks Colif for your Help, I will let you know .

 

[Michele_88]

Nothing to do, after 2 months the problem is the same, blue screen all the time with different errors all the time 🙁

 

[Colif]

🙁

Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

 

[Michele_88]

Hi Colif,
How are you?
I followed the option 1 instructions, I went to c/window/minidump and there are already 10 files .dmp, 2 of them are from this morning ahahahah anyway can I upload one of them?
Thx for your help

ps: Can I upload the file on gthub?

 

[Colif]

I am not sure about that site, not used it myself. I would use something like Google Drive or Onedrive or something like those... your site choice might be fine though

Upload all of them as the more we have, the more we have to work with.

I am going away next weekend but hopefully we can figure it out before then.

 

[Michele_88]

Alright I will do it asap
thx Colif

 

[Michele_88]

Here all the links at the files .dmp

https://drive.google.com/file/d/0B5c_CC3CMJU_QVFBaHgyc3d2QXM
https://drive.google.com/file/d/0B5c_CC3CMJU_UWJKNWw5RFdQY2s
https://drive.google.com/open?id=0B5c_CC3CMJU_U0stSUgtSUxIQkU
https://drive.google.com/open?id=0B5c_CC3CMJU_X2tablE5UHd6WU0
https://drive.google.com/open?id=0B5c_CC3CMJU_TjVnTjI4T2tLQ00
https://drive.google.com/open?id=0B5c_CC3CMJU_ZzhCaDhDTnh3TkU
https://drive.google.com/open?id=0B5c_CC3CMJU_R0NaWlQtU1N4SVU
https://drive.google.com/open?id=0B5c_CC3CMJU_TDZVbktpNjFGVWs
https://drive.google.com/open?id=0B5c_CC3CMJU_VEVOTXB4eXZHUkU
https://drive.google.com/open?id=0B5c_CC3CMJU_YjhqWkdwLXNaOUk
https://drive.google.com/open?id=0B5c_CC3CMJU_LURqQkQxUzREV2M

 

[johnbl]

I looked at one of the bugchecks it looked like it was in the plug and play manager. to debug you should change the memory dump type to kernel, then when you get the next bugcheck, provide the memory dump.
c:\windows\memory.dmp it will show what was going on with the other cpu cores and someone can use the debugger command !pnptriage to see if it indicates what the problem is.

you might also:
update the bios or reset it to defaults so it will rescan your hardware and provide a updated database of settings to windows.

the error cause in the bugcheck was a bad address, this can be a indication of bad memory timings and would indicate that you should update the bios and run memtest86 to confirm the memory timings.

(did not look at the other memory dumps, got go, wife is giving me the evil eye)

 

[gardenman]

Do what john says to do first.

If you still have problems, see if there is an update for your Killer Networking drivers. Six of the crashes were likely caused by Qcamain10x64.sys. Here is the driver you have installed:

Jan 11 2017 - Qcamain10x64.sys - Qualcomm Atheros Network Adapter driver http://www.killernetworking.com/

Basic crash dump info:

Spoiler

File: 091817-8562-01.dmp (Sep 17 2017 - 22:09:23)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 23 Hour(s), 34 Min(s), and 28 Sec(s)

File: 091717-8062-01.dmp (Sep 16 2017 - 19:46:05)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
*** WARNING: Unable to verify timestamp for Qcamain10x64.sys
Probably caused by: Qcamain10x64.sys (Process: System)
Uptime: 0 Day(s), 22 Hour(s), 28 Min(s), and 49 Sec(s)

File: 091717-7984-01.dmp (Sep 16 2017 - 22:33:17)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
*** WARNING: Unable to verify timestamp for Qcamain10x64.sys
Probably caused by: Qcamain10x64.sys (Process: System)
Uptime: 0 Day(s), 1 Hour(s), 47 Min(s), and 36 Sec(s)

File: 091117-7859-01.dmp (Sep 10 2017 - 16:28:40)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
*** WARNING: Unable to verify timestamp for Qcamain10x64.sys
Probably caused by: nwifi.sys (Process: System)
Uptime: 0 Day(s), 15 Hour(s), 51 Min(s), and 33 Sec(s)

File: 091017-8593-01.dmp (Sep 9 2017 - 23:41:19)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
Probably caused by: memory_corruption (Process: System)
Uptime: 1 Day(s), 1 Hour(s), 19 Min(s), and 20 Sec(s)

File: 090917-7859-01.dmp (Sep 8 2017 - 22:14:05)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 12 Hour(s), 14 Min(s), and 26 Sec(s)

File: 090817-9328-01.dmp (Sep 8 2017 - 09:58:32)
BugCheck: [KERNEL_SECURITY_CHECK_FAILURE (139)]
*** WARNING: Unable to verify timestamp for Qcamain10x64.sys
Probably caused by: Qcamain10x64.sys (Process: System)
Uptime: 3 Day(s), 13 Hour(s), 00 Min(s), and 09 Sec(s)

File: 090417-8125-01.dmp (Sep 4 2017 - 04:14:41)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
*** WARNING: Unable to verify timestamp for Qcamain10x64.sys
Probably caused by: Qcamain10x64.sys (Process: System)
Uptime: 4 Day(s), 14 Hour(s), 23 Min(s), and 31 Sec(s)

File: 083117-7734-01.dmp (Aug 30 2017 - 09:28:23)
BugCheck: [BAD_POOL_CALLER (C2)]
*** WARNING: Unable to verify timestamp for Qcamain10x64.sys
Probably caused by: nwifi.sys (Process: System)
Uptime: 0 Day(s), 3 Hour(s), 23 Min(s), and 10 Sec(s)

File: 081317-8609-01.dmp (Aug 13 2017 - 08:03:40)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
Probably caused by: memory_corruption (Process: System)
Uptime: 2 Day(s), 9 Hour(s), 42 Min(s), and 59 Sec(s)

File: 081117-9109-01.dmp (Aug 10 2017 - 22:19:28)
BugCheck: [BAD_POOL_HEADER (19)]
Probably caused by: memory_corruption (Process: System)
Uptime: 1 Day(s), 13 Hour(s), 13 Min(s), and 23 Sec(s)

More info: https://pastebin.com/C2kSMW71

 

[Colif]

Can you follow option one here
and then do this step below: Kernel Memory Dumps - Have Windows Create a Kernel Memory Dump on BSOD.

Follow John, I won't be here for a few days so he might figure it out without me

Killer drivers.. argh... see here for updates: http://www.killernetworking.com/driver-downloads

laptop appears to have both Intel and killer WiFi, I would think about removing killer completely and just use the Intel WiFi, its far less likely to be the cause.

 

[Michele_88]

ok guys, I'm waiting another crush, I put now Kernel memory Dumps and as soon as crush again I will upload the new file, in the meanwhile I updated the Qualcomm Atheros Network Adapter from device manager.

 

[Michele_88]

Ok it is just happened....

https://drive.google.com/open?id=0B5c_CC3CMJU_QzZiNVcxZXBIZ1k

 

[gardenman]

Hi, you uploaded a minidump that was name Kernel dump (but it's only a minidump). Colif provided instructions above on how to change the setting from minidump to Kernel. Try that again then be sure to upload the right file. The Kernel dump file will be located here: C:\Windows\MEMORY.DMP
It's usually a huge file. If possible, compress it (ZIP) before uploading it.

 

[Michele_88]

ah sry I didn't know, I mean I changed the minidump to kernel but after the crashes he keep giving me files .dmp in the minidump directory, anyway I found the memory.dmp I'm going now to uploaded it.
thx gardenman

 

[Michele_88]

here we go guys..

https://drive.google.com/open?id=0B5c_CC3CMJU_ejZVMGs4UXZRekU 155Mb

 

[Colif]

i have to remember that detail, I don't request them very often. It gets me everytime...

 

[Michele_88]

Any good news guys?

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://pastebin.com/x44HXujt

File: MEMORY.DMP (Sep 19 2017 - 06:56:31)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 2 Hour(s), 04 Min(s), and 10 Sec(s)

I can't help you with this. Wait for someone else to reply. Good luck.

 

[johnbl]

you have a overclocking driver running
C:\Program Files (x86)\Intel\Intel(R) Extreme Tuning Utility\Drivers\IocDriver\64bit\iocbios2.sys Thu Jul 14 21:39:19 2016

i7-7700HQ Launch Date Q1'17

there is a good chance that the old overclock driver is applying incorrect voltages for your cpu. (driver is older than the CPU release date)
remove the driver and see if you still get the bugcheck.
bad overclock is consistent with the bugcheck info.

thermals look like the cpu was only 82 degrees F
if the sensor lookup is correct. (not overheated)
--------
looks like you have 20 modifications to your nt kernel file. you will want to start an admin an command prompt or admin powershell and run
dism.exe /online /cleanup-image /restorehealth
and run a Malwarebytes scan
------------
utorrentie.exe and uTorrent.exe running on machine.
just in case you did not know it was running
------------
plug and play was not running at the time of the bugcheck (unlike the minidump)
I will look at some of the internal logs

------------
system was running in turbo mode even though the system was idle.
(you might update the bios or reset it to defaults, the turbo mode might make the CPU overheat even if nothing was running)

Processor Version Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Processor Voltage 8ah - 1.0V
External Clock 100MHz
Max Speed 8300MHz
Current Speed 3400MHz

Manufacturer Acer
Product Name Predator G3-571
Version V1.01
Chassis Type Notebook
Vendor Insyde Corp.
BIOS Version V1.01
BIOS Starting Address Segment e000
BIOS Release Date 03/29/2017