BSOD windows 7

[wizz12345]

Hi can you please have a look

 

[wizz12345]

file

 

[usasma]

5 errors, 5 different BSOD error codes, blaming 5 different causes.
This is most likely a hardware problem, but could be a compatibility issue instead.

It is possible that the following older drivers may be causing your problems.
Please either REMOVE or Update the older drivers listed below.

HOW TO FIND DRIVERS:
DO NOT use Windows Update or the Update Driver function of Device Manager as they are not the most current versions available.
Also, DO NOT update from the PC Manufacturer's website unless the Driver Reference cited below states that you should get the drivers from the OEM.

The most common drivers are located on this page: Driver Reference
If you can't find the driver, post back and we'll see what we can find.

Here's the older drivers that were found in the memory dump files:

[font=lucida console]
wacommousefilter.sys Fri Feb 16 13:12:17 2007 (45D5F401)
 - Wacom(tablet) Mouse Filter
 - [url=http://www.carrona.org/dvrref.html#wacommousefilter.sys]Driver Reference[/url]

RtNdPt60.sys Mon Dec 10 21:49:52 2007 (475DFAD0)
 - Netgear GA511 Driver file (Realtek chipset)
 - [url=http://www.carrona.org/dvrref.html#RtNdPt60.sys]Driver Reference[/url]
[/font]

In this case, the Netgear GA511 card does not support Win7 (although you may be using a different manufacturer, the chipset is likely to be the same - and to be incompatible with Win7). Try forcing a BSOD crash without the wireless card in the computer.

Please run Driver Verifier according to these instructions (with the wireless card in the computer):

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.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 13 14:57:40.636 2010 (UTC - 5:00)
System Uptime: 0 days 1:30:19.103
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iMapTransfer+24a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  DVDMaker.exe
Bugcheck code 0000000A
Arguments 00000000`00000008 00000000`00000002 00000000`00000000 fffff800`033f1266
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  9 17:40:48.938 2010 (UTC - 5:00)
System Uptime: 0 days 0:56:32.796
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiWaitForSchedulerEvents+1bc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`02c7da56 fffff880`03de25d8 fffff880`03de1e40
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  9 15:09:28.825 2010 (UTC - 5:00)
System Uptime: 0 days 1:35:59.667
Probably caused by : ntkrnlmp.exe ( nt!KiScanInterruptObjectList+43 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
Bugcheck code 0000003D
Arguments fffff880`02ffd0e0 00000000`00000000 00000000`00000000 fffff800`02ccd313
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Nov  7 18:27:13.891 2010 (UTC - 5:00)
System Uptime: 0 days 2:04:11.358
BugCheck D1, {24, 2, 0, fffff8800465b764}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+52764 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 000000D1
Arguments 00000000`00000024 00000000`00000002 00000000`00000000 fffff880`0465b764
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Nov  7 15:59:34.881 2010 (UTC - 5:00)
System Uptime: 0 days 2:02:30.738
Probably caused by : hardware ( volsnap!VspFreeContext+b0 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[wizz12345]

Just a quick update i think i have fixed all my BSOD's by uping the voltage on my RAM to 1.65.v and my nourthbridge to 1.v been ok for days now

 

[usasma]

Glad to hear it! Thanks for letting us know!