Quite a lot of dumps there. Only 2 of them that would be of any use to us though as the rest are weeks and months old.
System Information:
Code:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03c16000 PsLoadedModuleList = 0xfffff800`03e5b670
Debug session time: Thu Jan 26 21:09:47.506 2012 (GMT-7)
System Uptime: 0 days 6:02:27.832
CPU Infomration:
Code:
CPUID: "Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz"
MaxSpeed: 2670
CurrentSpeed: 2664
You're not overclocking anything - Good!
BSOD reports corrupt regions in some pool headers, but the consistency is there for blaming either the NT Kernel as being the BSOD instigator, or the atikmdag.sys driver.
Code:
atikmdag+0x3eb4d9:
fffff880`0568c4d9 488bc2 mov rax,rdx
fffff880`0568c4dc 48c1e83f shr rax,3Fh
fffff880`0568c4e0 4803c2 add rax,rdx
fffff880`0568c4e3 c3 ret
fffff880`0568c4e4 cc int 3
fffff880`0568c4e5 cc int 3
fffff880`0568c4e6 cc int 3
fffff880`0568c4e7 cc int 3
I'm seeing the faults here are being caused by your atikmdag on most occasions trying to read an address by referencing a pointer to some invalid/corrupt location in memory most probably.
So we'll try with a memory diagnostics test first to make sure that everything in RAM is okay.
Download and run
Memtest86 on boot:
http://www.memtest86.com- Download Memtest86 and burn to disk. (If you need software to do so I would highly recommend a program called ImgBurn, and it's also free)
- Reboot your computer and boot from the CD drive for which you have your Memtest86 disk.
- You may need to load the Boot menu which will enable you to choose a device to boot from, otherwise you'll have to change the boot order in the BIOS to boot from CD drives as first priority before the HDD
- Make sure to let it run and do it's thing for about the first 6 tests. If it passes those, then everything should be good, otherwise any failure to pass those tests indicates a corruption in your memory.
- If you get an error on one of the tests, then you should try by booting up your computer with each RAM inserted separately one at a time. When you find one that doesn't return any errors then test it in every single RAM slot to test for a bad socket.