random BSODs, screen freezes

ivanwakeup · 25 May 2014

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 · 25 May 2014

Blue Screen of Death (BSOD) Posting Instructions

ivanwakeup · 25 May 2014

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

EDIT: main post now includes the proper files.

Thedoctor44 · 25 May 2014

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.

Code:

EXCEPTION_RECORD:  fffff880031b6778 -- (.exr 0xfffff880031b6778)
ExceptionAddress: fffff8800256d3fa (nwifi!Dot11InitVElanRegistry+0x0000000000000392)
   ExceptionCode: c000001d (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.

Code:

fffff880`07246000 fffff880`073c3000   athrx      (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Mon Oct 05 17:33:57 2009 (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.

Code:

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 MijXfilt.sys

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

Code:

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:        Sat May 12 05:27:12 2012 (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.

Code:

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
 aswSP+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.

Code:

0: kd> !errrec fffffa8007e70028
===============================================================================
Common Platform Error Record @ fffffa8007e70028
-------------------------------------------------------------------------------
Record Id     : 01cf6a7bb289e183
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
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         : Internal timer (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 · 25 May 2014

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 · 25 May 2014

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 · 25 May 2014

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

ivanwakeup · 25 May 2014

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 · 25 May 2014

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

I will request a hardware expert.

Upload any new dump files.

ivanwakeup · 25 May 2014

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.