[W10StdV1703b15063 x64] Another BSOD Crash 0x7f

K

kvizerad

Member
Joined
Aug 8, 2017
Posts
18
Hi everyone!

Almost month past after I got my first 0x7f (8) BSOD, and now it appears again. Last time it was bluetooth driver causing problem, so I updated it. For almost 1 month PC run without any issues. I would very appreciate any help with that problem.

My spec:

Operating system: Windows 10 Home (Build 15063), 64-bit
Motherboard: ASUS ROG MAXIMUS IX FORMULA
Monitor Name: Generic PnP Monitor
Monitor Model: ASUS VX239
CPU: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (8 CPUs), ~4.2GHz (not overlocked)
Memory: 32768MB RAM Corsair Vengeance LPX (4x8Gb)
Hard disk 1: 240Gb SSD Corsair Force LS Series
Hard disk 2: 4Tb SATA-III HGST (Hitachi) Ultrastar 7K6000
Graphics: NVIDIA GeForce GTX 1070
Sound card: Realtek Digital Output (Realtek High Definition Audio)
Power Supply: 750W Corsair RM750i

External devices:
USB3 Hub (with additional power supply)
WD My Passpoet External drives 2Tb x 4
 

Attachments

Re: [Win 10 x64] Another BSOD Crash 0x7f

Hello kvizerad,

I'm afraid its the same problem back again with the newer driver you loaded after the last episode.

