Windows 7: Memory Corruption BSOD - Only on first boot.

fluffedup · 21 Mar 2010

Im constantly getting Memory Corruption BSOD within seconds or minutes of logging in to the computer. But the weird thing is after its crashed once it wont do crash again until a few hours later when you restart.

System Specs are in the tab at the bottom.

Ive replaced the graphics card with my old trusty 4870 ATI card and i still got these crashes. Ive even replaced the ram, i used to have 4GB of Corsair ram but changed to 8GB of G Skill 1600mhz ram.

The cpu is overlocked from 2.67ghz to 3.63ghz, all the overclocking was set up by a online company but after them failing to help me im willing to changed voltages etc, ill post details of the voltages later in case that might be the cause.

Ive replaced my keyboard/mouse/installed only basic software because memory corruption can range from any type of device/software/driver (googled it).
Ive also done a clean install of Windows 7 and removed and reseated most of the components.

Ive also attached the mini dumps in case anyone can make more sense from them than i can. Thanks.

zigzag3143 · 21 Mar 2010

Quote: Originally Posted by fluffedup

Im constantly getting Memory Corruption BSOD within seconds or minutes of logging in to the computer. But the weird thing is after its crashed once it wont do crash again until a few hours later when you restart.

System Specs are in the tab at the bottom.

Ive replaced the graphics card with my old trusty 4870 ATI card and i still got these crashes. Ive even replaced the ram, i used to have 4GB of Corsair ram but changed to 8GB of G Skill 1600mhz ram.

The cpu is overlocked from 2.67ghz to 3.63ghz, all the overclocking was set up by a online company but after them failing to help me im willing to changed voltages etc, ill post details of the voltages later in case that might be the cause.

Ive replaced my keyboard/mouse/installed only basic software because memory corruption can range from any type of device/software/driver (googled it).
Ive also done a clean install of Windows 7 and removed and reseated most of the components.

Ive also attached the mini dumps in case anyone can make more sense from them than i can. Thanks.

Well these were casued by memory corruption. One ither thing I noticed was that your AVP.exe (kaspersky AV) was in the stack on several of the crashes. I would remove the AV and test the memory by downloading memtestx86 and run it for 5 passes.

Let us know if you need help

Ken

Code:

031910-23134-01.dmp    3/19/2010 6:35:32 PM    BAD_POOL_HEADER    0x00000019    00000000`00000003    fffffa80`06692920    fffffa80`06692920    fffffa80`04692920    fltmgr.sys    fltmgr.sys+1b52                    x64        C:\Users\K\Desktop\Mini Dumps\031910-23134-01.dmp    4    15    7600    
031910-21528-01.dmp    3/19/2010 6:38:16 PM    IRQL_NOT_LESS_OR_EQUAL    0x0000000a    fffff680`000117e8    00000000`00000000    00000000`00000000    fffff800`02eb81ca    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Mini Dumps\031910-21528-01.dmp    4    15    7600    
031910-22666-01.dmp    3/19/2010 6:27:14 PM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041790    fffffa80`04aecc50    00000000`0000ffff    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Mini Dumps\031910-22666-01.dmp    4    15    7600    
032010-28704-01.dmp    3/20/2010 1:29:32 PM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041287    00000000`00000000    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Mini Dumps\032010-28704-01.dmp    4    15    7600    
032010-29094-01.dmp    3/20/2010 1:25:18 PM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041790    fffffa80`04abdb50    00000000`0000ffff    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Mini Dumps\032010-29094-01.dmp    4    15    7600    
032110-22994-01.dmp    3/21/2010 7:19:28 PM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041790    fffffa80`04abdb20    00000000`0000ffff    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Mini Dumps\032110-22994-01.dmp    4    15    7600    
032110-27034-01.dmp    3/21/2010 12:18:56 PM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041201    fffff683`ff7f55e0    8a000002`085ed025    fffffa80`06a784f0    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Mini Dumps\032110-27034-01.dmp    4    15    7600    
032110-34741-01.dmp    3/21/2010 11:53:40 AM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041790    fffffa80`04a8b750    00000000`0000ffff    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Mini Dumps\032110-34741-01.dmp    4    15    7600

fluffedup · 21 Mar 2010

Just uninstalled kaspersky to see if that fixes it but i got another crash after i restarted the computer (No Error given).

I attached the dump again, thanks for helping.

Ive left memtest running last night for 7 passes with no errors.

zigzag3143 · 21 Mar 2010

Quote: Originally Posted by fluffedup

Just uninstalled kaspersky to see if that fixes it but i got another crash after i restarted the computer (No Error given).

I attached the dump again, thanks for helping.

Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

Maybe we are starting to make some headway.

Lets start with your HD>
CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).
Copy/paste the results into your next post.

Ken

fluffedup · 21 Mar 2010

　
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 5)...
192000 file records processed. File verification completed.
228 large file records processed. 0 bad file records processed. 0 EA records processed. 88 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
266130 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
192000 file SDs/SIDs processed. Cleaning up 107 unused index entries from index $SII of file 0x9.
Cleaning up 107 unused index entries from index $SDH of file 0x9.
Cleaning up 107 unused security descriptors.
Security descriptor verification completed.
37066 data files processed. CHKDSK is verifying Usn Journal...
34448176 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
191984 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
203761747 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.
976657407 KB total disk space.
161188644 KB in 150123 files.
99272 KB in 37067 indexes.
0 KB in bad sectors.
322499 KB in use by the system.
65536 KB occupied by the log file.
815046992 KB available on disk.
4096 bytes in each allocation unit.
244164351 total allocation units on disk.
203761748 allocation units available on disk.
Internal Info:
00 ee 02 00 42 db 02 00 9e 7d 05 00 00 00 00 00 ....B....}......
09 02 00 00 58 00 00 00 00 00 00 00 00 00 00 00 ....X...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Windows has finished checking your disk.
Please wait while your computer restarts.

Windows has also started to say that the blue screen was caused by a faulty device / driver since removing avp, before it was uninstalled it said no solution was found.

fluffedup · 22 Mar 2010

Tried to turn computer on - BSOD no error.
Turned it on again - loaded but said there was an error with the keyboard driver being corrupt in a small pop up and crashed a few seconds after - SYSTEM_SERVICE_EXECPTION.

Wont boot into safe mode or normal even if i change keyboard/mouse... when i load safe mode it loads the files and then i get graphical artefacts at the top of the screen like coloured bars / dots everywhere and then resets to the bios.

Any ideas? The graphics card is currently a 4870 1gb gddr5 (5850 is being RMA'd) in case thats why i got weird colours .

Windows 7: Memory Corruption BSOD - Only on first boot.

Memory Corruption BSOD - Only on first boot. problems?