Constant BSODS, Issues booting, erratic Video Card Fan on boot, etc.

[writhziden]

The first four (last four upside down) items that show up as AUTO in the list of your upside down image are what need to be changed. The first four (TCL, TRCD, TRP, TRAS) should be 9-9-9-25

 

[Dave76]

I decided to enter the bios to see if anything had changed and something had. As you can see in the second attached picture, the bus frequency was set to 200 and the PCIE was set to 100. The time prior to this they were both set to auto. I was not given an option to change them back to auto, they were restricted specifically to a range (200-600 for the first one, cant remember the second one).

These will show when you set the AI Overclocking Tuner to Manual.
They are at the standard stock settings.
Don't worry about them.

As writhziden mentioned, change the first four RAM timings.
Just select them and you can enter the numbers.
Change the first four and leave the rest on 'Auto'.

 

[aquitas]

3 days ago, after reading writh's post I set those four settings to specified 9 9 9 25, crashed today while playing a game. DMP file attached. "Memory Management".

//edited.

 

[aquitas]

So I assume you guys have given up. For the record i found something very strange. I was looking through my order history on newegg and noticed that he ram i purchased was ddr3 1600 but you suggest i run my ram at 1333 which I assumed at the time was because you thought my ram was 1333. So that must mean that either you are wrong and my ram is really 1600 or newegg gave me the wrong ram. Assuming you were right and the build is still crashing (i have the timings still set to what you requested) or I should try the timings at 1600. The board specs on newegg says 1600 (o.c.)/1333 so I'm assuming either would work.

This is all interesting for me because i'm thinking of getting more ram and a new motherboard and I figured i would try to get ram of the same speed and timings as my current ram to save a little money and to possibly replicate these crashes with separate but identical hardware.

 

[writhziden]

Sorry you fell through the cracks. Dave probably thought I would analyze it and I probably thought he would or maybe we both missed that you uploaded an attachment. Whatever the reason, my apologies.

You were asked to run at 1333 because 1600 RAM is not compatible with your processor. Your processor can only reliably support 1333 RAM. AMD Phenom :

Integrated DRAM Controller with AMD Memory Optimizer Technology
[*]A high-bandwidth, low-latency integrated memory controller

• Supports PC2-8500 (DDR2-1066); PC2-6400 (DDR2-800), PC2-5300 (DDR2-667), PC2-4200 (DDR2-533) or PC2-3200 (DDR2-400) SDRAM unbuffered DIMMs – AM2+
  
  
• Support for unregistered DIMMs up to PC2 8500(DDR2-1066MHz) and PC3 10600 (DDR3-1333MHz) – AM3
  
  
• Up to 17.1GB/s memory bandwidth for DDR2 and up to 21GB/s memory bandwidth for DDR3
  Benefit: Quick access to system memory for better performance.

Running 1600 RAM at 1600 MHz may damage your processor, your RAM, the motherboard, and/or the power supply over time since it is essentially overclocking the processor to run at that speed.

System Building and Compatibility


The crash report you uploaded indicated memory_corruption, so it was probably still memory related.

 

[aquitas]

Ah it was the processor limiting the speed. So.... based on the BSOD, could be the ram, could be the ram slots?

 

[writhziden]

Have you changed your BIOS settings as requested by Dave and I? Timings, voltages, etc.?

Have you tried a different PSU?

Are you able to start with any configuration other than slots 2 and 4?


Dave is very good with these problems, and his suspects were the CPU and PSU. You have not yet stated whether you addressed those concerns.

 

[aquitas]

I have changed the settings and it has crashed since (see previous posts). I am not able to start in any other ram configuration. I'll try a different PSU soon.

 

[writhziden]

Try to borrow a PSU from a friend, or if you do buy one, make sure you but it from a store that will allow you to return it for a full refund if it does not solve the problem.

The fact that you cannot start in any other RAM configuration is worrisome. I would recommend contacting both the motherboard manufacturer and the processor manufacturer for troubleshooting steps.

 

[Dave76]

