I had an old Intel I5 670 lying around so I decided to put together a new build. I purchased the necessary parts from newegg/tigerdirect and put everything together without a problem. However, I ran into a problem that has plagued me for the last month. The specs are:
Intel i5 670
Asus p7p55D E-LX Lga 1156
G.Skill Ripjaws 4Gx2 DDR3 1600
Corsair TX750 PSU
XFX HD-687A-ZDFC HD6870 1gb
At first the system would randomly give me TDR (Timeout Detection and Recovery) Errors during which the screen would flicker and go black for 2 seconds and come back with the message: "Display Driver AMD Driver has stopped responding and successfully recovered." Before people start screaming "google it" I have and the same message can apply to errors having to do with all important computer components and I have tried everything google can offer that is why I need to make this thread.
I have tried:
Running stress tests on all components
Remove/Alternate Ram sticks and tried different slots
Changed voltages in the bios with default settings as well as overclocked CPU/RAm frequencies and voltages
At the moment I have resetted bios settings with the CPU running at 3.47 ghz and the ram running at 1333 even though I bought it to run at 1600.
So at the moment the problem deteriorated to no longer TDR errors but BSOD. I have gotten BSOD 3 times now running Bastion (the game) and Skyrim(game). This is the error message following the BSOD.
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.28
Locale ID: 1033
Additional information about the problem:
OS Version: 6_1_7601
Service Pack: 1_0
Files that help describe the problem:
I have a big case with ample fans and the temps are low. I am using latest GPU driver, latest bios version, and as far as I know latest drivers for everything else. All windows update installed except for foreign language packs.
Below is the information from the minidumps after BSOD (3 of them)
122711-18174-01.dmp 12/27/2011 2:39:45 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`02fddb51 fffff880`0caeae80 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\122711-18174-01.dmp 4 15 7601 275,520
ntoskrnl.exe ntoskrnl.exe+7c1e9 fffff800`02c68000 fffff800`03251000 0x005e9000 0x4e02aaa3 6/22/2011 6:53:23 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17640 (win7sp1_gdr.110622-1506) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe
122711-18392-01.dmp 12/27/2011 12:32:24 AM UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 fffff880`09605372 HIDCLASS.SYS HIDCLASS.SYS+5372 x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\122711-18392-01.dmp 4 15 7601 316,152
HIDCLASS.SYS HIDCLASS.SYS+5372 fffff880`09600000 fffff880`09619000 0x00019000 0x4ce7a665 11/20/2010 2:43:49 AM
ntoskrnl.exe ntoskrnl.exe+7c1e9 fffff800`02c67000 fffff800`03250000 0x005e9000 0x4e02aaa3 6/22/2011 6:53:23 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17640 (win7sp1_gdr.110622-1506) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe
122611-19032-01.dmp 12/26/2011 3:19:21 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`02666d58 00000000`00000002 00000000`00000000 fffff800`02cf1a93 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\122611-19032-01.dmp 4 15 7601 275,520
ntoskrnl.exe ntoskrnl.exe+26ee0 fffff800`02c65000 fffff800`0324e000 0x005e9000 0x4e02aaa3 6/22/2011 6:53:23 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17640 (win7sp1_gdr.110622-1506) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe
ntoskrnl.exe is just like it says:
NT - the backbone of current Windows Operating Systems comes from a version of Windows that was called Windows NT. This version of windows made security possible for Windows. Access can be restricted to resources depending on who/what is logged in.
OS - Operating System.
KRNL - Kernel. In a short form the model that Windows is built on looks kinda like this:
Operating System and Programs - Things users interact with. Users make requests at this layer which must be passed to lower layers.
Drivers - Tells Windows how to access the Kernel
Kernel - This is where the action happens. This thing knows what .exe even means.
BIOS and Firmware - Tells the next level above how to use the hardware
Hardware - Video Cards, Processors, RAM, etc
Some things included in the Kernel include: hardware virtualization, process and memory management, the Cache Manager, the Executive, the Security Reference Monitor, the Memory Manager, and the Scheduler.
All of those things at their core allow a computer to operate. If you didn't have a kernel, you could never make a computer do anything.
If the user program's and anything with sound and graphics were leaves and the hardware itself was roots, the Kernel would essentially be the tree trunk that everything must go through to get from one end to the other.
I just reinstalled windows 7, reset bios, downloaded all newest drivers for everything, even disconnected some things like the extra top fan, the media card reader. I also reseated the GPU, put the two RAM sticks into the other two slots of the motherboard, I am still getting BSODs. This time they all reference stop code 7f like so:
Additional information about the problem:
These are the bluescreenview results:
122911-21668-01.dmp 12/29/2011 9:39:28 PM UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 fffff800`02da08e7 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\122911-21668-01.dmp 4 15 7601 275,512
ntoskrnl.exe ntoskrnl.exe+3938e7 fffff800`02a0d000 fffff800`02ff6000 0x005e9000 0x4e02aaa3 6/22/2011 6:53:23 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17640 (win7sp1_gdr.110622-1506) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe
I read elsewhere that someone else with the same motherboard and the same errors BCCode A & 7F and the fix was a one shot purchase of motherboard, RAM, and PSU.
They didn't buy these things individually, but the problem was solved by doing this.
Especially the 7F seems to be focused mainly on failing hardware.
The people on the other forum having this problem did go through the logs and tried in earnest to fix it as if it were a software problem by uninstalling programs and changing their anti-virus provider and other things and none of it worked.
You might want to think about the potential of chasing hardware rather than continuing on with software.
You aren't OCing or anything are you?
Also, you might want to try manually underclocking things in the BIOS to see if it increases stability before you make any hardware changes.
I wish there was more I could tell you at this moment, but there doesn't appear to be to many other things to try.
If you have a similar computer you could borrow parts from, that would help narrow down the cause and keep you from replacing something that works.
Yea I read through a lot of forums of people with similar issues and there doesn't seem to be a resolution. I also noticed that many people with this problem also have newly built systems so I'm thinking some kind of hardware failure or incompatibility. However, I don't have spare parts to test out and narrow down the culprit. I am hoping it is either RAM or GPU because I can replace those with relative ease through warranty and such. I would hate for it to be the motherboard because that is a pain to replace and there is no guarantee the replacement will work.
Initially I OCed the CPU to run at 4.0 GHZ and everything checked out fine with stress tests and stable temps. However I did that immediately upon building the system so there is no point of reference. After the problems started happening I resetted everything to stock clocks but the problems persist.
Everything i'vre read realy says videocard problem, either with the drivers or the card itself. Have you tried the system with another card? Also good is to test the card in another system to see what it does.