Predator Sense causing BSOD

The1Reek
The1Reek Member Posts: 3 New User
edited November 2023 in 2018 Archives
Every time I try to open up predator sense it crashes giving me the blue screen of death. Showing KMODE_EXCEPTION_NOT_HANDLED. Says iocbios2.sys failed. Could find much info on this except it is an Intel file related to predator sense or intel extreme tuning utility. I have basic understanding of computers but I have done several troubleshooting options just from what I've read online. Uninstalled and reinstalled predator sense app, the last 3 windows updates and updated drivers. Any help would be greatly appreciated. Thank you

Best Answer

  • Red-Sand
    Red-Sand ACE Posts: 1,892 Pathfinder
    edited September 2018 Answer ✓
    iocbios2 actually comes with XTU SERVICE built into Predator Sense.

    You can click start and type "regedit" and hit enter then navigate to:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
    Then find iocbios2 registry in the left panel and right click > export and save to My Documents or somewhere safe.
    Then right click and delete iocbios2.

    On the Helios 300 you dont have use of the built in XTU profiles so there's no harm.

    Only issue you will have is when trying to uninstall Predator Sense you will have to install XTU (unless your already using it) in order to remove it. Not sure why you would remove it though.

    P.S. The person before me sounds like a bot 😂😂
    - Hotel Hero

Answers

  • Kamalika
    Kamalika Member Posts: 423 Specialist WiFi Icon
    Hi The1Reek,

    How to fix kmode_exception_not_handled BSOD error on Windows 10

    Trick 1 – Remove your antivirus software

    Sometimes kmode_exception_not_handled error can be caused by recently installed antivirus software. According to a report McAfee antivirus software is responsible for this error, so if your system has McAfee antivirus software then uninstall it immediately.

    Trick 2 – Try to boot your system after renaming the problematic file

    Users reported that simply modifying the name of problematic file. But keep in mind that altering the name of problematic system files isn’t always the best fix. You can also use a professional system repair tool in order to fix system files.

    Trick 3 – Uninstall ON/OFF Gigabyte

    ON/OFF Gigabyte is a program specially designed to work with USB power stations, according to users the driver for this software is out of date and incompatible with Windows 10. If you are using ON/OFF Gigabyte software on your Windows 10 system then make sure to uninstall it in order to fix kmode_exception_not_handled error.

    Trick 4– Update your BIOS

    Outdated BIOS can also generate kmode_exception_not_handled error; try to update your system BIOS by visiting your motherboard manufacturer’s website and download the latest version of BIOS for your motherboard.

    After downloading the latest BIOS, see motherboard instruction manual to see how to properly update BIOS.

    Note: updating Windows system BIOS is very advance procedure, if not executed correctly then it may harm your PC permanently.

    Trick 5 – Make sure that RAM is Ok

    Damaged or faulty RAM can generate kmode_exception_not_handled error. In order to make sure that the problem is caused by your RAM, you need to apply the below given steps:

    Step 1: Open the run dialogue box by pressing Windows Key + R and enter mdsched.exe. Hit Enter or click OK.Untitled-5 copy

    Step 2: You will see Windows Memory Diagnostic window. Select one of the two options and follow the instructions.

    Untitled-6 copy


    If I answered your question, please mark my post "accept" to make it easier for others to find the answer!
  • Red-Sand
    Red-Sand ACE Posts: 1,892 Pathfinder
    edited September 2018 Answer ✓
    iocbios2 actually comes with XTU SERVICE built into Predator Sense.

    You can click start and type "regedit" and hit enter then navigate to:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
    Then find iocbios2 registry in the left panel and right click > export and save to My Documents or somewhere safe.
    Then right click and delete iocbios2.

    On the Helios 300 you dont have use of the built in XTU profiles so there's no harm.

    Only issue you will have is when trying to uninstall Predator Sense you will have to install XTU (unless your already using it) in order to remove it. Not sure why you would remove it though.

    P.S. The person before me sounds like a bot 😂😂
    - Hotel Hero
  • sri369
    sri369 ACE Posts: 2,855 Pathfinder
    edited September 2018
    No offense, but removing antivirus... I'd rather prefer not have Predator Sense to leave the system without protection!
    -----
    Karma...
    LIKE - if helpful
    ACCEPT - if helped resolve
  • The1Reek
    The1Reek Member Posts: 3 New User
    Thank you Red-Sand. This stopped it from crashing. What action that I took caused this to happen? I have been using predator sense for months now. 
  • Red-Sand
    Red-Sand ACE Posts: 1,892 Pathfinder
    edited September 2018
    The1Reek said:
    Thank you Red-Sand. This stopped it from crashing. What action that I took caused this to happen? I have been using predator sense for months now. 

    Glad it worked.

    It may not have been anything you did exactly..
    XTU has always been finicky.

    Do you use XTU or Throttlestop maybe?
    - Hotel Hero
  • The1Reek
    The1Reek Member Posts: 3 New User
    I
    Red-Sand said:
    The1Reek said:
    Thank you Red-Sand. This stopped it from crashing. What action that I took caused this to happen? I have been using predator sense for months now. 

    Glad it worked.

    It may not have been anything you did exactly..
    XTU has always been finicky.

    Do you use XTU or Throttlestop maybe?
    I don't use either of those
  • I'm not sure then brother
    - Hotel Hero