Repeating BSODs

[Szlamozaur]

Hello

So i've been getting the same few BSODs over past couple of months. Thing is, they only occur whilst playing one and the same game or at least i can't recall any other situation. Game is called "Heroes of Newerth" however their support is kind of a failure so i thought i will try my luck here.
The BSODs happen no matter what system and configuration i'm using. I've been getting them both on Win XP Pro SP2/3 32 bit and Windows 7 Home Premium 64bit (which i'm using on daily basis now). About my specs, they've also changed along the way. Well, my MoBo died, so before it was GigaByte EP35 DS3, C2D E6750, 2-6gig ram, GF 8800 GT). Changed to ASUS P5Q-VM and Radeon 5850 HD Twin Razor MSI and currently permanently running with 6gig ram. Same processor and RAM remain. No tweaking/overclocking was done, ever, to any of the parts of my PC.
I did run memtest on my RAMs and they showed nothing, yet, from what i've been googling around, it seems to be something with the RAMs. But i'm pretty sure you guys will be better at figuring out what exactly is the problem.

Minidumps attached.

In advance - thanks for any help that might come.

As per PCWizard 2010 :

Mainboard : Asus P5Q-VM DO
Chipset : Intel Q45
Processor : Intel Core 2 Duo E6750 @ 2666MHz
Physical Memory : 6144MBDDR3-SDRAM
Video Card : ATI Radeon HD 5800 Series
Hard Disk : Seagate ST3400820AS ATA Device (400GB)
Monitor Type : Idek Iiyama PL2410HD - 24 inches
Network Card : Intel 82567LM-3 Gigabit Network Connection
Operating System : Windows 7 Home Premium Home Edition Media Center 6.01.7600 (64-bit)
DirectX : Version 11.00
Windows Performance Index : 5.9 on 7.9

 

[mgorman87]

Please upload a jcgriff2 report
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

It looks like most of your crashes are video related.

atikmdag.sys Tue Mar 08 23:32:17 2011 (4D7702D1)

Update your video card drivers. Download the latest from here - AMD.com | Support & Downloads
Before you install them go into device manager and uninstall your device. Choose the option to remove the drivers if given one. Reboot the computer and then install the drivers.

e1k60x64.sys Tue Oct 21 15:48:25 2008 (48FE3209)

Update your Intel network driver - http://downloadcenter.intel.com/Det...rsion=Windows 7, 64-bit*&DownloadType=Drivers

Dnetr28ux.sys Wed Aug 05 09:59:46 2009 (4A799052)

Without the full report, I don't know what D-Link device you have. Go to the support site and download the latest drivers for your device -http://www.dlink.com/support/

Please run these tests and report back the results
1. Memtest86 - Run for 7-8 passes - http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
2. Prime95 - Run all three tests (Small FFTs, Large FFTs, Blend) for 3-4 hours each or until fail - http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html
3. Hard drive scan using SeaTools - SeaTools for Windows | Seagate - Both long and short tests


BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Fri Jun  3 09:31:58.391 2011 (UTC - 4:00)
System Uptime: 0 days 6:23:42.248
Probably caused by : atikmdag.sys ( atikmdag+3fd68b )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x3B
PROCESS_NAME:  hon.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+3fd68b
BiosReleaseDate = 11/02/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz"
MaxSpeed:     2660
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Wed May 25 13:28:33.133 2011 (UTC - 4:00)
System Uptime: 0 days 4:18:27.850
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a13 )
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  hon.exe
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4a13
BiosReleaseDate = 11/02/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz"
MaxSpeed:     2660
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Sat May 21 15:07:15.233 2011 (UTC - 4:00)
System Uptime: 0 days 1:01:40.090
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+96a )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
PROCESS_NAME:  System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+96a
BiosReleaseDate = 11/02/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz"
MaxSpeed:     2660
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Mon May 16 18:13:26.281 2011 (UTC - 4:00)
System Uptime: 0 days 9:02:29.139
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_LINEAR_POOL::Free+c1 )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x3B
PROCESS_NAME:  hon.exe
FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_LINEAR_POOL::Free+c1
BiosReleaseDate = 11/02/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz"
MaxSpeed:     2660
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun May  8 09:20:24.189 2011 (UTC - 4:00)
System Uptime: 0 days 0:45:34.156
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+6378 )
BUGCHECK_STR:  0x1a_31
PROCESS_NAME:  WerFault.exe
FAILURE_BUCKET_ID:  X64_0x1a_31_nt!_??_::NNGAKEGL::_string_+6378
BiosReleaseDate = 01/04/2008
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EP35-DS3
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz"
MaxSpeed:     2660
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[Szlamozaur]

