Alright, so I'm back. Again.
So I tried the msconfig trick and it worked for about a week, then the same thing started happening again.
So I ran through verifier again, and it BS'd to an error of IRQL Not Less or Equal. Now whenever I try to run outside of Safe Mode, it blue screen's to that on a consistent basis.
Here is the jgriff dump for it. And I'm about ready to rip the motherboard and processor out, get the ram and video card out and rebuild. This is absurd.
Well I don't see any more of those dreaded firmware errors since April 20th. I don't know if that's good news or bad, though. I don't see any clues as to what the error is in this report. We're down to just swapping out parts now, I'm afraid. If I had to recommend a single part you purchase, it would be the motherboard, but if you can borrow a PSU, CPU, or RAM, that would also be good.
Is it possible that MSE could be causing this error and / or issues that I'm experiencing?
I've seen reports from other individuals having this issue and it seems to almost always be a third party software, network adapter, or an issue with antivirus software, is why I am asking.
I've recently replaced the RAM, so I can scratch that from the list. Unfortunately, I don't have any way of borrowing a PSU or CPU from anyone else, so I'd like to narrow it down as much as possible and not end up buying an entire new system to try and get this resolved.
The Verifier_Enabled dump points to dxgkrnl.sys, a Windows system driver. We can pretty much assume the problem is with hardware as a result.
I've never seen MSE cause a crash before, in the time I've been looking at BSODs (January 2010). I'd be very surprised if MSE were to cause a crash now.
If I'm not mistaken that particular file is a Direct X system file.
I'll go ahead and download the newest Dx redistributable and install it before I look at replacing hardware, see if that clears everything up. It might very well be the problem, as the issues started again after I installed a demo of another game on Steam and after a little over a week of solid stability. I'll post again and keep you updated Mr. King. Thanks again for the assistance.
Edit: I've also found some information on the evga forums stating that there is a known issue with Windows 7 SP1 and eVga Precision running during 3-D application use ( gaming ) that is causing issues with locking up. I'm thinking this might also be an issue, as I always have Precision running when I'm gaming. I'm going to test for a few days without Precision running while I'm doing said gaming on Rift, and see if the situation improves. I'll keep everyone updated.
Last edited by BearCave54; 04 May 2011 at 13:32.
I've also found some information on the evga forums stating that there is a known issue with Windows 7 SP1 and eVga Precision running during 3-D application use ( gaming ) that is causing issues with locking up. I'm thinking this might also be an issue, as I always have Precision running when I'm gaming. I'm going to test for a few days without Precision running while I'm doing said gaming on Rift, and see if the situation improves. I'll keep everyone updated.
Don't bother with the DirectX package; the problem is not actually being caused by DirectX. It certainly won't hurt to give the EVGA Precision removal a try though!
So the system freezes are happening FAR less frequently now, though they are still occurring and I think I might have found another issue.
This is the RAM I am using: Newegg.com - G.SKILL Ripjaws Series 12GB (3 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL9T-12GBRL
Now when I go into evga e-leet tuning utility, it has my timings for that RAM set to the following:
CAS Latency: 6 clocks
tRCD: 6 clocks
RAS Precharge: 6 clocks
Cycle Time: 19 clocks
tRFC: 86 clocks
Command Rate: 1T
The specifications for that RAM on the website state that it should be running at a timing of 9.
So my question is, with it running that low, could that be causing system instability as well? And if so, how do I change the timings? I've made it a point for a good long while to never mess with anything like that, due to a lack of comfort with it and knowledge. And the above timings are what it has set the ram for upon installation.
Boot to the BIOS setup, and enter Frequency/Voltage Control > Memory Feature, and change tCL to 9.
http://www.evga.com/support/manuals/...32-BL-E758.pdf
Worth a shot, certainly.
Quote