patobaresi, you have 3 dump files. One is the one you posted the screenshot of, a Machine Check Exception. The other 2 are 0X124, which are about the same thing.
Code:
Use !analyze -v to get detailed debugging information.
[COLOR=red]BugCheck 124[/COLOR], {0, fffffa80077928f8, 0, 0}
Probably caused by : GenuineIntel
Followup: MachineOwner
That code is a generic hardware error but gives no clue which identifies the specific hardware component that caused it. It just means that a hardware component has failed/is failing or a bad driver is causing that piece of hardware to act as though it were failing.
To start, please go to your Motherboard's web site and update all of your drivers. Make sure all of your Windows Updates are current and installed.
Please go into bios and see what your sata controller is set to (IDE, AHCI or Raid), set optimized defaults, set your sata controller to what it is right now, set your ram to Manufacturer's specs and set your boot order, save and exit. Do not change anything else. Please, while in BIOS, tell me what your +12V, +5V and +3.3V readings are. If you are overclocking anything, set everything to default levels. No overcocking until we get you stable.
Then please open an elevated command prompt ( click start, type
cmd in the search box,
right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste
sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.