Please upload a jcgriff2 report
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

It looks like most of your crashes are video related.

Done, files attached. Also attached a 'System Health Report'.

atikmdag.sys Tue Mar 08 23:32:17 2011 (4D7702D1)

Update your video card drivers. Download the latest from here - AMD.com | Support & Downloads
Before you install them go into device manager and uninstall your device. Choose the option to remove the drivers if given one. Reboot the computer and then install the drivers.

I got the newest drivers. These BSODs happened on both, new drivers and the drivers provided with the card (which i bought a few months ago).

e1k60x64.sys Tue Oct 21 15:48:25 2008 (48FE3209)

Update your Intel network driver - http://downloadcenter.intel.com/Det...rsion=Windows 7, 64-bit*&DownloadType=Drivers

Done.

Dnetr28ux.sys Wed Aug 05 09:59:46 2009 (4A799052)

Without the full report, I don't know what D-Link device you have. Go to the support site and download the latest drivers for your device -http://www.dlink.com/support/

It's D-Link DWA-140.
Done.

Please run these tests and report back the results
1. Memtest86 - Run for 7-8 passes - http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
2. Prime95 - Run all three tests (Small FFTs, Large FFTs, Blend) for 3-4 hours each or until fail - http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html
3. Hard drive scan using SeaTools - SeaTools for Windows | Seagate - Both long and short tests

Did memory tests before, came up empty - as in all passed. Will run them again thou, possibly later today.
For the moment, i did run hard drive scans :

S.M.A.R.T. Check - passed
Short Drive Self test - passed
Short Generic test - passed
Long Generic test - passed

Thanks for all the input so far.

 

[mgorman87]

Ok.

Update your computer to SP1 - Learn how to install Windows 7 Service Pack 1 (SP1)

 

[Szlamozaur]

So i've updated to SP1 and also run the memtest+ for about 24 hours, which ended reaching to 13 passes. No errors appeared. Yet, i still got another BSOD - memory_management

Any other ideas ?

 

[mgorman87]

Have you run the three Prime95 tests yet? (Small FFTs, Large FFTs, Blend)

Can you also run a memtest from cold boot. Leave the computer off overnight and when you turn it on in the morning have it boot right to memtest and run it for 2-3 passes.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jun  6 11:52:23.212 2011 (UTC - 4:00)
System Uptime: 0 days 2:31:30.851
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  hon.exe
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3
BiosReleaseDate = 11/02/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz"
MaxSpeed:     2660
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[Szlamozaur]

I started the Small FFTs test, and it quickly rockedted to 80 degrees (celsius) temperature at the cpu and i don't really like this fact. It's a Core2Duo E6750 CPU and generally it shouldn't exactly be running at that temperature for too long, right ? So for the moment i'm abandoning this and will run memtest from cold boot tomorrow before going to work, and will leave it for at least 8 hours.

//edit

9 minutes into the Small FFTs and i got my proc at 87 celsius..

Till what point can i push it ? As in, till what temperature, without risking a fried proc AND/OR mobo ?

 

[mgorman87]

According to Intel the max temp of your CPU is 77 degrees celcius. 86 is way too hot. You need to get that issue taken care of before you do any more type of testing.

 

[Szlamozaur]

When im not doing anything, it idles at 45-50 degrees celsius.

So is there a possibility that in fact my in-game BSODs are caused by overheating ? All in all, i run at 1920x1080, high details and the game itself is quite demanding. I never really controlled the temperatures whilst playing cause didn't think it could get to some severe situation.

 

[Szlamozaur]

All right, ignore the previous one.
I've ran the memtest from the cold boot, before leaving for work. It took approx. 5 minutes to pop up with about 10400 errors or some other ridiculous number. With this being said, i guess it's down to getting new memory. I'm not even going to bother to check which stick is screwed.
Nonetheless, thanks for all the tips. Rep added

 

[mgorman87]

All right, ignore the previous one.
I've ran the memtest from the cold boot, before leaving for work. It took approx. 5 minutes to pop up with about 10400 errors or some other ridiculous number. With this being said, i guess it's down to getting new memory. I'm not even going to bother to check which stick is screwed.
Nonetheless, thanks for all the tips. Rep added

Let us know if the new memory solves the problem

 

[Szlamozaur]

So far so good, no BSODs in-game on default settings of my ram sticks. Got kingston hyperx pc2-6400, but running them at 5300 for the moment.

once again - thanks for the help