This seems to be a hardware issue. Please proceed with HW testing: Hardware Diagnostics
Code:0: kd> .bugcheck Bugcheck code 0000000A Arguments 00000000`d2afc082 00000000`00000002 00000000`00000001 fffff800`d26c1f4e //Memory not present, either pageable, or invalid when accessed at IRQL 2 0: kd> kn # Child-SP RetAddr Call Site 00 fffff800`d403d5b8 fffff800`d27e55e9 nt!KeBugCheckEx //BSOD 01 fffff800`d403d5c0 fffff800`d27e3e3a nt!KiBugCheckDispatch+0x69 02 fffff800`d403d700 fffff800`d26c1f4e nt!KiPageFault+0x23a //Page not present in memory, cannot write to address 03 fffff800`d403d890 fffff800`d273605a nt!KiDeferredReadyThread+0xee //Schedule thread for execution 04 fffff800`d403d9e0 fffff800`d27dd5ea nt!KiRetireDpcList+0x8fa //Drain DPC list 05 fffff800`d403dc60 00000000`00000000 nt!KiIdleLoop+0x5a //Processor asleep, waiting for instruction MODULE_NAME: hardware //Not necessarily hardware, but certainly a misaligned instruction pointer, could be a number of things //Bad RAM, written to wrong address (caused by bad IP in DPC object), failing CPU (probably ALU) FAILURE_BUCKET_ID: IP_MISALIGNED
It's very difficult to say what the problem is, it could be multiple things, although a hardware failure may well be possible.Code:0: kd> .bugcheck Bugcheck code 0000001E Arguments ffffffff`c0000005 00000000`00000082 00000000`00000008 00000000`00000082 0: kd> kn # Child-SP RetAddr Call Site 00 fffff801`3bc3c768 fffff801`3a3f36fa nt!KeBugCheckEx //Bugcheck, exception not handled 01 fffff801`3bc3c770 fffff801`3a368fed nt!KiFatalExceptionHandler+0x22 //Fatal exception, terminate process 02 fffff801`3bc3c7b0 fffff801`3a2ebd35 nt!RtlpExecuteHandlerForException+0xd //Transfer control to exception handler 03 fffff801`3bc3c7e0 fffff801`3a2f00ee nt!RtlDispatchException+0x1a5 //Run time library control 04 fffff801`3bc3ceb0 fffff801`3a36d6c2 nt!KiDispatchException+0x646 05 fffff801`3bc3d5a0 fffff801`3a36be14 nt!KiExceptionDispatch+0xc2 //Dispatch exception to handle fault 06 fffff801`3bc3d780 00000000`00000082 nt!KiPageFault+0x214 //We hit a page fault, memory not present 07 fffff801`3bc3d918 fffff801`3a39d7f4 0x82 //Looks like KiInitialThread function 08 fffff801`3bc3d920 fffff801`3a2b0286 nt!PpmIdleExecuteTransition+0x2b844 //Wake processor, transition from power state, probably C state 09 fffff801`3bc3db10 fffff801`3a3655bc nt!PoIdle+0x2f6 //Power idle 0a fffff801`3bc3dc60 00000000`00000000 nt!KiIdleLoop+0x2c //Processor asleep, waiting for instruction
Looking at your older dumps, if they're related then this is probably bad programming code in a driver/drivers.
Update your GPU drivers as stated previously.Code:0: kd> .bugcheck Bugcheck code 000000D1 Arguments 00000000`00000000 00000000`00000002 00000000`00000008 00000000`00000000 //Execute instruction at an IRQL of 2 using a null IP 0: kd> kn # Child-SP RetAddr Call Site 00 fffff801`a0b625d8 fffff801`9efd25e9 nt!KeBugCheckEx 01 fffff801`a0b625e0 fffff801`9efd0e3a nt!KiBugCheckDispatch+0x69 02 fffff801`a0b62720 00000000`00000000 nt!KiPageFault+0x23a //Typical minidump, basically no information saved
I suggest you configure your settings to create a complete memory dump, and enable driver verifier.
Make sure you enable Force IRQL checking, that seems to be a common problem.
Thanks for responses will try the suggestions and see how things go. Will get back to you helpful ppl tomorrow.
getting more crashes than usual with the new video drivers... just enabled complete crash dumps and force irql and will report back with the data.
edit: just went through memtest prime and furmark. No problems there. Guess I am just waiting for a crash right now gaming with a complete dump
Last edited by hel1011; 28 Jan 2015 at 00:37.
The latest driver for your N670 PE 2GD5/OC card from MSI was 10-31-12, for Win8. They really don't keep up to date with them, do they?
From Nvidia, the latest is much more current (assuming 64bit architecture!): NVIDIA DRIVERS GeForce Game Ready Driver WHQL - You might try removing the old driver completely, restarting, and then installing this new one. But that may be besides the point, as the crash dumps are the focus at this point.
Take them out of SLI mode and see if you get an improvement. I noticed that held mine back at one point.
Could be a driver issue...
It looks like the driver is creating the problem long before the crashes, by implementing the bad code into a DPC routine, then doing something else; when the processor comes to drain the DPC queue on the target processor, each DPC routine is executed, resulting in the bad DPC executing and crashing the system.
That being said, the processor involved in the crash is consistently the primary core, which could be the cause of the problem, meaning you might have a failing CPU. It's difficult to say exactly at this time, so we need a dump file.
Hey all, thank you for the continued help. I had one crash yesterday but the complete dump did not save since I had less than 25gb free space. I have freed up hdd so the next time i should be good to go. The crash however did say that it came from the nvidia driver in its short report (the newest driver 347.25). I switched the position of my video cards on my mb but it still crashed. Maybe I should update my bios? Haven't done that in a year or so
After viewing your files I noticed multiple WHEA errors (power related issues eg., PSU, overclocking, wrong voltage settings). One of the first things that came to mind was taking a look at your hardware, specifically your video. The reason your computer only has the BSOD when you game is because of the power consumption on load from your graphic cards in SLI matched with other hardware components such as your CPU, ram et al. There are one of two ways to rectify this situation, and alleviate you of your troubles. The first solution is remove one of your MSI 670 graphics card's from your motherboard. The other solution is replace your 750w psu and purchase a power supply unit in the 1000w range, 1200w might be overkill but at least you'd be in the safe zone. Keep us updated.
Just upload any new dump files when possible.
You do not need 1000w for your components, 750w is more than enough...
That is not the reason for his crashes, WHEA errors do not necessarily mean power issues. They simply mean a hardware component has failed, the CPU reported the error, transferred control to Windows which invokes the WHEA error handler, determines the type of failure and most likely bugchecks the system.
^750 is enough, but the PSU must actually support SLI and more.
Here is an excellent "how to pick the right PSU"... tutorial for you: How to Pick the Right Power Supply | Maximum PC