Windows 7: MEMORY_MANAGEMENT BSOD during game.

usasma · 26 Apr 2012

Patience please. These things sometimes take a while to solve. In this case we've almost finished removing all the problems due to 3rd party drivers. The last 2 things are 1) to remove the traces of the BS_I2cIo driver device and 2) to update the wired network card drivers.

Is Driver Verifier still working? If so, then the absence of any Driver Verifier memory dumps is highly significant. Please let me know as this may change the direction of our testing.

I believe that the error regarding BS_I2cIo in the perfmon /report is due to you removing the driver.
Is that the case? Did you follow my instructions to remove the driver?
If that's the case, go into Device Manager, locate the device (you may have to enable the showing of Hidden Devices in order to find it), then right click on it and select "Uninstall"
Reboot and check to see if it comes back or not.

The only older driver left on your system (that shows in the memory dumps) is your wired network driver (Rt64win7.sys). Please:
- download a fresh copy of the latest driver from here: Realtek
- uninstall the current wired driver/software from your system
- install the freshly downloaded copy.

If you get another BSOD after that (and it's one of the one's that's likely to benefit from Driver Verifier) then we'll try Driver Verifier again. If it's not, then we'll look at either hardware or Windows problems.

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)
Rt64win7.sys     Thu Feb 26 04:04:13 2009 (49A65B0D)
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)
NuidFltr.sys     Fri Apr 08 18:58:16 2011 (4D9F9308)
point64.sys      Wed May 18 04:07:20 2011 (4DD37E38)
LMouFilt.Sys     Fri Sep 02 02:23:15 2011 (4E607653)
bcmwlhigh664.sys Tue Apr 19 03:13:08 2011 (4DAD3604)
nvhda64v.sys     Tue Jan 17 07:45:46 2012 (4F156D7A)
LHidFilt.Sys     Fri Sep 02 02:23:09 2011 (4E60764D)
RTKVHD64.sys     Tue Mar 27 05:01:50 2012 (4F7181FE)
cpuz135_x64.sys  Wed Sep 21 04:23:41 2011 (4E799F0D)
nvlddmkm.sys     Tue Apr 03 09:01:59 2012 (4F7AF4C7)
nvBridge.kmd     Fri May 20 23:58:23 2011 (4DD7385F)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\042612-19531-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Thu Apr 26 10:30:54.472 2012 (UTC - 4:00)
System Uptime: 0 days 0:26:49.064
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+22a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  iw5mp.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!ObReferenceObjectByHandleWithTag+22a
Bugcheck code 00000050
Arguments fffff880`09bef008 00000000`00000000 fffff800`033baf4a 00000000`00000002
BiosVersion = 6.00 PG
BiosReleaseDate = 01/10/2008
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\042512-23244-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Wed Apr 25 19:05:59.310 2012 (UTC - 4:00)
System Uptime: 0 days 8:00:47.027
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_POLICY::Reset+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_POLICY::Reset+0
Bugcheck code 00000050
Arguments fffff880`03045bf4 00000000`00000000 fffff880`02dc8f6c 00000000`00000000
BiosVersion = 6.00 PG
BiosReleaseDate = 01/10/2008
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

zharek · 27 Apr 2012

ok, got the updated realtek driver in. and removed the BS_I2cIo it was hidden under non-plug and play.

So Now ill do some testing to see if i bsod. for some reason when i have verifier running my games lag, is it a backgroud service or what? or maybe its not verifier at all, should i have it running now, or just wait for another bsod?

usasma · 27 Apr 2012

Driver Verifier does extra things to the drivers - so it's normal to see a bit of lag while it's running.

Turn Driver Verifier off for now.
Best case is that you don't have any further BSOD's
Other scenarios include
- BSOD that doesn't need Driver Verifier to tell us what it is
- BSOD that needs Driver Verifier to tell us what it is

What we're looking for is assurance from the system that this isn't a 3rd party driver problem. If we get that, then it's safe to move on to either hardware or Windows troubleshooting.

So wait to see if you get BSOD's.
If you do, zip them up and upload them and we'll move on from there.

zharek · 30 Apr 2012

hmm Blue screens seem to have stopped, 2 days now going on 3rd.

zharek · 03 May 2012

