Win 7 64 BSOD Errors

[redux]

Hi,
Recently I’ve been getting (on average) 1 BSOD every day. I used “Who Crashed” to analyse the cause of the crashes and it seems that each time it is a different issue.
The BSOD does not occur under load. Most times I am just web browsing when it occurs. (IE or Opera). I’ve run memtest and no errors occurred.
I update drivers and firmware whenever available. I can’t relate the occurrence of crashes with any particular update and the occurrences have spanned over newer drive updates. ATI drivers being a good example.)
The system health report states that I have no AV, but I am using MS Essentials. It also states that “Device is not present, not working properly, or does not have all of its drivers installed”. I’ve checked this and no error is showing in device manager. If I show hidden devices I can see under non plug and pray devices that there is a warning on, archlp, which the health report states is “tv_ConfigMgrErr24. I don’t have a tv card so I’m guessing this might be the ATI graphics card. (?)
I've attached BSOD Dump & System File Collection & System Health Report as per the sticky.
Any help on understanding the problem would be much appreciated!
Software:
Windows 7 x64 - Full retail version
Average age of hardware build - min 12 months, max 24 months
OS installed less than 6 months ago.
Using latest firmware and drivers
Hardware:
ATI 4870x2
Asus Xonar D2X
Intel X25-M G2 160GB
Mobo – Asus rampage Extreme - BIOS @ auto settings
8GB OCZ DDR3 RAM

 

[Jonathan_King]

I suspect the issue is with your 2005 ASACPI.sys file. Please install the latest ATK0110 Driver for XP/Windows 7/Vista from this link: ASUSTeK Computer Inc.-Support-

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jul  4 16:00:17.718 2010 (UTC - 4:00)
System Uptime: 0 days 1:28:54.218
BugCheck 1000007E, {ffffffffc0000005, fffff8800377312f, fffff88002954d68, fffff880029545d0}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGCONTEXT::Render+83f )
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul  2 06:50:58.329 2010 (UTC - 4:00)
System Uptime: 0 days 1:23:50.829
BugCheck 50, {fffff1201579ab98, 1, fffff88001495d4d, 7}
Probably caused by : Ntfs.sys ( Ntfs!NtOfsReadRecords+279 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  Steam.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 14 08:14:56.806 2010 (UTC - 4:00)
System Uptime: 0 days 4:03:44.680
BugCheck FC, {fffff880062b7b78, 8000000149367963, fffff880062b7220, 2}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+424d7 )
BUGCHECK_STR:  0xFC
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 13 11:16:16.608 2010 (UTC - 4:00)
System Uptime: 0 days 7:30:49.482
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck 3B, {c0000005, fffff96000319a61, fffff880073475e0, 0}
Probably caused by : Unknown_Module_fffff880`01e1bcb8 ( Unknown_Module_fffff880`01e1bcb8>+16770d8 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 12 10:42:01.466 2010 (UTC - 4:00)
System Uptime: 0 days 0:33:29.966
BugCheck 3B, {c0000005, fffff960001f94c0, fffff88009d9e1f0, 0}
Probably caused by : win32k.sys ( win32k!PDEVOBJ::bAllowShareAccess+0 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  msnmsgr.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jul  4 06:22:51.239 2010 (UTC - 4:00)
System Uptime: 0 days 0:33:20.739
BugCheck D1, {fffff8800b1867dd, 2, 1, fffff88001877c2f}
Probably caused by : tcpip.sys ( tcpip!TcpIndicateData+7f )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]

 

[redux]

Thanks Jonathan I really appreciate your help. I’ve updated the driver and will post back if it worked. Again my sincere thanks for taking the time out to help me.

 

[Jonathan_King]

You're very welcome. A grateful attitude encourages us to help even more.

 

[redux]

Hi, I really thought that driver might have been the problem, but I’ve just had another blue screen. I’ve attached the dump file it generated.
Maybe I should try a fresh install?

 

[Jonathan_King]

Please enable driver verifier: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 15 11:36:14.125 2010 (UTC - 4:00)
System Uptime: 0 days 3:12:21.000
BugCheck 1000007E, {ffffffffc0000096, fffff80001a50011, fffff880023e3fc8, fffff880023e3830}
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+1c1 )
PROCESS_NAME:  services.exe
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[redux]

Hi Johnathan,

I've set up driver verifier. When the next bsod occurs does it put the crash info in the dump file or do I need to collect it somewhere else?

Thanks

 

[Jonathan_King]

It will place the dump in C:\Windows\Minidump.

Don't bother running the tool again. Just upload the dmps only.

Here is a tutorial for that: http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

 

[redux]

Hi Johnathan, I ran driver verifier before reading your post and got one BSOD, but a dump file was not generated. After switching if off I got another BSOD, again with no dump file. I've just had another BSOD and a dump file was created as attached. Reading the other threads the lack of a dump file does not seem to bode well.

 

[redux]

Hi Johnathan, I've just re-run memtest and I picked up some errors, so it seems that ram is to blame. Sorry about troubling you. This is a great forum for authorative help. You guys do a great job.

 

[Jonathan_King]

Try testing the sticks individually. If you find a good one, test it in all slots to see whether it is a motherboard, RAM, or compatibility issue.

 

[redux]

I've just tested each module seperately in the same slot and 2 out of 4 failed, so I'm guessing its the ram not the mobo, but if I get anymore problems I will test all of the slots with a good module.