Windows 7: Various crash, BSOD scenarios

(1) Experiencing frequent BSOD when I use wireless networking
(2) Failing to shutdown ~40% of the time. Today, BSOD during shutdown
(3) Crashing occasionally when WLAN is turned off and using an ethernet connection.

I am getting several frequent error messages in my event viewer, two of which have been occurring since I booted the computer for the first time on March 26th.
(a) Realtek PCIe FE Family Controller is disconnected from network
(b) LMS service cannot connect to Intel(R) MEI driver I know (a) is my network card. To address (b), I have tried uninstalling and reinstalling the Intel chipset drivers.

I have performed windows and HP diagnostic tests: chkdsk /f /r, memory tests, sfc /scannow, drive self tests. No problems in device manager.

I have run the SF diag tool and attached the information in the zip file.

Thanks for your help. This forum is very informative.

Ben

Hello Ben !! Welcome to SF !!

I guess the crash has caused by vmnetadapter.sys i.e. VMware virtual network adapter driver (32-bit) i would remove it and see if that makes any difference. Because Address regions for 'vmnetbridge' and 'Rt64win7.sys' overlap.

Update the Following Drivers



Bugcheck:


Hope this helps,
Captain

Captain,
Thanks for looking at my data. I will try and update the listed drivers tomorrow. Are both vmnetadapter.sys and vmnetbridge.sys appearing in the bugcheck? I searched for them and learned they are virtual network drivers for a program called VMware workstation which I use to run XP and Linux virtual machines. This may be a naive question, but If I uninstall and reinstall the driver, will the address still overlap?

Ben

It might to be honest no sure about the step of VM and NIC cards let me see if i can find someone who know about it

Hi Benjis78,

It looks like memory space is allocated incorrectly. Capt is right is suggesting you look for updated drivers, as it's the drivers that allocate the memory. Check versions on both sides (Realtek and VMware). What version of VMware are you running? I can vouch for 6.5.4 Build-246459 being Win7 64bit stable.

This error can also occur due to memory and/or page file corruption. Take you RAM out, give it a good dusting, put it firmly back in. Also empty your pagefile at shutdown (also called clearing your virtual memory).

To do this type secpol.msc into RUN or SEARCH and press ENTER. When the Security Policy opens, navigate to Local Policies, Security Options, and look for the entry "Shutdown: Clear Virtual Memory Pagefile", Enable this and reboot. After you reboot you disable the pagefile clearing at shutdown. Your pagefile is like extra RAM (but it uses your Hard Disk Drive) The reason that we clear the pagefile is to ensure that no incorrect or corrupt data stored in it causing the issue.

-Timo

Hi Timo,
I am running VMware Workstation Version 7.1 Build 261024 released on May 25th. This version supports Ubuntu 10.04 which I am using to learn computational biology applications. It is "supposed" to be stable for Win 7 64-bit.

I have a question about the drivers which Captain listed yesterday. How was the list generated? I have checked two of the drivers in my system folder (iirsp.sys, sis4raid.sys) and the dates in Captain's list don't match those on my machine. My machine shows more recent dates for both.

I should be able to follow your instructions to empty my pagefile. But as for the RAM, my machine is nearly brand new, a 3 month old laptop. I have opened many desktops, but never a laptop. If dust were a problem, wouldn't the memory tests have failed?

Thanks for your help.

Ben

Ben,

You are probably looks the create and modified date that might be different with the actual Driver date. To find the list of Driver and the actual date

Once it's done go to C Drive there you'll find the List in Driverlist.txt file.

Sounds fun, i'll load up this version tomorrow and run some tests for you on my 64bit box (it's midnight here).

I'll take another look a the dump to verify the driver details, in the meantime would you please post up screen prints of your versions/dates that I can compare against.

I believe that the list is from the dump you posted, i'll take another look and i'll provide more information then (Capt Jack may answer before I get that far through, he's usually pretty quick).

Unlikely to be dust then (as it's so new), but it doesn't rule out faulty RAM. MEMTEST is a nice guide and often picks this up; but it doesn't always. Let's keep this in the back of our minds and we can revisit it if nothing else proves useful.

FYI - (Save this for later, I just wanted to answer your question). Laptop RAM is usually accessed in one of three ways.
1. A nice little cover unscrews in the bottom, especially designed to make changing the RAM easy.
2. You lift the keyboard up and the RAM is under it
3. An idiot designer forces you to pull apart the bottom of your laptop to access the RAM or the second piece of RAM (thankfully a lot less likely in 2010).

The Ram is usually held in by two clips either side, push them like a clothes peg and take out your RAM. You'rs may be different though as your laptop is new.

@Ben - I told you he was fast. :-)
@Capt - Good Advice Capt. +1

Timo,
Here are the properties screens of the two drivers I mentioned.