BSOD on a 2 day old install!

Looks like MagicDisc is the cause now. Try removing the program, and see what happens.

...Summary of the Dumps:

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Oct 28 16:56:33.909 2010 (UTC - 4:00)
System Uptime: 0 days 0:13:06.127
BugCheck C4, {81, fffffa8006d4a460, 8a, 0}
*** WARNING: Unable to verify timestamp for mcdbus.sys
*** ERROR: Module load completed but symbols could not be loaded for mcdbus.sys
Probably caused by : mcdbus.sys ( mcdbus+36823 )
BUGCHECK_STR:  0xc4_81
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Try testing your RAM: RAM - Test with Memtest86+

What is the make/model of your PSU?

If the BSODs persist, upload a new report.

Hmm...I still see MagicDisc and MagicISO in your start menu. Try removing both programs again.

...Summary of the Dumps:

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Oct 28 16:56:33.909 2010 (UTC - 4:00)
System Uptime: 0 days 0:13:06.127
BugCheck C4, {81, fffffa8006d4a460, 8a, 0}
*** WARNING: Unable to verify timestamp for mcdbus.sys
*** ERROR: Module load completed but symbols could not be loaded for mcdbus.sys
Probably caused by : mcdbus.sys ( mcdbus+36823 )
BUGCHECK_STR:  0xc4_81
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Install these JMicron card reader drivers: ftp://driver.jmicron.com.tw/jmb38x/X...00.50_WHQL.zip

Your Microsoft keyboard drivers are old too; uninstall the software, in Programs and Features, and then go to Device Mangager > Keyboards, and uninstall the drivers for the keyboard. Reboot, and just use the generic drivers Windows automatically installs.

Try testing your RAM: RAM - Test with Memtest86+

What is the make/model of your PSU?

...Summary of the Dumps:

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Oct 29 09:58:59.056 2010 (UTC - 4:00)
System Uptime: 0 days 0:10:10.274
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