Windows 7 Troubleshooting Frequent BSODs: Kernel Data Inpage Error, RAM, HDD, or PSU Issues?

TFK19

New Member
Joined
Jan 23, 2014
Messages
4
I have been getting this BSOD along with another Stop 0xF4, driver_power_state_failure (only once), kernel_data_inpage_error, and memory_management they pop up sporadically. The most common being the kernel_data BSOD. I removed one ram stick from slot 4 and the PC doesn't freeze up anymore, so that one might be bad. I did a scan with Hard Disk Sentinel and it says my drive is at 52% health and has ~392 days life left. It could be many problems please help, i'm new here and it looks like you guys know what you are doing.

MOBO: ASUS M4A785-M
RAM: Samsung 3GB DDR2 M378T2863RZS-C (removed 1 stick that i think is bad)
CPU: AMD Phenom X4 9850 Black Edition (STOCK SPEED)
OS: Win 7 x64
AV: MSE x64
GFX: ATI Radeon HD 4800 Series 1GB
PSU: PC Power and Cooling S75QB 750W

I attached all the required files in one folder, like specified.

I have also gotten some 0x000000ED UNMOUNTABLE_BOOT_VOLUME BSOD, i usually run CHKDSK /F /R and it fixes it on reboot. What worries me is that it could either be PSU, RAM, or HDD
 

Attachments

Last edited:
Solution
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004dea8f8, 0, 0}

Probably caused by : AuthenticAMD

Followup: MachineOwner

Hi,
several dmp files were like the one above which is usually a hardware error. As you've already found a bad RAM stick please test the others using the app found here...
Sort by date Sort by votes
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004dea8f8, 0, 0}

Probably caused by : AuthenticAMD

Followup: MachineOwner

Hi,
several dmp files were like the one above which is usually a hardware error. As you've already found a bad RAM stick please test the others using the app found here:
http://www.memtest.org/

Your HDD sounds in a poor way too. I'd seriously consider replacing it if possible.

Your OS could well be corrupt too. Try running a system file check. Open an admin cmd prompt (find cmd prompt in the start menu, rightclick on it and choose properties, then run as admin). Type:
sfc /scannow
Press enter and await results.

As your processor is in the dmp file as failing please test using Prime95. This is just a stability test. Watch the temperature if it looks like it's going to climb above 70c stop the test. If any worker threads fail then stop the test. Test for around an hour.
http://www.mersenne.org/freesoft/

aswRvrt.sys Fri Oct 04 08:48:58 2013 : Avast AV lease un-install and use MSE:
Link Removed

I couldn't find any system drivers. Please update the following:
AMD chipset driver.
Link Removed

AMD GPU driver:
Link Removed

Via Audio:
Link Removed

Network:
Link Removed

Your actual motherboard website is here in case you need to refer to it
http://www.asus.com/Motherboards/M4A785M/#support
 
Upvote 0 Downvote
Solution
Thanks for your reply kemical.
  • So here's what happened got another BSOD for kernel_data_inpage_error
  • Waited 15 minutes for dump, nothing did a hard reset
  • On reboot BIOS Changed Boot device to another HDD, i switched it back to the OS Drive
  • Logged In, removed all Drivers that you sent updates for, except Audio, the server has errors and stops at 3.8MB, then chrome says server error, other DLs worked perfectly fine
  • Ran CCleaner
  • Rebooted, and ran Prime95 for 45 minutes, no errors on all 4 cores, never went above 46C, passed all tests, I ran the 2nd Test Large FFTS, then merged the Worker threads to one window for screenshot
  • Reinstalled all drivers & rebooted
  • Ran SFC /SCANNOW with errors, included screenshot and CBS log, sorry for typos in cmd
After that I kept using the PC for 2 hours with no problems. I included the new .dmp file of the latest BSOD. As for the RAM, that's going to be out of the way, I bought a new ram kit, and an HDD that i will get tomorrow in the mail. I want to make sure nothing else is wrong with the PC before the install of the new hardware. If it turns out that those two weren't the problem, then I have extra hardware for future problems.

As for AVAST i uninstalled AVAST yesterday and replaced it with MSE. Ran CCleaner to make sure it erased it's reg data. It seems that many people are advised to remove AVAST? What's the problem with that Antivirus, curiosity?
 

Attachments

Upvote 0 Downvote
Code: 
2014-01-24 16:11:01, Info                  CSI    00000321 [SR] Verify complete
2014-01-24 16:11:01, Info                  CSI    00000322 [SR] Repairing 5 components
2014-01-24 16:11:01, Info                  CSI    00000323 [SR] Beginning Verify and Repair transaction
2014-01-24 16:11:02, Info                  CSI    00000324 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-s..chrecognizerenu.ale_31bf3856ad364e35_6.1.7600.16385_en-us_2a26b846c28f1791\l1033.ngr do not match actual file [l:18{9}]"l1033.ngr" :
  Found: {l:32 b:XFpqKNLaq/RdyBpTFQ033TcG750MAPb4wDzDmkcfwjs=} Expected: {l:32 b:wq7Nf8+TNyCEXeeVYi/bcRBnWJMnXxl0GdkrOvt94eI=}
