MEMORY_MANAGEMENT BSOD during game.

zharek · 23 Apr 2012

Windows 7 64 bit
motherboard TF520 A2+
Processor Amd athlon 64 x2 dual core 3.2 ghz
memory: 4096MB Ram
graphics card: geforce gtx 550TI

Need to know the actual cause of this, Never seen this blue screen before.

blue screen's stopped for about a month and now they are back. :/

attached jcgriff reports.

usasma · 23 Apr 2012

You have a NETGEAR WNDA3100v2 N600 Wireless Dual Band USB Adapter
Win 7 doesn't like these devices - and with older (Vista-era) drivers it's sure to cause BSOD's. You have a later version of the driver(s), but I've continued to see problems with these devices.
Here's my rant about these devices:

I do not recommend using wireless USB devices. Especially in Win7 systems.
These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

AFAIK - ATITool is not compatible with Win7. Please uninstall it: Driver Reference Table - ATITool.sys

MSI Afterburner (along with Riva Tuner and EVGA Precision) will often cause BSOD's in Win7 systems. Please uninstall it immediately.

If overclocking, please stop and return the system to default (stock) values while we're troubleshooting. Feel free to resume the overclock once the system has been stabilized. Please let us know if you are overclocking and if you've stopped overclocking for the duration of our troubleshooting.

Your BIOSTAR I2C I/O driver that's found in the BIOSTAR BIOS Flash Utility dates from 2006. Please uninstall that program from your system.

Please understand that the earlier BSOD's are likely to point in a false direction due to the absence of SP1. Only the latest memory dump shows that SP1 is installed.

Please run Driver Verifier according to these directions: Driver Verifier Settings

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