I have changed the settings and it has crashed since (see previous posts). I am not able to start in any other ram configuration. I'll try a different PSU soon.

Can you please confirm the settings you have changed?
It will help us to know exactly what has been done, so we will know what to try next.

I have just re-read the entire thread, there are several suggestions that have been asked and there is no clear answer what the procedure/results were.

Your biggest issue is the RAM channel A being dead, this can be a settings issue (not likely in this case), CPU or motherboard issue. Remotely possible damage caused by bad PSU.

As mentioned previously, your PSU is suspect, test with other known good PSU if possible.

Are these the settings you changed?
Can you confirm each step?

Do you have 'Driver Verifier' enabled?

What PSU do you have?

Did you seat your CPU in the new motherboard?
Bent CPU pins can cause these type of issues.

Agree with writhziden, set your RAM to 1333MHz to see if it will boot.
If writhziden's post above is your CPUZ snips, then you are at 668.9 MHz which is close enough to 1333 MHz.

@meepster, what are/were the exact settings you manually entered?

Download your motherboard manual if you don't already have it: ASUSTeK Computer INC. M4A78T-E

If one RAM card won't post in slots 1 or 3, this is indicating a CPU IMC (Integrated Memory Controller) memory channel issue as that is channel A.
RAM slots 2 and 4 are channel B.
Normal position for your motherboard with two RAM cards is slots 1&2 (counting from the CPU outwards), the orange slots. When running two RAM cards you need to have one in channel A and one in channel B. Slots 1&2 (preferred) or slots 3&4.
View attachment 216856 View attachment 216857
Your motherboard is listed as compatible on the G Skill site: F3-12800CL9D-4GBNQ (2Gx2)
That doesn't mean you don't need to adjust some settings to get it to work correctly.

In your BIOS:
Go to 'DRAM Frequency Control' manually set it to 1333 MHz.
Go to 'CPU/NB Voltage' manually set it to 1.20v.
Go to 'DRAM Voltage' manually set it to 1.60v.
Set your first four RAM timings manually to 9-9-9-25.
Set the 'DRAM Command Rate' manually to 2T.
Save and exit your BIOS.

First have only one RAM card installed in slot #2, this is to ensure the system will still boot, as it did before.
If it boots, then shut down, install one RAM card in slot #1, re-boot.
If it fails then I would say you CPU IMC (Integrated Memory Controller) is damaged or not able to function.
This could be due to a bent CPU pin.

Let us know the results, or if you have any questions.

Have you checked the CMOS battery?
Download HWiNFO64
Click on the 'Sensors' button, scroll down and post the 'VBAT' voltage.
Should be above 3.0v.

Do you have any Asus utilities installed?
Un-install them for testing.
They are known to cause system instability.

In response to previous posts:
Re-placing hardware doesn't mean the new hardware is guaranteed to work correctly, it is rare to get two bad components in a row but, it has happened and will happen again.
With new hardware, if the issue isn't resolved, the same tests need to be repeated.

As mentioned previously, you may need to install older graphics drivers, some new drivers are just not stable, others will have issues with certain hardware, so you may need to test several.

I didn't see anywhere in the test where it allows you to change the amount of times the test run passes, i must have missed it?

Memtest86+ will run until you stop it, if it stops on it's own, that is a failed test.
You need to run a minimum of seven full passes, this will take up to 8 hours, best to run overnight.


In conclusion:
I will research for further information, please reply with full details of what you have and have not tried.
It is your computer and you are the one that ultimately decides what you will do, just keep us informed.

Let us know if you have any questions.

 

[aquitas]

Attached:
-All dump files dating from beginning of thread to
todays date

-pictures of current bios settings

