Recent content by saturn49

The W3670 came today and....as many of you suspected, it didn't help. So I was left with the GPU (GTX 660), something on the motherboard, or declaring the system cursed. As a last ditch effort, I went into the BIOS and disabled everything I could find: USB 3.0 ports Azalia Codec (wtf is this...

I have a 15th gen CPU+MB+RAM+M.2 spec'd out in another tab. Think of this as an academic exercise. ;-) I do think it would be really interesting if Westmere still works but Gulftown does not. There are very few differences between them...

The clean install of Windows 11 made the SSD drive GPT and it was still (sorta) able to boot. Surely that's not the reason for the IRQ_NOT_LESS_OR_EQUAL bluescreen though right? I would think it would blow up long before then. The USB install made by Rufus is also GPT and seems to work fine...

If the partition table was wrong / unsupported, theoretically I'd not be able to boot into the installer from USB at all right? Not in front of the right computer at the moment, but I tried Alt-A and it said "Use Rufus MBR disabled" and said "enabled" when I hit it agian, so presumably using...

I took Rufus' defaults, I didn't see an option to override legacy MBR vs UEFI GPT mode. The USB stick has no problem booting though, and these systems certainly don't support UEFI.

The 520M is apparently also westmere (like my W3690 that works). The i7-950 is slightly earlier Bloomfield. No overclocking here. I stopped doing that after the Celeron 300A -> 450Mhz hack.

No, they are GIGABYTE, same as yours, just slightly different model.

Since both motherboards are different revisions, they have different BIOS versions. Both are up to date with the latest available for their respective revisions though.

Yep. The installer warns me that the hardware isn't supported but I click Acknowledge or whatever and it blissfully continues. It bluescreens after the second reboot.

In theory, yes. However, I'm having trouble on with an i7-950 with a clean installation. So I'm wondering if there's some other instructions (besides SSE4.2) that are required for 24H2.

They were BS, but I think that's changing. 24H2 is starting to use some newer instructions that aren't available on older CPUs. This makes sense - they've (mostly) successfully stood their ground on supported CPUs, and now they can set their compiler up to take advantage of these newer...

Strangely, the one that works has all kinds of stuff plugged into it (including an ancient GPIB card). There was literally just a keyboard and mouse plugged into the one that didn't work. The GPUs are also different (working: GTX 2080Ti, non-working GTX 660) but since the 660 has drivers...

I tried a fresh install of Windows 11 on a blank SSD and it still didn't work. I checked the minidump with windbg and there's no driver in the crash stack, just the kernel. A bad driver could have corrupted something first, but again, this is the same motherboard with a different CPU that I...

Has anybody actually gotten 22H2 to run on an i7-950? I tried this past week and it bluescreens after the second reboot. No problems running Windows 10. I also have a very similar system (same motherboard) with a Xeon W3690 that runs 22H2 just fine. I'm wondering if I found the inflection...