amdxata.sys      Fri Mar 19 12:18:18 2010 (4BA3A3CA)
mcdbus.sys       Tue Feb 24 05:34:07 2009 (49A3CD1F)
MpFilter.sys     Wed Apr 06 16:07:29 2011 (4D9CC801)
scmndisp.sys     Fri May 27 06:30:22 2011 (4DDF7D3E)
speedfan.sys     Fri Mar 18 12:08:46 2011 (4D83838E)
dc3d.sys         Wed May 18 04:07:24 2011 (4DD37E3C)
point64.sys      Wed May 18 04:07:20 2011 (4DD37E38)
LHidFilt.Sys     Fri Sep 02 02:23:09 2011 (4E60764D)
LMouFilt.Sys     Fri Sep 02 02:23:15 2011 (4E607653)
Rt64win7.sys     Thu Feb 26 04:04:13 2009 (49A65B0D)
BS_I2cIo.sys     Mon Dec 11 02:48:39 2006 (457D0D57)
nvhda64v.sys     Tue Jan 17 07:45:46 2012 (4F156D7A)
RTKVHD64.sys     Tue Mar 27 05:01:50 2012 (4F7181FE)
cpuz135_x64.sys  Wed Sep 21 04:23:41 2011 (4E799F0D)
bcmwlhigh664.sys Tue Apr 19 03:13:08 2011 (4DAD3604)
nvlddmkm.sys     Tue Apr 03 09:01:59 2012 (4F7AF4C7)
nvBridge.kmd     Fri May 20 23:58:23 2011 (4DD7385F)
NuidFltr.sys     Fri Apr 08 18:58:16 2011 (4D9F9308)
scmndisp.sys     Wed Jan 17 02:48:03 2007 (45ADD4B3)
bcmwlhigh664.sys Wed Oct 13 14:18:34 2010 (4CB5F7FA)
nvlddmkm.sys     Thu Jan 26 05:19:23 2012 (4F2128AB)
MpNWMon.sys      Wed Apr 06 16:07:23 2011 (4D9CC7FB)
aswMonFlt.sys    Tue Mar 06 19:01:51 2012 (4F56A56F)
aswFsBlk.SYS     Tue Mar 06 19:01:31 2012 (4F56A55B)
aswTdi.SYS       Tue Mar 06 19:01:56 2012 (4F56A574)
aswSnx.SYS       Tue Mar 06 19:04:05 2012 (4F56A5F5)
aswrdr2.sys      Tue Mar 06 19:02:19 2012 (4F56A58B)
aswSP.SYS        Tue Mar 06 19:04:03 2012 (4F56A5F3)
amdxata.sys      Tue May 19 13:56:59 2009 (4A12F2EB)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\042312-20529-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Mon Apr 23 16:08:08.688 2012 (UTC - 4:00)
System Uptime: 0 days 13:56:06.405
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29dbf )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+29dbf
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff781`c0000000 00000000`00009d17 0000953f`00012a82
BiosVersion = 6.00 PG
BiosReleaseDate = 01/10/2008
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\031412-27768-01.dmp]
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Debug session time: Thu Mar 15 02:23:31.120 2012 (UTC - 4:00)
System Uptime: 0 days 0:58:41.056
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  LoLLauncher.ex
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169
Bugcheck code 00000050
Arguments fffff880`03172e28 00000000`00000000 fffff880`03d5a0b9 00000000`00000001
BiosVersion = 6.00 PG
BiosReleaseDate = 01/10/2008
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\031412-20607-01.dmp]
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Debug session time: Thu Mar 15 01:24:18.936 2012 (UTC - 4:00)
System Uptime: 0 days 10:23:40.871
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  Reckoning.exe
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169
Bugcheck code 00000050
Arguments fffff880`07fc1f88 00000000`00000000 fffff880`03d8b0b9 00000000`00000000
BiosVersion = 6.00 PG
BiosReleaseDate = 01/10/2008
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\031412-16816-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Mar 14 04:10:35.081 2012 (UTC - 4:00)
System Uptime: 0 days 1:43:35.845
Probably caused by : ntkrnlmp.exe ( nt!SepDuplicateToken+3d2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!SepDuplicateToken+3d2
Bugcheck code 00000050
Arguments fffff880`096e25ac 00000000`00000000 fffff800`02fa7af2 00000000`00000002
BiosVersion = 6.00 PG
BiosReleaseDate = 01/10/2008
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\031312-19266-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Mar 14 01:00:40.897 2012 (UTC - 4:00)
System Uptime: 0 days 3:11:42.723
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  Reckoning.exe
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169
Bugcheck code 00000050
Arguments fffff880`09cc7118 00000000`00000000 fffff880`10b840b9 00000000`00000000
BiosVersion = 6.00 PG
BiosReleaseDate = 01/10/2008
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\031312-17940-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Tue Mar 13 21:48:17.068 2012 (UTC - 4:00)
System Uptime: 0 days 15:32:24.894
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+22a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  audiodg.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!ObReferenceObjectByHandleWithTag+22a
Bugcheck code 00000050
Arguments fffff880`09a2d000 00000000`00000000 fffff800`02fc7b5a 00000000`00000002
BiosVersion = 6.00 PG
BiosReleaseDate = 01/10/2008
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

zharek · 23 Apr 2012

My netgear driver is a windows 7 driver ~ latest.

I have uninstalled the programs you mentioned. And I believe I removed the BS_I2cIo.sys.

should I reupload a report to see if I did it correctly?

zharek · 23 Apr 2012

I would also like to mention that that is not the only blue screen, just the latest after i cleared my system register/and everything else. so .dmps got erased. there has been others.

Also I would like to note that one of my cores of my cpu failed a prime95 test in just 3 minutes.

mobo is 6 years old, proc is 5.

usasma · 23 Apr 2012

If one of your cores has failed Prime95 this becomes primarily a hardware problem.
Start with the free diagnostics here: Hardware Diagnostics
Try the video and CPU tests further down the page.

zharek · 24 Apr 2012

Prime95:

FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected

usasma · 24 Apr 2012

Yes, that's an error in Prime95
Which test were you running? Did you run the other tests (Blend, Small FFT's and Large FFT's)? If so, which caused errors the quickest - and which caused errors the slowest?

Please run the other tests that I suggested above.

zharek · 24 Apr 2012

worker #2 Blend

completed 1 test ~3 minutes

FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected

worker #2 small FFTs

completed 1 test ~3 minutes

FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected

worker #1 in place large FFTs

completed 1 test ~ 2 minutes

FATAL ERROR: Rounding was 8192, expected less than 0.4
Hardware failure detected,

8192? (holy crap?)

worker # 2 in place large FFT's

completed 2 test ~ 4 minutes

FATAL ERROR: Final result was 090392D0, expected: EEEC1181.
Hardware failure detected,

zharek · 24 Apr 2012

im guessing that my cpu is severely trashed

usasma · 24 Apr 2012

Prime95 stresses 3 components:
- RAM
- CPU cache
- memory controller (included in new CPU's, on mobo with older CPU's)
Your CPU has the controller on the CPU - not on the motherboard.

These features don't directly relate to tests that you ran, but they do give some significant hints.
In short, if the Blend test doesn't cause errors quicker than the others - then we suspect your CPU (because the other tests error'd out faster). This is just guesswork, so we need further verification.

To do that, you have to run the tests that I suggested earlier. Among them are CPU stress tests that will give more accurate results if your CPU is failing.