Various crash, BSOD scenarios

[TimStitt]

Hi benjis78,

I've been through the event logs and there are a few patters emerging.

Before we go any further, please consider my request to re-install VMWARE, these events may or may not be related to your BSOD issue and we should at least attempt to reinstall VMware first before we go down the wrong road.

I know this is dragging on a bit, but if you could please test for BSOD between each change it will help us pinpoint the issue.

The Capt and I have both mentioned that your firewall/antivirus may be causing your problem and Capt has suggested that you uninstall it and we disabled this for testing purposes, yet found that the the issue still occurs. However, like the misleading information in the mini-dump that you first posted, it' s been niggling at me. Let's take the Capt's advice because regardless of the product being disabled, the drivers that it uses are likely to be still loaded in windows. Importantly, the new information in the event log entries support this scenario. Especially the fact that many of the BSOD's are commonly preceded by the loading of the the Zone alarm vsdatant.sys.

Here is the other event log follow-ups; but please note that they may not all be related:

Events 7218,7220,7225 - Unisntall the Intel Chipset Identification Utility as ChipUtil325.exe is crashing constantly (Events 7218,7220,7225)

Root list catalogue (Events 7701) It looks like your Certificate Revocation List (CRL) is not up to date. I posted something on this recently, I'll reference it and get back to you shortly.

Channel Error 36888 refers to Secure Channel (sChannel), this uses Transport layer Secrity (TLS) and SSL (Secure Sockets Layer) for security encryption, although it uses TLS by default. You may see advice to uncheck the use of TLS in your browser (ie - internet options, advanced tab) to remove this error but I don't think it will fix your issue (just hide it from you). This error can be caused by:
- An certificate catalogue that's not up to date (which you have)
- Power management issues (which I will revisit below)
- Port permission on your firewall (which we are going to uninstall anyway)

Event 10016 errors this occurs when permission for the COM Server application for a particular application is not allowed. We can set the permissions to allowed by using dcomcnfg.exe but first I need to know what they are.
- Open REGEDIT and click on computer
- Navigate to HKEY_CLASSES_ROOT\CLSID\CLSID
View attachment 84920
- Press F3 (for FIND)
- Paste in the first of the below APPID's and search for it
- When you find it, in the right hand column you should have another registry entry could AppID, double click on this then copy and paste the value data here.
View attachment 84919
- Repeat for the next APPID
- If there is no AppID in the right column, please right click on the EVENT APPID that you found in the CLSID key and export a copy, then attach it to your thread.
View attachment 84921
(Note the Key's I used in the examples are not your EVENT APPID key (I don't have those two on my system)

(Event 26964)
EVENT APPID
{145B4335-FE2A-4927-A040-7C35AD3180EF}
EVENT APPID
{D3DCB472-7261-43CE-924B-0704BD730D5F}

Power Management
Previously we talked about sleep mode and I want to ensure that your wireless adapter is not affected. I know that we ruled out that your PC is not going into sleep mode or coming out of it to cause the issue, but what if it's just checking for it and crashing? There is one event entry that may support this scenario so let's rule this out (and I forgot to note which event number sorry ).
- Open device manager Type devmgmt.msc into RUN or SEARCH and press ENTER.
- Navigate to your wireless network device
- Right click and select properties
- On the Power management tab, UNTICK "Allow the computer to turn this device off"
- Ok exit
- repeat this for all network adapters (where the Power Management option exists)
- Open control panel and click on power options
- Select Change plan settings (in your current plan)
- select "put the computer to sleep 'NEVER' from the dropdown"
- Save Changes

 

[TimStitt]

The CRL I said I'd get back you and it was on the previous page (I thought it was another post).

In regards to the Failed extract of third-party root list, at a quick guess your Certificate Revocation List (CRL) has an expired certificate or the database is out of date. Here's the official Microsoft Fix for those two scenarios'. The CRL may have become corrupt during a BSOD.

 

[Capt.Jack Sparrow]

It would be great if we have some more information about your System. Follow these instructions ans post us the Logs. http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[benjis78]

