Windows 10: BSOD with IRQL_GT_ZERO_AT_SYSTEM_SERVICE

After upgrading to Windows 10, have gotten at least 6 BSOD crashes in 48 hrs with: IRQL_GT_ZERO_AT_SYSTEM_SERVICE

Is there an explanation and easy solution?  I don't have the time or inclination for anything more than a simple fix, shouldn't have to be doing this in the first place.

Hi,

Thank you for posting your query on Microsoft Community.

I understand that you receive blue screen error after installing Windows10. We will assist you to resolve this issue.

This issue may arise when some of the Windows components or applications gets corrupted.

I suggest you to remove all the external devices connected to the computer and check if it helps to resolve the issue.

If the issue persist, please follow the steps given in the link below:

Resolving Blue Screen errors in Windows.

http://windows.microsoft.com/en-us/windows-8/resolve-windows-blue-screen-errors

Note: The steps provided in the article is for Windows 8 or 8.1, which is also applicable for Windows10.

If the issue persist, let’s perform a Clean Boot.

A Clean Boot is performed to start Windows by using a minimal set of drivers and startup programs. This helps eliminate software conflicts that occur when you install a program or an update or when you run a program in Windows 8.1, Windows 8, Windows 7, or Windows Vista. You may also troubleshoot or determine what conflict is causing the problem by performing a clean boot.

Please refer the steps from the link below to perform a Clean Boot:

https://support.microsoft.com/en-us/kb/929135?ppud=4&wa=wsignin1.0

Note: Please go through the section: How to reset the computer to start as usual after troubleshooting with clean boot of the Kb article to boot the computer in normal startup after fixing the issue.

Hope the information helps. Let us know if you need further assistance. We will be happy to help.

Thank you.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Besides demonstrating how to do a clean boot, your response basically says:  go back to Windows 8.1.  All due respect but that doesn't communicate much confidence in Windows 10.   But OK...

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hello,

I solved the problem like that:

- format system drive

- re-install WINDOWS SEVEN PRO with valid activation key (at least 10 years old !!! Welcome back to the futur)

- download all updates for WIN7

- no application

- as nothing ask to upgrade to windows 10 (it would be), I made a Windows 10 install CD

- I install WIN10 from CD on WIN7

- WIN10 said me "invalid key" (****), I ignored it

- at the complete install... yes! No BSOD, and WIn10 works well (an well activated !)

- I think you have a lot of work to do before a complete and secured upgrade from old windows on all PCs...

- But when it works, it is a really good product. Microsoft, we love to hate you!!!!  ;-)

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thanks!  Impressive solution, even if draconian.  I'll wait to hear from others ...

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

It turns out the correct solution is:
  1. Run Windbg on the memory dump file
  2. Identify the process "audiodg.exe" as the exit point
  3. Google audiodg.exe and BSOD to expose the driver "stdriver.sys" as a suspect
  4. Google stdriver.sys and BSOD to expose the "SoundTap" application fron NCH Software as a suspect
  5. Remove SoundTap from the system, reboot and re-install
No BSODs in 3 days, was 1 - 5 per day.  Total Time to research and fix: 3 hrs

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

 
 

Question Info


Last updated June 23, 2020 Views 6,344 Applies to: