[SOLVED] BSOD when watching some types of videos and playing some kinds of games

S

Scarecrow

Member
Joined
May 20, 2014
Posts
10
I've been getting the blue screens for something like 9 months. It's gotten to the point where I can expect atleast 1 bsod a day. I've tried a few driver scans and I have updated everything according to those scans and used virus scans etc. I ran a verifier through CMD a few min ago according to the specs on https://www.sysnative.com/forums/bs...indows-8-1-8-7-and-windows-vista.html#post303 . And when I booted up, I would blue screen and had to system restore.
Thank you for your time.
 
Not a problem, thanks!

There don't appear to be any crash dumps located in your jcgriff2 output folder. If you navigate to C:\Windows\Minidump, are there any .DMP contents inside? If not, please make sure of the following:

1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

4. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

If you cannot get into normal mode to do any of this, please do this via Safe Mode.

Regards,

Patrick
 
1. I do have a Minidump folder at that directory but it was empty. Theres a chance that a scan or cleaning I've done might have emptied it? not sure.

2. I could not find anything saying "Automatically manage paging file size for all drives" in that location :(

3. This was as you instructed

4. The Windows Error Reporting Service was not "started", so I set it to that now. I've also changed it from Manual to automatic.

Thank again for your quick response.
 
Great, but regarding #2:

example.png

It should flow like this (from left to right) if done properly. Please accept my apologies as it appears my instructions need to be updated. On Windows 8.1, I have to do it like this - Advanced System Settings > Advanced > Performance > Settings > Advanced > Change.

Regards,

Patrick
 
So I've crashed 4 times today. Something I guess I forgot to mention is that as of the past month or so my computer will simply freeze instead of a full on bluescreen. Today I think was 2 freezes and 2 bsod. There is 1 dmp in the folder now though.
 

Attachments

At least we finally have a crash dump now.

The attached DMP file is of the WHEA_UNCORRECTABLE_ERROR (124) bug check.

A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).

If we run an !errrec on the 2nd parameter of the bug check (address of the WER structure) we get the following:

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

[COLOR=#ff0000]Error         : ICACHEL1_IRD_ERR (Proc 4 Bank 1)[/COLOR]
  Status      : 0xb080000000040151

L1 Cache error, specifically either not either not enough voltage to the CPU itself, or the CPU has encountered math issues (faulty CPU).


There is only so much you can do with a bugcheck like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:

1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - Speccy - System Information - Free Download

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - How To Clear CMOS (Reset BIOS)

3. Ensure your BIOS is up to date.

4. The only software conflict that can usually cause *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite. If you have something like this software-wise, remove it ASAP.

5. If all of the above fail, the only left to do is replace your processor as it is faulty.

Regards,

Patrick
 
Does the traditional Control Panel > Add/Remove program not work in this instance, is that why you're asking?

Regards,

Patrick
 
I looked up in the control panel to remove it but I'm almost positive it was not listed. I DO have an Asus board though and I remember updated the bios about a month ago so I would just assume I have the AI Suite. But like I said it wasn't showing up in the programs to add/remove.
 
How did you update the BIOS, through the BIOS itself with a ROM or with their software?

Regards,

Patrick
 
Right, okay, so there may not even be AI Suite then. Probably a CPU issue then, unfortunately.

Regards,

Patrick
 
CRAP! I would often get bluescreens with the notice, "A clock interrupt was not received on a secondary processor". Would that kind of alert also be indicative of a cpu malfunction?
 
Yep, that's an 0x101 bug check which often when tied with 0x124's certainly provides extra evidence regarding a faulty CPU. Essentially that implies that the processors did not 'talk to each other' on time, therefore the system bug checked. It can be caused by a simple driver issue, however, paired with 0x124's as I said (which you are getting) that fault the L1 cache, we definitely have a CPU issue.

Regards,

Patrick
 
That's painful to hear, but at least I can pretty much rest easy knowing what it is now. Ill just have to run my cpu into the ground until I can replace it. Thanks for your help. I appreciate for sure :wave:
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top