random BSODs, screen freezes

[ivanwakeup]

Hey guys,

I'm looking for some advice/help for a problem I've recently been having with my PC. For the past 1 or 2 months, i've been getting screen freezes and intermittent BSODs, particularly while gaming. I found this weird because I haven't upgraded or changed anything in the system in a few years now.

my system specs are:

intel i5 2500k @ 4.5ghz/1.33V (load temps with prime95 are 60C)
corsair vengeance 1600mhz 8gb ram
nvidia GTX460 (stock clocks, 78C load temp)
MSI PG67A-G43 Mmobo
seasonic 620W psu

most components are less than 3 years old, i think the GPU is about 5 years old now.

obviously my first thought was to test the memory, which i did. The RAM passed 10 hours of memtest86 with no errors, and also passed my mobo's built in memtest utility. my PSU seems to be supplying steady power. I did manage to get the system to freeze while running prime95 the first time, however i've since ran it 2 more times and I can't get it to produce any errors yet.

the problem generally only occurs while gaming, so i thought my gpu might be a problem. took it apart and reapplied thermal paste, temps dont go above 78C. I know the gpu is still old, so could this be causing the problems anyway?

any advice/direction would be greatly appreciated.

 

[Kraiden]

http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[ivanwakeup]

sorry, thanks for that. will post back with minidump shortly.

EDIT: main post now includes the proper files.

 

[Thedoctor44]

Looking at your dump files I see numerous different bugcheck stop errors.

They is no clear sign of indication but there is something that has caught my eye.
The image of a wifi driver is giving errors.