still getting a bsod after playing any game i have installed, or the game itself crashes (usually crashes first, then bsods) report is in the attached file, help appreciated

hopefully some new clues will be there.

usasma · 03 May 2012

MSINFO shows:
1 on 5/1
2 on 5/3
and one involving bcmwlhigh664.sys on 4/30

But, only one memory dump seems to have been captured (dating from 5/3) - and it's a Verifier Enabled memory dump. It blames memory corruption (NOT a 3rd party driver).

In this case I'd have to start wondering about hardware.

I still suspect your wireless USB device (just because I always suspect those devices) - and the memory dump on 4/30 blames it's driver (bcmwlhigh664.sys). Please replace the driver (uninstall the old one, then download and install a fresh copy). Be sure not to reinstall the other, older drivers related to the card (or we'll be starting over).

Once that's done, it's time to start testing your CPU and your RAM.

Run as many of the CPU stress tests from here as you can: Additional Hardware Diagnostics
If none of them fail, then run Prime95 on each stick in each slot (individually). This will most likely point out a problem stick or slot.

Run the Prime95 Blend test for an hour on each stick in each slot. You can stop a test as soon as errors show up. Then move on to the next stick/slot until you've tried all combinations.

Then try it by moving both sticks around into different slots (following the mobo manufacturer's RAM instructions) and run them for an hour each to see what happens.

Just FYI - I'm also wondering about your BIOS as it dates from 2008. Do you know if there's any updates for it?

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)
MpFilter.sys     Fri Mar 09 06:05:26 2012 (4F59E3F6)
scmndisp.sys     Fri May 27 06:30:22 2011 (4DDF7D3E)
speedfan.sys     Fri Mar 18 12:08:46 2011 (4D83838E)
nvhda64v.sys     Tue Jan 17 07:45:46 2012 (4F156D7A)
LMouFilt.Sys     Fri Sep 02 02:23:15 2011 (4E607653)
RTKVHD64.sys     Tue Mar 27 05:01:50 2012 (4F7181FE)
dc3d.sys         Wed May 18 04:07:24 2011 (4DD37E3C)
NuidFltr.sys     Fri Apr 08 18:58:16 2011 (4D9F9308)
point64.sys      Wed May 18 04:07:20 2011 (4DD37E38)
LHidFilt.Sys     Fri Sep 02 02:23:09 2011 (4E60764D)
bcmwlhigh664.sys Tue Apr 19 03:13:08 2011 (4DAD3604)
cpuz135_x64.sys  Wed Sep 21 04:23:41 2011 (4E799F0D)
nvlddmkm.sys     Wed Feb 29 13:04:52 2012 (4F4E68C4)
nvBridge.kmd     Fri May 20 23:58:23 2011 (4DD7385F)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\050312-31637-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Thu May  3 08:31:11.915 2012 (UTC - 4:00)
System Uptime: 0 days 0:33:34.632
Probably caused by : memory_corruption ( nt!MiEmptyWorkingSet+1c5 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!MiEmptyWorkingSet+1c5
Bugcheck code 0000000A
Arguments fffff6fc`40061e68 00000000`00000000 00000000`00000000 fffff800`0317dc35
BiosVersion = 6.00 PG
BiosReleaseDate = 01/10/2008
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

zharek · 03 May 2012

i unplugged my wireless adapter and tested the games after, all the games ran perfectly fine, no crashes or bsod. this has actually been a problem before and the same test got the same results, i know its the adapter now because the first time it happened i directly connected to a router and everything played fine, but im unable to do that in my current location.

WNDA3100v2

this is my device, i have already gotten the latest drivers; version 2.0.0.1, is there a way to stop the problems with this device? thank you for your time and continued assistance

usasma · 03 May 2012

AFAIK the only way to stop the problem is to either:
- buy a wireless PCI card to stick in a slot in your motherboard.
- buy a very, very long cable to use a wired connection.

I really don't think that there's a way to make the wireless USB device stable with your system. We've seen too many of these problems with these devices.

zharek · 03 May 2012

what if i run windows xp? would it be stable then?

and could you recommend a pci wireless card?

zharek · 03 May 2012

sorry for double post, but i was also wondering about whether their might be a hotfix?

Windows 7: MEMORY_MANAGEMENT BSOD during game.

MEMORY_MANAGEMENT BSOD during game. problems?