Random BSOD on new custom build & clean install of Win 7 Pro 64

less then two weeks ago I built a new PC to replace an old ailing computer (that I had built a number of years ago)

Ever since I've had it running however it, apparently randomly, will BSOD then restart. This has been happening several times a day even after a re-install I carried out last Friday. I was careful to use an anti-static mat and wrist strap whilst assembling the components.

EDIT: forgot to rename the zip file before uploading.

Hello and welcome Stellaflora I am no expert at reading those dump files but am just wondering if you can find what the CPU temp is seeing that it is shutting down and then restarting.

Try Speccy to find out what it is it isn't an absolute exact measurement but close enough for this purpose.

Speccy - Download < download from piriform

Code:

BugCheck 7F, {8, 80050033, 406f8, fffff80002cc7024}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Followup: MachineOwner
----------------------------------------------------------------------------------------------------
BugCheck 7F, {8, 80050033, 406f8, fffff80002c7b024}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Followup: MachineOwner
-----------------------------------------------------------------------------------------------------
BugCheck 7F, {8, 80050033, 406f8, fffff80002c8c024}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Followup: MachineOwner
----------------------------------------------------------------------------------------------------
BugCheck 7F, {8, 80050033, 406f8, fffff80002ccd024}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Followup: MachineOwner
----------------------------------------------------------------------------------------------------
BugCheck BE, {fffff683ff7ed000, 8a00000d0869025, fffff88002e1b160, b}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+44cde )

Followup: MachineOwner
----------------------------------------------------------------------------------------------------
BugCheck 1A, {41790, fffffa80025c9320, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

Followup: MachineOwner
----------------------------------------------------------------------------------------------------
BugCheck 50, {fffff8a0661ec010, 0, fffff80002e039bc, 5}


Could not read faulting driver name
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )

Followup: Pool_corruption
----------------------------------------------------------------------------------------------------
BugCheck 1A, {41790, fffffa80025c9320, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

Followup: MachineOwner
----------------------------------------------------------------------------------------------------
BugCheck 1A, {41790, fffffa80025c9350, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

Followup: MachineOwner
---------

According to Carrona.org ......

• STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP : Usual causes: Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack
• STOP 0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY : Usual causes: Device driver, Memory
• STOP 0x0000001A: MEMORY_MANAGEMENT : Usual causes: Device driver, memory, kernel
• STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA : Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

Do the following:

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stop Overclocking.

Code:

CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410

Revert all CPU and GPU settings back to default. Dont overclock.

Uninstall Marvell SATA controllers.

Code:

Start Menu\Programs\Marvell
Start Menu\Programs\Marvell\91xx driver CoolMaster\David

Uninstall them in Control Panel> Programs and Features.

Uninstall these programs, too.

Code:

Start Menu\Programs\ASUS
Start Menu\Programs\ASUS\AI Suite II

Finally, when all is done, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Stellaflora said:

I'm currently running Memtest86+, which seems to be finding lots of errors! (259,840 so far, and it's only been running 15mins)

Stop testing.

A single error is enough to determine that the RAM is faulty. If the RAM is within warranty, RMA it; otherwise get a new kit that is compatible with your motherboard.

EDIT: If the RAM is not under warranty, and if dont want to buy all the sticks just want to replace the faulty one, follow " Part 3: If You Have Errors:" part of RAM - Test with Memtest86+. It will help you to determine actually which particular RAM module is faulty.

Leave it open - once the new RAM is installed and everything is working OK, you can mark it as solved then if you like.

You get the replacement RAM, apply them, observe if it is really free from issues with those or not, and let us know the situation.

If there is no more issues with the replacement RAM, then mark this thread as solved. OK? :)

Edit: In short, follow what my Golden friend suggested

If Arc and Golden don't mind my two cents worth if you get RAM try get sticks that come in paired or quad sets they are more likely to match each other rather than installing a mixed lot of sticks :)