• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Windows 11 24H2 Green Screen of death.

ir_cow

Staff member
Joined
Sep 4, 2008
Messages
5,134 (0.84/day)
Location
USA
Looking for insight for a workaround.

24H2 installs on Z890 + 285K. The second NVIDIA drivers are installed either through Windows update or NVIDIA own file, a green screen of death comes up. Windows becomes corrupted and requires a reinstall. If I take a 23H2 or 22H2, no problems. Just 24H2 is busted. I haven't tried it on the Z790 platform yet, so that will be my next attempt.

Any idea how to make 24H2 like NVIIDA? I only tested with 30 and 40 series so far.

Update: Disabling iGPU fixed the problem. Only other solution I found is to use 23H2 or 22H2.
 
Last edited:
"Green" screen of death? Never seen one of those.. Would you happen to have screen shots of the error messages?
 
Looking for insight for a workaround.

24H2 installs on Z890 + 285K. The second NVIDIA drivers are installed either through Windows update or NVIDIA own file, a green of death comes up. Windows becomes corrupted and requires a reinstall. If I take a 23H2 or 22H2, no problems. Just 24H2 is busted. I haven't tried it on the Z790 platform yet, so that will be my next attempt.

Any idea how to make 24H2 like NVIIDA? I only tested with 30 and 40 series so far.

Haven't had any issues with a variety of 24H2 builds and Nvidia releases in that time frame. You sure it's not a Arrow Lake issue?
 
"Green" screen of death? Never seen one of those.. Would you happen to have screen shots of the error messages?
No error message. its a full green screen. Someone a few years ago had the same thing. In that case it seem people were thinking it was a bad video card. Promise you it is not a bad GPU. Could be Motherboard related though. Only have one Z890 so I can't rule that one out.

Haven't had any issues with a variety of 24H2 builds and Nvidia releases in that time frame. You sure it's not a Arrow Lake issue?
That is what I am trying to figure out. Using 22H2 on my personal computer as well with Z690 Raptor Lake and this is the first time using 24H2. I might just stick with 22H2 for testing if M$ won't behave with Arrow Lake.
 
Any idea how to make 24H2 like NVIIDA? I only tested with 30 and 40 series so far.

Try with a Radeon, to understand if the issue is really from the Nvidia driver or another part.
Then, try with another, older Nvidia driver.

If the green screen persists, then return to a previous Windows version from an earlier date.
 
Isnt this the same IGP + Nvidia problem of Arrow Lake? I believe you can solve it by disabling IGP althogeter.
 
Windows becomes corrupted and requires a reinstall.

This is the big issue here, and it suggest either just bad software (be it Windows or drivers) or something like faulty RAM, but because it only happens when you install the latest version I'm guessing some incompatibility issue that hasn't yet been resolved in software.

The workaround is do not install 24h2.
 
Low quality post by 3valatzy
In my experience, funky colored frozen screens always come from a faulty video card. I'm not saying it is, but to narrow down the problem, any chance you can test with another card?
 
This is the big issue here, and it suggest either just bad software (be it Windows or drivers) or something like faulty RAM

Sorry for derailing this topic.

I wrote in another windows 11 pro topic.

I doubt my KC3000 2TB drive is faulty. It should be less than a year old. My windows 11 Pro 24h2 wants do, and if not aborted, repairs on every bootup the C: drive. If the drive would have been faulty, I would have seen it ages with my gentoo linux partition, while compiling, while doing backups and in daily usage. My current Windows 11 pro has some sort of file corruption for the NTFS - C: partition.

Another workaround is use Ryzen 9 9800X3D and Radeon RX 7900 XTX.

No - I highly doubt it. Ryzen 7600X / Radeon 7800XT here. The windows installation is barely customised. It's for gaming only. To get experience a bit with Windows 11 - as the job world requires it.

-- Just for information - read about it - never saw it myself: duckduckgo for example knows about the green screen of death.

-- An operating system for AMD64 should work on any processor without the magic driver "bullshit" when it meets the required cpu instructions. I would not blame the cpu instructions of that particular intel processor.
 
Wasn't there a whole issue with reviewers getting their Windows installs borked by the IGP + nV drivers as @adilazimdegilx pointed out?
This was one of many unforced errors from Intel, with others including BSODs on Windows install due to a driver conflict with NVIDIA devices when the IGP is enabled. This issue did not exist on prior architectures and seems to be a combination of the new IGP claiming the PCIE resources and of NVIDIA’s driver code not having an error handler for 0 PCIE resource availability. You can bypass it by disabling the IGP, but for a lot of people, this will be frustrating.
 
"Green" screen of death? Never seen one of those..
Essentially the exact same thing as BSOD (blue screen of death) but for "Windows Insider" builds.

Since Windows Insider builds are "test" or "beta" builds, I say just "hurry up and wait". That is, "hurry up" and use the Feedback Hub to report your "findings", then "wait" for a new release.
 
Since Windows Insider builds are "test" or "beta" builds, I say just "hurry up and wait". That is, "hurry up" and use the Feedback Hub to report your "findings", then "wait" for a new release.
OP isn't using a beta build, it's just a green screen
No error message. its a full green screen.
 
"Green" screen of death? Never seen one of those.. Would you happen to have screen shots of the error messages?
Longhorn ~4051 era. Just the BSOD with a background color change, emphasis on solid middle brightness level green.
It's been an extremely long time since I've heard or thought about it but it was in there.
Can't remember what caused them outside a manual Ctrl+Scroll memory dump.
Are you sure it's just a solid color screen like a test page? There's no error message text?
 
Can be two types - without any messages (plain green colour screen), and with similar text as the blue screen:

1732465424526.png

1732465448406.png


Usually comes from some type of a hardware issue with the graphics.

 
Isnt this the same IGP + Nvidia problem of Arrow Lake? I believe you can solve it by disabling IGP althogeter.
This.

Also isntall offline, don't make a MS account (Google: bypassnro if there's no option for that), bring NVCleanstall and network drivers on USB stick, start NVCleanstall and it will block GPU driver updates, so you can connect Ethernet
 
Can be two types - without any messages (plain green colour screen), and with similar text as the blue screen:

View attachment 373117
View attachment 373118

Usually comes from some type of a hardware issue with the graphics.

GSOD is like BSOD. Now a Blank Screen, no matter what color it is with no text on it means a hard graphical lockup.
 
Never had a problem and I've been using 24H2 from build 26100.1. Looks like something related to Arrow Lake, i'd go by process of elimination, first thing I'd do is disable the Intel graphics, then the next thing would be to download last 5 driver versions or so, and go from there. Shift+F10 OOBE\BYPASSNRO on setup if you didn't prep with Rufus.

GSOD indicates it's a preview build too, try a stable release of 24H2 as well
 
Isnt this the same IGP + Nvidia problem of Arrow Lake? I believe you can solve it by disabling IGP althogeter.
I will try this. It is a fresh windows install, so only way back is a different ISO.

Never had a problem and I've been using 24H2 from build 26100.1. Looks like something related to Arrow Lake, i'd go by process of elimination, first thing I'd do is disable the Intel graphics, then the next thing would be to download last 5 driver versions or so, and go from there. Shift+F10 OOBE\BYPASSNRO on setup if you didn't prep with Rufus.

GSOD indicates it's a preview build too, try a stable release of 24H2 as well
I grabbed it from Microsoft official. Shouldn't be the preview build, but it was released on October 30th. Also because I refuse to give M$ my information it's always the offline install method.

Going to try to disable igpu since it's not used anyways.
 
Essentially the exact same thing as BSOD (blue screen of death) but for "Windows Insider" builds.
Ah, fair enough. Never seen it personally. Then again, I've only tested insiders builds during the Win11 rampup and beta phase.

I grabbed it from Microsoft official. Shouldn't be the preview build, but it was released on October 30th.
Plot thickens. Read into the green-screen problem. The generally agreed upon cause, even by some at microsoft, is video related. However, there does seem to be indications that it can also be file-system error related as well.

Have you checked the drive in question for sector errors? A "surface" scan(even for SSDs) might be in order. Not 100% on this idea, but it seems plausible and worth mentioning.
 
Last edited:
Plot thickens. Read into the green-screen problem. The generally agreed upon cause, even by some at microsoft, is video related. However, there does seem to be indications that it can also be file-system error related as well.

Have you checked the drive in question for sector error? A "surface" scan(even for SSDs) might be in order. Not 100% on this idea, but it seems plausible and worth mentioning.
I was thinking the same thing. Didn't mention it, but first attempt was a brand new SSD and I figured I just had a bad unit. Tried 2 others, SSD SATA and NVME, which gives me the same results.
 
I was thinking the same thing. Didn't mention it, but first attempt was a brand new SSD and I figured I just had a bad unit. Tried 2 others, SSD SATA and NVME, which gives me the same results.
I was thinking the same thing. Didn't mention it, but first attempt was a brand new SSD and I figured I just had a bad unit. Tried 2 others, SSD SATA and NVME, which gives me the same results.
During the P3 days I was always disabling the igp to avoid problems when a gpu was installed
 
Back
Top