Blue Screen Blues

Ok guys I really need your help here. I have had random blue screens since upgrading from Vista Business to Windows 7 Ultimate. I have upgraded my drivers manually then finally installing DriverEasy and doing it that way. It showed I had two out date drivers. I installed those last night and later that evening it crashed again. This morning every time I tried to boot up I got the Blue Screen or a reboot. Even tried Safe Mode with the same result, restore to previous nothing worked. I got mad took a nap had a nightmare about computers woke up turned my box on and it booted up. It shows now one of the drivers I installed last night is no longer installed it is the Alcor Micro USB 2.0 Card Reader it now shows it as out of date. Attached is the last error I could get and all my dump files. If someone could give me an idea of what driver is causing the problem that would be great.
http://www.forestpro.net/Ghostwalker...umps/Error.txt
http://www.forestpro.net/Ghostwalker...ump%20Files.7z

Ghostwalker said:

Ok guys I really need your help here. I have had random blue screens since upgrading from Vista Business to Windows 7 Ultimate. I have upgraded my drivers manually then finally installing DriverEasy and doing it that way. It showed I had two out date drivers. I installed those last night and later that evening it crashed again. This morning every time I tried to boot up I got the Blue Screen or a reboot. Even tried Safe Mode with the same result, restore to previous nothing worked. I got mad took a nap had a nightmare about computers woke up turned my box on and it booted up. It shows now one of the drivers I installed last night is no longer installed it is the Alcor Micro USB 2.0 Card Reader it now shows it as out of date. Attached is the last error I could get and all my dump files. If someone could give me an idea of what driver is causing the problem that would be great.
www.forestpro.net/Ghostwalker/Crash%20Dumps/Error.txt
www.forestpro.net/Ghostwalker/Crash%20Dumps/Dump%20Files.7z

The Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

Please do the following:
- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center )
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Dump Files\032810-22265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x83047000 PsLoadedModuleList = 0x8318f810
Debug session time: Sun Mar 28 15:32:48.485 2010 (GMT-4)
System Uptime: 0 days 19:46:54.093
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {d, 0, 0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

OLD DRIVERS THAT NEED TO RE UPDATED

Code:

bp32drv4.sys        0x83d30000    0x83d48000    0x00018000    0x3d2da8ab    7/11/2002 11:47:55 AM                        
secdrv.SYS        0x9a4a9000    0x9a4b3000    0x0000a000    0x45080528    9/13/2006 9:18:32 AM                        
nvmfdx32.sys        0x8ec02000    0x8ed01600    0x000ff600    0x489357fd    8/1/2008 2:37:49 PM

Thanks for your reply Im in the process of doing all you said, thanks