Various crash, BSOD scenarios

[benjis78]

(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

 

[Capt.Jack Sparrow]

(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

sisraid4.sys Thu Oct 02 03:26:04 2008
SiSRaid2.sys Wed Sep 24 23:58:20 2008
nfrd960.sys  Wed Jun 07 02:41:48 2006
lsi_fc.sys   Wed Dec 10 04:16:09 2008
iirsp.sys    Wed Dec 14 03:17:54 2005
arc.sys      Fri May 25 02:57:55 2007
adpu320.sys  Wed Feb 28 05:34:15 2007
adpahci.sys  Tue May 01 23:00:09 2007 
adp94xx.sys  Sat Dec 06 05:24:42 2008
000.fcl      Fri Sep 26 18:41:22 2008

Bugcheck:

[FONT=Book Antiqua][COLOR=Navy]Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul  8 17:00:40.655 2010 (GMT+6)
System Uptime: 0 days 0:02:58.888
PROCESS_NAME:  System
BUGCHECK_STR:  0xc4_91
OVERLAPPED_MODULE: Address regions for 'vmnetbridge' and 'Rt64win7.sys' overlap[/COLOR][/FONT]

Hope this helps,
Captain

 

[benjis78]

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

 

[Capt.Jack Sparrow]

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

 

[TimStitt]

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

 

[benjis78]

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

 

[Capt.Jack Sparrow]

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

[FONT=Book Antiqua][COLOR=Navy]Start | CMD | Right Click and Run as administrator | driverquery > c:\Driverlsit.txt[/COLOR][/FONT]

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

 

[TimStitt]

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.

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

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'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).

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

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.

 

[TimStitt]

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

[FONT=Book Antiqua][COLOR=Navy]Start | CMD | Right Click and Run as administrator | driverquery > c:\Driverlsit.txt[/COLOR][/FONT]

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

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

 

[benjis78]

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

 

[benjis78]

I have tried to find new driver versions for the ones listed by Cap, but I cannot. I called IBM about "nfrd960.sys", was placed on hold twice for 15 minutes and then transferred to an phone extension of Software Engineering that had been disconnected. What am I supposed to do?

 

[Capt.Jack Sparrow]

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

Hello,

Timo might be Offline i guess I'll answer this question as best as i can. As I mentioned before the Create Date and Modified date is just the Date when the driver went into your System. The Driver Date when it was manufactured is what i mentioned as 2005. If you look under copy rite you might see it says 2002-2005.

Regarding the Drivers you might wanna check these websites IBM Support - IBM ServeRAID software matrix but i'm not 100% if that's the correct one.

Hope this helps,
Captain

 

[TimStitt]

Hi Ben,

Sorry for the delay, I've tried twice to get back to you but been pulled away on both attempts today.

After looking through the dumps I have to agree that the vmnetbridge and vmnetadapter modules are blocking an input output request packet (IRP). Further investiagation has led me to beleive that this is because the windows Kernal has enabled what it calls "substantial checking" of vmnetadapter.sys. It's actually the Windows Kernel that blocks the driver and causes the crash becuase it suspects that vmnetadapter.sys will corrupt the system by sharing address regions with Rt64win7.sys. The Kernal (and maybe the Captain ) believe that this is the fault of vmnetadapter.sys (not Rt64win7.sys.) and I've been unable to prove it wrong so far.... and so far I agree.

Some useful Info
You mentioned that you can force the blue screen by enabling wireless networking, is this all the time 100% guaranteed? If so a workaround while we are troubleshooting this might be to disable the VMware network connections
unless they are needed (like when you use VMware), when it's time to use vmware disable the wireless adapter and enable the vmware.... this might get you through in a pinch while we work on the problem.

So how do we fix this?
We really need to check your drivers, update windows, and check the windows system integrity. so....

1. Run wMicrosoft update and install any new patches including those for hardware.
2. Check that all Windows system files are safe and sound by running an SFC /SCANNOW
3. Replace all copies of vmnetadapter.sys. I have attached the version 6 one that I have (as a roll back may fix your issue). Also try to replace it with the latest in case your installed one is corrupt. I am trying to download the latest version of vmware now and will post the driver up for you after I install it, that's if you're unable to get it yourself from the installation media. Remember that the driver may reside in more than one place so do a thorough search (it's likely to be in %PROGRAMFILES%\Vmware, ]%windir%\Programfiles (x86)\vmware, %windir%\system32\driverstore\filerepository; but do a generic search and then check that all found drivers are the same version (let me know if not).
4. If you can recreate it (i.e. force the blue screen), please disable your firewall and antivirus and then try to cause the blue screen. This was fairly common with the vmnetwork adapter a couple of years ago with some firewall products. If you get no blue screen with the firewall disabled then we'll take this retro issue further.
5. Check the version of the driver in the SIGVERIF.txt file found in the %HOMEDRIVE%\users\public folder and compare this against the version/s of the driver that you have. Please post your results. This file contains the verified driver as of windows' last check.
6. Grab the latest Realtek driver for your wireless card. Get this from the Realtek website and not MS update. BTW - The official Microsoft learning response on this point is to install the original drivers from the hardware disk, so try this too.

If this fails
I suggest updating all hardware drivers from the manufacturers website/s and that you consider removing vmware, stripping away all remnants of it (except the virtual machines) from the registry, user profile, drivers etc, reinstall it and reattach your virtual machines.

-Timo
I'll be back to you as soon as I can with the results of my vmware update and new drivers.

PS: I have two copies of the vmnetadapter.sys they are both from version 6 and are attached. If you find different versions, check the digital security tab (right click properties) to verify that they are legit and say VMware,Inc as the Name of Signer. Make a copy of them both and swap them in in out of your repositories. Trying one version installed and a blue screen attempt and then the next. You can have more than one version if a programmer leaves an older one in the package or if windows already had it.

 

[benjis78]

Hi Timo,
I am not sure if wireless networking wil cause blue screen 100% of the time. I have observed it occurs much less frequently when I used the wired LAN.
Concerning you troubleshooting steps:
(1) I have run MS update several times in the last two days. I don't know if it was set to check for hardware. I will check the settings.
(2) I ran SFC /SCANNOW last night and it reported no problems.
(3) I will try
(4) I will try
(5) I will try
(6) Last night I tried unsuccessfully to update the Realtek driver. I downloaded an executable from Realtek (FE/GbE Family Controller, NDIS 6.20 Miniport driver Windows 7(64-bit)) which was supposed to be able to update it. The program locked up during installation of the updated driver. I tried to update twice. I then deleted the device from device manager, scanned for hardware changes and attempted to manually install the rt64win7.sys driver from the appropriate realtek folder. This failed as well. Windows would only install the version coming from HP.

I spent several hours looking for the drivers Cap listed. I even called IBM about a driver of theirs and was disconnected after waiting 30 minutes. Can you offer any suggestions on searching for drivers?

Thanks,
Ben

 

[TimStitt]

Good Morning Ben (it is for me anyway),

In regards to Drivers:
What network adapter is your wireless? There are two for your machine on the HP website. In looking into the PC specs that you added I can't see I wireless Realtek driver, only a LAN driver. So I think that the Lan driver and the VMware driver are the two that are butting heads.

Grab your HP drivers from here; but just double check first to ensure that the model at the top of the screen matches yours (I'm cabable of major typo's ).

In regards to your processor, there are no updated drivers unless you're using the integrated graphics accelerator. This is used for onboard graphics (controlled by your motherboard) and some chips don't even have it. If you navigate to the Intel download centre you can search yourself (I'm unable to post a more direct link).

Sometimes it's hard to find exact drivers because a company uses many components in their hardware. Installing the drivers above, should cover you for the majority of drivers that your system uses. With the exception for drivers for virtual devices (such as VMware) and drivers for attached devices such as your printer. But you can always look these up on the manufacturers website. The packages that you download and install should look after the drivers that Capt jack mentioned. I think that this way is easier than trying to find individual drivers and has the added benefit of updating all drivers on your system.

In regards to the promised vmware driver - I've just installed vmware but need a new license key for this version... watch this space.

One more tidbit of curiosity - Does the blue screen occur when coming out of hibernation or sleep? or can it happen while you are happily using the pc?

 

[benjis78]

Good morning Timo, what country are you in?

I tested the effect of wireless networking on BSOD. BSOD occurs within 15 minutes both when ZoneAlarm Antivirus/Firewall is enabled and disabled.
I was able to manually install the Realtek FE family controller driver Rt64win7.sys. I let the manual install hang for almost 20 minutes and then powered off the computer. When I booted back up, the warning message concerning the Realtek controller was not in the event viewer.
I have not yet tried your vmware adapters yet. I will answer your questions from your last post after I eat supper. My wife says the food is getting cold.

 

[TimStitt]

Good morning Timo, what country are you in?

I tested the effect of wireless networking on BSOD. BSOD occurs within 15 minutes both when ZoneAlarm Antivirus/Firewall is enabled and disabled.
I was able to manually install the Realtek FE family controller driver Rt64win7.sys. I let the manual install hang for almost 20 minutes and then powered off the computer. When I booted back up, the warning message concerning the Realtek controller was not in the event viewer.
I have not yet tried your vmware adapters yet. I will answer your questions from your last post after I eat supper. My wife says the food is getting cold.

At the moment Singapore, I'm in the process of migrating from Australia.

I just had a similar call about breakfast from my wife

Good news on the realtek driver and attached is the latest vmnetAdapter.sys file from the latest vmware workstation version. I never usually say this, but fingers crossed that mine crashes too, then I troubleshoot locally.

 

[benjis78]

Hi Timo,
My wife said "we wives know what we are talking about!" There is a very good Genome Research Institute in Singapore. I have read lots of their papers.

My wireless adapter is Intel Centrino Advanced-N 6200 AGN. There are lots of options in the device properties but I have never adjusted them. I don't know much about wireless. This is my first computer with it.

The blue screen happens when I am using the computer. I have never hibernated the computer. I have put it to sleep and had the computer restart itself, but I don't remember if I saw a blue screen.

 

[benjis78]

Timo,
I don't have a file called "SIGVERIF.txt" on my machine. I do have sigverif.exe located in windows\system32 and windows\winsxs.

Ben

 

[benjis78]

Timo,
I read how to use the app. Here are the sigverif entries:
vmnetadapter.sys 5/20/2010 2:5.1 Signed vmnetadapter.cat Microsoft Windows Hardware Compatibility Publisher
vmnetbridge.sys 5/20/2010 2:6.0,2:6.1 Signed oem31.CAT Microsoft Windows Hardware Compatibility Publisher

In driver properties, vmnetadapter.sys says version 4.0.3.0. The driver vmnetbridge.sys says the 4.0.3.0 as well.