-pictures of HWiNFO64 (don't ask why I used a camera
instead of a screenshot, I wasn't thinking)


Software/Driver Consistency/Stress tests done:
-all suggested in this thread with ample passes
(although the hard drives I only tested on three
occasions for 10+ passes, still very thurough)

What I have tried:
- Bios settings are as requested (sometimes after
reboot after crash I get message from board that it
is unable to overclock, from there I either reset it
to default after which it eventually crashes, or i go
into bios settings, confirm that none of the settings
are different than you suggested, let it boot, and
then it eventually crashes)

- Bios update

- No MOBO software/asus utilities (EPU, Cool & Quiet,
Turbo V, etc)

- Flashing bios

- Verbal threats

- Domestic Abuse

Hardware tests in order:

- Ram (three different types/capacities) in all
possible slot configs. None boot except slots 2 and
4, crashes occur with all sticks

- 2 different video cards, both with drivers updated

- 2 different hard drives

- crashes occur in all combinations of the above
mentioned



What am i currently trying?:

- Different power supply (with suggested bios
settings) - does not boot with any ram configuration
other than slots 2 and 4

- Different power supply (with suggested bios
settings) - will run with original sticks of ram in
slots 2/4 until it crashes again, will post crash
log, then will try with one stick in 2 until crash,
one in 4 until crash, and have 2 other sticks of a
different brand to try as well, will update post with
new crash logs as they occur - hopefully this will
confirm ram is or isnt the issue


Other notes:

-CMOS battery in good shape

-Driver Verifier has been disabled since the post
where it's use was suggested

-Have run memtests 3 times all over night 3 nights

This took a while to type so it's possible I left out some information you wanted. If you need more detail let me know. Sorry for weird format... typed up in notepad.

 

[Dave76]

Thanks for the info recap, it helps.

The biggest concern is the RAM channel A is not working.
This could be due to CPU bent pins, only way to check is to remove the CPU and do a visual inspection. You must re-apply new thermal paste when re-installing the CPU cooler.
Other possibility is a bad motherboard, possibly RAM slots.
Best way to check is to put another CPU in your system or your CPU in another system, let us if this is possible.


What BIOS version are you using now?
We need to check if the BIOS version is 'Beta' or we may find that a particular version is unstable.

What is the CMOS battery voltage?
We have seen in other threads, several pages later, an issue that was thought to be 'ok', turned out to be significant.

There are a few RAM testing programs with 'memtest' in the name, some of them aren't so good, is the one you used 'memtest86+'?

The memory clock in HWiNFO64 is off also, it's showing that it is set in BIOS at 200MHz.
Either CPUZ and HWiNFO64 aren't programed for your motherboard or there is a motherboard or BIOS issue.
Can you post the HWiNFO64 Main Page - Memory, under 'Current Performance Setting' snip?

Sounds like it might be the CMOS battery or a issue with BIOS, could be the programs aren't reporting correctly.

Download OCCT and run the CPU:OCCT test for 30 minutes.
When the test is finished or fails it will generate some graphs, post these graphs when you get them. This may give us a bit more information to work with.

 

[aquitas]

I feel like every time I troubleshoot an issue that I report to you, a new issue comes up before I can start troubleshooting. This is the case. Tried to boot this morning, now the OS BSOD's before I can log in. PAGE_FAULT_IN_NONPAGED_AREA. Pretty straight forward. Happens with all possibly bootable configurations of RAM. Only doesnt bsod when i boot from a different drive. Issue resides in page files of main drive I'm assuming. Tried to repair with disk, BSODs before progress can be made. At this point I'm just hoping I can somehow pull my personal files off of the drive. I tried booting from my old drive while the possibly corrupted drive was still plugged in but didn't work. Couldn't give it boot priority in BIOS, only the corrupted drive showed up in the boot list. Switched the cables/slots and still wouldnt boot to old drive. Old drive will boot if it's the only drive plugged in. Whole thing is ****ed. Frustration like you wouldn't believe. Thinking of ditching the build and starting from scratch. Put together a build on pcpartpicker but am a little hesitant to purchase it given how poorly this build is holding up. Although i feel like i've learned a lot from my current build, I'd like some input from someone with more experience. Aside from r/buildapc do you know of anywhere where i can go to to discuss builds in depth? Assuming you can't give out advice on building stable builds.

 

[Dave76]

Is that the HDD you ran Disk check on?

Run SeaTools on all of your hard drives.

A failing HDD can cause many issues, you might be able to put it in another computer or external HDD case to get the data off of it.

It's a fairly generic crash code.

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

If you can get the crash files, I'll take a look at them and see if there is any better info there.
Blue Screen of Death (BSOD) Posting Instructions

Why would you think we 'can't give out advice on building stable builds'?
If you want to upgrade your system, I would get a new motherboard and CPU, also a new HDD and/or SSD, get a good quality PSU.
You can use your existing components like RAM, your working HDD, case, graphics card, monitor, keyboard and mouse.

Start a thread in the Hardware & Devices forum, include what you want, if you have any preferences, components you already have, and your budget.

You will get a lot of replies, everyone has advice on that topic.

 

[aquitas]

Thank you for your help. I'm going to make that post today. I'm fairly new to this website and was under the impression that discussion was limited to OS/hardware troubleshooting. Good to know! Given your knowledge of what my computer has been doing lately I wanted to ask you one more thing about my hardware before I decide what to order. I'm thinking that maybe I need a new case as well. When I press and hold the power down button sometimes the power shuts off like it should, but sometimes it powers down, but when i release the button it restarts the computer instead of leaving it off. I asked about this issue earlier in the post and it was suggested as a possible setting in the bios. My concern is that the wiring in the case could be faulty. I would like to know if I am putting any future purchased hardware (the motherboard where the cases cables hook into possibly at risk. Could other parts be damaged because of faulty case wiring?

If it's the case's wiring that is the issue I would have to replace the whole case (even though it's in great shape. Because several of the cables are soldered in place.

 

[Dave76]

Yes, it is possible that bad case wiring can cause damage. Check for loose connections on all the wiring.
The switch may just be bad.

What case do you have?

 

[aquitas]

I have the azza solano red/black version
Newegg.com - AZZA Solano 1000 Black/Black Japanese SECC Steel/Metal mesh in front ATX Full Tower Computer Case

Last time i cleaned it there was only one cable unattached, it went to a plug near the power suply that i never use(only one cable going into the cable wasn't soldered) I couldn't visably see damage. There are several plug in spots on the top of the case near the power button including speakers, headphones, usb, a reset button etc. When i wear headpohones plugged into that front jack i get a lot of extra noise through them.

 

[Dave76]

The headphone noise indicates a bad connector or loose wire.

You might try to replace the on/off switch and fix the other loose wire, taking it to a shop may cost too much, you will need to decide if the money is better spent on a new case.

Keep us informed on what you plan on doing.

 

[aquitas]

I decided to scrap the old build case included. I took what I could from it, (the ram, the video card, and the two hard drives). My new build is fully installed. Looks and runs great. My OS is running on a solid state. I wiped my 500 gig and am using it for storage. The 1tb drive has a corrupted page file and nothing I have done has successfully allowed for me to do ANYTHING with the drive.

The issue is that it blue screens as soon as the mobo is done loading.

I've tried giving boot priority to my solid state, repairing, reverting to last known config, safemode, repair console, booting from cd, reimaging, repairing from cd, reverting from cd, all of them blue screen before repair, replacement, or access can be done. I even burned HDD Erase to a disk and tried to wipe the drive that way, wouldn't work (didnt blue screen with HDD Erase, just said failed). I'm completely stuck. I've never seen something this stuborn. Every suggestion I read for repairing/disabling/replacing the pagefile suggests that I do things that I can't do because it bluescreens before I can access the menu that their method requires.
I'm at a loss.

Here's an album of my new build! Glad0s Build - Imgur

 

[Dave76]

Can you update your 'System Specs' with your new components?
The pics look nice.

Is everything running fine except the 1TB HDD?
With the 1TB HDD disconnected it's stable?

Run Seatools on your Seagate 1TB HDD.
Download and run Seatools
How to use SeaTools for Windows
Short Drive Self Test and Long Drive Self Test.

If your system won't boot with the 1TB HDD connected, use the Seatools DOS version and install it on a CD or USB stick.
Seatools for DOS tutorial

Let us know the results and we can decide where to go from there.