Page 1 of 2 12 Last
  1. #1

    [W10StdV1703b15063 x64] Another BSOD Crash 0x7f

    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
    Attached Files Attached Files


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2

    Join Date
    Jul 2017
    Location
    Cambridge, UK
    Age
    59
    Posts
    96

    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:
    BugCheck 7F, {8, fffff801faa25e70, fffff801faa0dfc0, fffff801f7e92657}
    
    *** WARNING: Unable to verify timestamp for btfilter.sys
    *** ERROR: Module load completed but symbols could not be loaded for btfilter.sys
    Probably caused by : btfilter.sys ( btfilter+14702 )
    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.
    kvizerad says thanks for this.

  3. #3

    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.

  4. #4
    xilolee's Avatar
    Join Date
    Dec 2013
    Location
    World, Europe, Italy
    Posts
    2,247
    • specs System Specs
      • Manufacturer:
        XILOLEE.com
      • Model Number:
        XILO
      • Motherboard:
        ASROCK FM2A88M Pro3+ chipset A88X Bolton-D4
      • CPU:
        A10-7800, 4 CPU, 4 thr, 65/45W, FM2+, 28nm, Steamroller/Kaveri
      • Memory:
        10GB (Nanya and kingston ddr3-1333 9-9-9-24)
      • Graphics:
        Radeon R7 720MHz (8 GPU cores, integrated in CPU)
      • Sound Card:
        RealTek ALC662 (integrated in MB)
      • Hard Drives:
        Seagate ST500DM002-1BD142 500GB 7200RPM
      • Power Supply:
        SuperFlower 450W 80+ Platinum (SF-450P14PE)
      • Case:
        Sharkoon VG4-S
      • Cooling:
        Realtek RTL8111GR (NIC integrated in MB)
      • Display:
        Samsung SyncMaster SA100 LS22A100NS-EN
      • Operating System:
        Windows 10 Home/Standard x64

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

    Hi kvizerad.

    I was replying with a more detailed post, but I closed the browser by accident (grrrr).
    I'll be synthetic:
    1. 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.
    2. 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:
    3. 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:
    4. 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 by xilolee; 09-17-2017 at 09:36 AM.
    kvizerad says thanks for this.

  5. #5

    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.

  6. #6
    Sysnative Staff
    BSOD Kernel Dump Analyst
    Contributor

    Join Date
    May 2015
    Location
    The Netherlands
    Age
    21
    Posts
    648
    • specs System Specs
      • Manufacturer:
        Custom build
      • Motherboard:
        Gigabyte B150-HD3P-CF
      • CPU:
        Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
      • Memory:
        16GB DDR4 Crucial Ballistix Sport LT BLS8G4D240F
      • Graphics:
        Intel(R) HD Graphics 530
      • Sound Card:
        (1) Intel(R) Display Audio (2) Realtek HD Audio
      • Hard Drives:
        Crucial MX200 500GB & 2x Toshiba DT01ACA300
      • Power Supply:
        Corsair RM550x
      • Case:
        Fractal Design Define S
      • Cooling:
        Cooler Master TX3 i
      • Display:
        24" Liyama ProLite XB2483HSU-B2 & 24" Dell Ultrasharp U2414H
      • Operating System:
        Windows 10 Pro

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

    Speccy is a program that provides more detailed information about hardware
    Speccy - System Information - Free Download
    kvizerad says thanks for this.

  7. #7

    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.

  8. #8
    xilolee's Avatar
    Join Date
    Dec 2013
    Location
    World, Europe, Italy
    Posts
    2,247
    • specs System Specs
      • Manufacturer:
        XILOLEE.com
      • Model Number:
        XILO
      • Motherboard:
        ASROCK FM2A88M Pro3+ chipset A88X Bolton-D4
      • CPU:
        A10-7800, 4 CPU, 4 thr, 65/45W, FM2+, 28nm, Steamroller/Kaveri
      • Memory:
        10GB (Nanya and kingston ddr3-1333 9-9-9-24)
      • Graphics:
        Radeon R7 720MHz (8 GPU cores, integrated in CPU)
      • Sound Card:
        RealTek ALC662 (integrated in MB)
      • Hard Drives:
        Seagate ST500DM002-1BD142 500GB 7200RPM
      • Power Supply:
        SuperFlower 450W 80+ Platinum (SF-450P14PE)
      • Case:
        Sharkoon VG4-S
      • Cooling:
        Realtek RTL8111GR (NIC integrated in MB)
      • Display:
        Samsung SyncMaster SA100 LS22A100NS-EN
      • Operating System:
        Windows 10 Home/Standard x64

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

    Quote Originally Posted by kvizerad View Post
    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.
    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).
    kvizerad says thanks for this.

  9. #9

    Re: [W10StdV1703b15063 x64] Another BSOD Crash 0x7f

    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 . Will look forward for system reaction.


  10. #10
    xilolee's Avatar
    Join Date
    Dec 2013
    Location
    World, Europe, Italy
    Posts
    2,247
    • specs System Specs
      • Manufacturer:
        XILOLEE.com
      • Model Number:
        XILO
      • Motherboard:
        ASROCK FM2A88M Pro3+ chipset A88X Bolton-D4
      • CPU:
        A10-7800, 4 CPU, 4 thr, 65/45W, FM2+, 28nm, Steamroller/Kaveri
      • Memory:
        10GB (Nanya and kingston ddr3-1333 9-9-9-24)
      • Graphics:
        Radeon R7 720MHz (8 GPU cores, integrated in CPU)
      • Sound Card:
        RealTek ALC662 (integrated in MB)
      • Hard Drives:
        Seagate ST500DM002-1BD142 500GB 7200RPM
      • Power Supply:
        SuperFlower 450W 80+ Platinum (SF-450P14PE)
      • Case:
        Sharkoon VG4-S
      • Cooling:
        Realtek RTL8111GR (NIC integrated in MB)
      • Display:
        Samsung SyncMaster SA100 LS22A100NS-EN
      • Operating System:
        Windows 10 Home/Standard x64

    Re: [W10StdV1703b15063 x64] Another BSOD Crash 0x7f

    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".
    kvizerad says thanks for this.

  11. #11

    Re: [W10StdV1703b15063 x64] Another BSOD Crash 0x7f

    I run PC on the optimized defaults right now (about 1,5 hour). It seems OK.

  12. #12
    Tekno Venus's Avatar
    Join Date
    Jul 2012
    Location
    UK
    Age
    20
    Posts
    5,943
    • specs System Specs
      • Manufacturer:
        Custom Built
      • Motherboard:
        ASUS Z170I ITX
      • CPU:
        Intel Core i7 6700K
      • Memory:
        16GB DDR4
      • Hard Drives:
        500GB Samsung 850 EVO, 2TB Seagate HDD
      • Power Supply:
        450W Corsair SFX
      • Case:
        Silverstone SG13 ITX
      • Cooling:
        Corsair H60i
      • Display:
        Dell U2715H - 2160x1440 27 inch
      • Operating System:
        Windows 10 Pro x64

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

    Quote Originally Posted by xilolee View Post
    Quote Originally Posted by kvizerad View Post
    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.
    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).
    That hyperthreading bug is a very rare occurrence, normally only triggered under very specific loads and is not relevant here :)


  13. #13
    xilolee's Avatar
    Join Date
    Dec 2013
    Location
    World, Europe, Italy
    Posts
    2,247
    • specs System Specs
      • Manufacturer:
        XILOLEE.com
      • Model Number:
        XILO
      • Motherboard:
        ASROCK FM2A88M Pro3+ chipset A88X Bolton-D4
      • CPU:
        A10-7800, 4 CPU, 4 thr, 65/45W, FM2+, 28nm, Steamroller/Kaveri
      • Memory:
        10GB (Nanya and kingston ddr3-1333 9-9-9-24)
      • Graphics:
        Radeon R7 720MHz (8 GPU cores, integrated in CPU)
      • Sound Card:
        RealTek ALC662 (integrated in MB)
      • Hard Drives:
        Seagate ST500DM002-1BD142 500GB 7200RPM
      • Power Supply:
        SuperFlower 450W 80+ Platinum (SF-450P14PE)
      • Case:
        Sharkoon VG4-S
      • Cooling:
        Realtek RTL8111GR (NIC integrated in MB)
      • Display:
        Samsung SyncMaster SA100 LS22A100NS-EN
      • Operating System:
        Windows 10 Home/Standard x64

    Re: [W10StdV1703b15063 x64] Another BSOD Crash 0x7f

    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?
    By the way, BIOS version was 0505, now is 1009; changes:
    Read More:
    Last edited by xilolee; 09-17-2017 at 10:30 AM.
    kvizerad says thanks for this.

  14. #14

    Re: [W10StdV1703b15063 x64] Another BSOD Crash 0x7f

    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.

  15. #15
    xilolee's Avatar
    Join Date
    Dec 2013
    Location
    World, Europe, Italy
    Posts
    2,247
    • specs System Specs
      • Manufacturer:
        XILOLEE.com
      • Model Number:
        XILO
      • Motherboard:
        ASROCK FM2A88M Pro3+ chipset A88X Bolton-D4
      • CPU:
        A10-7800, 4 CPU, 4 thr, 65/45W, FM2+, 28nm, Steamroller/Kaveri
      • Memory:
        10GB (Nanya and kingston ddr3-1333 9-9-9-24)
      • Graphics:
        Radeon R7 720MHz (8 GPU cores, integrated in CPU)
      • Sound Card:
        RealTek ALC662 (integrated in MB)
      • Hard Drives:
        Seagate ST500DM002-1BD142 500GB 7200RPM
      • Power Supply:
        SuperFlower 450W 80+ Platinum (SF-450P14PE)
      • Case:
        Sharkoon VG4-S
      • Cooling:
        Realtek RTL8111GR (NIC integrated in MB)
      • Display:
        Samsung SyncMaster SA100 LS22A100NS-EN
      • Operating System:
        Windows 10 Home/Standard x64

    Re: [W10StdV1703b15063 x64] Another BSOD Crash 0x7f

    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).
    Last edited by xilolee; 09-17-2017 at 10:31 AM.

  16. #16
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    16,438
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    Re: [W10StdV1703b15063 x64] Another BSOD Crash 0x7f

    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

  17. #17

    Re: [W10StdV1703b15063 x64] Another BSOD Crash 0x7f

    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"
    [W10StdV1703b15063 x64] Another BSOD Crash 0x7f-event_1-png
    3. 06:53 - Get last warning
    [W10StdV1703b15063 x64] Another BSOD Crash 0x7f-event_2-png
    4. 06:56 - Get BSOD
    [W10StdV1703b15063 x64] Another BSOD Crash 0x7f-event_3_crash-png
    Attached Files Attached Files

  18. #18
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    16,438
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    Re: [W10StdV1703b15063 x64] Another BSOD Crash 0x7f

    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
    kvizerad says thanks for this.

  19. #19

    Re: [W10StdV1703b15063 x64] Another BSOD Crash 0x7f

    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.

  20. #20

    Join Date
    Jul 2017
    Location
    Cambridge, UK
    Age
    59
    Posts
    96

    Re: [W10StdV1703b15063 x64] Another BSOD Crash 0x7f

    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
    kvizerad says thanks for this.