Hey Timo,
My power management has been set to high performance for the longest time (was taking laptop to work). In this setting, I already had the computer set to never sleep.
I have done my best to follow your instructions to collect info from the registry, but I am slightly inebriated and very sleep deprived. I did not see AppIDs in either right column, so I have exported the copies of event appIDs.

Captain Sparrow, I have posted the system info using one application you created. I will read your current link's instructions tomorrow.

Thanks,
benjis78

 

[jcgriff2]

Hi -

I would suggest that you remove Zone Alarm completely. Even though you have disabled Z/A, boot and kernel mode drivers continue to run and may be interfering.

If these BSODs are software related, Driver Verifier should be of assistance here. If D/V flags a driver it will BSOD your system and hopefully name a 3rd party driver.

Driver Verifier - jcgriff2.com

Also, additional system information would be helpful --> http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Regards. . .

jcgriff2

.

 

[TimStitt]

Hi Ben, Drink up! (d)

There's only 7 things left on my list. In case we still can't resolve it after you tick these off, Capt. Jack and I have been discussing some other experts that we'll bring in and maybe we can come up with something else by bouncing ideas around.

1. Power settings - turn this off on the network adapters properties via device manager.
2. Zone alarm - please re-read my reasoning above and uninstall it and try to recreate a BSOD
3. Vmware - Please reinstall it
4. Intel Chipset Identification Utility- There's no need to keep this installed, remove it.
5. vmware drivers[/B/ - replace with the old drivers that I posted

Also these two for good measure...

6. Event 10016 errors, they're unlikely to be related, but here's how to fix them. I've verified that this guide also works in Windows 7.
7. 3rd part root list - Also less likely to be related. Click here to see the fix.

 

[TimStitt]

Hi -

I would suggest that you remove Zone Alarm completely. Even though you have disabled Z/A, boot and kernel mode drivers continue to run and may be interfering.

If these BSODs are software related, Driver Verifier should be of assistance here. If D/V flags a driver it will BSOD your system and hopefully name a 3rd party driver.

Driver Verifier - jcgriff2.com

Also, additional system information would be helpful --> http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Regards. . .

jcgriff2

.

Jcgriff2, I was just going to send you a message for some advice on this one. You read minds too I see? ... and Thanks.

 

[benjis78]

Hi Timo,
So yesterday I rolled back my wireless driver by two versions using the Intel and not HP version. I could not find the HP version at HP. Once again, the install hung and I had to reboot. But driver installed.
The computer did not crash on wireless networking with or without ZoneAlarm enabled. I then enabled the vmnetadapters, and there was no crash on wireless networking. The computer did fail to shut down about ~ 50% of the time.

This morning I began running Verifier as Jcgriff2 suggested. The computer crashes anytime I click on internet explorer, either with wireless networking enabled or disabled. It crashed one time while I was looking at the Verifier GUI. I have seen no faults listed in it yet.

I am currently running the program from the BSOD posting suggestions and will post it when it is finished.

Where is the intel chipset identification utility installed? I don't see it in my add/remove programs list. There is something there about intel management console, I think.

I will uninstall, reinstall VMware when I come home from work. Should I worry about residual registry keys from my original 7.0 and 7.1 installs?

Relunctantly, I will uninstall Zone Alarm. I am relunctant because I used this program for five years on XP SP2 and SP3 with virually no issues ever. I will then enable windows firewall. How do I protect my computer without an antivirus program? This makes me nervous. I repeat, this makes me nervous.

I have a very elementary understanding of firewalls and viruses, but I have managed to kill every virus or piece of malware I have gotten without having to wipe my drives.

benjis78

 

[benjis78]

The BSOD analysis application hung on "the task collecting step?" for over twenty minutes. I need to go to work so I closed the program, ran perfmon. I tried to upload the zip file but it failed to upload. I will try to upload it again from work.

 

[benjis78]

Hi Timo,
I am having trouble uploading the zip file

 

[benjis78]

Hey Guys,
I had to attach the BSOD analysis and perfmon archive as an .rar file. For some reason, I wasn't able to upload it as zip even though it was well below the size restriction.

benjis78

 

[TimStitt]

Hi Timo,
So yesterday I rolled back my wireless driver by two versions using the Intel and not HP version. I could not find the HP version at HP. Once again, the install hung and I had to reboot. But driver installed.
The computer did not crash on wireless networking with or without ZoneAlarm enabled. I then enabled the vmnetadapters, and there was no crash on wireless networking. The computer did fail to shut down about ~ 50% of the time.

This morning I began running Verifier as Jcgriff2 suggested. The computer crashes anytime I click on internet explorer, either with wireless networking enabled or disabled. It crashed one time while I was looking at the Verifier GUI. I have seen no faults listed in it yet.

I am currently running the program from the BSOD posting suggestions and will post it when it is finished.

Where is the intel chipset identification utility installed? I don't see it in my add/remove programs list. There is something there about intel management console, I think.

I will uninstall, reinstall VMware when I come home from work. Should I worry about residual registry keys from my original 7.0 and 7.1 installs?

Relunctantly, I will uninstall Zone Alarm. I am relunctant because I used this program for five years on XP SP2 and SP3 with virually no issues ever. I will then enable windows firewall. How do I protect my computer without an antivirus program? This makes me nervous. I repeat, this makes me nervous.

I have a very elementary understanding of firewalls and viruses, but I have managed to kill every virus or piece of malware I have gotten without having to wipe my drives.

benjis78

Hi Ben,

The nervous part - we all get it too, we're all just as nervous about removing antivirus. Just remove it and test vigorously. Many of the Guru's here use Microsoft Security Essentials (it's free).

Intel management console, that sounds promising - remove that and see if the error dissimilars from your event log. It won't remove any drivers just the console itself.

When you say the PC crashes when you click on internet explorer, where talking more BSOD's yeah? This may be a side effect of the older drivers, we might have fixed one isssue only to get another.

These hanging installs really concern me. Is there any thing in the event log about them?

The problems seem to be getting worse, installs are freezing, it won't shut down, BSOD's - I'm wondering also how far back your system restores go? A system wide rollback wouldn't lose any documents and might fix your issue. Or a Repair Install. Let's wait on these until we hear back from jcgriff2, he's a regular BSOD guru and I'm hoping that he finds something that our seaworthy Capitan and/or I have missed.

About the registry keys - yes we probably should strip them out. There was a VMWare registry cleaner but they haven't updated it (as far as I know) for version 7 of VMWare yet. So the safest way I can think of is to use the windows installer cleanup utility from Microsoft and then remove the vmware folders manually. Just make sure that you have a copy of your registration keys and remember not to delete your virtual machines. So ensue that they are not inside one of these folders first.
* %userprofile%\appdata\local\VMware
* %CommonProgramFiles(x86)%\VMware (note: 64bit only)
* %ProgramFiles%\VMware (note: 32bit only)

 

[benjis78]

Timo,
With the verify application running according to Jcgriff2's instruction, clicking on internet explorer led to an almost instantaneous BSOD. Let me say again, before configuring verify today, I had no BSOD on wireless networking last night after I rolled back the drivers.

The hanging installs only occur when I am installing a non-HP driver. I have had no problems installing drivers from the HP web site. I will examine the event viewer later tonight. I don't understand much of what I see in the event viewer, so can you offer any suggestions to identify the useful information? I think I do understand that one event can reference other events.

benjis78

 

[Capt.Jack Sparrow]

I was checking the Log Files. There are few things that needs to be done.

According the MSINFO32 File the problem device its mentioning is HP Integrated Module with Bluetooth 2.1 Wireless Technology i.e. USB\VID_03F0&PID_231D for this series i found the Driver in HP website for Windows 7 here is the Link download and apply it Software Support for HP Integrated Module with Bluetooth Wireless Technology for Microsoft Windows 7 HP Mini 110-1119NR PC - HP Customer Care (United States - English)

Regarding the Zone Alarm it's a totally different case with XP. The reason XP fine because users run at FULL admin all the time, where Vista and Windows 7 because of UAC it causes the problem. Zone Alarm is notorious one in this category because it tends to block the Network ports under svchost.exe so it's a Highly recommend to uninstall Zone Alarm and make sure you run the Removal Tool to clean the left over entries.

Regarding the Event Viewer Error:

Log Name: Application
  Source: Microsoft-Windows-CAPI2
  Date: 2010-07-12T19:40:12.401
  Event ID: 4107
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Rodriguez-PC
  Description: 
Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

According to one of the thread here manual install of the Cab file appears to be fix the issue http://www.sevenforums.com/crashes-debugging/96968-capi2-error.html i.e download http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab and install it manually. Rest of the Event Viewer error are most related to your Network card. I'm suspecting it might be the Hardware itself causing it but before coming into any conclusion we have to run few test.

Event[389]:
  Log Name: System
  Source: Service Control Manager
  Date: 2010-07-13T09:18:13.120
  Event ID: 7001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Rodriguez-PC
  Description: 
The Computer Browser service depends on the Server service which failed to start because of the following error: 
The dependency service or group failed to start.

Computer Browser service - Default Description

Maintains an updated list of computers on the network and supplies this list to computers designated as browsers. If this service is stopped, this list will not be updated or maintained. If this service is disabled, any services that explicitly depend on it will fail to start.

More: Computer Browser - Process and Service wiki

Hope this helps,
Captain

 

[usasma]

Driver Verifier is supposed to cause a BSOD - that's where (if successful) the name of the offending driver comes from.

Your Bluetooth module is disabled. Did you do this deliberately? If so, why?

9 memory dumps from 12 Jun to 08 Jul 2010 (~1 month)
3 different STOP errors, with 3 different causes blamed
The 08 Jul 2010 dump file is a Driver Verifier Enabled Minidump and blames ntkrnlmp.exe

The STOP 0x9F errors show IRP blocking as having occurred. Please follow these directions for running different settings in Driver Verifier:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

NETw5s64.sys is implicated once in the STOP 0x9F error in pci.sys
vmnetadapter.sys is implicated 6 times (symbol checking) - but not as directly as the NETw5s64.sys file is.

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: http://<a href="http://www.carrona.org/dvrref.html" target="_blank">Driver Reference</a>Driver Reference ).
Please pay particular attention to any dated 2008 or earlier:

fffff880`04597000 fffff880`045c2000   000      000.fcl      Fri Sep 26 09:11:22 2008 (48DCDF7A)
fffff880`01000000 fffff880`0107b000   adp94xx  adp94xx.sys  Fri Dec 05 18:54:42 2008 (4939BF42)
fffff880`01400000 fffff880`01456000   adpahci  adpahci.sys  Tue May 01 13:30:09 2007 (46377921)
fffff880`01200000 fffff880`0122f000   adpu320  adpu320.sys  Tue Feb 27 19:04:15 2007 (45E4C6FF)
fffff880`0124d000 fffff880`01266000   arc      arc.sys      Thu May 24 17:27:55 2007 (4656035B)
fffff880`016d8000 fffff880`016e9000   iirsp    iirsp.sys    Tue Dec 13 16:47:54 2005 (439F418A)
fffff880`016e9000 fffff880`01708000   lsi_fc   lsi_fc.sys   Tue Dec 09 17:46:09 2008 (493EF531)
fffff880`017ea000 fffff880`017fa000   nfrd960  nfrd960.sys  Tue Jun 06 17:11:48 2006 (4485EF94)
fffff880`01af8000 fffff880`01b06000   SiSRaid2 SiSRaid2.sys Wed Sep 24 14:28:20 2008 (48DA86C4)
fffff880`01b06000 fffff880`01b1e000   sisraid4 sisraid4.sys Wed Oct 01 17:56:04 2008 (48E3F1F4)

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul  8 07:30:40.655 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:58.888
BugCheck C4, {91, 2, fffff80003013c40, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4904 )
BUGCHECK_STR:  0xc4_91
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jul  4 11:50:36.389 2010 (UTC - 4:00)
System Uptime: 0 days 1:29:37.012
BugCheck 9F, {3, fffffa80054b1700, fffff80000b9c518, fffffa8005ba89d0}
*** WARNING: Unable to verify timestamp for vmnetadapter.sys
*** ERROR: Module load completed but symbols could not be loaded for vmnetadapter.sys
Probably caused by : ntkrnlmp
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul  3 11:52:20.475 2010 (UTC - 4:00)
System Uptime: 0 days 1:03:22.099
BugCheck 9F, {3, fffffa8005533e30, fffff80000b9c518, fffffa8009fd1160}
*** WARNING: Unable to verify timestamp for vmnetadapter.sys
*** ERROR: Module load completed but symbols could not be loaded for vmnetadapter.sys
Probably caused by : ntkrnlmp
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun 23 22:08:41.375 2010 (UTC - 4:00)
System Uptime: 0 days 1:09:53.608
BugCheck 9F, {3, fffffa80061bc060, fffff80000b9c518, fffffa80087bfc10}
Probably caused by : pci.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 22 13:15:59.216 2010 (UTC - 4:00)
System Uptime: 0 days 0:31:07.839
BugCheck 7F, {8, 80050033, 6f8, fffff80002ec7c91}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 12 21:45:47.957 2010 (UTC - 4:00)
System Uptime: 0 days 0:15:41.580
BugCheck 9F, {3, fffffa80054c1bb0, fffff80000b9c518, fffffa8005b7c680}
*** WARNING: Unable to verify timestamp for vmnetadapter.sys
*** ERROR: Module load completed but symbols could not be loaded for vmnetadapter.sys
Probably caused by : ntkrnlmp
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 12 21:29:10.341 2010 (UTC - 4:00)
System Uptime: 0 days 8:30:09.574
BugCheck 9F, {3, fffffa80054b2700, fffff80004d79518, fffffa80055a33b0}
*** WARNING: Unable to verify timestamp for vmnetadapter.sys
*** ERROR: Module load completed but symbols could not be loaded for vmnetadapter.sys
Probably caused by : ntkrnlmp
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jun 11 20:53:22.189 2010 (UTC - 4:00)
System Uptime: 0 days 5:57:39.813
BugCheck 9F, {3, fffffa80054c1060, fffff80000b9c518, fffffa800c021e10}
*** WARNING: Unable to verify timestamp for vmnetadapter.sys
*** ERROR: Module load completed but symbols could not be loaded for vmnetadapter.sys
Probably caused by : ntkrnlmp
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun  9 12:19:11.239 2010 (UTC - 4:00)
System Uptime: 0 days 1:23:38.862
BugCheck 9F, {3, fffffa80054cf4d0, fffff80004d79518, fffffa8005feae10}
*** WARNING: Unable to verify timestamp for vmnetadapter.sys
*** ERROR: Module load completed but symbols could not be loaded for vmnetadapter.sys
Probably caused by : ntkrnlmp
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/FONT]

 

[benjis78]

Hi Usasma,
I disabled the bluetooth module because I don't have any bluetooth devices that I want to communicate with my computer. Has my disabling it caused a problem?
The computer crashed several times while verifier was running. It hasn't created any minidumps. No new minidumps have appeared since July 8th.
I am very frustrated with my attempts to find drivers. If you read my earlier posts, I waited on the phone with IBM (to ask about their driver) for 30 minutes before being disconnected. I have also been to Silicon Integrated Solutions' site and downloaded a raid driver package but they were older than my current driver.
I appreciate you giving me these resources about drivers.

benjis78

 

[benjis78]

By the way, I have turned verifier off for now in order to do some of the other tasks, like uninstalling zone alarm.

 

[benjis78]

Captain,
I looked at computer browser service in services.msc. It is running and none of the programs it depends on are disabled.

 

[benjis78]

Dear all,
I have uninstalled Zone Alarm with the uninstaller utility from the manufacturer. I have deleted the Intel Chip identification utility (it did not have an installer) executable.

 

[benjis78]

Usasma,
I have gone through the list of drivers. In my device manager, they are all hidden and listed as non-plug and play drivers. According to Driver Reference, these are mostly hardware controllers(?) for SCSI and SATA devices / cards. I have visited the manufacturer's web sites. There are many devices to choose from and the majority are not for Windows 7, but Vista or Server 2008.

I have attached a list of the driver versions on my computer and notes I made about them. Can you check your device manager and see what versions you have?

benjis78