BSOD over&over again

Hello people,

Ever since I got this new system, I keep getting the BSOD's.
They come up with different descriptions, but with same annoyance level.
I have even reinstalled windows, twice, to no avail.

The detailed system specs are in my profile.

Thank you very much,
Filip

hoorooz said:

Hello people,

Ever since I got this new system, I keep getting the BSOD's.
They come up with different descriptions, but with same annoyance level.
I have even reinstalled windows, twice, to no avail.

The detailed system specs are in my profile.

Thank you very much,
Filip

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp,sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads

when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.

Cheers, mate.
I will proceed with the removal, and I will get back with the results.

Thanks a bunch!

After uninstalling the Daemon tools soft along with the driver, using the tool you recommended, I rebooted my system.
After the reboot, in the middle of an MS Security Essentials update, the BSOD appeared again.
What should I do now?

hoorooz said:

After uninstalling the Daemon tools soft along with the driver, using the tool you recommended, I rebooted my system.
After the reboot, in the middle of an MS Security Essentials update, the BSOD appeared again.
What should I do now?

Upload the DMP file and download malwarebytes and run it in safe mode just in case.

Hi there,

Right in the middle of the scan with malware bytes, i got the BSOD again.
It was in safe mode.
The dump files report is generated after this BSOD.

Thank you.

hoorooz said:

Hi there,

Right in the middle of the scan with malware bytes, i got the BSOD again.
It was in safe mode.
The dump files report is generated after this BSOD.

Thank you.

Newest related to memory corruption. Malwarebytes was running at the time but I am wondering if this isnt malware.

Do you have a backup from prior to the problem?

This is a new system that I just built.

Immediately after I finished installing Windows for the first time, on this "virgin" system, let's say a few hours after the system install, the BSOD appeared.

This is also the reason of me not having a backup.
Firstly I installed a Win7 x86, and thought it was a problem related to the amount of ram being bigger than the OS sees. So I formatted my C drive and installed a Win 7 x64. Same problems with the BSOD. I reformatted my system again.

So, now, I'm at the 3rd system installed, and again, with the same BSOD issues.

What now?

hoorooz said:

This is a new system that I just built.

Immediately after I finished installing Windows for the first time, on this "virgin" system, let's say a few hours after the system install, the BSOD appeared.

This is also the reason of me not having a backup.
Firstly I installed a Win7 x86, and thought it was a problem related to the amount of ram being bigger than the OS sees. So I formatted my C drive and installed a Win 7 x64. Same problems with the BSOD. I reformatted my system again.

So, now, I'm at the 3rd system installed, and again, with the same BSOD issues.

What now?

With 3 OS installs we can pretty much rule out software (unless you have installed something like a malware app or firewall that may be cuasing it) so we now need to start on hardware

Lets start with memory

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.