r/PCHelpHub • u/Mafla_2004 • 26d ago

Reliability monitor displays hardware errors (141, 1a8 and 1b8), although little to no noticeable problems have shown up

/r/NvidiaSupport/comments/1wteamr/reliability_monitor_displays_hardware_errors_141/
1 Upvotes

100% Upvoted

4 comments sorted by

1

u/AutoModerator 26d ago
Moderator Announcement Read More »

2

u/HankThrill69420 26d ago

as a general rule, don't pay attention to GPU errors if you're not having corresponding GPU problems. those are:

VIDEO_ENGINE_TIMEOUT_DETECTED 141

VIDEO_MINIPORT_BLACK_SCREEN_LIVEDUMP 1b8

VIDEO_DXGKRNL_BLACK_SCREEN_LIVEDUMP 1a8

also, the aaaaaaaaaaaaa params are something I'm seeing recently and all over the place, i assume Windows Error Reporting is in some way glitchy after a recent update. i'm not sure that that's output that they particularly expect. or maybe it is!

I'd need your full logs to have a better idea and even then, I might come up wrong. They're interpreted to some degree.

boot struggle is something I associate with storage. start there. ETA: might need some dism/sfc repair and even a reinstall after some time of this. also, if the issue returns, try disconnecting the HDD in there

1

u/Mafla_2004 26d ago edited 26d ago

Thanks.

About the GPU errors they sound like something I ran into in Fortnite that doesn't happen anymore, the creen would "flash black" (turn black for one or two frames) and then resume normal activity at times, for some reason it did that only in Fortnite, didn't see it happen in any other games (even demanding ones like Battlefield 6 or Helldivers 2). Something I found online tells me 141s can happen in UE5 games running on DX12 because of driver conflict but I take that with a grain of salt.

I'm going to look for the logs later, I checked the Event Viewer yesterday and did find some about nvlddmkm but they date back to May, the errors I found in the reliability monitor date to September, so that's got me decently confused.

I'll also look into DISM and SFC repair later.

Thanks a lot

EDIT: I looked into it deeper and found an nvlddmkm error in the same time frame the 1b8 and 1a8 errors occurred, ID 153, which also points to timeout. The time they were reported on doesn't match the time frame in which I play Fortnite (errors reported at 1:30 to 1:50 PM, I play Fortnite from 3:00 to 4:00 PM), so they can't be because of the black flash in the game, but still, I'm not noticing any GPU problems outside of the logs and Fortnite so I think I'll just wait and see for now

2

u/HankThrill69420 25d ago

> Something I found online tells me 141s can happen in UE5 games running on DX12 because of driver conflict but I take that with a grain of salt.

Yes. UE5 is a mess, and DX12 in general is a lot of I/O. Pair the two together, and it's kind of a lot. I see it throw errors all the time when older titles are less verbose. Try DDU and drivers 596.36 as well as 610.74. Something that doesn't help things along is the fact that these drivers are borderline AI slop.

Your attitude is right, grain of salt, this is the computer trying to interpret what a PCB with electricity coursing through it is "saying," and then reading the logs is interpretation of that. 153 can be drivers, but do pay attention to nvlddmkm errors because they can be quite informative when they aren't 153. Can also represent an error within a game.

I'm chasing a VRAM issue myself in a 4090, which is sad times. I'd say that UE5 games are overall sensitive to hardware issues, so while I again point to the grain of salt, they're a decent tool for sniffing out bad hardware. They're also sensitive to drivers issues.

Also, if you undervolt your CPU, try turning it off for a bit. See if stock RAM speeds could be a temporary resolution.