Windows 7 Mainly caused by ntoskrnl.exe , dxgmm1.sys , atikmdag.sys

[Secumfex]

So I'm getting an abundant amount of BSODs while gaming, for quite some time now. It's basicly bound to happen, everytime I play a game, after 15 to 45 minutes.

How ever, it may (even though by far less frequently) happen while surfing.

The BSODs Names range from SYSTEM_SERVICE_EXCEPTION over PAGE_FAULT_IN_NONPAGED_AREA to BAD_POOL_HEADER , which occur most frequently.

I attached the minidumps from the last few days.

The files or services that BlueScreenView suggests to have caused the BSOD are mainly the following:
- atikmdag.sys
- ntoskrnl.exe
- win32k.sys
- dxgmms1.sys
- dxgkrnl.sys

As a layman I'd say this sounds a lot like GPU / GPU Driver related errors, plus, it mainly happens while playing GPU heavy games (BFBC2, GTA4 at the moment).

Steps I have done so far:
- Deinstalled Pen Tablet Drivers (BSODs occured somewhat from the same time)
- Deinstalled NIS
- Deinstalled ATI CCC and Installed ATI Drivers without CCC
- Deinstalled Daemon Tools
- Ran memtestx86 (2 runthroughs - no errors)
- Ran check disk (no errors)
- Ran system drivers check (no errors)
- Swapped RAM Slots
- Took 1 RAM out
- Swapped remaining RAM with one i took out
- Put both back in
- Checked all fans are running
- Watched temperatures while playing (not even close to 60 or 55 C° , so no overheating at all)

I'm running out of ideas, I'd love to hear if anyone has any advice left for me to try out.
I did not yet convince myself it'd be a good idea to replace ntsokrnl.exe even though some websites advise it.
May it also be my hard disks dying? Or may it even be a late Windows 7 Update causing the trouble (I have read many posts like mine elsewhere lately)?

Since I guess it's a driver issue, can someone point out to me, which ones I should update/remove/reinstall and howI should do that?

CPU-Z Screencaps:
Link Removed due to 404 ErrorLink Removed due to 404 ErrorLink Removed due to 404 ErrorLink Removed due to 404 ErrorLink Removed due to 404 Error

The latest Dump being:
Link Removed due to 404 Error

I'm not overclocking anything, haven't changed any BIOS settings, but also never updated it since I got the new hardware somewhen 2010 (?).

Basic PC Specs:
Windows 7 64-bit Service Pack 1 (didnt notice that until now... are there newer SPs?)
ASRock H55M Pro - Mainboard
Intel Core i5 750 - CPU
2x GEIL 2GB CL7-7-7 DDR3-1333 (I'm wondering whether my Frequencys are correct?) - RAM
Radeon HD5770 - GPU

Is there anything else I should post for further information?



Edit: thanks for moving =)

 

[Elmer]

Just a quickie, just because they haven't "solved" your problem, please don't step backward. It is, after all, a process of elimination!

Update:
GEARAspiWDM.sys Mon May 18 13:17:04 2009 Gear Software CD-ROM Class Filter Driver v4.015.1 (Feb 2010). Also comes with iTunes

Your dumps are still showing Graphics related problems, but old drivers can cause erroneous problems.

And BFBC2Game.exe is mentioned

 

[nmsuk]

If you go into your bios and memory timings can you set you command rate to 2T please. There no way the board or memory with multiple sticks is going to be capable of 1T. We know the sticks are fine and tested with each slot. If you boot to windows with one stick do you still get the bsods?

UPDATE

Just been doing some research and everywhere I look the memory says it's 7-7-7-24 timings for the slowest speed the memory will do. For 1333Mhz though the timings should be 9-9-9-24.

UPDATE2

Just been checking my machine that has Geil memory in it seems to have the SPD info set wrong.

 

[Secumfex]

Just a quickie, just because they haven't "solved" your problem, please don't step backward. It is, after all, a process of elimination!

Of course, uninstalled GEAR driver (manually) again.

Your dumps are still showing Graphics related problems, but old drivers can cause erroneous problems.

And BFBC2Game.exe is mentioned

Yes, I get the BSODs always when I play BFBC2. Should I have pointed that out more clearly?
They occur mostly, but not only when i play Battlefield Bad Company 2. I haven't tried any other games in the past week, really.

I'm googling on that topic right now, turns out BFBC2 shows an ATI Catalyst related issue that causes BSODs. But only on the newer ATI drivers ( 10.3 + , so the newest Catalyst, 10.6 has this issue, too). So ironically, looks like new drivers can cause erroneous problems problems, too .

I'm going to try out an older driver, see whether that helps.

If you go into your bios and memory timings can you set you command rate to 2T please. There no way the board or memory with multiple sticks is going to be capable of 1T. We know the sticks are fine and tested with each slot. If you boot to windows with one stick do you still get the bsods?

Command Rate is set to 2T already. I got BSOD with only 1 stick, too.

UPDATE

Just been doing some research and everywhere I look the memory says it's 7-7-7-24 timings for the slowest speed the memory will do. For 1333Mhz though the timings should be 9-9-9-24.

UPDATE2

Just been checking my machine that has Geil memory in it seems to have the SPD info set wrong.

So what's your advice? Can I manually set another timing? Ram itself is labled 7-7-7-24, though.

 

[nmsuk]

Yes you could manually set the timings in the bios. 9-9-9-24. Should be fairly straight forward. If you try it, try bbfc2 and see if it's any better.

 

[Elmer]

Yes, I get the BSODs always when I play BFBC2. Should I have pointed that out more clearly?

No.
I should read more carefully! If going backwards with your drivers, not a problem. Just make sure they are "WHQL" listed. There was one, pre Xmas that caused no end of problems. Sadly, off the top of my head I cannot remember which it was, Could have been 10.12.

 

[Secumfex]

Looks like it was an issue related to the brand of DIMM.
those PC3-10660(10666) 1333Mhz Value Dual from Geil seem to be quite infamous for their misbehaviour with standard BIOS timing settings.

Instead of 7-7-7-24 at 1333MHz, they now run perfectly fine (if not even faster) at 6-6-6-20 and 1066Mhz.

I think this thread is now safe to close