BSOD netw5s64

Hello Korea, Welcome to sevenforums!!

Your BAD_POOL_CALLER is typically a bad driver, but can be a memory issue, but we will save memtest86+ for after the drivers.

While im going through your current drivers that may need updating go ahead and go to the intel website and update your Intel Wireless Wifi Adapter. (netw5s64.sys) (Support for the Intel® Wireless WiFi Link 4965AGN)

I will update this post with drivers that need to be updated.

UPDATE:
mcdbus.sys Tue Feb 24 04:34:07 2009 Update or Remove MagicISO (MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor)

GEARAspiWDM.sys Mon May 18 07:17:04 2009 Check for Update (CD-ROM Filter Drive) (GEAR Software - DVD Mastering Software & CD Burning Software & GEAR PRO Mastering)

Also Recommend Updating Your Avira Anti-Virus/Security. As those drivers are a little old but not out of the range of up to date drivers. (Knowledgebase for Home)

Also Go to Toshiba Support Website, as most of your Toshiba drivers tend to be close to What i call obsolete drivers. (Pushing the Date of 2009) (http://www.csd.toshiba.com/cgi-bin/t...p?nav=download)

- Tony

koreaboi22 said:

Thank you foryour response
I uninstalled MagicIso a while back and I don't understand why this is coming up for no apparent reason.
I went that website and I updated my CD-ROM drive,
I switched from the trial version of Avira premium to the free version of Avira so that I can update easily.
I went to the Toshiba support website and I downloaded all of the missed drivers. However, I am confused on one part: my wireless adapter, Intel Centrino n 6200 says that the driver is uptodate and it was uploaded on 1/2010. But the most updated on Toshiba driver was 11/04/2010. It still stated that my driver is 1/2010. I hope this clarified a bit. Also, I would also add that when I tried to go to hibernation mode, my laptop would turn to sleep mode. Please help! thank you.

Go to your system32 directory (C:\Windows\System32) and Rename mcdbus.sys from .sys to .bak This will break it from starting up, obviously the magic ISO driver is still in your system32 folder, if you no longer see it then disregard.

As for your wireless adapter, as long as the support website states that it is up to date then thats good. Just wanted to make sure it was up to date because it was referenced in your dump file.

As for Hibernation and sleep modes.

Got to start type in Power Options click Power Options or hit (enter) Click choose when to turn off the display then click Change advanced power options.

In the dialog box scroll down and Expand Sleep your sleep and hibernation options are there. choose when to sleep and when to hibernate.


Post the results of your updated drivers if you get any BSOD.

- Tony

Note that I have also been getting regular BSODs on my HP laptop since the last round of Windows Updates in this same driver. I don't know (yet) which update may be triggering it, but going back to the last driver release from 2009 and it's been stable. Going back to the 2010 release (March, I think) and the instability returns every time the system goes to sleep.

cluberti said:

Note that I have also been getting regular BSODs on my HP laptop since the last round of Windows Updates in this same driver. I don't know (yet) which update may be triggering it, but going back to the last driver release from 2009 and it's been stable. Going back to the 2010 release (March, I think) and the instability returns every time the system goes to sleep.

That's Exactly Why i don't allow windows update to automatically install any critical/important updates. I check stability before i allow Windows Update to update any files.

Some will be totally against that. But this is just proof Windows Update can very well mess things up :)

- Tony

koreaboi22 said:

Hello
I tried to search for the mcdbus but I canno locate it. does this mean it's not an issue anymore?

Yes you should be clear. Let us know if you have any other issues or any new BSOD

- Tony

TonyTiger2004 said:

That's Exactly Why i don't allow windows update to automatically install any critical/important updates. I check stability before i allow Windows Update to update any files.

Some will be totally against that. But this is just proof Windows Update can very well mess things up :)

- Tony

Windows update didn't update the driver, I did. I also have confirmation from Intel that there is a small problem with the driver from March on specific hardware (including my HP laptop), and after upgrading it to a version from April 2010 last night everything is fine.

cluberti said:

TonyTiger2004 said:

That's Exactly Why i don't allow windows update to automatically install any critical/important updates. I check stability before i allow Windows Update to update any files.

Some will be totally against that. But this is just proof Windows Update can very well mess things up :)

- Tony

Windows update didn't update the driver, I did. I also have confirmation from Intel that there is a small problem with the driver from March on specific hardware (including my HP laptop), and after upgrading it to a version from April 2010 last night everything is fine.

At least you got that figured out, Thanks for sharing :)

- Tony