2014-01-24 16:11:02, Info                  CSI    00000325 [SR] Cannot repair member file [l:18{9}]"l1033.ngr" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-01-24 16:11:03, Info                  CSI    00000326 [SR] Cannot repair member file [l:26{13}]"msdsm.sys.mui" of msdsm.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2014-01-24 16:11:03, Info                  CSI    00000327 Manifest hash for component [ml:280{140},l:200{100}]"wow64_microsoft-windows-v..e-filters-tvdigital_31bf3856ad364e35_6.1.7601.17669_none_4446dba7a233f848" does not match expected value.
Expected:{l:32 b:5e94c8779e8e9b5b0cb51f8b1cf855a30900e169f137d650c3e3a2e5f6a234b9}
Found:{l:32 b:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855}.
2014-01-24 16:11:03, Info                  CSI    00000328 Unable to load manifest for component [ml:280{140},l:200{100}]"wow64_microsoft-windows-v..e-filters-tvdigital_31bf3856ad364e35_6.1.7601.17669_none_4446dba7a233f848"
2014-01-24 16:11:03, Info                  CSI    00000329 [SR] Cannot verify component files for Microsoft-Windows-Video-Capture-Filters-TVDigital, Version = 6.1.7601.17669, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2014-01-24 16:11:03, Info                  CSI    0000032a [SR] Cannot verify component files for System.Transactions, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
2014-01-24 16:11:03, Info                  CSI    0000032b [SR] Cannot verify component files for System.tlb, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
2014-01-24 16:11:04, Info                  CSI    0000032c Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-s..chrecognizerenu.ale_31bf3856ad364e35_6.1.7600.16385_en-us_2a26b846c28f1791\l1033.ngr do not match actual file [l:18{9}]"l1033.ngr" :
  Found: {l:32 b:XFpqKNLaq/RdyBpTFQ033TcG750MAPb4wDzDmkcfwjs=} Expected: {l:32 b:wq7Nf8+TNyCEXeeVYi/bcRBnWJMnXxl0GdkrOvt94eI=}
2014-01-24 16:11:04, Info                  CSI    0000032d [SR] Cannot repair member file [l:18{9}]"l1033.ngr" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-01-24 16:11:04, Info                  CSI    0000032e [SR] This component was referenced by [l:288{144}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.Microsoft-Windows-SpeechRecognizer-Deployment-LanguagePack"
2014-01-24 16:11:05, Info                  CSI    0000032f Hashes for file member \??\C:\Windows\Speech\Engines\SR\en-US\l1033.ngr do not match actual file [l:18{9}]"l1033.ngr" :
  Found: {l:32 b:XFpqKNLaq/RdyBpTFQ033TcG750MAPb4wDzDmkcfwjs=} Expected: {l:32 b:wq7Nf8+TNyCEXeeVYi/bcRBnWJMnXxl0GdkrOvt94eI=}
2014-01-24 16:11:05, Info                  CSI    00000330 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-s..chrecognizerenu.ale_31bf3856ad364e35_6.1.7600.16385_en-us_2a26b846c28f1791\l1033.ngr do not match actual file [l:18{9}]"l1033.ngr" :
  Found: {l:32 b:XFpqKNLaq/RdyBpTFQ033TcG750MAPb4wDzDmkcfwjs=} Expected: {l:32 b:wq7Nf8+TNyCEXeeVYi/bcRBnWJMnXxl0GdkrOvt94eI=}
2014-01-24 16:11:05, Info                  CSI    00000331 [SR] Could not reproject corrupted file [ml:520{260},l:76{38}]"\??\C:\Windows\Speech\Engines\SR\en-US"\[l:18{9}]"l1033.ngr"; source file in store is also corrupted
2014-01-24 16:11:06, Info                  CSI    00000332 [SR] Cannot repair member file [l:26{13}]"msdsm.sys.mui" of msdsm.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2014-01-24 16:11:06, Info                  CSI    00000333 [SR] This component was referenced by [l:188{94}]"Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.INF_msdsm"
2014-01-24 16:11:06, Info                  CSI    00000334 [SR] Could not reproject corrupted file [ml:520{260},l:74{37}]"\??\C:\Windows\System32\drivers\en-US"\[l:26{13}]"msdsm.sys.mui"; source file in store is also corrupted

This is just a small section of the CBS log. You'll notice that drivers relating to the processor are corrupt and your probably best just re-installing. I would wait however until you get the new drive and RAM.
As for Avast. It has been known to cause issues in the past and general rule of thumb is to just take it out of the equation.
 
Upvote 0 Downvote
You my friend are a genius! But how in the world can processor drivers get corrupt never had that happen before?
 
Upvote 0 Downvote
Hi,
thank me when it's fixed.. As for corrupt drivers, well there's always a chance of something being corrupted whenever a hard shutdown is performed or similar catastrophic events like a bsod for instance. Although the machine is actively shutting down to prevent damage continual bsods are plainly not good.
Best of luck with the new build and please do post back if any issues are encountered.
 
Upvote 0 Downvote
I moved to a different city so I have no idea what ever happened with the pc but, I bet that will probably fix it with brand new hardware and os install
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

  • Solved
Windows 10 Troubleshooting BSOD: Kernel Data Inpage Error Related to HDD Issues
Replies
1
Views
2K
kemical
S
  • Solved
Windows 8 W8.1 Kernel Data Inpage Error
Replies
12
Views
10K
kemical
S
  • Solved
Windows 8 BSOD Kernel Data Inpage Error/ ntoskrnl.exe
2
Replies
39
Views
24K
kemical
N
  • Solved
Windows 8 Kernel Data Inpage Error
Replies
3
Views
2K
kemical
  • Solved
Windows 7 Kernel Data Inpage Error - Desperately Need Help!! :(
Replies
5
Views
5K
adeleng