Windows 7: BSOD (possibly hardware) Memory_Management

I've been scouring the web for a possible answer for my BSOD...but so far no software changes have worked...

Starting when I had vista I got the BSOD and just before I upgraded (clean boot) to Windows 7 64 bit it wasn't multiple times a day...or as it was at a time...during start up
One of the first ones I actually reported was to yahoo answers called partmgr.sys
Blue screen of death I'm In HELL!? - Yahoo! Answers

The first idea I got from there that helped for a time was doing a defrag..but it didn't last by the next day I was back into the cycle of BSOD hell
And I rarely got the same error twice, but from what I read around the web sometimes they are covering up the problem
So I bring forth to you today a zip folder with the mini dump files...because I can't read them and that's helped so many others...oh and the reason I've been considering it to likely be hardware issue is because lately (I just went and re installed Windows 7 to see if that helped...which it did somewhat) I've been only getting Memory_Management BSOD

Hope there is something I can do...there is a lot of the history of my issue in the yahoo answers post

Please update this driver:

Code:

fffff880`02cbe000 fffff880`02d2e000   VSTBS26  VSTBS26.SYS  Thu Oct 16 07:54:06 2008 (48F690AE)
fffff880`04002000 fffff880`040cd000   VSTCNXT6 VSTCNXT6.SYS Thu Oct 16 07:52:22 2008 (48F69046)
fffff880`04473000 fffff880`045e7000   VSTDPV6  VSTDPV6.SYS  Thu Oct 16 07:57:45 2008 (48F69189)

They belong to Conexant SoftK56 Modem Driver and Conexant HSF_HWB2 WDM driver
What third party Antivirus software are you using?

I would suggest you to turn on Driver Verifier, it will flag your bad drivers:
Using Driver Verifier to identify issues with Drivers

Code:

BugCheck 1A, {41287, 30, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42be5 )

Followup: MachineOwner
---------
BugCheck 1A, {61940, 8929000, 9e1000000f51c800, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1fd63 )

Followup: MachineOwner
---------
BugCheck A, {0, 2, 0, fffff80002e8c1b1}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+171 )

Followup: MachineOwner
---------

Let us know if you need help

Tuan

Ok well I have Bsecure antivirus software (I think I'm running the old version...so that may be part of the problem)
But I also have a Netgear Wireless USB Adaptar which is what the driver upgrade was referring to, I was waiting for the next BSOD and just got it...I did install the driver, though I may have chosen the wrong setting to stick with when it asked me (because I didn't quite know what it was asking--though it might not mean anything anyway)

After I post this I'm going to take a break from the internet and pull out the piece of hardware and see if I get a BSOD with it out...cause that may be the problem there...


Oh and I'm now getting the Driver_IRQL_Not_Less_Or_Equal BSOD

Unfortunately just leaving the Netgear hardware disconnected didn't work as it happened again...so may I ask what steps would be suggested for solving this problem?

I would suggest you to uninstall the wrong driver and reinstall the right one. Then uninstall the antivirus you are using and replace it by MSE: http://www.microsoft.com/security_essentials
Update Conexant drivers as I mentioned, then if BSODs still occur, please turn on Driver Verifier, it will let us know what exactly is the problem

Regard,

Tuan

Alright, I'll do that, and thanks for all the help, it's been great to see progress made!

So I went 3 days w/o any BSOD but I also hadn't done any of what you had suggested..because it was working fine so why bother, today I went to watch some online video and I got one, so I then followed those steps, and once again got a BSOD though all it said was something about running a CHKDSK /F and it mentioned that a driver should be checked if listed, but none was, so then on reboot I also got a BSOD which was a stop error with little to no information....oh and I forgot to mention that the second BSOD that happened today was also while watching a online video (though I don't know if that matters...I hadn't watched any online video all weekend so that'd be my presumption)
idk what I should do, it seems like maybe the Netgear device is causing the problem...so the constant download of video may have caused it to flip....uhh well have you any suggestions? I'm going to reinstall my protection service as I trust it...

Thought I'd add this cause I know it helps, but I read through and I noticed that it said driver wg111v2.sys and that is the name of the Netgear device / version number....

Well, so basically you need to update that driver. In looking through your driver, I can see that wg111v2.sys date from 2007. Window 7 doesn't like out of date driver, and based on what you have described so far, it is probably the cause.
Please update the driver rightaway, it is NETGEAR WG111v2 54Mbps Wireless USB 2.0 Adapter NT Driver

I still see the Conexant driver still date from 2008, update them please

And this as well, they also product from NetGear
scmndisp scmndisp.sys Wed Jan 17 14:48:03 2007 (45ADD4B3) NetGear, Neutral wireless solution

Please don't turn on Driver Verifier yet. If you already did turn it on, turn it off and update the drivers. You need to update the netgear driver rightnow, it is the cause.

Who knows about window better than Microsoft? That's why I suggested you to use MSE for testing purpose. If that is not the cause, you can reinstall anytime you want

Your choice, I'm always happy to help u, but u need to follow my advise

Regard,

Tuan

Alright, and thanks for all your help, that appears to be the cause, and Microsoft MSE probably is really good but there are some extra benefits..or so I'm told, though I thank you for bringing MSE to my attention as I have never heard of it prior.

I don't think there is a new Netgear driver yet, as I went to their website and downloaded their latest one and that's what I've been running (most of the time, I did try and earlier version to see if it worked..but it didn't) so I'm just going to write them a message or something, but thanks again for all your help!