Laptop BSOD even after Win10 Reset

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 12
    Windows 10
    Thread Starter
       #11

    UPDATE:

    Just had two BSODS.

    Kernal_security_check_failure
    AND
    Interrupt_Exception_not_handled.

    If you need logs or event viewer let me know. Just fyi :)
      My Computer


  2. Posts : 12
    Windows 10
    Thread Starter
       #12

    UPDATE 2:

    Alright, after 3 BSODS, ive been tracking time and looking in event viewer.

    Every time, the first error is Event ID 1001, Source: hpdskflt.sys. It says the following:

    "The description for Event ID 1001 from source hpdskflt cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.If the event originated on another computer, the display information had to be saved with the event.The following information was included with the event: The request is not supported"

    Having not a lot of tech-knowledge, it seems like a faulty driver, no? Ive been googling and its seems to be a HP-driver - which makes sense since this PC is HP.

    ALSO!
    In system32, ive found the driver. When I hit properties, and "Digital signatures", there is 2 - the last being Microsoft Windows Hardware Compatibility Publisher from 12. oct - About the time my PC broke. None of the other drivers have this.

    So, what do I do? Is this the cause of my pc crashes? Do I delete it or repair?
      My Computer


  3. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       #13

    Whenever you have a BSOD please post a zip so that it can be troubleshooted:

    BSOD - Posting Instructions - Windows 10 Forums

    Many HP computer already have BIOS UEFI diagnostics.
    HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support

    If you open HP.com > software and drivers > enter the computer's serial or product number > download and install the most up to date version of the UEFI diagnostics.
    Or download version 6.4 from: HP PC Hardware Diagnostics | HP® Official Site

    Power on the computer in the evening and repetitively click the F2 or F10 key and run the UEFI diagnostics in loop until failure mode. Allow it to loop overnight and the next day click the keyboard escape key to end the testing.
    If there was a failure (even the battery) it will display an error code and the testing will be incomplete.
    Report into the thread the HP BIOS UEFI diagnostic test results. See if you can get at least 2 loops. The duration of testing is most impacted by the amount of RAM and size of the drive.


    Code:
    16/10/2017 14.42    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 50
    P2: ffffba00cb77a750
    P3: 0
    P4: fffff800ce5b6abc
    P5: 2
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\101617-6687-01.dmp
    \\?\C:\Windows\Temp\WER-7468-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28C5.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28E4.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28F5.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_8490c485e73e5f4e1ae8c615b1dbbeaee03725_00000000_cab_0b203c5d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: b94a3ef7-7181-44a9-844e-e96b23046449
    Report Status: 2049
    Hashed bucket:16/10/2017 14.42    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 50
    P2: ffffba00cb77a750
    P3: 0
    P4: fffff800ce5b6abc
    P5: 2
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\101617-6687-01.dmp
    \\?\C:\Windows\Temp\WER-7468-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28C5.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28E4.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28F5.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_8490c485e73e5f4e1ae8c615b1dbbeaee03725_00000000_033c2904
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: b94a3ef7-7181-44a9-844e-e96b23046449
    Report Status: 4
    Hashed bucket:
      My Computer


  4. Posts : 12
    Windows 10
    Thread Starter
       #14

    Thank you very much for helping. Heres the BSOD zip:

    Attachment 158414

    BSODs from gaming happened at 22:13 and 22:21, about 2 hours ago.

    Ill use the UEFI and post more when done :) Thanks!
      My Computer


  5. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #15

    Nothing of much use showing in the dump or the Event log. You can try stressing different parts of the laptop though, CPU, GPU and RAM, one at a time and see if any failures occur. These take time to do them right. If you don't want to take the time then don't do it at all.

    ===================================================
    Follow this tutorial to stress test your CPU:
    Prime95 - Stress Test Your CPU - Windows 10 Forums

    ===================================================
    Follow this tutorials to stress test your GPU:
    FurMark - GPU Stress Test - Windows 10 Forums

    If you have a AMD APU instead of a discreet GPU, try UNIGINE 3D Benchmark..

    ===================================================
    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses


    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    warning   Warning
    MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.


    If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note   Note
    MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.


    Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

    Take a picture when done and post in the forum please.

    ===================================================
    Lastly, try Driver Verifier:
    Driver Verifier
    is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Pay close attention to PART TWO and make sure the correct boxes are checked.

    Warning:
    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it.

    If you get a BSOD for any of these tests, rerun dm_log_collector and upload the resulting zip file.

    See here for Disk Cleanup: Open and Use Disk Cleanup in Windows 10 Performance Maintenance Tutorials
    Note: DO NOT check Compression.
      My Computers


  6. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       #16

    The computer's BIOS version that is currently in use is 2016.
    Update the BIOS to the 2017 version:
    HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support


    If this HP software is already installed the software update is listed as critical (Dated September 2017) as there can be fatal problems.
    If it has not already been installed please update:
    HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support


    With the BIOS not being up to date there may be other drivers offered in 2017 that have not yet been installed.
    There were chipset drivers in September 2017.
    Download and install all drivers with a 2017 date to make sure all drivers are up to date for the troubleshooting:
    HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support


    It appears that you had been using Windows driver verifier to produce some of the misbehaving drivers.
    Which link did you use for the test settings?

    Currently the computer that is troubleshooting the bsod mini dumps with the windbg debugging is incompletely debugging where it could not get thread contents or read irp information:
    5: kd> !thread
    ffffdd8cdbcd5080: Unable to get thread contents
    5: kd> !Irp ffff9e09d3bd08b0
    ffff9e09d3bd08b0: Could not read Irp



    However some of the malfunctioning drivers were identified with preliminary windbg debugging:
    bedaisy.sys
    netwtw04.sys

    1) Download and install: HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support


    2) The bedaisy.sys is not on the drivers list.
    See if you can identify the software/application and uninstall it if it is no longer used or reinstall it to update its driver.



    BEDaisy.sys BattleEye anti-cheat driver

    Initially released on 8 January 2015
    http://www.battleye.com/download.html

    Code:
    Netwtw04     Intel(R) Wireless Adap Intel(R) Wireless Adap Kernel        Manual     Running    OK         TRUE        FALSE        2.981.888         3.579.904   0          02/07/2017 20.25.56    C:\WINDOWS\system32\DRIVERS\Netwtw04.sys         8.192
    Code:
    BattlEye Service    BEService    Stopped    Manual    Own Process    "c:\program files (x86)\common files\battleye\beservice.exe"    Normal    LocalSystem    0
    Code:
    Event[2447]:  Log Name: System
      Source: Service Control Manager
      Date: 2017-10-16T23:44:16.360
      Event ID: 7045
      Task: N/A
      Level: Information
      Opcode: N/A
      Keyword: Classic
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: LAPTOP-KNLE1P34
      Description: 
    A service was installed in the system.
    
    
    Service Name:  BEDaisy
    Service File Name:  C:\Program Files (x86)\Common Files\BattlEye\BEDaisy.sys
    Service Type:  kernel mode driver
    Service Start Type:  demand start
    Service Account:
    Code:
    Name    [00000002] Intel(R) Dual Band Wireless-AC 7265Adapter Type    Ethernet 802.3Product Type    Intel(R) Dual Band Wireless-AC 7265Installed    YesPNP Device ID    PCI\VEN_8086&DEV_095A&SUBSYS_50108086&REV_61\C82158FFFF246FE400Last Reset    16/10/2017 23.43Index    2Service Name    Netwtw04IP Address    192.168.0.11, fe80::1ca:913b:3231:408aIP Subnet    255.255.255.0, 64Default IP Gateway    192.168.0.1DHCP Enabled    YesDHCP Server    192.168.0.1DHCP Lease Expires    17/10/2017 23.43DHCP Lease Obtained    16/10/2017 23.43MAC Address    ‪C8:21:58:24:6F:E4‬Memory Address    0xC3300000-0xC33FFFFFIRQ Channel    IRQ 4294967274Driver    c:\windows\system32\drivers\netwtw04.sys (19.51.4.2, 7,29 MB (7.643.648 bytes), 13/07/2017 17.41)

    Code:
    Event[2405]:  Log Name: System
      Source: Netwtw04
      Date: 2017-10-16T23:43:08.364
      Event ID: 7036
      Task: N/A
      Level: Information
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: LAPTOP-KNLE1P34
      Description: 
    The \Device\NDMP1 service entered the Intel(R) Dual Band Wireless-AC 7265 state.
    
    
    Event[2406]:
      Log Name: System
      Source: Netwtw04
      Date: 2017-10-16T23:43:08.442
      Event ID: 7010
      Task: N/A
      Level: Information
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: LAPTOP-KNLE1P34
      Description: 
    7010 - driver enabled (miniport init)


    Code:
    16/10/2017 20.13    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 139
    P2: 3
    P3: ffffda8166f74b30
    P4: ffffda8166f74a88
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\101617-6312-01.dmp
    \\?\C:\Windows\Temp\WER-7015-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26F0.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2710.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2720.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_6cd6c791572321f69c71073bf7f3db96cbed9_00000000_cab_17c036bf
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: cc788c3a-ad36-4f43-b828-c330a007a15e
    Report Status: 2049
    Hashed bucket:16/10/2017 20.13    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 139
    P2: 3
    P3: ffffda8166f74b30
    P4: ffffda8166f74a88
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\101617-6312-01.dmp
    \\?\C:\Windows\Temp\WER-7015-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26F0.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2710.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2720.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_6cd6c791572321f69c71073bf7f3db96cbed9_00000000_0314271f
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: cc788c3a-ad36-4f43-b828-c330a007a15e
    Report Status: 4
    Hashed bucket:
    16/10/2017 20.22    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 3d
    P2: fffff80218064c38
    P3: fffff80218064480
    P4: 0
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\101617-6421-01.dmp
    \\?\C:\Windows\Temp\WER-7343-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER273E.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER275E.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER276E.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3d_65cb92acdf1455a0b862414040c2b25bc9d234_00000000_cab_176c33e1
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 6fdb0f3a-e191-4c26-9672-28621afb453f
    Report Status: 2049
    Hashed bucket:
    16/10/2017 20.22    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 3d
    P2: fffff80218064c38
    P3: fffff80218064480
    P4: 0
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\101617-6421-01.dmp
    \\?\C:\Windows\Temp\WER-7343-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER273E.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER275E.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER276E.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3d_65cb92acdf1455a0b862414040c2b25bc9d234_00000000_0310276d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 6fdb0f3a-e191-4c26-9672-28621afb453f
    Report Status: 4
    Hashed bucket:
    16/10/2017 14.42    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 50
    P2: ffffba00cb77a750
    P3: 0
    P4: fffff800ce5b6abc
    P5: 2
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\101617-6687-01.dmp
    \\?\C:\Windows\Temp\WER-7468-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28C5.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28E4.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28F5.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_8490c485e73e5f4e1ae8c615b1dbbeaee03725_00000000_cab_0b203c5d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: b94a3ef7-7181-44a9-844e-e96b23046449
    Report Status: 2049
    Hashed bucket:
    16/10/2017 14.42    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 50
    P2: ffffba00cb77a750
    P3: 0
    P4: fffff800ce5b6abc
    P5: 2
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\101617-6687-01.dmp
    \\?\C:\Windows\Temp\WER-7468-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28C5.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28E4.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28F5.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_8490c485e73e5f4e1ae8c615b1dbbeaee03725_00000000_033c2904
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: b94a3ef7-7181-44a9-844e-e96b23046449
    Report Status: 4
    Hashed bucket:
    16/10/2017 21.18    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: c4
    P2: e2
    P3: ffff9e09d3bd08b0
    P4: 23e5f880080
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\101617-12437-01.dmp
    \\?\C:\Windows\Temp\WER-14625-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7C92.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7D0F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7EA6.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_526ecaa9916291eca44bdc2cf4117c81bb8c53_00000000_cab_22608915
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 40f72668-f054-41d8-a37d-b97d566ef042
    Report Status: 2049
    Hashed bucket:
    16/10/2017 21.18    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: c4
    P2: e2
    P3: ffff9e09d3bd08b0
    P4: 23e5f880080
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\101617-12437-01.dmp
    \\?\C:\Windows\Temp\WER-14625-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7C92.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7D0F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7EA6.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c4_526ecaa9916291eca44bdc2cf4117c81bb8c53_00000000_03387ee4
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 40f72668-f054-41d8-a37d-b97d566ef042
    Report Status: 4
    Hashed bucket:
    Last edited by zbook; 16 Oct 2017 at 21:05.
      My Computer


  7. Posts : 12
    Windows 10
    Thread Starter
       #17

    Thank you so much for helping, updating BIOS and drivers now.

    I did use Driver Verifier, but only shortly because I googled a BSOD and they said it would help. I just searched for old drivers and there were none.

    After that, I had a driver problem, but ran Verifier again and fixed it.

    Bedaisy.sys is PUBG (the game) anti-cheat software, and Ive been having crashes in other games, so not sure it thats the problem. Ill report back in a moment after BIOS and driver updates.

    The UEFI also ran 9 times without problems, will post dumps when I find where they are hidden :)
      My Computer


  8. Posts : 12
    Windows 10
    Thread Starter
       #18

    Im not sure the Chipset driver installs...

    When I download and install, I select directory but it just opens a CMD really fast saying something with directory, and Im not sure its getting properly installed.

    BIOS went fine though, and intsalling the rest of 2017 now.
      My Computer


  9. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       #19

    If you want you can reinstall any driver from the HP website and have all up to date drivers.
    Like software, drivers get corrupted, so updating drivers by downloading them again fixes the corruption.
    So if you want to download any driver that is the latest driver and is not a 2017 driver you can do that too.

    Once you completely update all drivers you can test them with windows driver verifier.

    Please create a brand new restore point before starting windows driver verifier.
    Creating a backup image with Macrium and placing the backup image onto another drive or into the cloud adds another layer of protection:
    Macrium Software | Macrium Reflect Free

    This is a link with the test settings:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
    This is a link with the 3 methods to turn off windows driver verifier:
    Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials

    If you have any bsod please post a new zip:
    BSOD - Posting Instructions - Windows 10 Forums
      My Computer


  10. Posts : 12
    Windows 10
    Thread Starter
       #20

    Huge thank you zbook!

    After BIOS update and some driver updates, it magicly doesnt BSOD anymore. I have no idea what is going on, but I love it.
    Huge thank you to you all, have a nice day!
      My Computer


 

  Related Discussions
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 12:40.
Find Us




Windows 10 Forums