Random BSOD (mostly during gaming) going on for 5 years since built PC

Page 4 of 5 FirstFirst ... 2345 LastLast

  1. Posts : 41,474
    windows 10 professional version 1607 build 14393.969 64 bit
       #31

    Are you going through the windows recovery or advanced troubleshooting menu?
    Then startup options?
    Then restart
    Then select #6: safe mode with command prompt
    Then type or copy and paste: verifier /reset
      My Computer


  2. Posts : 24
    Windows 10 Home Premium
    Thread Starter
       #32

    Yes that is exactly what I am doing, and once I restart my computer it just blue screens again as if verifier was still on.
      My Computer


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

    Next time in the Windows advanced troubleshooting menu choose command prompt instead of startup options. Again this is not safe mode with command prompt but earlier in the menu where command prompt is a choice.
    It will open with Administrator: X:\windows\system32\cmd.exe
    Then type or copy and paste: verifier /bootmode resetonbootfail
      My Computer


  4. Posts : 24
    Windows 10 Home Premium
    Thread Starter
       #34

    Ok I'm about to sleep but will try tomorrow! Thanks.
      My Computer


  5. Posts : 24
    Windows 10 Home Premium
    Thread Starter
       #35

    Hey zbook. I haven't had any random bluescreens in a while, and I just got one today - from ladfgss.sys

    According to whocrashed its a logitech driver for my headphones, but I cannot find it online anywhere, can you help?
      My Computer


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

    Did verifier /bootmode resetonbootfail work?
    Please submit an updated zip file.
    That is a logitech driver.
    Start with the HP web site to see if there are HP approved drivers for your computers configuration and operating system:
    HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support

    Logitech Support + Downloads
      My Computer


  7. Posts : 24
    Windows 10 Home Premium
    Thread Starter
       #37

    Here is the new zip file
      My Computer


  8. Posts : 24
    Windows 10 Home Premium
    Thread Starter
       #38

    Just had another blue screen, KMODE EXCEPTION NOT HANDLED with the failure being USBXHCI.SYS.

    I will attach a new zip file, do you think my problem might have something to do with the USB drives on my PC? The razer mouse, logitech headset are both plugged into usb.
      My Computer


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

    Do you have an alternative mouse?
    If so please use it and uninstall all razer software/drivers using device manager and control panel
    And please uninstall all logitec software/drivers using device manager and control panel.

    If you can please do not install any replacement drivers while using windows driver verifier to see if this fixes the latest bsod.
      My Computer


  10. Posts : 41,474
    windows 10 professional version 1607 build 14393.969 64 bit
       #40

    Code:
    BugCheck C4, {2000, fffff8019a5c26e5, 0, 6e657a72}*** WARNING: Unable to verify timestamp for rzendpt.sys*** ERROR: Module load completed but symbols could not be loaded for rzendpt.sysProbably caused by : rzendpt.sys ( rzendpt+26e5 )
    Code:
    BugCheck C4, {2000, fffff800b40d26e5, 0, 6e657a72}*** WARNING: Unable to verify timestamp for rzendpt.sys*** ERROR: Module load completed but symbols could not be loaded for rzendpt.sysProbably caused by : rzendpt.sys ( rzendpt+26e5 )
    Code:
    BugCheck C4, {2004, ffffb0097787e068, fffff80ea03001f8, ffffdf80105276e8}*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption
    Code:
    BugCheck 50, {ffff8901088455f8, 0, fffff801389e5413, 2}*** WARNING: Unable to verify timestamp for ladfGSS.sys*** ERROR: Module load completed but symbols could not be loaded for ladfGSS.sysCould not read faulting driver nameProbably caused by : ladfGSS.sys ( ladfGSS+5413 )
      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 19:31.
Find Us




Windows 10 Forums