Page 1 of 2 12 Last

Similar Threads

  1. [SOLVED] [Win 10 x64] BSOD Crash 0x7f (8)
    By kvizerad in forum BSOD, Crashes, Kernel Debugging
    Replies: 9
    Last Post: 08-15-2017, 03:10 PM
  2. [SOLVED] BSOD - Win7 x64 - 0x7f
    By Wiliwula in forum BSOD, Crashes, Kernel Debugging
    Replies: 7
    Last Post: 03-26-2016, 12:18 PM
  3. [SOLVED] BSOD 0x7f UPEXPECTED_KERNEL_TRAP_MODE caused by ntoskrnl.exe - Windows 8.1 x64
    By error01671 in forum BSOD, Crashes, Kernel Debugging
    Replies: 14
    Last Post: 06-08-2015, 05:23 AM
  4. Getting BSOD 0x7F - Windows 7 x86
    By Docfxit in forum BSOD, Crashes, Kernel Debugging
    Replies: 14
    Last Post: 04-09-2015, 01:38 AM
  5. [SOLVED] [Win7 x64] BSOD 0x7f UNEXPECTED_KERNEL_MODE_TRAP caused by ntoskrnl.exe
    By JX24 in forum BSOD, Crashes, Kernel Debugging
    Replies: 3
    Last Post: 06-17-2014, 04:27 PM

Log in

Log in