Windows 10: BSOD problem FAULTY HARDWARE CORRUPTED PAGE

I am having bsod problems and the problem of the bsod is FAULTY HARDWARE CORRUPTED PAGE. I did a restore factory settings from the windows 10 options like 1 month ago. After I got the bsod , I ran a malwarebytes full scan and no threats detected. So far I gotten 4 bsods.
Ram 6GB Graphics Card Nvidia GTX 960 Processor AMD FX 6100 SIX CORE 1TB HDD and 500GB HDD Windows 10 Pro 64 BIT


:)

 

BSOD Faulty Hardware Corrupted Page

You're welcome & thanks for your feedback. I'll lurk in the background for the time being to see if my colleague Sumit's suggestions bear any fruit. That being said...

(1) If you're still running OS Build 15063.632 (vs. OS Build 15063.674) and/or KB4041676 still isn't offered when running a manual check for updates, there's a distinct possibility that Microsoft either pulled the update (at least temporarily) or has "gated"
the update (i.e., only being offered to certain computers to determine if the Known Issues have been resolved). As usual, Microsoft isn't providing any transparency here.

(2) Windows Update is notorious for offering & installing driver updates which are either incompatible or not needed. One or more of these driver updates may be playing a role here, especially if you didn't install/update drivers via ASUS after doing the clean
install of Win10 Pro.

If & when an unneeded/unnecessary driver update is installed, you can rollback the driver then hide the update before Windows Update can get around to installing it again. [Resetting Windows Update after hiding an update is a wise move, too.]

It is possible to configure the system such that NO driver updates are ever offered or installed via Windows Update - again, resetting Windows Update prior to making the change is recommended (by me, at least).

(3) I won't argue with you over the efficacy, if any, of using registry cleaners - but I will encourage you to save backups of any/all changes you make using such a utility in the future and don't delete them until 6 months or more have passed. Better to have
backups & not need them than the other way around.

Enjoy your weekend.

 

BSOD Faulty Hardware Corrupted Page

I think I've answered all the questions that have been asked so far, the notification lag did throw me off, so if there's any info you still need please let me know.

 

There is only one dump in the zip file you uploaded. Are you using a program that cleans your hard drive, like CCLeaner? If so, please stop until this is resolved as it's deleting .dmp files.

Similar problem here, turned out to be memory. Windows 10 BSOD | Windows Forum

RAM:

Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums



Information




MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.



Warning
MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.



Note
MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

 

Also noticed there is a 2.8 BIOS update available on the MSI web site: Support For 970A-G45 | MSI USA | Motherboard - The world leader in motherboard design

Your memory is not installed correctly to support Dual Channel mode. According to the manual:

Attachment 91742

Remove one of the 2GB modules for now until you can populate all 4 slots with identical 2GB modules.

 

So one of my memory is not installed correctly?

 

It's not installed according to specs for Dual Channel to work properly. In single channel mode it may be okay.

Run Memtest86+ overnight tonight and see if it finds any problems.

 

Ok I ran memtest and it found 4 errors

 

You say its not installed according to specs does that mean my ram isnt faulty or is it faulty? I had 4 errors for the ram

 

Any error means defective RAM. Now you need to narrow it down to the one that is bad and remove it. Leave two installed in SLOT2 and 4. If you want to add more memory then get two more 2GB of same manufacture if possible,

 

Good luck, let me know how you make out please.

 

I ran into this issue in the last week. I ran MDSCHED, said nothing was wrong with Ram.

But this little thing was in my System Event Log:

Code: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Machine Check Exception Error Type: Unknown Error Processor APIC ID: 1 The details view of this entry contains further information.[/quote] And the Detail View shows this:

