Tech Support Forum banner
Not open for further replies.
1 - 3 of 3 Posts

· Registered
2 Posts
Discussion Starter · #1 ·
I'm getting this driver-related BSOD on the other computer which is running Windows Vista. It had never happened before (at least, I hadn't ever witnessed it) until today when I was uninstalling Virgin Media Security with Radialpoint so I could install the updated version with Trend Micro. However, when the install of the latest version had passed 85% I left the room. When I returned the computer had crashed and restarted, and then shortly after while looking at it, it crashed and restarted again. This is now happeneing every time a short while after Windows has started. The thing is: if I disconnect the USB Belkin Wireless Receiver, it stops happening, so I'm almost certain it is related to this piece of hardware.

Here is a copy of the two dump files I have from that computer. Help is greatly appreciated!


· TSF Team Emeritus, Microsoft MVP
7,498 Posts
NOTE: Please provide the following information for a more detailed response:

Just FYI, wireless USB devices on Win7 systems are notorious for causing BSOD's. Here's my rant on this subject:
I do not recommend using wireless USB devices. Especially in Win7 systems.
These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.
Your nVidia storage drivers are blamed in both crashes. I'd also suggest updating your nVidia chipset drivers (as they date from 2007)

Please also update your Realtek wired networking drivers - as they date from 2006

If all of this doesn't stop the BSOD's, please run 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 "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- 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 to stop Driver Verifier from loading (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
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\Mini011112-01.dmp]
Built by: 6002.18484.x86fre.vistasp2_gdr.110617-0336
Debug session time: Wed Jan 11 13:36:14.269 2012 (UTC - 5:00)
System Uptime: 0 days 0:31:54.956
BugCheck D1, {6dc, 2, 0, 807c5277}
*** WARNING: Unable to verify timestamp for nvstor32.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor32.sys
Probably caused by : nvstor32.sys ( nvstor32+2277 )
PROCESS_NAME: coreServiceShel
FAILURE_BUCKET_ID: 0xD1_nvstor32+2277
Bugcheck code 000000D1
Arguments 000006dc 00000002 00000000 807c5277
BiosVersion = PBDV10.P18
BiosReleaseDate = 09/10/2008
CPUID: "Intel(R) Celeron(R) CPU E1400 @ 2.00GHz"
MaxSpeed: 2000
CurrentSpeed: 1999


· Registered
2 Posts
Discussion Starter · #3 ·
I tried updating the drivers mentioned and so far so good, no more crashes - whereas before it was happening within a short while of Windows starting every time. The computer performance seemed to improve aswell.

I managed to update the Virgin Media security properly now, although this seemed to have slowed the computer down a bit again.

Thanks very much for your help. Fingers crossed there shouldn't be any more BSODs.
1 - 3 of 3 Posts
Not open for further replies.