Windows 7 Ultimate 64-bit crash/BIOS crash

i have been having increasingly frequent bsods/ complete bios hangs"- ie the keyboard numlock does not even respond. Today i needed to restart enough times for my bios to check its NVRAM.

when the bsod started i didn't install any new software and last week i reinstalled windows 7 .after the re-install my pc ran fine for 4 days and i was back to square one.

i believe i have found a clue. I disabled cores 2,3,4 and my system now seems stable. I doubt its the cpu itself because the problem was postponed with the reinstalling of my windows

oddly enough my minidump folder is completely empty

Specs
ram : 2x2GB , DDR3 , dual channel
Cpu:AMD phenom II x4 965
Power supple: 550w - LPG-43
OS : windows 7 ultimate 64 bit
GPU:nvidia 9800 GT (problem existed also with a 6600le)
Motherboard:ASUS

PS: i have updated my bios to check if it solves anything and there was no change

Check these settings to see if it will then save future minidumps. If it then starts to save them, put them in a zip file and add as an attachment to future posts.

As the mindump file is empty your system is not set to save memory dumps. Follow this guide to set it up correctly.

I would also suggest you check that the voltage settings are correct for your RAM and CPU. You will need to find the recommended voltage from the manufacturer's site.

ok i did what you said i should do and i have also reanbled my other cores. PRoblem seems gone now as my pc is now running fine for more that 2 days without any glitches. i dont know what the problem was but it gone now.

You are now set to save any minidumps, if or when you have any more BSOD's, it will just be a waiting game to see if any more happen.

and the waiting game is over. I have had a few completly hangs and bsod between today and yesterday. attached is the three mini dumps that was created.

You have three different error codes from these minidumps. One states hardware, one states memory corruption and the other is inconclusive. The most likely cause is that you have faulty RAM.

Run Memtest86+ overnight and allow it to complete at least 8 passses or until it shows errors. Remove one of the sticks before running the test and then swap the sticks and repeat the test.

Hi,

Do you remember making any recent changes to the computer prior to this issue?

I would suggest you to follow the steps in the link and check if the issue persists:

http://windows.microsoft.com/en-us/windows7/Resolving-stop-blue-screen-errors-in-Windows-7

Also check event viewer for error follow the steps in the link:

http://windows.microsoft.com/en-US/windows7/What-information-appears-in-event-logs-Event-Viewer

@kristian nope I did not make any recent changes

@Mark56 i ran memtest86+ for 4 runs and it found errors. I removed one stick and ran memtest86 again. It ran for 22 runs without errors. So i rebooted into windows and 5 minutes later my pc restarted.it didn't generate a new minidump though.

i have tested my other ram module with 10 passes and memtest did not pick up any errors at all, and 5 minutes after booting with both sticks in my pc i get a restart

and here is *three more minidumps if that would help

here is some more hardware information from AMDoverdrive that may be helpfull in some way

I just want to confirm what you have done. After finding errors with both sticks inserted you removed one stick and continued the test for 22 passes and it found no errors. Yes?

When you rebooted had you put the other stick back in? If not try running the PC with just the single stick that memtest found no fault with.

The last three minidumps all suggest a memory fault but includes one that could be Malware (amongst other things)

-----------------------------------------------------------

If either stick is faulty this would be expected, you need to run the PC on the stick that memtest passed and leave the other one out. If that still produces crashes then we need to dig deeper as it is very unlikely that both sticks have errors.

From the memtest results it is clear that one of your sticks does have errors and should be replaced.

Another check you should make is that the RAM voltage is set in the Bios correctly. You will need to look up the recommended voltage on the Kingston site for your model of stick.

After scanning one stick for 22 runs and finding no errors i rebooted with only that stick and less than 5 minutes later my pc rebooted(was still loading apps and desktop stuff).
I even at swapped the sticks and did 10 runs on that stick and no errors were found.

i'll check the required voltage of the sticks and adjust them if necessary.

One weird quirk i forgot to mention is that memtest86+ detected my one stick as dddr1333 and the other as ddr400, which is weird since are a matched pair and have identical specs.

Hope that clarifies it

i justed checked and for my memory "KHX1600CD93/2G" the recommended voltage is 1.7v-1.9V and it was set to 1.590v. I incremented it to 1.605V. Will check stability and increment again if necessary.It will now be just a waiting game,again.

This incorrect voltage setting may explain some of the strange behaviour and misleading Memtest results. Can you set it higher so that it is within the recommended voltage as 1.605V is still below what it should be.

sure i can set it higher and i will in the future. I just have some weird fear of adjusting voltages, so i will slowly day by day increase it bit by bit.

There is nothing to fear from setting the RAM to the manufacturers recommended setting. Anything below what they recommend is underclocking the RAM and prone to cause errors.

As long as you do not go above the maximum recommended voltage you will be perfectly safe.

ok i tried setting it to 1.7v but it kept jumping back to 1.695V will try again tomorrow after my semester test by actually setting it in bios(currently adjusting via AMDoverdrive).

thanks again for everyone helping me out with my pc. I really appreciate it and i'll keep you posted if anything happens.

I would set it mid way using the Bios to 1.8V and see how it performs.

Only happy to try and help but we are not there yet.

and once again i spoke too soon , attached is the newest minidump