Code: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2/5/2018 8:15:37 AM Event ID: 19 Task Category: None Level: Warning Keywords: User: LOCAL SERVICE Computer: ASUS10-PC Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Machine Check Exception Error Type: Unknown Error Processor APIC ID: 1 The details view of this entry contains further information. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{C26C4F3C-3F66-4E99-8F8A-39405CFED220}" /> <EventID>19</EventID> <Version>0</Version> <Level>3</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2018-02-05T16:15:37.716091300Z" /> <EventRecordID>43859</EventRecordID> <Correlation ActivityID="{C8249BC8-1265-4246-97C8-144AD0D638DC}" /> <Execution ProcessID="1824" ThreadID="440" /> <Channel>System</Channel> <Computer>ASUS10-PC</Computer> <Security UserID="S-1-5-19" /> </System> <EventData> <Data Name="ErrorSource">3</Data> <Data Name="ApicId">1</Data> <Data Name="MCABank">0</Data> <Data Name="MciStat">0xdc3fe1000001fbfc</Data> <Data Name="MciAddr">0xfbe99cbffbfd</Data> <Data Name="MciMisc">0x0</Data> <Data Name="ErrorType">256</Data> <Data Name="TransactionType">256</Data> <Data Name="Participation">256</Data> <Data Name="RequestType">256</Data> <Data Name="MemorIO">256</Data> <Data Name="MemHierarchyLvl">256</Data> <Data Name="Timeout">256</Data> <Data Name="OperationType">256</Data> <Data Name="Channel">256</Data> <Data Name="Length">864</Data> <Data Name="RawData">435045521002FFFFFFFF03000200000002000000600300000F0F1000050212140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BB83B88A7B9C9ED30102000000000000000000000000000000000000000000000058010000C00000000102000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000400000000102000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000058020000080100000102000000000000011D1E8AF94257459C33565E5CC3F7E80000000000000000000000000000000002000000000000000000000000000000000000000000000057010000000000000000000000000000B20F06000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000100000000000000B20F06000008020101200000FFFB8B17000000000000000000000000000000000000000000000000000000000000000001000000020000002ABFA6819C9ED301010000000000000000000000000000000000000000000000FCFB010000E13FDCFDFBBF9CE9FB000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data> </EventData> </Event>[/quote] I forget how to dump my logs, I used to have a script on my Desktop that did it.

Whatever this is, it may be an OS Corruption issue. My system was running perfectly for the last 3 years since I replaced my Processor, but I had been running a Windows 7 partition that will no longer boot. In searching for "HARDWARE ERROR PAGE FAULT" it dumped me into this thread, but one other result already suggested running MDSCHED and SFC /SCANNOW. Doing Scannow right now.

I'm in the middle of transferring everything to a new Intel 15 system, but I need this heap to continue working for a while.

There were 3 Bugcheck Exceptions, but there were two of these in my Applications Events, suggesting a driver issue, and my drivers had been updated by a forced Windows 10 update:

Code: The description for Event ID 0 from source ForceWare Intelligent Application Manager (IAM) cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: Ray! StartServiceCtrlDispatcher[/quote] But I'm not sure what driver that is. The Chipset is Forceware, so I'll have to find the Forceware Driver for this board for Windows 10.

 

You had memory errors running memtest86+. That is what you need to run while removing ram until you identify the defective DIMM then replace it.
Let's get that fixed before working on any other problems at that can be the cause of all the problems.

 

No, the search I ran that pointed me here also pointed me to a result that said to run Windows Memory Check, and then run SFC after that. I did both, there were no memory errors detected. Then SFC did not find anything. Finally, I ran a DISM restorehealth. I didnt see any reason to run Memtest, seeing as it passed the MS test. If the Ram is Bad, it will error out within the first few tests.

It's been about 36 hours since I had the last BlueScreen, and I have not had any of those Event Log Entries, not for the page fault, or the Forceware Intelligent Application Manager.

I'm hoping it was just a software issue that was the result of a forced update to the latest version of windows 10. It really screwed me up, after the update, all of my desktop icons were bad, and Office and NOD32 all failed to start or were missing pieces of their programs. So I rolled windows back to 10240 and it fixed everything. My system has been in a semi hosed state ever since.

This system has one AMD 4400+ CPU OC'd by 7% (for the last 12 years), and I put in two identical 2GB DDR2/800 sticks. Under Windows 10 it's been running better than it did under 7, but the forced update mangled me seriously.

But every winter, as a ritual I have to remove my RAM from all of my PCs and reseat them. Because the nighttime temp drops to about 38 degrees F. Usually under 40 and I have to reseat the ram due to expanding or contracting. But I did not have to do that this year because it has not gone below 40 degrees.

If the ram starts to have issues, I know what to do, but my only worry is that I replaced my CPU about 3 years ago, one of the cores fried. Got a new chip for 20 bucks, and the Ram, I bought that about 2 years ago to replace two 1GB sticks. I'm running 32 bit Windows 10 so I cant have more than 4gb, and my Asus M2N Motherboard will not accept any more than 4gb either. But I've had this board since 2005, and I know exactly how to seat the RAM. I'm just not sure about the Ram BIOS settings, I have it set up for regular dual channel operation.

I'm not going to be running this PC much longer anyway, it's just acting as a 2nd PLEX server until I can transfer all my apps and HDDs to my new i5 Optiplex tower. That one is set up as 64bit so I can use the full 8gb of Ram.

The next time I reboot, I'll post my RAM settings, I think that might have been part of the issue. I set it for what I understood to be Dual Channel Op, but it has a lot of strange settings in there, I've never seen on any other board.