Various BSOD crashes and system instability - Windows 7 Pro

[pwalsh56]

Hello all,

I am having BSOD problems, and have been for a few months now. For the most part, they are random and fairly sporadic, yet today I had two within five minutes.

My system is a HP s3531.uk and runs Windows 7 Professional. The BSOD's themselves vary each and every time. There are 5 crash dumps in my minidump folder, although at my last count I've had more than five BSOD's, as the system has froze several times on the BS, so I had to shut it down manually and obviously the crash dump didn't complete.

I've already checked RAM and my HD for errors, to rule them out. I'm aware though that that doesn't mean they aren't to blame. Also, I've not installed any new software/hardware since the BS's started, of for some time before the first, so I'm pretty sure it isn't that.

Lastly, for a while before the first, and ever since, the whole system seems to be getting more and more sluggish, slow, unresponsive, and generally a pain to use. It also seems to freeze fairly often, without a BS appearing.

While running Windows (and MSE in background) only, it appears to be using around 1.1Gb of RAM. Don't know if that's normal Windows behaviour, or that it might be indicative of some problem.

Due to the general instability of the system, I'm fearful I might have come across some form of Virus or Malware that MSE can't track, though I sure hope not.

Lastly (apologies for the huge post) I've attached all of the crash dumps from the system, and hope that someone smarter than I can make head or tail of the problem.

Cheers in advance!

 

[usasma]

Primarily STOP 0xA errors blaming the kernel of the operating system (not likely IMO).

Many older drivers on the system, please visit the manufacturer's support website and update ALL 0f your drivers (don't use Windows Update or the Update drivers function of Device Manager). Here's a list of the drivers that were found in the memory dumps:

[FONT=lucida console]

nvstor32.sys Mon Jun 22 18:19:03 2009 (4A400357)
nvstor.sys   Wed May 20 02:44:09 2009 (4A13A6B9)
amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
vmnetbridge.sys Mon Aug 10 08:05:29 2009 (4A800D09)
snp2uvc.sys  Mon Jun 22 21:37:07 2009 (4A4031C3)
STREAM.SYS   Mon Jul 13 19:50:57 2009 (4A5BC861)
sncduvc.SYS  Mon Dec 29 04:13:29 2008 (495894B9)
VMkbd.sys    Thu Oct 22 06:50:57 2009 (4AE03911)
SCDEmu.SYS   Sun Jul 26 22:43:19 2009 (4A6D1447)
MpFilter.sys Tue Sep 14 17:23:59 2010 (4C8FE7EF)
ws2ifsl.sys  Mon Jul 13 19:55:01 2009 (4A5BC955)
nvmf6232.sys Thu Jul 30 19:47:55 2009 (4A72312B)
GEARAspiWDM.sys Mon May 18 08:16:53 2009 (4A1151B5)
atikmpag.sys Wed Mar 10 17:33:47 2010 (4B981E4B)
VMNET.SYS    Mon Aug 10 08:03:57 2009 (4A800CAD)
atipmdag.sys Wed Mar 10 18:12:09 2010 (4B982749)
vmnetadapter.sys Mon Aug 10 08:04:00 2009 (4A800CB0)
hcmon.sys    Thu Oct 22 06:00:39 2009 (4AE02D47)
netr73.sys   Wed May 20 04:47:39 2009 (4A13C3AB)
vmci.sys     Thu Oct 22 05:25:26 2009 (4AE02506)
vwifimp.sys  Mon Jul 13 19:52:09 2009 (4A5BC8A9)
RTKVHDA.sys  Tue Aug 04 05:48:13 2009 (4A7803DD)
dump_nvstor32.sys Mon Jun 22 18:19:03 2009 (4A400357)
vmx86.sys    Thu Oct 22 07:36:25 2009 (4AE043B9)
vmnetuserif.sys Thu Oct 22 06:16:06 2009 (4AE030E6)
vstor2-ws60.sys Mon Oct 12 17:06:25 2009 (4AD39A51)
MpNWMon.sys  Tue Sep 14 17:23:50 2010 (4C8FE7E6)
NisDrvWFP.sys Tue Sep 14 17:24:12 2010 (4C8FE7FC)
FsUsbExDisk.SYS Thu Sep 11 02:42:10 2008 (48C8BDC2)
MpFilter.sys Fri Nov 20 19:22:10 2009 (4B0732B2)
atikmdag.sys Wed Sep 09 00:21:01 2009 (4AA72D2D)
MpNWMon.sys  Fri Nov 20 19:22:01 2009 (4B0732A9)
MpKsl8a419406.sys Tue Mar 30 22:06:14 2010 (4BB2AE16)
MpKsl01ad55f7.sys Tue Mar 30 22:06:14 2010 (4BB2AE16)
MpKsl29289454.sys Tue Mar 30 22:06:14 2010 (4BB2AE16)
MpKsl3351c49a.sys Tue Mar 30 22:06:14 2010 (4BB2AE16)

[/FONT]

