Had a blue screen of death and have system issues

Do you use a PS2 mouse (or a USB one)? The perfmon report shows issues with a PS2 mouse.
If you use USB, then this is safe to ignore.

There are no memory dumps (BSOD reports) included in the upload. If you're using a temp file cleaner, please stop. Otherwise, please do the following:

Upload Dump Files:
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service . I recommend Windows Live SkyDrive - http://skydrive.live.com or another free, file-hosting service. Then post the link to it in your topic so that we can download it.

Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDump

The MSINFO32 report is corrupt. Whille this isn't unusual, I rely on this heavily. Please do the following:

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
http://www.carrona.org/memdiag.html (read the details at the link)
http://www.carrona.org/hddiag.html (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: http://www.carrona.org/malware.html (read the details at the link)

Either don't let your cleaner clean memory dump files - or just don't clean anything until we're finished here. There's no actual harm in cleaning - but it removes the files that we need to use.

You must ensure that your NETGEAR WPN111 Adapter has Win7 drivers (NOT Vista drivers!). If you are unable to find Win7 drivers, remove the device until we're finished troubleshooting. Vista drivers on these devices are a known cause of BSOD's. Here's my rant on these devices:

I do not recommend using wireless USB devices.
These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

Older versions of MSI Afterburner are also known to cause BSOD's in Win7 systems. Please uninstall this program for your system and then test for further BSOD's. I wouldn't reinstall this program if this were my system.

Only one BSOD shows in MSINFO32 - it was today (6/11/2011) at 12:24am and was this: 0x50_nt!MmEnumerateAndReferenceImages+10c

That's not real helpful for us, so I'd suggest running Driver Verifier according to these directions. It'll try and force a BSOD, so you should be able to capture the memory dump file. Just zip it up and upload it here when it happens.

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:

Code:

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

https://cid-121c25216cdd7631.skydriv...pqHh5inIhPs%24

Okay, i got the computer to crash again. I've got a mini-dump file and a MEMORY.DMP at the link above. I've got a couple of txt files from running the dds tool and the attach text has some errors on it. I was wondering if i sent them to you if you would you fix these problems?

No need to upload the MEMORY.dmp file if you have a Minidump file for the crash - the system creates the MEMORY.dmp and then extracts the minidump from that.

Did you get the BSOD error before or after you removed the wireless USB adapter?
Did you also uninstall the software for the wireless USB adapter? If not, please do so now.
What are you using to connect to the internet now that the wireless USB adapter isn't connected?

If the BSOD came before you removed the wireless USB adapter - then run Driver Verifier again
If it came after you removed the wireless USB adapter - update your the drivers for the current connection and then run Driver Verifier again.

Please update these older drivers:
OLDER DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

Code:

nvstor32.sys      Tue Aug 04 20:27:05 2009 (4A78D1D9)
http://www.carrona.org/dvrref.html#nvstor32.sys 

timntr.sys        Wed Aug 29 08:13:12 2007 (46D562D8)
http://www.carrona.org/dvrref.html#timntr.sys 

tdrpman.sys       Mon Nov 12 08:35:28 2007 (473856A0)
http://www.carrona.org/dvrref.html#tdrpman.sys 

snapman.sys       Thu Nov 22 03:19:58 2007 (47453BAE)
http://www.carrona.org/dvrref.html#snapman.sys 

HSXHWBS2.sys      Wed Jun 20 14:28:36 2007 (467971D4)
http://www.carrona.org/dvrref.html#HSXHWBS2.sys 

bdfndisf6.sys     Fri Aug 20 11:41:10 2010 (4C6EA216)
http://www.carrona.org/dvrref.html#bdfndisf6.sys 

bdfwfpf.sys       Fri Aug 20 11:41:00 2010 (4C6EA20C)
http://www.carrona.org/dvrref.html#bdfwfpf.sys 

SCDEmu.SYS        Sun Nov 08 22:21:19 2009 (4AF78AAF)
http://www.carrona.org/dvrref.html#SCDEmu.SYS 

HSX_DPV.sys       Wed Jun 20 14:29:51 2007 (4679721F)
http://www.carrona.org/dvrref.html#HSX_DPV.sys 

HSX_CNXT.sys      Wed Jun 20 14:28:20 2007 (467971C4)
http://www.carrona.org/dvrref.html#HSX_CNXT.sys 

Interesting info in the DDS and ATTACH files, but I'm not a malware removal specialist so I have no clue about how to use them.

BSOD BUGCHECK SUMMARY

Code:

Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\061111-25942-01.dmp]
Built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun 11 20:42:38.643 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:48.781
Probably caused by : ndis.sys ( ndis!ndisPassIrpDownTheStack+52 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  0x7E_VRF_BAD_IP_ndis!ndisPassIrpDownTheStack+52
Bugcheck code 1000007E
Arguments c0000005 00000004 88323420 88323000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``