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: BSOD on new build - Increasing memory volts stabilised for 12 hours

08 Mar 2014   #1

Windows 7 X64
 
 
BSOD on new build - Increasing memory volts stabilised for 12 hours

Hi all,

Well i've come here in desperation because i've tried every common sense solution off my own back and come up with nothing.

I built my pc exactly a week ago, and after the first couple of days i started getting infrequent bsod screens. I tried googling codes, installing different drivers(first using revo uninstaller), changed my antivirus from avast to microsoft security essentials, used the "whocrashed" program, tested some basic bios settings, and mildly increased ram volts(with some short lived success).

I'm currently in the proccess of testing ram modules individually out of each available ram slot, i've tried one and it passed memtest86+ 7 times over, and i'm just about to try it in the other ram slot....then repeat the process with the 2nd ram module.

The BSOD happens when idle on desktop as much as it happens when doing anything specific. It sometimes happens within minutes of booting windows, sometimes it takes an hour, and when i tried upping the default memory volts from 1.5v to 1.53v it lasted over 12 hours, including completing an initial 6 hours of prime 95 testing, and then after being idle for another 6 hours it BSOD.

The temporary increase in stability when the voltage change happened, makes me think ram modules, but i'll see what memtest86+ comes up with.

Meanwhile i'm really hoping some knowledgeable fellow on here might spot something very obvious software related in the dumps.

Any help will be very much appreciated.

I'll edit my post with dumps very shortly as per the forum guide.


My System SpecsSystem Spec
.

08 Mar 2014   #2

Windows 7 X64
 
 

SFDiagnostictool grabbed files attached.


Attached Files
File Type: zip rogster.zip (1.07 MB, 3 views)
My System SpecsSystem Spec
08 Mar 2014   #3
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Code:
BugCheck D1, {fffffa804a6a2f80, 2, 0, fffff88000e2a520}

Probably caused by : ACPI.sys ( ACPI!memcpy+60 )

Followup: MachineOwner
---------
Upload the list of all the third party drivers Using NirSoft DriverView :
  • Download and execute Driverview
  • View > Hide Microsoft Drivers
  • Edit > Select all
  • File > Save Selected Items
  • In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
  • Zip the .txt file and upload it.
My System SpecsSystem Spec
.


08 Mar 2014   #4

Windows 7 X64
 
 

Here you go


Attached Files
File Type: zip Driverview.zip (2.5 KB, 1 views)
My System SpecsSystem Spec
08 Mar 2014   #5
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Not finding anything there which I was suspecting.

So we have to take an alternative way.

First step, Disable hibernate. Then observe if the D1 BSODs are still occurring or not. Let us know at the very first instant.
My System SpecsSystem Spec
08 Mar 2014   #6

Windows 7 X64
 
 

Hybernation is already disabled, just double checked in registry editor.

Did a few SSD tweaks the first day my system was built, disabling hybernate was on the list.

I didnt do any SSD tweak i hadn't already done on my last windows build 2 years ago though....that system never had a single problem.
My System SpecsSystem Spec
08 Mar 2014   #7

Windows 7 X64
 
 

Here you go, another BSOD just now.


Attached Files
File Type: zip rogster 2.zip (767.9 KB, 2 views)
My System SpecsSystem Spec
09 Mar 2014   #8
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

The same thing continues.
Code:
BugCheck D1, {fffff8801def43c4, b, 8, fffff8801def43c4}

Probably caused by : ACPI.sys ( ACPI!READ_PM1_STATUS+23 )

Followup: MachineOwner
---------
ACPI may be a issue, but not for the ACPI.sys file. Something else must be playing there.

As the bugcheck code is D1 which indicates a driver issue, 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
10 Mar 2014   #9

Windows 7 X64
 
 

Ok will do.

Just fyi, i threw two 8gb modules(matching of course)of 2400mhz ddr3 corsair vengeance into my rig the night before last, and havent suffered a single BSOD since.

But i'll update if needed, and i really appreciate the help up to now.
My System SpecsSystem Spec
Reply

 BSOD on new build - Increasing memory volts stabilised for 12 hours




Thread Tools



Similar help and support threads for2: BSOD on new build - Increasing memory volts stabilised for 12 hours
Thread Forum
Solved Increasing memory decreases Windows Experience Index Hardware & Devices
Increasing incidence of BSOD on MSI GT683 - suspect memory problem BSOD Help and Support
Increasing Dedicated Video Memory for Dell Laptop Graphic Cards
Memory & System Handle count constantly increasing Performance & Maintenance
increasing virtual memory in windows 7 Performance & Maintenance

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 08:45 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33