Blue Screen crashes

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 (not RapidShare as the analysts usually can't download from it) - then post the link to it.
Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDump

Something messed up with it, but I was able to extract the dump files using an alternate method....:)

6 memory dump files, all are STOP 0x9F errors. More info on this error here: BSOD Index

Between the 8th and 18th of February something happened to your system that has caused problems with the memory dump analysis'.
On the 8th your build was: 7600.16385.x86fre.win7_rtm.090713-1255
On the 18th your build was: 7600.16481.x86fre.win7_gdr.091207-1941
And, also on the 18th (and later) your system cannot load the symbols for ntkrnlpa.exe (the kernel of the Windows operating system).

As such, all of this that I'm doing is based on supposition - and it may not help you out.
I'd suggest that you:

- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds

I'd suggest running this check:

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
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.

and these free 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)

Also, please remove or update 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.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How 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.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:

Code:

DLABMFSM.SYS Mon Jul 23 18:02:42 2007 - Roxio Drag-to-Disc  by Sonic Solutions (Sonic Solutions - DVD Burning - DVD Decoder - DVD & Video Editing Software) or Roxio (Roxio - DVD Burning & CD Burning Software - Creator & Toast Software)
DLABOIOM.SYS Mon Jul 23 18:02:37 2007 - Roxio Drag-to-Disc  by Sonic Solutions (Sonic Solutions - DVD Burning - DVD Decoder - DVD & Video Editing Software) or Roxio (Roxio - DVD Burning & CD Burning Software - Creator & Toast Software)
DLACDBHM.SYS Mon Jul 23 17:49:30 2007 - Roxio Drag-to-Disc  by Sonic Solutions (Sonic Solutions - DVD Burning - DVD Decoder - DVD & Video Editing Software) or Roxio (Roxio - DVD Burning & CD Burning Software - Creator & Toast Software)
DLADResM.SYS Mon Jul 23 18:04:10 2007 - Roxio Drag-to-Disc  by Sonic Solutions (Sonic Solutions - DVD Burning - DVD Decoder - DVD & Video Editing Software) or Roxio (Roxio - DVD Burning & CD Burning Software - Creator & Toast Software)
DLAIFS_M.SYS Mon Jul 23 18:01:39 2007 - Roxio Drag-to-Disc  by Sonic Solutions (Sonic Solutions - DVD Burning - DVD Decoder - DVD & Video Editing Software) or Roxio (Roxio - DVD Burning & CD Burning Software - Creator & Toast Software)
DLAOPIOM.SYS Mon Jul 23 18:03:19 2007 - Roxio Drag-to-Disc  by Sonic Solutions (Sonic Solutions - DVD Burning - DVD Decoder - DVD & Video Editing Software) or Roxio (Roxio - DVD Burning & CD Burning Software - Creator & Toast Software)
DLAPoolM.SYS Mon Jul 23 18:01:41 2007 - Roxio Drag-to-Disc  by Sonic Solutions (Sonic Solutions - DVD Burning - DVD Decoder - DVD & Video Editing Software) or Roxio (Roxio - DVD Burning & CD Burning Software - Creator & Toast Software)
DLARTL_M.SYS Mon Jul 23 17:48:47 2007 - Roxio Drag-to-Disc  by Sonic Solutions (Sonic Solutions - DVD Burning - DVD Decoder - DVD & Video Editing Software) or Roxio (Roxio - DVD Burning & CD Burning Software - Creator & Toast Software)
DLAUDF_M.SYS Mon Jul 23 18:01:56 2007 - Roxio Drag-to-Disc  by Sonic Solutions (Sonic Solutions - DVD Burning - DVD Decoder - DVD & Video Editing Software) or Roxio (Roxio - DVD Burning & CD Burning Software - Creator & Toast Software)
DLAUDFAM.SYS Mon Jul 23 18:02:20 2007 - Roxio Drag-to-Disc  by Sonic Solutions (Sonic Solutions - DVD Burning - DVD Decoder - DVD & Video Editing Software) or Roxio (Roxio - DVD Burning & CD Burning Software - Creator & Toast Software)
DRVMCDB.SYS  Mon Jul 23 17:53:48 2007 - Roxio Drag-to-Disc  by Sonic Solutions (Sonic Solutions - DVD Burning - DVD Decoder - DVD & Video Editing Software) or Roxio (Roxio - DVD Burning & CD Burning Software - Creator & Toast Software)
DRVNDDM.SYS  Mon Jul 23 17:42:35 2007 - Roxio Drag-to-Disc  by Sonic Solutions (Sonic Solutions - DVD Burning - DVD Decoder - DVD & Video Editing Software) or Roxio (Roxio - DVD Burning & CD Burning Software - Creator & Toast Software)
PxHelp20.sys Wed Jun 20 18:26:00 2007 -    Sonic CD/DVD driver (used by many different CD/DVD programs) - pxHelp20.sys programs
wdcsam.sys   Wed Apr 16 04:27:02 2008 - Western Digital RAID Manager - http://www.westerndigital.com

If all of this doesn't fix things, please try running 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 "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.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Once again, there's no sure results with this because of the inability to access the appropriate symbols for the ntkrnlpa.exe file (and others). So fixing that should be the top priority. Running Driver Verifier may not give us any significant results due to the symbol problems.

Here's a summary of the BSOD's:

Code:

Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Feb  6 17:01:56.712 2010 (GMT-5)
System Uptime: 0 days 2:01:21.257
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Mon Feb  8 10:18:48.146 2010 (GMT-5)
System Uptime: 0 days 1:23:21.691
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Thu Feb 18 23:23:52.931 2010 (GMT-5)
System Uptime: 0 days 12:00:05.476
*** 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.16481.x86fre.win7_gdr.091207-1941
Debug session time: Tue Feb 23 19:13:12.929 2010 (GMT-5)
System Uptime: 0 days 3:02:36.474
*** 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.16481.x86fre.win7_gdr.091207-1941
Debug session time: Thu Feb 25 23:09:38.570 2010 (GMT-5)
System Uptime: 0 days 3:49:51.115
*** 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.16481.x86fre.win7_gdr.091207-1941
Debug session time: Sun Feb 28 23:49:33.606 2010 (GMT-5)
System Uptime: 0 days 4:09:22.151
*** 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