Code: 
[COLOR=#1e1e1e]BugCheck [/COLOR][COLOR=#1e1e1e]7F[/COLOR][COLOR=#1e1e1e], {[/COLOR][COLOR=#1e1e1e]8[/COLOR][COLOR=#1e1e1e], [/COLOR][COLOR=#1e1e1e]fffff801faa25e70[/COLOR][COLOR=#1e1e1e], [/COLOR][COLOR=#1e1e1e]fffff801faa0dfc0[/COLOR][COLOR=#1e1e1e], [/COLOR][COLOR=#1e1e1e]fffff801f7e92657[/COLOR][COLOR=#1e1e1e]}[/COLOR]

[COLOR=#1e1e1e]*** WARNING: Unable to verify timestamp for [/COLOR][COLOR=#1e1e1e]btfilter.sys[/COLOR]
[COLOR=#1e1e1e]*** ERROR: Module load completed but symbols could not be loaded for [/COLOR][COLOR=#1e1e1e]btfilter.sys[/COLOR]
[COLOR=#1e1e1e]Probably caused by : [/COLOR][COLOR=#1e1e1e]btfilter.sys[/COLOR][COLOR=#1e1e1e] ( [/COLOR][COLOR=#1e1e1e]btfilter+14702[/COLOR][COLOR=#1e1e1e] )[/COLOR]

Your driver: btfilter.sys Tue Apr 18 11:17:07 2017 (58F5E7A3)

x BlueRobot provided a full explanantion of the mechanics of the crash in the previous thread. It is the same again.

If possible see if there is a more recent driver available.
 
Re: [Win 10 x64] Another BSOD Crash 0x7f

Hi philc43!

Thanks for your reply. It seems that the only option I have is to disable bluetooth device in BIOS - there are no any new drivers on ASUS site.
 
Re: [Win 10 x64] Another BSOD Crash 0x7f

Hi kvizerad. :wave:

I was replying with a more detailed post, but I closed the browser by accident (grrrr).
I'll be synthetic:
  • There's a new bios (and I think you should update it because of a hyperthreading bug in your CPU (microcode?): read carefully your manual about the updating.
  • Your ram isn't present in motherboard QVL.
    Compatible, and similar to yours, ram models present in your MB QVL, shows three dots (meaning they were tested succesfully in all slots/dimms):
    Read More:
  • Your motherboard isn't present in Corsair DDR4 Motherboard Compatibility.
    Maximus viii hero (z170 compatibility), instead of it, is present. Compatible ram models according to it:
    Read More:
  • A speccy snapshot could provide more information about your RAM (maybe the current loaded profile is correct, maybe not. In this case, you could try a lower profile... Not sure about terminology and I never tried these adjustments on my own...).
 
Last edited:
Re: [Win 10 x64] Another BSOD Crash 0x7f

Hi xilolee!

Actually there is new BIOS indeed, but I don't want to risk my warranty flashing BIOS while I have no experience in it. I'll save it for extreme measures.

Thats interesting, I never thought that little difference in RAM timing could result in something serious. CMK32GX4M4A2800C16 isn't in the list, but on the other hand CMD32GX4M4A2800C16 is, base difference between CMK and CMD is different heatspreader design (CMD have a bit more expensive and effective heatspreader). So don't really think that is the case.

Still if RAM was uncompatible with Motherbord that does not explain absolutely idle period of PC running (since February 2017 till August 2017) - I didn't have any issue or BSOD for like 6 months.

I'm sorry for asking dumb question but what is speccy? Snapshot of BIOS settings? I'm sorry asking this but English isn't my first language.
 
Re: [Win 10 x64] Another BSOD Crash 0x7f

Hi, axe0!

Thanks for explanation! I'll install it as soon as get to my PC. Should i provide any specific information from speccy?

At the moment I decided to disable Bluetooth in BIOS.
 
Re: [Win 10 x64] Another BSOD Crash 0x7f

kvizerad said:
Actually there is new BIOS indeed, but I don't want to risk my warranty flashing BIOS while I have no experience in it. I'll save it for extreme measures.
Click to expand...
I don't think you'll risk the asus warranty for an updated bios they created.
By the way, you should read this link (your cpu is part of the kaby lake family): Major Hyper-Threading Flaw Destabilizes Intel Kaby Lake, Skylake CPUs (click).
You could try to disable the hyper-treading (if you need bluetooth).
 
Well I did it. After another (third by count) BSOD I decided to flash new BIOS version. Damn, that is creepy process when you do it on your own for first time in life :eek4:. Will look forward for system reaction.

​
 
Did you also read and apply this?

"Ensure to load the BIOS default settings to ensure system compatiblity and stability. Select Load Optimized Defaults item under the Exit BIOS menu".
 
Re: [Win 10 x64] Another BSOD Crash 0x7f

xilolee said:
kvizerad said:
Actually there is new BIOS indeed, but I don't want to risk my warranty flashing BIOS while I have no experience in it. I'll save it for extreme measures.
Click to expand...
I don't think you'll risk the asus warranty for an updated bios they created.
By the way, you should read this link (your cpu is part of the kaby lake family): Major Hyper-Threading Flaw Destabilizes Intel Kaby Lake, Skylake CPUs (click).
You could try to disable the hyper-treading (if you need bluetooth).
Click to expand...

That hyperthreading bug is a very rare occurrence, normally only triggered under very specific loads and is not relevant here :)
 
With bluetooth enabled?

@Tekno Venus: it could be my English is not very good, but I translate "major flaw" as "very big problem".
If it is not major, it should be minor.
Maybe should they have used minor instead of major? :noidea:
By the way, BIOS version was 0505, now is 1009; changes:
Read More:
 
Last edited:
Bluetooth is enabled both in CMOS settings and Windows. I wonder if that solve the problem. Otherwice I'll just disable it.

By the way, I tried to figure out specific conditions make BSOD appears. There is some common thing about all three cases of BSOD - it occured after PC was on for quite a long time (more than 10hrs). I'll let PC work this night and look if something happens.
 
Very long time could be some months, not 10 hours...
I just read months on emule forum, I haven't tried it (just some days, or maybe a week). :w2::wink11a:
 
Last edited:
Give the system a good work out and check your 3rd party drivers at the same time.

Run Driver Verifier - Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista

Let it run for at least 24 hours in the background.

If BSODs are a software (3rd party driver) issue, Driver Verifier should BSOD the system and flag a 3rd party driver.

If BSOD, get the dump from \windows\minidump, zip it up and attach to your next post.

Regards. ..

jcgriff2
 
Well, it seems it weren't BIOS issues causing that problem - I get another two BSOD's (10.01.2017 and 10.04.2017). Sourse - bluetooth again.

I checked windows logs also, here how it goes:

1. 21:30 - PC on
2. 03:33 - Get first warning: "A command sent to the adapter has timed out. The adapter did not respond"
Event_1.PNG
3. 06:53 - Get last warning
Event_2.PNG
4. 06:56 - Get BSOD
Event_3_Crash.PNG
 

Attachments

What happened with Driver Verifier?

One of the 2 most recent dumps named Bluetooth - Driver Reference Table - btfilter.sys

You must find an update for the driver or disable Bluetooth.

Unfortunately, you have Atheros Bluetooth and updates for it are extremely hard to find, if not impossible.

Regards. . .

jcgriff2
 
Hi jcgriff2!

I've installed newest bluetooth drivers - it didn't take any effect (BSOD continues to occur)

I disabled Bluetooth in BIOS, but still I wonder if it could be hardware problem with USB adapter or onboard Bluetooth device.
My PC is still under warranty but I don't want to RMA untill I'll be sertain that it is hardware issue causes BSOD.
 
Looking at your latest BSOD crash dumps I also see that the Kaspersky drivers get mentioned in one of the threads. I would try running your system with the Kaspersky software removed and see if this makes a difference.

Code: 
ffffc001`190f14c0  fffff801`0d07fa4e*** WARNING: Unable to verify timestamp for klflt.sys
*** ERROR: Module load completed but symbols could not be loaded for klflt.sys
klflt+0x2fa4e

ffffc001`190f2228  fffff801`0aa759a2*** WARNING: Unable to verify timestamp for klbackupdisk.sys
*** ERROR: Module load completed but symbols could not be loaded for klbackupdisk.sys
klbackupdisk+0x59a2
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top