"BLUE-SCREEN" I can't even log-in to my pc

Please boot into Safe Mode and do this:

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

The error messages are all over the place. Usually this is indicative of a hardware failure.

Bugcheck code 000000D1
Bugcheck code 0000007F
Bugcheck code 0000001A
Bugcheck code 00000050
Bugcheck code 000000A0
Bugcheck code 0000001E
Bugcheck code 00000050
Bugcheck code 0000001E
Bugcheck code 0000001A
Bugcheck code 0000000A

So, please start with these free bootable 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)

Although this driver isn't present in all the dump files, it is present in enough of them (7 out of 10) that it should be updated: UsbFltr.sys Mon Apr 09 06:09:44 2007
It belongs to your Ortek USB Keypad Driver or your Razer Tarantula USB Keyboard

Here's a summary of the BSOD's:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Jan 18 21:30:17.719 2010 (GMT-5)
System Uptime: 0 days 0:03:55.218
BugCheck D1, {f0d2cd7, 2, 1, fffff8800141d7cc}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Jan 18 21:36:04.833 2010 (GMT-5)
System Uptime: 0 days 0:03:37.253
BugCheck 7F, {8, 80050033, 6f8, fffff800028c312b}
Probably caused by : hardware ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  mscorsvw.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Jan 18 22:08:00.221 2010 (GMT-5)
System Uptime: 0 days 0:26:40.641
BugCheck 1A, {41287, 8000, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42c75 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Jan 18 20:01:02.531 2010 (GMT-5)
System Uptime: 0 days 0:05:07.577
BugCheck 50, {fffff88006534688, 1, fffff80002895f4b, 0}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  msiexec.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Jan 18 23:56:23.031 2010 (GMT-5)
System Uptime: 0 days 0:51:36.452
BugCheck A0, {b, 17f8ba000, 3, 5be85000}
Probably caused by : ntkrnlmp.exe ( nt!PopWriteHiberPages+a3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jan 20 14:23:02.411 2010 (GMT-5)
System Uptime: 0 days 0:10:07.831
BugCheck 1E, {ffffffffc000001d, fffff800028b88c1, 2, 7c40017e00}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  SearchProtocol
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jan 20 14:27:18.763 2010 (GMT-5)
System Uptime: 0 days 0:03:45.184
BugCheck 50, {5800000, 1, 7fef7edc3ff, 8}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+430e7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jan 20 14:32:42.348 2010 (GMT-5)
System Uptime: 0 days 0:04:37.769
BugCheck 1E, {ffffffffc0000005, fffff80002bae580, 1, 621f90}
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+40 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jan 20 15:11:18.785 2010 (GMT-5)
System Uptime: 0 days 0:11:54.206
BugCheck 1A, {41287, 2018, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42c75 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  LogonUI.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jan 21 15:14:50.475 2010 (GMT-5)
System Uptime: 0 days 0:02:42.521
BugCheck A, {57fffffff8b, 2, 1, fffff8000284d23a}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  firefox.exe

Do you have a Razer keyboard? Please uninstall it in Safe Mode (if possible).

Have you performed the H/W Diagnostics that I suggested?

If you don't have the Razer keyboard software installed, then it may have come with the Dynex keyboard.
But if the computer is working OK, don't worry about it.