0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

Question

0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

Vikenty Sokolov 45

Hello, sorry for my bad english, in past year i have bsod in games constantly and some times in chrome or another programs. I can't see BSOD but my screen turn black with some color pixels. Here is my minidump files and memtest86: https://drive.google.com/drive/folders/12XTr18rLta0cazbr3axtxREMt38gQWhk?usp=share_link

I'm reinstall windows like 20 times, trying different XMP profile and without it and it doesnt matter, it happens like ones a day or more often, and i have programs crashes too, but today and tommorow dump file didnt save, on windows log it says that the problem is in the system hidden partition, but i have new ssd and previous problems are the same. If anyone can help me im vary glad, because this problem like headache. Thanks

P.S. yes im tryed sfc /scannow and Dism /Online /Cleanup-Image /RestoreHealth

Accepted answer

5 additional answers

Your answer

Answer 1

Limitless Technology 44,766

Hi. Thank you for your question and reaching out. I’d be more than happy to help you with your query

When a 0x1a61941PAGETABLERESERVEDBITSSETIMAGEhardware_ram error occurs, it means that the system has detected an invalid page table entry in the RAM. This can be caused by a hardware issue or a driver issue. To resolve this, you should first check if the hardware is functioning correctly, then check the driver for the RAM for any conflicts or issues. You may also need to reset the system BIOS settings and/or update the BIOS to the latest version.

If the reply was helpful, please don’t forget to upvote or accept as answer, thank you.

Vikenty Sokolov 45 Reputation points

2023-02-20T01:23:46.56+00:00

thanks, after reinstall and update all drivers it little bit better i think, but i have new problem, and minidump file: https://mega.nz/file/V1YFSSBL#K61TUNvNrSrmRv7Qv1IQBIssDw2iUkxpc2hn4-Hs7AM

Answer 2

Vikenty Sokolov 45

thanks, after reinstall and update all drivers it little bit better i think, but i have new problem, and minidump file: https://mega.nz/file/V1YFSSBL#K61TUNvNrSrmRv7Qv1IQBIssDw2iUkxpc2hn4-Hs7AM

Péter Király 0 Reputation points

2023-09-29T15:29:58.5066667+00:00
Hi there, I am not sure if you have your problem resolved by now or still persisting. I was checking the forums to help my friend with similar issue so I have checked your minidump you provided.

First I drop the analysis and then in the code bracket the source.
Bugcheck Code:

The error that occurred is MEMORY_MANAGEMENT with a stop code of 1a. This typically indicates severe memory management issues which could be related to bad RAM, incorrect hardware timings, driver conflicts, or rarely, software bugs.

Subtype of the BugCheck:

The subtype (Arg1) is 0000000000061941, which provides more specific information about the nature of the MEMORY_MANAGEMENT error. In this case, the subtype refers to PAGE_TABLE_RESERVED_BITS_SET, which indicates an inconsistency detected in the memory page table.

Other Arguments:

Arg2, Arg3, and Arg4 are memory addresses and specific values that can be used in a deep dive analysis, typically requiring symbol files and the exact state of the system at the time of the crash.

Key Information:

The Failure.Bucket is particularly informative: 0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram. This reinforces the idea that this crash is tied to a hardware issue with the RAM.

Crashing Process:

The crash was triggered while msedge.exe (Microsoft Edge browser) was running. However, given the nature of the crash, it's unlikely that Edge itself is the primary culprit. It may have merely been the application that was executing when the underlying issue became evident.

Stack Text:

This section provides a call stack snapshot at the time of the crash. From the provided information, it shows functions related to memory management, kernel operations, and some GUI operations (win32kbase, win32kfull). The crash seems to have been precipitated during some system-level memory operations.

Module and Image Name:

The crash points towards hardware_ram, which again stresses a probable RAM/hardware issue.

Answer 3

Docs 15,846

If the computer is having BSOD please open a new thread posting results of the V2 log collector for troubleshooting.

https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

https://www.elevenforum.com/t/bsod-posting-instructions.103/

Vikenty Sokolov 45 Reputation points

2023-02-25T12:44:01.5366667+00:00

thanks for answering: https://drive.google.com/file/d/1sy4-6bwB1azAeFu_YjoVGs4-aPAaEPGH/view?usp=share_link

Answer 4

Docs 15,846

Please open a new thread.

Vikenty Sokolov 45 Reputation points

2023-03-01T14:28:54.55+00:00

i open it here, thanks: https://www.tenforums.com/bsod-crashes-debugging/202977-bsod-hardware_ram.html

Answer 5

Docs 15,846

This thread was already marked as answered.

If possible, open a new thread in MicrosoftQ&A / learn.microsoft.com with the V2 share link.

Vikenty Sokolov 45 Reputation points

2023-03-04T23:02:38.04+00:00

Thanks for answer, new thread link: https://learn.microsoft.com/en-us/answers/questions/1186530/bsod-problem-every-day

Share via

0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

5 additional answers

Your answer