Search results

No, that's not what I asked for. I don't want a manually taken live system dumps (which is what you've uploaded), I want the file C:\Windows\Memory.dmp like I asked for. Sadly that's probably been overwritten now by the useless live system dump you just generated! Upload the file...

Thanks for the uploads but when uploading to Google Drive (or similar) you need to make the files public ('anyone with the link can access'). However, the 0x101 CLOCK_WATCHDOG_TIMEOUT BSOD cannot be fully debugged with the minidumps we typically ask for, we'll need the full kernel dump. It's...

To keep thing simple; open an elevated command prompt and enter the following command... powercfg -h off That will definitely turn hibernation off, and with it Fast Startup. I agree with @SpyderTracks 100% that turning off the power switch at the back is necessary - it's very hard to run a PC...

If it is, then the abominable snowman is genuine, the Earth actually is flat, and Elvis really is working in a chip shop in the High Street...

Given the problems you're having I don't think that Memtest86 is good enough. No RAM tester can ever detect all RAM issues. I suggest you remove one RAM stick (ensure its in the correct slot for one stick) and see whether you can make it fail. Then swap RAM sticks and try on just the other one...

Perhaps he's a depressive and didn't want to be saved?

Interestingly, the 2012 torch came through here too!

Try booting with each RAM stick, one at a time - and check with the manual for the right slot to use for a single RAM stick. Keep everything at stock frequencies and voltages. Please download and run HWMonitor (free), expand the CPU temps section so we can see every core. Then post a screenshot...

You might know that the Olympic Flame, which was lit in Olympia earlier this week, does a tour of Greece before it heads off to the host country. Today it came to Agios Nikolaos on Crete, where I live, on its tour of Greece before heading off to France.... That last torch bearer is my...

How can you possibly know this? I'm sure that Gigabyte didn't write that warning just for fun. It's usually a mistake to opt for more RAM than you need (it just increases the workload for the Windows memory manager), it's equally a mistake to opt for faster RAM than you actually need, or you...

Can you please post the full specs from your order page so we can see exactly what you have.

If that drive does turn out to fix your issues please report back to PCS. They need to know that the Seagate Firecuda might not be stable with that motherboard and CPU.

Yep, got that. Thanks. The most recent BSOD (16th April) is very similar to the earlier dumps in that the processor involved (processor 12) is coming out of idle. To try to explain in detail what (I think) is happening I'll go into some details. If you're not intertested then skip to the...

Can you upload the Sysnative file output again to a different cloud service? OneDrive still reports problems for me on any browser.

The RAM not being on the QVL doesn't mean it won't work it just means that it's not been tested and verified as stable with that motherboard. However, you're right that there is no 32GB RAM over 5600MHz on the QVL at all, so it may be that your new RAM is not well supported (or stable). In...

OneDrive seems to be having issues. I'll try and download the file later. Are the power setting mitigations still active (C_States disabled, processor power both at 99%)?

Earlier in this thread you installed Windows to the PCS SSD and all seemed to go well? Have you tried moving that drive to the one the Firecuda is in and then installing Windows on that PCS drive in the PCIe 4 M.2 slot? That should show us whether this is a motherboard problem or not. I also...

Is the new RAM you bought on the QVL for the motherboard?

I'd still be interested to see what happens if you try booting with each RAM stick on its own...

The thing about random read when you have only one drive is I/O queuing within Windows. With a sequential read or write it's one I/O as far as Windows is concerned so once it starts you have the drive to yourself. With random reads each read is a separate I/O operation and they each have to sit...