Good information and trouble shooting so far.
I am not overclocking any of my hardware.
Tried to run chkdsk and as it was going through it BSODed. Rebooted in safe mode and attempted to run chkdsk in there. BSODed again. Neither time did it come anywhere close to finishing the test.
When I went to boot my computer to run Seatools (I’ve been using my laptop to access the internet and post and only turning my computer on to run the tests since it tends to BSOD after sitting there and hour and I don’t want to damage it) it froze after the windows logo came up but before the blue logon screen. I had to do a hard restart. After that it logged on fine but I shut it down normally.
I have used several of those stress tests in the past and never had problems with overheating or crashing. I’ve used furmark before and usually have Coretemp running in the background, which monitors CPU temp. My CPU temp holds steady at 28-31 C at idle. Overheating hasn’t been a problem ever in the past for me, though I realize something could have broken in the interim.
Good steps, always a good idea to start eliminating the hardware.
Sorry for not following directions entirely but I was following my earlier hunch and removed my two extra memory modules. After doing this my system has become more stable. Since doing this I have been able to run the tests you told me too w/out getting BSODs.
Since you have four RAM slots and 12GB RAM, did you buy them at the same time?
Same brand and frequency and timings?
Did you leave the 2x2GB cards or the 2x4GB cards installed?
This can sometimes be fixed by adjusting the RAM settings.
Can you
download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.
I went back to the SFC scan you told me to run and ran it from within windows (I made a repair disc and tried to do it from boot but when I get to the part to select which operating system to fix it doesn’t show my install. I know you can load drivers for your HDD so I checked online to find ones for my HDD and none exist. So since I can’t see it in the boot version I just tried to do it within windows. Maybe this is caused by having a dualboot?). Running The SFC scan w/in windows it did say it found corrupt files and was unable to fix some of them. So I ran it again as the tutorial instructed. Same thing, some corrupt files unable to fix. I ran it 2 more times with the same results. I’ve attached the log from the scans.
The last thing I did was run chkdsk as instructed. Chkdsk completed without any issues or crashes. It told me it the drive was clean. While it was running it didn’t report any damaged sectors or files.
Again I’m sorry for not following directions. I was just worried that all the BSODs would damage my computer and doing the tests always resulted in a crash so I thought to avoid that I’d try this. My initial tests in memtest 86+ showed all my memory was good but I tested them all in the same slot. Which means that if the memories all fine then it might be one of the dimm slots on my mobo.
The problem may be caused if the repair disk was made from a non SP1 version of Windows 7.
What is your other dual boot OS?
Do you have a OS image backup?
I further tested this by redoing the the memtest86+ and the RAM checks out. I haven’t had any issues since pulling the memory out of the extra dimm slots and even have swapped some memory with it and it’s been stable.
Always test RAM in different slots.
Did you run memtest86+ with all four RAM cards installed?
How many passes did you let memtest86+ run for on the previous tests?
Do you still only have two RAM cards installed?
Post the CPUZ and BIOS setting info requested and we can adjust the settings to see if that will help.
Your last crash:
Code:
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
IMAGE_NAME: nvlddmkm.sys
FAILURE_BUCKET_ID: X64_0xD1_nvlddmkm+12b04e
This may be caused by the RAM issue.
You may want to uninstall your Nvidia driver, run Driver Sweeper, then install a new version.
Your System Event Logs stopped in July, so no current useful info there.
Same for the App Event Logs which stopped in September.
Code:
Unloaded modules:
fffff880`0a5d2000 fffff880`0a5d8000 RTCore64.sys
This driver is known to cause crashes in Windows 7.
If you have any ECS utilities installed, un-install them for testing purposes.
Also, RivaTuner or MSI Afterburner.
Code:
Unloaded modules:
fffff880`0a001000 fffff880`0a1f9000 EX64.SYS
Looks like you may be having issues with Norton Anti-Virus, we can look at that later.
Code:
tdrpman.sys Mon Nov 12 21:36:33 2007
tifsfilt.sys Wed Aug 29 20:37:29 2007
timntr.sys Wed Aug 29 20:38:23 2007
This driver is out of date and should be removed.
What version of Acronis or Seagate DiscWizard are you using?
If you're using
Seagate DiscWizard They have a new version available (V.14387).