If that doesn't stop the BSOD's, then try running Driver Verifier according to these directions:

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

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Sun Feb  6 08:15:50.652 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:18.603
Probably caused by : ntkrpamp.exe ( nt!EtwpFindGuidEntryByGuid+4d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x8E
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  0x8E_nt!EtwpFindGuidEntryByGuid+4d
Bugcheck code 1000008E
Arguments c0000005 82ed56da 9d18fbb4 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Sun Feb  6 08:11:38.048 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:34.999
BUGCHECK_STR:  0x1a_41289
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iTunes.exe
FAILURE_BUCKET_ID:  0x1a_41289_nt!MiLocateWsle+c1
Bugcheck code 0000001A
Arguments 00041289 6a3ee001 0000293d 06a8e009
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Fri Jan 28 07:19:06.663 2011 (UTC - 5:00)
System Uptime: 0 days 0:06:47.614
Probably caused by : ntkrpamp.exe ( nt!ExpScanGeneralLookasideList+22 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  SYSTEM
FAILURE_BUCKET_ID:  0xA_nt!ExpScanGeneralLookasideList+22
Bugcheck code 0000000A
Arguments ffffffe0 00000002 00000000 82cdc1dc
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Sat Jan 15 09:03:45.451 2011 (UTC - 5:00)
System Uptime: 0 days 0:11:10.262
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000
Probably caused by : ntkrpamp.exe ( nt!KiSystemFatalException+f )
BUGCHECK_STR:  0x7f_d
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  0x7f_d_nt!KiSystemFatalException+f
Bugcheck code 0000007F
Arguments 0000000d 00000000 00000000 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Wed May  5 09:36:03.910 2010 (UTC - 5:00)
System Uptime: 0 days 0:09:47.861
Probably caused by : ntkrpamp.exe ( nt!KiTryUnwaitThread+46 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  iTunes.exe
FAILURE_BUCKET_ID:  0xA_nt!KiTryUnwaitThread+46
Bugcheck code 0000000A
Arguments 00000034 00000002 00000001 82a74028
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]

 

[pwalsh56]

Thank you for the quick response usasma! I'll get right onto updating all drivers, and get back to you once done. Quick question though; when you say the manufacturer's website, are you referring to the manufacturer of the system, HP? Or each individual manufacturer of every part of the system?

Thanks!

 

[usasma]

I normally request that you go to the manufacturer of each individual device. But with such a huge list it may be more efficient to visit the PC manufacturer's website and get their updates. The point is that you'll get the latest drivers from the device manufacturer's website - and depending on the PC manufacturer those drivers may take a while to get on the PC manufacturer's website (or they may never appear there).

If you use the PC manufacturer's website, we'll have to look at the drivers again IF you have another BSOD occur. Not a big problem, and it definitely will save you a lot of time!

 

[pwalsh56]

Ok, I have attempted going to the PC manufacturer's website, I'm not sure if I'm missing something out, not seeing an option or something, but I cannot find any drivers to download.

I've put in the product name and number, it's been found, yet when I go to Software & Driver donloads, after choosing the OS, all it shows is a bunch of software application downloads I've never even heard of before, much less used.

Could someone check on the HP website to make sure I'm not just being a clot and missed something?

Failing that, I see the only thing for it is to update each driver one by one, correct? in which case, how would I go about finding out which driver file name in the list above corresponds to each component of the system?

 

[usasma]

Nope, you're doing it right. HP just doesn't have drivers listed for your system.
So, here's what to do...

type in your browser

http://www.carrona.org/dvrref.html#

then copy and paste the name of each driver after the # sign and press Enter

for example:

http://www.carrona.org/dvrref.html#sncduvc.SYS

It is case-sensitive, so be careful.
The table is designed with info in the 3rd column to help you out, and links in the 4th column to get you started looking for the drivers. If OEM is listed in the 4th column, just post back here and we'll see what we can find.

Do this for all the drivers - starting with the oldest first.
- Most of those starting with "nv" are your nVidia chipset drivers - you'll find that here: http://www.nvidia.com/object/nforce_vista_win7_64bit_15.49.html
- The 4 MpKsl... one's at the end are update files for Microsoft Security Essentials - don't bother with them, Windows Update will handle it.
- Don't worry about dump_nvstor32.sys - it's a copy of nvstor32.sys that Windows uses during the crash - no need to update it as it'll be recreated from the updated version when you next reboot.

In case it's needed later on, here's the link to the mobo specs: http://h10025.www1.hp.com/ewfrf/wc/...c=en&dlc=en&cc=uk&lang=en&product=3755531#N66

 

[pwalsh56]

Thank you! I'll get on with this - may take a while though as I've other stuff to do before going to work tomorrow. I'll post back with updates every now and then.

 

[cool91abhi]

bsod crash

till now my system was working well.but i today itself i got 3 BSOD crashes.my system is brand new dell inspiron regularly updated.i'm a naive user and cant figure out how to solve it.for details i'm attaching the dump files.

 

[usasma]

cool91abhi - please start your own topic so that your issue can get the individual attention that it deserves

 

[pwalsh56]

Apologies for the long time between posts! Lots of other stuff keeping me away from the computer, but I can get on with some work now. I've just tried the web link for both of the 2008 drivers - the first one being FsUsbExDisk.SYS, which has the link +++ ìœ ë¹„ì¿¼í„°ìŠ¤ 디지털 ì •ë³´ ì»¨í…ì¸ ë³´ì•ˆ ê¸°ìˆ ì˜ 최강자 테르텐 +++. I've searched the site and can't seem to find driver downloads anywhere. The second 2008 driver; sncduvc.SYS, has OEM listed in the 4th column.

I figured I should check in before going on with any others as you had previously said I should update them oldest first.

All the information I have on the first 2008 driver:
FsUsbExDisk.SYS Thu Sep 11 02:42:10 2008 (48C8BDC2) +++ ìœ ë¹„ì¿¼í„°ìŠ¤ 디지털 ì •ë³´ ì»¨í…ì¸ ë³´ì•ˆ ê¸°ìˆ ì˜ 최강자 테르텐 +++

All the information on the second:
sncduvc.SYS Mon Dec 29 04:13:29 2008 (495894B9) Suyin USB 2.0 Webcam driver OEM - none at 實盈股份有限公司 or http://www.sonix.com.tw/sonix/downloads.do/

Thanks.

 

[usasma]

The FsUsbExDisk.SYS stuff is associated with DRM - so this'll be a driver that's provided by some copyrighted content that you've put on your system. Probably not an HP driver. But, I'd look to see what's installed on your system and remove it if possible.

Try these for the webcam: ASUSTeK Computer Inc.-Support- download_item_mkt
Go to the Camera section and download the 2nd one (Suyin Camera Driver for Win7 32 bit)

 

[pwalsh56]

Ok, I'll just skip the FsUsbExDisk.SYS stuff? I'll go back to it later and see what it's associated with - how would I check to see what content provided it? And by removing it, you mean the driver files, or the content itself?

The webcam drivers: I tried all three download options for that file, both download, extract, and then when I run them, a few popups appear, the 2nd being an error message. They're attached to the message if you'd like to see them; don't think they're of much use though.

 

[usasma]

Go to Device Manager
Locate the webcam
Right click on it and select "Properties"
Then select the "Details" tab
In the dropdown box, select "Hardware ID"

In the Hardware ID, let us know the 4 characters immediately after VID_ and the 4 characters immediately after PID_
We'll use those to search for drivers on the web.

 

[pwalsh56]

Right, in Hardware ID there is two values;
USB\VID_04F2&PID_A133&REV_0100&MI_00
USB\VID_04F2&PID_A133&MI_00

But it certainly looks to me as if the VID_ value and the PID_ value are the same in each.

 

[usasma]

Try these:

Driver Details - Toshiba

Model Content Page

Model Content Page

If they don't work, then we'll have to disable the camera and it's driver while we're troubleshooting. To do this, disable the camera in Device Manager - then go to C:\Windows\System32\drivers and rename the driver from .sys to .BAK Reboot and that'll stop it from loading.

 

[pwalsh56]

I've noticed that all those drivers appear to be for Toshiba products - but the webcam I have is a Bush product, any significance, or will the drivers still work?

Seperate qestion, which I probably should have asked before now, should I uninstall the original driver, or not?

 

[pwalsh56]

I've taken the intervening time to figure out what FsUsbExDisk.SYS is associated with - Samsung New PX Studio, a program I use to transfer content between my Samsung mobile phone and my PC.

The site I found is here (if it's of any interest); FsUsbExDisk.SYS Windows process - What is it?

 

[usasma]

Thanks for that information. I've added it to the Driver Reference website.
If you visit, make sure to refresh the page
http://www.file.net/process/fsusbexdisk.sys.html

 

[pwalsh56]

Spotted a mistake in an earlier post; the program for use with FsUsbExDisk.SYS is the Samsung New PC Studio, apologies. Also, could you answer the questions in the post before that? It's in the quote below. Thanks!

I've noticed that all those drivers appear to be for Toshiba products - but the webcam I have is a Bush product, any significance, or will the drivers still work?

Seperate qestion, which I probably should have asked before now, should I uninstall the original driver, or not?

P.S. I've had a look at some of the 2009 dated drivers too, most of them shouldn't give too much grief, although I've not updated them, just looked at the link posted, so I could be wrong.

 

[usasma]

Sorry, I get all wrapped up in new information on drivers - and I end up losing track of what we were doing!

The device manufacturer's sell that device to several different PC manufacturer's - so Toshiba may decide to support Win7 while the other manufacturer's don't. If that's the case, then the only place to get the drivers (for Win7) will be Toshiba.

Where did you get the information that this is a Bush product? I wasn't able to find any computer products made by "Bush" in my internet searches.

It's always a good idea to uninstall the drivers before installing the new one's. This helps to eliminate problems that the installer may not be able to cope with.