Reoccuring BSOD over the past few weeks

spiceking_99 · Apr 3, 2015

I have gotten BSODs related to memory management and I have run both chkdsk and the memory diagnostic tool on windows and have come up with no errors. Here is the information from the latest BSOD.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041790
BCP2: FFFFFA8006D8B0D0
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\040315-34897-01.dmp
C:\Users\Username\AppData\Local\Temp\WER-106236-0.sysdata.xm

WyomingKnott · Apr 3, 2015

Can you provide information such as what operating system you are using and your hardware specs?

Can you see if this tells you anything useful: https://msdn.microsoft.com/en-us/library/ff560129

johnbl · Apr 3, 2015

os version was 7601 which is windows 7 service pack 1
the bugcheck was in memory management (bugcheck code 0x1a)
the suberror code was 0x41790 which is:
0x41790
A page table page has been corrupted. On a 64 bit version of Windows, parameter 2 contains the address of the PFN for the corrupted page table page. On a 32 bit version of Windows, parameter 2 contains a pointer to the number of used PTEs, and parameter 3 contains the number of used PTEs.

the page table provides mapping between virtual memory and physical memory and that mapping has been corrupted. Normally you would start by running memtest86 and confirm your system runs without errors. if you don't find the cause of the problem, you would boot into windows, update as many drivers as you can, remove any suspect drivers and see if you still get a bugcheck. If you still get a bugcheck you would run cmd.exe as an admin then run
verifier.exe /standard
this will turn on some extra driver checking and will try to catch data corruption at the time of the corruption rather than later when the corrupted data is used by a driver.

use verifier.exe /reset to turn off this checking after you get then next bugcheck.
copy the memory dump to a server with public access and post a link.

spiceking_99 · Apr 26, 2015

I ran Memtest86 for 16 hours to scan the whole memory and it only got through a pass and a half. It said it had some errors or something but nothing serious like it said "Contiguous Errors: 1" for hours and hours. I could not get a log because it did not officially finish.

spiceking_99 · Apr 27, 2015

"bugcheck you would run cmd.exe as an admin then run
verifier.exe /standard
this will turn on some extra driver checking and will try to catch data corruption at the time of the corruption rather than later when the corrupted data is used by a driver."

I tried this and got a blue screen and had to use system restore with the windows startup repair tool.

johnbl · Apr 27, 2015

yes, if verifier detect driver corruption it will bugcheck the system and save a memory dump,
you would then reboot in safe mode and run cmd.exe as an admin and run
verifier.exe /reset
to turn off the checking, reboot normally and then copy the memory dump to a server and post a link.

spiceking_99 :

spiceking_99 · May 17, 2015

I updated my Radeon HD 7800 card and I have not had a BSOD in weeks so I believe I got my answer now. Thank you for your help johnbl and wyomingknott.

Search

Reoccuring BSOD over the past few weeks

spiceking_99

Reputable

johnbl

WyomingKnott

Legenda in Aeternum

johnbl

Polypheme

spiceking_99

Reputable

spiceking_99

Reputable

johnbl

Polypheme

spiceking_99

Reputable

TRENDING THREADS

Latest posts

Moderators online

Share this page