Just a guess, but try Uninstalling the Unknown Device (right click on it and select "Uninstall")
Then reboot to see if it's reinstalled.
I'm wondering if the Unknown Device is your DLink DWL-G122 wireless USB adapter. Try removing that device to see if the Unknown Device goes away. If so, please only install Win7 drivers with these devices - they don't work well (IME) with any other driver in Win7. If you can't locate Win7 drivers, I'd suggest installing a wireless card inside the computer case - as they're more powerful, reliable, and compatible - and they don't have the sort of issues that the USB adapters have.
Do you have any other USB devices that may be inactive at this time?
Uninstall Daemon Tools as it's known (in some cases) to cause BSOD's. Check to ensure that the SPTD.sys driver is removed
Stop the Btmchk program from loading at startup - it appears related to AdobeReader, but it starts from a questionable location (using rundll32.exe to launch it out of your Temp files). This could be a symptom of a virus infection, so I'd conduct several scans on your system to rule this out.
Uninstall RivaTuner and nTune for now. If you want to, you can reinstall them when we're done. I seem to remember that one of these has issues with Win7 - so it may be wise to research them a bit more before installing them. Your copy of the Riva Tuner driver dates from 2007 - so I'd immediately suspect that. Your nTune driver may be from 2007 also (the nvoclk64.sys driver dates from 2007).
If overclocking, please return the system to default settings and don't overclock until we're finished troubleshooting. The troubleshooting is designed for normally operating systems - so overclocking can skew the results and prevent us from figuring this out. Once we've achieved a stable system without overclocking, then we can set the overclock and troubleshoot any issues with it.
There are 8 memory dumps, with 6 different BSOD errors that blame at least 6 different causes - this most likely points to a hardware problem. The overclock can also cause this, as can compatibility issues (such as the issues I recalled w/Riva Tuner or nTune).
4 of the errors point at video components - so that's the most likely problem now. See this troubleshooting guide for the STOP 0x116 errors: STOP 0x116: VIDEO_TDR_ERROR troubleshooting
As this is probably a hardware issue, and there's other components mentioned in the error messages, please run these free hardware diagnostics:
H/W Diagnostics:
Please start by running these
bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (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:
Malware (read the details at the link)
You can also try these free stress tests to see if there are video or other system stress issues:
Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors
(whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
Finally, your PxHlpa64.sys driver is dated from Wed Oct 18 13:34:14 2006. Here's some info on it: Driver Reference If you're unable to locate the program that it belongs to, just rename the driver to PxHlpa64.BAK and see what CD/DVD program it breaks.
BSOD BUGCHECK SUMMARY
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep 8 06:03:00.258 2010 (UTC - 4:00)
System Uptime: 0 days 0:18:01.710
BugCheck 24, {1904fb, fffff88009772c48, fffff880097724b0, fffff880012d4a91}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefix+121 )
PROCESS_NAME: SearchProtocol
BUGCHECK_STR: 0x24
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 5 16:15:57.375 2010 (UTC - 4:00)
System Uptime: 0 days 0:14:31.828
BugCheck 116, {fffffa8004a964e0, fffff8800ffa8cf8, 0, 2}
*** 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+119cf8 )
BUGCHECK_STR: 0x116
PROCESS_NAME: System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 5 12:45:57.096 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:18.548
BugCheck 1A, {5100, fffff6fc80615240, 2d, d390000101523863}
Probably caused by : win32k.sys ( win32k!AllocateObject+dd )
BUGCHECK_STR: 0x1a_5100
PROCESS_NAME: winlogon.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 4 19:17:43.559 2010 (UTC - 4:00)
System Uptime: 0 days 2:18:31.620
BugCheck D1, {3a00c11704b4, 2, 8, 3a00c11704b4}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME: lsm.exe
BUGCHECK_STR: 0xD1
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug 2 20:51:17.644 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:42.705
BugCheck 3B, {c0000096, fffff880068b1ab7, fffff88008605e60, 0}
Probably caused by : nvoclk64.sys ( nvoclk64+1ab7 )
BUGCHECK_STR: 0x3B
PROCESS_NAME: NVMonitor.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug 2 20:48:53.513 2010 (UTC - 4:00)
System Uptime: 0 days 0:21:17.575
BugCheck 3B, {c0000096, fffff880065ecab7, fffff880075b9e60, 0}
Probably caused by : nvoclk64.sys ( nvoclk64+1ab7 )
BUGCHECK_STR: 0x3B
PROCESS_NAME: NVMonitor.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug 2 19:41:39.886 2010 (UTC - 4:00)
System Uptime: 0 days 6:45:14.338
BugCheck 116, {fffffa800594f4e0, fffff8800ff7ca20, 0, 2}
*** 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+112a20 )
BUGCHECK_STR: 0x116
PROCESS_NAME: System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 17 13:35:40.838 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:18.290
BugCheck 1000007E, {ffffffffc000001d, fffff88005cb0d23, fffff8800357df18, fffff8800357d780}
*** WARNING: Unable to verify timestamp for anodlwfx.sys
*** ERROR: Module load completed but symbols could not be loaded for anodlwfx.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR: 0x7E
PROCESS_NAME: System