Question Lian li Galahad 2 AIO fail - windows non paged error

[simjosh1]

I've been on here a ton to find help but never posted before...

I have a PC that I built after a 10+ year hiatus and now I'm stumped.
pC put together 6+ months ago and ran fine until this past Wednesday.

Get home after work and I've got a blue, unknown error sorry...

Restart, crash, I look at bios and notice CPU temps at 95c... Oh no !

I get a new AIO and sure enough the pump failed and after looking up Lian li Galahad 2 performance issues, I do remember a noise I amateurishly ignored a couple weeks back!

So, now I got the new AIO, PC starts and loads Windows but it'll crash after 10-30 seconds once logged in stating, nonpagging file error.

I've tried, restart windows, restore, bootable USB drive repair... Basically every suggestion I could find so far.... Nothing works so far..

I guess at this point I'm concerned I could have a hardware issue but I don't want to randomly buy or swap parts.... I'm wondering if anyone's got a more scientific approach.

Thanks a ton!!

Intel i7-13700k
ASUS 3060TI
990 1T SAMSUNG M.2 HDD
64GB RAM (2x 32gb Corsair vengence)
Asus z790-f rog strix motherboard


I had xmp enabled on ram, removed that too btw....

 

[Ralston18]

PSU: make, model, wattage, age, condition (original to build, new, used, refurbished, used)?

Look in Reliability History/Monitor: any error codes, warnings, or informational events being captured just before or at the time of the crashes?

You can also look in Event Viewer. Not as user friendly as Reliabillty History/Monitor but may help discover a potential culprit.

To help with Event Viewer:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

Increasing numbers of errors and varying errors etc, are a sign of a faltering/failing PSU.

 

[simjosh1]

PSU: make, model, wattage, age, condition (original to build, new, used, refurbished, used)?

Look in Reliability History/Monitor: any error codes, warnings, or informational events being captured just before or at the time of the crashes?

You can also look in Event Viewer. Not as user friendly as Reliabillty History/Monitor but may help discover a potential culprit.

To help with Event Viewer:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

Increasing numbers of errors and varying errors etc, are a sign of a faltering/failing PSU.

Thermaltake Toughpower GF A3 750w, new to build. "Gold atx 3.0".

The only error I've gotten since replacing the AIO has been the nonpagging file error alone.

I did get a bios (maybe) warning that CPU was new when I replaced the AIO and it prompted me to check the bios settings to ensure it was compatible... Nothing was changed or removed CPU wise so I kept stock settings .

I'm not sure if I can get into history monitor as Windows loads but I got just enough time to restart or shut down before nonpagging file blue screen.

I'll do research on history monitor and events and try and look at it when I get off at lunch or for the day.

Thanks for the reply!

 

[simjosh1]

Thermaltake Toughpower GF A3 750w, new to build. "Gold atx 3.0".

The only error I've gotten since replacing the AIO has been the nonpagging file error alone.

I did get a bios (maybe) warning that CPU was new when I replaced the AIO and it prompted me to check the bios settings to ensure it was compatible... Nothing was changed or removed CPU wise so I kept stock settings .

I'm not sure if I can get into history monitor as Windows loads but I got just enough time to restart or shut down before nonpagging file blue screen.

I'll do research on history monitor and events and try and look at it when I get off at lunch or for the day.

Thanks for the reply!

I've reviewed both applications and I won't have enough time to buy either the reliability or event viewers. After complete long in I will get the nonpagging blue screen before accessing .. or best case I would have time to route the paths to said locations but not enough time before crash to view and understand data there.

Thanks,
Josh

 

[Ralston18]

Power down, unplug, open the case.

Clean out dust and debris.

Verify by sight and feel that all connectors, cards, RAM, jumpers, and case connections are fully and firmly in place.

Unplug and replug or unseat and reseat as applicable., Especially RAM.

Note: check the motherboard's User Guide/Manual. Some motherboards require that the first physically installed RAM be placed in a specific slot. DIMMA2 most likely. Reseat RAM accordingly.

 

[Colif]

nonpagging file error.

i suspect its the C drive. checking it will be fun part if its crashing right after boot. There is one way...

Do you have your win 11 install disk?
put it in PC at startup
boot to the logon screen
click on the power button in bottom right of screen (might be left)
while holding shift, click restart now

this loads you into a blue menu
choose Use a device
pick the USB from the list and PC will boot from it.

• on screen after languages, choose repair this pc, not install.
  
• choose troubleshoot
  
• choose advanced
  
• choose command prompt
  
• type notepad and press enter
  
• in notepad, select file>open
  
• Use file explorer to navigate to C:/ and copy the memory.dmp file onto a USB
  

upload the memory.dmp file to a file sharing website (probably need to zip it) and show link here.

that might at least show us the error codes. And perhaps the cause.
You could probably do a lot of that from inside windows but if I am right and its page file, running off USB should mean it won't restart in 30 seconds...

 

[Ralston18]

Reference:

"I've reviewed both applications and I won't have enough time to buy either the reliability or event viewers."

Did you mean "to try" versus "to buy".

Reliabiltiy History/Monitor and Event Viewer are part of Windows.

 

[simjosh1]

Yes try not buy! Sorry cell phone replies!

 

[simjosh1]

i suspect its the C drive. checking it will be fun part if its crashing right after boot. There is one way...

Do you have your win 11 install disk?
put it in PC at startup
boot to the logon screen
click on the power button in bottom right of screen (might be left)
while holding shift, click restart now

this loads you into a blue menu
choose Use a device
pick the USB from the list and PC will boot from it.

• on screen after languages, choose repair this pc, not install.
• choose troubleshoot
• choose advanced
• choose command prompt
• type notepad and press enter
• in notepad, select file>open
• Use file explorer to navigate to C:/ and copy the memory.dmp file onto a USB

upload the memory.dmp file to a file sharing website (probably need to zip it) and show link here.

that might at least show us the error codes. And perhaps the cause.
You could probably do a lot of that from inside windows but if I am right and its page file, running off USB should mean it won't restart in 30 seconds...

Ok,
I had a USB with Windows and I ended up trying a "restore point" 1 more time from USB if that makes a difference...


I was able to restore!!!

When Windows loaded next I did get an execute stop page crash but the second load finished setting up Windows.

1) I went to advance settings and created a 10,000mb page file max/min, over the recommended 9450mb size. (No longer automatically managed by Windows.
2) removed auto restart from Windows ...

This has me to a point where the PC hadn't crashed as of 6am this morning.

If there's any additional information that I need to grab now since windows isn't crashing I'll do whatever.... I know Asus Armory Crate was buggy and the system wouldn't let me do a defrag of HDD as it was already "optimized".

All internals (hardware and plugs) were seated properly, no dust or debris found... pC kept in a study and I never go in there ATM and I'm just running blue iris on the PC for now.

 

[kira-faye]

Reinstall Windows, from scratch. No repairs, no restore points, just wipe it (copy anything you need first, obviously) and all of this will go away. It was just drive corruption due to multiple improper shut-downs while the system was overheating. No modern PC hardware will (should) be damaged by heat, everything has throttling built in at the hardware level now.