• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
Join the HP Community Solve‑a‑thon | Help Others & Share Your Solutions | Live on Zoom | 2:30 PM to 2:30 AM IST | Every Wednesday Click here to know more
Check out our WINDOWS 11 Support Center info about: OPTIMIZATION, KNOWN ISSUES, FAQs, VIDEOS AND MORE.
HP Recommended

Anyone else recently start getting blue screen of deaths on Intel HPs? I keep getting:

 

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff803752d6697, Address of the instruction which caused the BugCheck
Arg3: ffffa585a505e8f0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

SYMBOL_NAME:  nt!CcCopyReadEx+1f7

IMAGE_VERSION:  10.0.26100.6899

STACK_COMMAND: .cxr 0xffffa585a505e8f0 ; kb

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

FAILURE_BUCKET_ID:  IP_MISALIGNED_GenuineIntel.sys

 This has now happened on two different units of the same HP OmniDesk running Intel Core Ultra 7-265. I thought the first one was faulty hardware so I exchanged it, but since it is happening on the second one as well, it must be a software problem. A post on reddit suggests its a bug in Intel that HP needs to fix with an updated BIOS: https://www.reddit.com/r/techsupport/comments/1oekxew

 

I tried reinstalling Windows but that does not solve the problem. Yes, Windows Update is up-to-date with the latest drivers.

 

Anyone else having this problem? Know of any solution besides wait for HP?

3 REPLIES 3
HP Recommended

Hi @random_cust_756 

 

Welcome to the HP Support Community! We're here to help you get back up and running.

 

The SYSTEM_SERVICE_EXCEPTION (3b) error you’re seeing is linked to the Intel driver GenuineIntel.sys, and it can be stabilized by updating BIOS, chipset, and Intel drivers. Reinstalling Windows alone won’t resolve it.

 

Why this happens

The crash report points to GenuineIntel.sys with a misalignment error. This is tied to Intel’s low‑level driver interaction with Windows kernel routines. 

 

Since you’ve already reinstalled Windows and kept updates current, the next step is to ensure the firmware and Intel drivers are refreshed directly from HP and Intel.

 

Step‑by‑step actions

 

1. Update BIOS and chipset drivers from HP

  • Go to the official HP support page for your OmniDesk model:
    HP OmniDesk – Software and Drivers
  • Enter your product details and download the latest BIOS and chipset drivers.
  • Install them carefully and restart the system.

 

2. Refresh Intel drivers

  • Visit Intel’s driver center:
    Intel Drivers and Software
  • Use the Intel Driver & Support Assistant tool to scan your system.
  • Update graphics, wireless, and storage drivers to the latest versions.

 

3. Run Windows System File Checker

  • Open Command Prompt as administrator.
  • Type sfc /scannow and press Enter.
  • This repairs any corrupted system files that may interact poorly with drivers.

 

4. Check Event Viewer logs

  • Press Windows + X > Event Viewer.
  • Under Windows Logs > System, look for critical errors around the time of the crash.
  • This helps confirm whether the issue is tied to Intel drivers or another subsystem.

 

5. Test hardware stability

  • Restart and press F2 repeatedly to enter HP PC Hardware Diagnostics.
  • Run the extensive test for memory and storage.
  • This ensures the crashes aren’t being triggered by failing hardware.

 

You’re not facing a hardware defect—the repeated BSODs are caused by driver misalignment. By updating BIOS and chipset from HP, refreshing Intel drivers, and checking system integrity, you can stabilize the system. 

 

If the issue persists, monitoring Event Viewer and diagnostics will confirm whether it’s purely driver‑related.

 

 

If my response helped, please mark it as an Accepted Solution It helps others and spreads support. 💙 Also, tapping "Yes" on "Was this reply helpful?" makes a big difference! Thanks! 😊

 

Take care, and have an amazing day!

 

Regards, 

Hawks_Eye

I'm an HP Employee.


If this reply helped resolve your issue, please select the Accept as Solution as it helps others in the community quickly find the answer they’re looking for.


And if you found this reply helpful, clicking Yes below is a great way to let us know we’re providing the support you need, as it encourages us to keep improving and sharing helpful guidance.

HP Recommended

Thanks, @Hawks_Eye

 

I have already done (1), (2), (3), (4), and (5). All drivers are up-to-date (I double checked with Windows Update and HP Support Assistant). BIOS and chipset is up-to-date (I double checked with HP Support Assistant and Intel Driver & Support Assistant). 'sfc /scannow' finds no corruption. EventViewer does not provide any other insights aside from what I have shared here. I have run hardware diagnostics both at boot and from within Windows, and no errors have been found. Plus, as I said in the OP, I actually returned my first unit of this desktop because I was concerned these BSODs may be caused by a hardware problem, so the fact that they are still happening on a second unit means it is unlikely to be a hardware problem.

 

Reddit posts think the issue is being caused by a bug in Intel microcode (https://www.reddit.com/r/techsupport/comments/1oekxew/comment/nozxnk9/). Intel has released a patch but now HP needs to issue an updated BIOS. Any idea when that will happen?

HP Recommended

You are very welcome @random_cust_756 

 

I appreciate the thorough checks you’ve already carried out—it’s clear you’ve been very methodical in ruling out software corruption and hardware faults. Given that everything is up to date and diagnostics are clean, your conclusion that this is tied to Intel microcode and requires a BIOS update is well‑reasoned.

 

Here’s what you can do to stay ahead of the fix:

 

1. Monitor HP’s driver and BIOS release page for your model

  • Visit the HP Software and Drivers page and enter your OmniDesk product number.
  • Check under BIOS and Firmware categories regularly. Updates are posted there once validated for your hardware.

 

2. Use HP Support Assistant / HP App

  • Keep the HP App installed and run Diagnose & Fix periodically.
  • The app will notify you automatically when a new BIOS or firmware package is released for your system.

 

3. Intel Driver & Support Assistant

  • Continue running Intel’s tool as you’ve done. While BIOS updates come from HP, Intel may release interim driver updates that reduce instability until firmware is refreshed.

 

4. Stability workarounds until BIOS update arrives

  • Ensure Windows is fully patched, including optional updates.
  • If BSODs are frequent, you can reduce load by disabling fast startup or adjusting power plans to “Balanced,” which sometimes lessens kernel‑level driver stress.

 

At this stage, the most practical path is to keep watch for the BIOS release from HP that incorporates Intel’s microcode patch. Once available, installing it should resolve the SYSTEM_SERVICE_EXCEPTION crashes you’re seeing.

 

 

Regards,

Hawks_Eye

I'm an HP Employee.


If this reply helped resolve your issue, please select the Accept as Solution as it helps others in the community quickly find the answer they’re looking for.


And if you found this reply helpful, clicking Yes below is a great way to let us know we’re providing the support you need, as it encourages us to keep improving and sharing helpful guidance.

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.