Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


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

27 Feb 2013   #1
Stellaflora

Windows 7 Professional 64-bit
 
 
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.


My System SpecsSystem Spec
.
28 Feb 2013   #2
ICIT2LOL

Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
 
 

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
My System SpecsSystem Spec
01 Mar 2013   #3
Stellaflora

Windows 7 Professional 64-bit
 
 

I've used the monitoring software the came with my motherboard and the CPU temp rarely goes over 40C.

Also, I've updated the Zip file to account for more recent crashes.

I forgot to mention, system will sometimes crash and restart when attempting to shut down or use hibernate.
My System SpecsSystem Spec
.

01 Mar 2013   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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 ......
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   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   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   Tip

Let us know the results, with the subsequent crash dumps, if any.
My System SpecsSystem Spec
01 Mar 2013   #5
Stellaflora

Windows 7 Professional 64-bit
 
 

I've uninstalled both programs
I've disabled the CPU overclocking (the BIOS seems to default to auto overclocking, aiming for 3800)

I'm currently running Memtest86+, which seems to be finding lots of errors! (259,840 so far, and it's only been running 15mins)
My System SpecsSystem Spec
01 Mar 2013   #6
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Quote   Quote: Originally Posted by Stellaflora View Post
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.
My System SpecsSystem Spec
01 Mar 2013   #7
Stellaflora

Windows 7 Professional 64-bit
 
 

Thank you very much for your help.
They should be under warranty, I bought them from Amazon on 23rd Jan this year.

Should I mark this as solved or wait until the replacement RAM has been installed?
My System SpecsSystem Spec
01 Mar 2013   #8
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

Leave it open - once the new RAM is installed and everything is working OK, you can mark it as solved then if you like.
My System SpecsSystem Spec
01 Mar 2013   #9
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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
My System SpecsSystem Spec
01 Mar 2013   #10
ICIT2LOL

Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
 
 

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
My System SpecsSystem Spec
Reply

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




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Custom Build with frequent random BSOD error 0x00000f4 (possible fix)
Hello All, I am new here, but I have been surfing through the forums tirelessly in order to try to remedy this BSOD situation that was plaguing my first build. I hope that I can offer something to others that may be having a similar problem. I can only assume that this problem springs up with...
BSOD Help and Support
BSOD on new custom build random in timing
Hiya, any help with this is much appreciated Win 7 Pro 64bit 4gb RAM 4x MSI R9 270x MSI Z77A-G45 MB Celeron G1620
BSOD Help and Support
One week old custom build getting random BSOD when idle but not gaming
I've been getting BSOD for the past 4 days but they only occur around once or twice per day. The BSOD happens only when my computer is idle but not when gaming. Help would be much appreciated. I've attached the zip file of the minidump files. FYI, most of the time the error code is...
BSOD Help and Support
Custom Build PC Random BSOD sometimes
Hello, My friend has a Custom Built computer (1Y old) and now he has problems his computer crashing with the DRIVER_POWER_STATE_FAILURE message. I hope someone can help us finding the problem any help is appreciated. Thanks In Advance.
BSOD Help and Support
Custom build, Random BSOD, ntoskrnl.exe, dxgmms1.sys
W7 64bit SP1 AMD Athlon X 3 450 3.2GHz ARCTIC COOLING Freezer 7 Pro Rev.2 GIGABYTE GA-970A-UD3 Corsair 4G XMS3 TW3X4G1333C9A G XFX Radeon HD5770 Corsair 650TX 650W CREATIVE SB X-Fi Titanium 500GB WD Caviar Black
BSOD Help and Support
New custom build system. 60+ clean installs. Always random BSODs.
First of all I must apologize about my limited English. I'll try to do my best to explain my situation because I really need help. I usually prefer to look for solutions by myself, because I think it's a good way to learn, but this time is different: after hours reading posts and more posts I...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 17:27.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App