New
#41
Get to know your board. Asus
M4A785TD-V EVO
With onboard video
Do some reading.
Try the things that I mentioned and then we will see.
Last edited by Zardoc; 19 Mar 2011 at 19:42.
Get to know your board. Asus
M4A785TD-V EVO
With onboard video
Do some reading.
Try the things that I mentioned and then we will see.
Last edited by Zardoc; 19 Mar 2011 at 19:42.
so should I download and install the chipset driver from the Asus site?Get to know your board. Asus
M4A785TD-V EVO With onboard video
Do some reading.
Try the things that I mentioned and then we will see.
Sent from my Nexus One using Tapatalk
Ok. So I installed my video card into the computer and installed the latest video drivers. I shut down the computer for around 4 hours. When I came home I turned it on and as soon as it got to the windows loading screen it BSOD. The first time it was 0x7F. I restarted the computer and booted again. At the same spot it BSOD. This time it was 0x7E. I restarted again. Same spot it BSOD. This time it was 0x19. I restarted it one more time and again at same spot it BSOD. This time it was 0x7E. After the fourth one I turned off the computer with the switch on the PSU. I unplugged the hard drive power and sata cable and then plugged it back in. I turned the computer back on and it booted into windows without any BSOD and I'm on it right now typing this. I've run multiple hard drive tests and they all pass. Would this be motherboard related?
I've run every single test that was recommended and none of them produced any errors.
I just turned the computer back on after having it off a couple hours and this time it made it to the windows welcome screen and BSOD. I did it twice and both times it gave 0x1E and I was able to get system dumps. I then shut off the computer, unplugged the power and sata cable from the hard drive, plugged it back in and booted up the computer. It booted into windows and is running fine.
I'm also running driver verifier fyi if that helps reading the dumps
Last edited by mgorman87; 12 Mar 2011 at 22:06.
mgorman, first of all I want to thank you for filling out your System Specs.
I would like to concentrate on the memory that is installed on your machine, and rule it out once and for all.
All of your stop errors are related to memory and/or the way the memory is handled.
From the way you describe the symptoms the system is not handling the release of memory when it is being shutdown, and occasionally it affects startup.
I notice in the one CPU-Z-SPD tab report here That the stick is installed in slot#3. Have you tried running this stick in any of the other three remaining slots?
And, if you did not rotate the stick as suggested here under Technical Information in Troubleshooting Memory Errors while running the memtest86 your test results are inconclusive.
I ask this because one MB I had was very particular where the memory was installed, and it took me several hours before I found the right combination and the MB would run properly.
If you have kept this stick in slot#3 the entire time we have been trying to troubleshoot, here is what I want you to do.
Remove the stick, and install it in slot#1.
Use the machine like you have described; with the rebooting after an hour, several hours, and/or immediately after you make the change, and observe the result, does it increase/eliminate the BSODs or no change?
Then try slot#2, and #4 in the same manner, and observe the result.
Please post back on your findings.
There is also a distinct possibility that your MB will have trouble in running only one stick of ram.
Crucial, the memory company is ambiguous on whether or not your MB requires a matched set of ram. See here
In the Manufacturer Specs section it states:But, a little lower it states:Although the memory can be installed one module at a time, the best performance comes from using matched pairs of modules.Although Windows 7 can run on one 2GB stick of memory I feel your machine is being starved for ram. it is like putting a two barrel carburetor on an automobile racing engine, and until you can obtain another stick of G.SKILL 1x2GB DDR3-1333 or a matched set of at least 4GB from a friend or family member this issue of stop errors will never go away.Q: Do I have to install matching pairs?
A: No.
No, you can install modules one at a time, and you can mix different densities of modules in your computer. But if your computer supports dual-channel memory configurations, you should install in identical pairs (preferably in kits) for optimal performance.
Q: Does my computer support dual-channel memory?
A: Yes.
To benefit from the performance advantages offered by dual-channel systems, you should install memory in identical pairs. Installing a kitted pair is the best way to ensure that your modules are identical, right down to the chip count.
I have tried it in slot 1 and the same results but that was in the beginning before I corrected the other issues. I will try moving them to different slots. Also, this memory was originally purchased as a pair but the owner lost the second stick. I will have to purchase another set of memory sticks and try that.
Does the memory that I have need to be listed on the list of compatible memory for the motherboard or is that not important?
Also, I ran Hot CPU tester and the Complex Matrix test returned an error that said cpu (0) checksums do not match and then I ran it again and it said cpu (1) checksums do not match? I can upload the log when I get home from work.
Do my symptoms have anything to do with a bad CPU?
EDIT: I also noticed that the memory I have is rated as DDR3 1600 (800 MHz) yet it is only running at DDR3 1333 (667 MHz).
I came across this thread. It explains exactly the problem im having.
Asus motherboards + G.Skill memory: Cold boot issues and possible workaround - GSKILL TECH FORUM
It states that certain ASUS motherboards have issues with G.Skill memory where you get BSOD on cold boots. I am going to purchase a pair of corsair memory (same speed) and see if the problem continues.
@Anak
It has a 500W PSU and I have nothing installed in the computer except for HDD and memory. I will test it though and report back.