EXCEPTION_RECORD:  fffff880031b6778 -- (.exr 0xfffff880031b6778)
ExceptionAddress: fffff8800256d3fa ([COLOR="red"]nwifi!Dot11InitVElanRegistry[/COLOR]+0x0000000000000392)
   ExceptionCode: [COLOR="Red"]c000001d[/COLOR] (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

Now looking at your msinfo file I can see your wireless network driver.
Then using the crash dumps I can see that the driver is extremely old.
Update it here.

fffff880`07246000 fffff880`073c3000   athrx      (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        [COLOR="red"]Mon Oct 05 17:33:57 2009[/COLOR] (4ACA1FF5)
    CheckSum:         0017C3B2
    ImageSize:        0017D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I can also see that your MotionInJoy driver is causing issues.

Unable to load image \SystemRoot\system32\DRIVERS\MijXfilt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for [COLOR="red"]MijXfilt.sys[/COLOR]

Now I recommend removing this driver as it has caused a lot of issues but you could try an update first here.

fffff880`01ecf000 fffff880`01ef1000   MijXfilt T (no symbols)           
    Loaded symbol image file: MijXfilt.sys
    Image path: \SystemRoot\system32\DRIVERS\MijXfilt.sys
    Image name: MijXfilt.sys
    Timestamp:        [COLOR="red"]Sat May 12 05:27:12 2012[/COLOR] (4FADE6A0)
    CheckSum:         00022009
    ImageSize:        00022000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Avast is also causing issues.
Remove it using the uninstall tool.

Unable to load image \SystemRoot\System32\Drivers\aswSP.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
 [COLOR="red"]aswSP[/COLOR]+0x10c7b

Replace Avast with MSE and Malwarebytes.

   Warning

Do not enable the free trial of malwarebytes pro, make sure you deselect the option when asked.

You have had 0x124 errors but there is a possibility of a driver issue that caused it.
but we'll take a look anyway.

0: kd> [COLOR="Green"]!errrec fffffa8007e70028[/COLOR]
===============================================================================
Common Platform Error Record @ fffffa8007e70028
-------------------------------------------------------------------------------
Record Id     : 01cf6a7bb289e183
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : [COLOR="Green"]Machine Check Exception[/COLOR]
Timestamp     : 5/13/2014 17:42:07
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007e700a8
Section       @ fffffa8007e70180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000206a7
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007e700f0
Section       @ fffffa8007e70240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : a7 06 02 00 00 08 10 00 - bf e3 9a 1f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8007e70240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007e70138
Section       @ fffffa8007e702c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : [COLOR="red"]Internal timer[/COLOR] (Proc 0 Bank 3)
  Status      : 0xbe00000000800400
  Address     : 0x00003800036e286c
  Misc.       : 0x000000000003ffff

This is either driver related as stated earlier or it looks like the processor is faulty.
The machine check exception means the CPU has found a fault with a hardware piece and has crashed the system to prevent damage.
Now normally we can't determine the cause but it looks like the CPU might be failing due to an internal timer failure.
I suggest running Prime95 to determine whether it's faulty or not.


Stress test your CPU with Prime95

I recommend running Prime95 for around 2 hours

   Warning

As with most stress tests your component's temperature will rapidly increase.
It is advised that you download a temperature monitoring program like HWmonitor
Keep an eye on your temperatures and stop the tests if it starts to overheat

You've had quite a few 0x124 bugchecks actually with the same response of an internal timer error on processor 0 cache bank 3.

 

[ivanwakeup]

wow, thanks for taking the time to look! This is very helpful.

I did not reapply thermal paste to my CPU, but just to my GPU. and no, it did not seem to stop the freezing. I ran prime95 for about 30 minutes and my top CPU temp was 62C, i believe. I'll go ahead and update the drivers you mentioned and remove Avast to see if that helps.

with the numerous internal timer error on processor 0 is this more likely to be CPU rather than driver related?

 

[Thedoctor44]

It would be but those bugchecks stopped quite a while ago so it's actually pretty doubtful at this moment in time unless you did something to help it.

You could try running Prime95.
It sounds more processor related to be honest because as far as I know there's something faulty with that CPU.
We cannot assume anything though until you run Prime95.

 

[ivanwakeup]

updated drivers and removed avast, currently running prime95 once more. will report back with findings.

 

[ivanwakeup]

Alright,

I got the system to blue screen after about 1hr 50 min of p95. I don't understand what couldve gone wrong, because my temps (according to hwmonitor) seemed fine? my max load temp was 64C.

one thing i noticed is that my mobo's BIOS seems to report a much higher idle temperature - about 45C compared to the 35C that HWmonitor reports. CoreTemp also reports about 35C temp. Which temperature should I trust?

I've scaled my OC down to 4ghz and 1.29Vcore. Where do i go from here?

 

[Thedoctor44]

I didn't realize, you need to stop overclocking altogether!

I will request a hardware expert.

Upload any new dump files.

 

[ivanwakeup]

currently trying to upload the new dump files....but i keep getting an internal server error on the upload file screen when the upload progress is complete?

not sure what the problem is.

 

[Thedoctor44]

Hmm, have you made sure the dump files are in a .zip folder?

 

[ivanwakeup]

Alright, there we go. Had to create a new directory for the second dump. new upload attached.


as an additional note, I noticed that during the last p95 test I was getting weird beep iterations coming from my case. I've read that this can be a motherboard utility for notifying you that temperatures are getting too hot? I'm not sure on this one.

 

[Thedoctor44]

Yep a 0x124 bugcheck, make sure you restore all overclocking to factory settings.
There is sufficient cooling right?
Try reapplying some thermal paste.

Finally try Memtest86.


Memtest86 will test your RAM

   Information

Run Memtest86 for at least 8 passes so we get enough information to confirm that your RAM isn't failing

 

[ivanwakeup]

I will try reapplying thermal paste. I already ran memtest86 just last night for 9 passes, and I received no errors. should I run it again anyway?

 

[Thedoctor44]

Ok, you should be fine with memtest86 then.
Which Prime95 test did you run?
Try the Large FFT test.

 

[essenbe]

Hi ivanwakeup, I will try to offer some help, if you don't mind. First, I need you to completely fill out your system specs in as much detail as possible. The simplest way is to click 'My System Specs' in the bottom left corner of your last post and there will be a link to update system specs. When you are finished be sure to click save at the bottom of the page. If you need to know exactly what we want, click my system specs at the bottom of this post to see mine.

Next, if you don't already have it, please download and install CPUz. With your computer at idle, please post screenshots (http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html ) of the CPU, Mainboard, memory and SPD tabs. On the SPD tab, I only need screenshots of the dimm slots populated with ram.

Next, please open CPUz to the CPU tab and Core Temp and run Prime95 (never run but 1 CPU temp monitoring program at a time). Please post screenshots of CPUz and Core temp after Prime95 Blend test has been running for an hour.

It is my opinion that the CPU is the last component of a computer that is subject to go bad, especially with Sandy and Ivy Bridge. However there are a lot of things that can make your computer throw a 124 error. in fact most anything can. But, over time components wear and age and don't work quite the same way as they did when new. I will also tell you that as you can see by the badge at the bottom of my signature, I am not opposed to overclocking, if done right. That being said, any computer that is not stable at stock will never have a stable overclock. Please post those screenshots and let me see what is going on.

 

[ivanwakeup]

thanks for the reply essenbe. Attached are the screenshots from CPU-Z.

when I have time I can run p95 again, although my load temps for my PC after about 2 hours running the software were 64C.

 

[essenbe]

OK, are you at idle there? If so, you should be at 1600 MHz and your Vcore should be around 1.0V, unless you turned EIST off. You should be able to enable XMP in your bios and run your ram at 1600MHz instead of the 1333 it is now. Just be sure to set your Dram Voltage to 1.5V.

 

[ivanwakeup]

Yep, was at idle there. I purposely didnt have my ram set to 1600Mhz because I thought i was having problems with it, although now i'm fairly certain my ram is fine.

so i reapplied thermal paste to my cpu....and now it runs about 1-2C hotter, even dialed back down to stock clock.

given i had arctic silver 5 on there before and now just a generic brand paste. The main thing that confuses me is that my BIOS suggest that my CPU idle temp is about 45C (which is obviously much higher than you would want for this cpu) but both HWmonitor and CoreTemp say it is about 37-38C now with the generic thermal paste. Which one do i trust?

I have a hyper 212+ cooler and i've heard people get idle temps as low as 27-28C, so im confused why mine is so much higher.

 

[essenbe]

Bios is usually more correct, but it will always be higher than in Windows as EIST is not applied in bios where it usually is in the OS. It usually takes a while for thermal paste to cure, and you should see temp drops around 2-3C. How long depends on the paste you applied. Artic silver 5 can take as much as 200 hours, while some others much less.

Depending on the ambient of where you are right now and the airflow in your case, with the warmer weather, you can expect some increase in your CPU temps. Never expect to be below ambient, it isn't possible with air or even water. I trust you did clean the old paste off before applying the new paste. Also, consider you are using software to read temps which is notoriously wrong. It is worse at idle temps. The higher the temps go, the more accurate the readings are, for some reason. Besides, in reality, we don't care what idle temps are, it's when it is put under stress that matters most. Having said that, I do agree that I would like to see idle temps drop a few degrees. Are you using manual or offset voltage in bios? That can make a great difference in CPU temps.