BSOD on start up error 0x0000003b

You can hold off on the AMD chipset from AMD and just install the chipset drivers from your motherboard support site to start.

Aso to the disc issues: Yes, you may use the disc you originally bought.

I am assuming you want me to back this stuff up. I really don't care if I lose it unless you want to save the DMPS. I only had it in working condition for like a week. Thanks.

No need to backup the .dmps. I have them on my system saved, and hopefully they won't be needed after the clean installation. :)

Alright I gonna wipe everything now i'll let you know how it goes.

Well some bad news. I deleted my old windows stuff and had unallocated space so I started to install windows. I then leave it for maybe 20 mins and come back to a blue screen. The cause of the error is NTFS.sys and is tells about disk corrupton and chkdsk /r. So where do I go from here now that I don't even have windows? Is this a sign that my Hard drive is bad? Or should I try installing windows with out using my video card for display? Thanks

NTFS could mean your hard drive, hard drive connections, memory, motherboard, or CPU in the order from most likely to least likely. Did you run the chkdsk? Use your installation disc to start the installation software -> Command Prompt at Startup -> Do the following:

chkdsk /r c:
chkdsk /r d:
chkdsk /r e:
chkdsk /r f:

.etc until you get the message that the volume could not be opened for direct access. For any drives that do not give the message:
Windows has checked the file system and found no problems
run chkdsk again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.

I realize you may only have one disk show up in Windows explorer, but you may have more than one disk through recovery/installation options. This is because the system creates a hidden boot partition (which will be C: in recovery), you may have a recovery partition for your PC that is hidden (which will be D: in recovery), and you will have your primary Windows partition (which may be E: in recovery). A custom PC will likely have at least C: and D: to scan.

How many times do I have to run disk check? And you are saying that I most likely have a C drive and a D drive. Alright I am going to get started.

Alright I just want to make sure this is right. I've ran c: drive 3 times but it was so very quick. I am now running d: drive which is taking sometime, but seems completely normal. And then I will try e: , but I doubt I have and e: drive. I'll check though. How many times should I run these tests? And after I run them so many times should I try memory test because you said that was a possible cause too? Thanks

C: will probably be fast since it is likely your System Reserved partition. That partition is 100 MB, so it is rather small. You should run them as many times as required to get the message that Windows did not find any problems. Here is an example:

Code:

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  303104 file records processed.                                          File verification completed.
  388 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              82 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  375112 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  303104 file SDs/SIDs processed.                                         Cleaning up 241 unused index entries from index $SII of file 0x9.
Cleaning up 241 unused index entries from index $SDH of file 0x9.
Cleaning up 241 unused security descriptors.
Security descriptor verification completed.
  36005 data files processed.                                            CHKDSK is verifying Usn Journal...
  37105088 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  303088 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  66106402 free clusters processed.                                         Free space verification is complete.
Windows has checked the file system and found no problems.

 361306111 KB total disk space.
  96337404 KB in 217196 files.
    124928 KB in 36006 indexes.
         0 KB in bad sectors.
    418171 KB in use by the system.
     65536 KB occupied by the log file.
 264425608 KB available on disk.

      4096 bytes in each allocation unit.
  90326527 total allocation units on disk.
  66106402 allocation units available on disk.

Internal Info:
00 a0 04 00 1e dd 03 00 82 7c 06 00 00 00 00 00  .........|......
01 02 00 00 52 00 00 00 00 00 00 00 00 00 00 00  ....R...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Alright so windows did not find any problems. I ran it many times and nothing came up. Although the end of the.scans differ a but from your end of your scan. When I try to acess e drive it says I don't have the right permissions or something like that. I know that those are the only drives because I did try all the other drives. And I'm getting kind of worried because my 30day return policy from newegg is almost up. Got any ideas? Thanks