More and more lately, I have been getting Kernel Data Inpage Error BSODs. They mostly happen when I am using Photoshop or other high memory tasks.
Attached is the SF_DD_MM_YYYY.zip crash report thing.
Any help is appreciated.
Ianaf,
All your .dmps come with bug check 7A some information on their usual causes...
Scan the system for possible virus infection:STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR
Usual causes: Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack
Source: Carrona.org
ESET online scanner:
Run windows defender offline at last:
Upload a screenshot of your hard disk using crystal disk info:
- CrystalDiskInfo - Software - Crystal Dew World
- Screenshots and Files - Upload and Post in Seven Forums
Run Disk Check on your hard disk for file system errors and bad sectors on it:
For monitoring the heat/celsius of the system, use Speccy or HWinfo:
- Speccy - System Information - Free Download
- CPUID - System & hardware benchmark, monitoring, reporting
Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:
Let us know the results of above ^
Then proceed with testing RAM sticks:
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
Hope that helps.The goal is to test all the RAM sticks and all the motherboard slots.
Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.
If you get errors, stop the test and continue with the next step.
1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.
2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.
If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.
In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
TDSSKiller came up with a few threats, don't know if they are important. Screencapped the best I could.
I am working on the rest of that stuff now.
Alright.
Let us know the results.
BTW, Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.
Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.
SFC /Scannow finished and said this: "Windows Resource Protection did not find any integrity violations."
Speccy says average CPU temperature is 46 C.
And attached is the crystaldisk screenshot, and the msinfo32.
Still working on the rest.
Click on the Caution button. In the resulting window, Pull all the sliders to the ultimate left, and apply. Does it change anything there?
When I clicked on it, all the sliders were already at the left.
Run chkdsk /f/r, following the option two of the tutorial Disk Check
See if it changes the situation or not.
I am running Windows defender offline now, so I will check in later and try that.
Okay.
I completed everything on koolkat77's list, and the chkdsk /f/r.
Crystaldisk still looks the same, health status says "caution."
I haven't had a BSOD yet, but it is only the beggining.
Quote