New
#11
None of the BSOD's are Driver Verifier Enabled Memory Dumps.
They are 4 memory dumps with 4 different error messages and 4 different reasons.
As such I'd have to assume that this is a hardware problem or a Windows problem (and that Driver Verifier won't do a thing for this type of error - although it won't hurt to run it).
So, start with these diagnostics:
And, check your file system: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)
*****
Additional tests for certain specific circumstances:
Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Try this free stress test: Free Software - GIMPS
Then, please remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.
Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"
CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall/remove:
- some driver links are on this page: http://www.carrona.org/drvrdown.htmlHow To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:
Summary of the BSOD's:Code:StarOpen.SYS Tue Jun 27 15:15:56 2006 - AT&T, Verizon, and/or Virgin mobile phone driver file. Rtnicxp.sys Mon Mar 31 01:41:05 2008 - Realtek Network driver adfs.SYS Thu Aug 14 10:57:15 2008 - Adobe File System driver
Code:*** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Built by: 7600.20576.x86fre.win7_ldr.091115-1505 Debug session time: Tue Jan 26 15:31:31.173 2010 (GMT-5) System Uptime: 0 days 11:05:59.140 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe BugCheck D1, {5d, 2, 1, 919e076f} Probably caused by : kbdclass.sys ( kbdclass!KeyboardClassServiceCallback+2c7 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Built by: 7600.20576.x86fre.win7_ldr.091115-1505 Debug session time: Fri Jan 29 14:32:46.027 2010 (GMT-5) System Uptime: 0 days 3:59:16.993 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe BugCheck 1000008E, {c0000005, 8325afc6, 9b0aabec, 0} Probably caused by : hardware ( nt+223fc6 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Built by: 7600.20576.x86fre.win7_ldr.091115-1505 Debug session time: Fri Jan 29 16:33:26.176 2010 (GMT-5) System Uptime: 0 days 1:59:29.752 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Built by: 7600.20576.x86fre.win7_ldr.091115-1505 Debug session time: Fri Jan 29 18:27:10.256 2010 (GMT-5) System Uptime: 0 days 0:13:59.223 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe *** WARNING: Unable to verify timestamp for Ntfs.sys *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
Quote