Random BSODs and freezes

[MarsMoon]

I've been having random BSODs and freezes since I can remember using my now pretty old computer (around 7 years). Never found the cause since BSOD stop errors were random. There are some repetitive stop errors but it's not always the same one, so I wasn't actually ever able to completely solve the problem.

The crazy thing is that sometimes these BSODs happen without me making any software or hardware modifications at all. There will be a period of time that everything works totally fine, then a period of a few days/weeks when I get random BSODs. Although I have to say that these BSODs almost NEVER happen after the computer has been turned on for a while (most of the time they happen in the first 30 minutes after turning the computer on) and almost never more that 2 or 3 (I'd say 3 was max) "per day". The most common occurrence is 1 BSOD though.

I have attached the log files and would really appreciate if someone is able to help in any way. It's quite annoying having these random BSODs/freezes.

Recently I've started getting random freezes too. It doesn't go to the BSOD screen it just freezes my picture on the screen and the sound goes all berserk (making a constant buzzing glitchy sound). All I can do is hard reset the computer.

Another thing worth mentioning is, that sometimes after resetting the computer from BSOD or a freeze, when the first BIOS screen shows up it sometimes freezes doing the initial check-ups on the "initializing USB controllers" (like this: http://docs.oracle.com/cd/E19957-01/821-1347/figures/bios_screen1.gif). The only way to solve this problem is either a random number of hard resets or even better turning the computer off for a minute or so and turning it back on and it then boots normally into Windows.

I would really appreciate if someone is able to help since these random BSODs/freezes are quite a bit annoying.

PS: I've done the Memtest86 a couple of times too with no errors.

 

[Arc]

[COLOR=Red]21.11.2014[/COLOR] 3:08:54     C:\Windows\system32\DRIVERS\atikmpag.sys

Dont use a BETA/Omega display driver.

Uninstall the installed display driver using DDU. Then install the CCC 14.4 WHQL only.

Let us know for any further BSOD after doing it.

Also, Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.

eXtreme Power Supply Calculator - The only power supply calculator trusted by PSU manufacturers and computer enthusiasts
​

Let us know the wattage of the PSU installed.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.
___________________________________________

BugCheck 119, {1, 1a8, 299, 298}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+3a783 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 00000000000001a8
Arg3: 0000000000000299
Arg4: 0000000000000298

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x119

PROCESS_NAME:  System

CURRENT_IRQL:  b

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

DPC_STACK_BASE:  FFFFF80000BA0FB0

LAST_CONTROL_TRANSFER:  from fffff8800183422f to fffff80002ec2ec0

STACK_TEXT:  
fffff800`00b9a468 fffff880`0183422f : 00000000`00000119 00000000`00000001 00000000`000001a8 00000000`00000299 : nt!KeBugCheckEx
fffff800`00b9a470 fffff880`0410eec5 : fffff800`0304dcc0 00000000`000001a8 00000000`00000000 00000000`00000299 : watchdog!WdLogEvent5+0x11b
fffff800`00b9a4c0 fffff880`0410f131 : fffffa80`06945000 fffff800`00b9a5d0 00000000`000011ac fffffa80`05448040 : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
fffff800`00b9a4f0 fffff880`0410ef82 : 00000000`000001a8 fffff800`00b9a568 fffffa80`0693b000 00000000`000001a8 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x19d
fffff800`00b9a540 fffff880`0401513f : fffffa80`05e52480 fffffa80`05805000 fffffa80`05249060 00000000`00000003 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff800`00b9a570 fffff880`03e3a783 : 00000000`00000000 00000000`00000180 fffff800`00b9a620 00000000`00000001 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff800`00b9a5a0 00000000`00000000 : 00000000`00000180 fffff800`00b9a620 00000000`00000001 00000000`00000202 : atikmpag+0x3a783


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmpag+3a783
fffff880`03e3a783 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  atikmpag+3a783

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  546e9eb6

FAILURE_BUCKET_ID:  X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_atikmpag+3a783

BUCKET_ID:  X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_atikmpag+3a783

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x119_1_driver_reported_invalid_fence_id_atikmpag+3a783

FAILURE_ID_HASH:  {3394e43e-7046-c9b0-b82a-73ed6afa0f3e}

Followup: MachineOwner
---------

0: kd> lmvm atikmpag
start             end                 module name
fffff880`03e00000 fffff880`03e96000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri Nov 21 07:38:54 2014 (546E9EB6)
    CheckSum:         00093077
    ImageSize:        00096000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[MarsMoon]

[COLOR=Red]21.11.2014[/COLOR] 3:08:54     C:\Windows\system32\DRIVERS\atikmpag.sys

Dont use a BETA/Omega display driver.

Uninstall the installed display driver using DDU. Then install the CCC 14.4 WHQL only.

Let us know for any further BSOD after doing it.

I have been experiencing these crashes long before Omega drivers even existed though. And I never used BETA drivers.

I have however, per your instructions, removed current Omega drivers with DDU and installed the recommended ones (14.4).

Also, Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.

eXtreme Power Supply Calculator - The only power supply calculator trusted by PSU manufacturers and computer enthusiasts
​

Let us know the wattage of the PSU installed.

I have a 500 W PSU. The calculator you provided says its capable of running my PC configuration although it's pretty close:

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

It's not that hot as far as I know. Here's Speccy's summary:


Wouldn't my computer crash after hours of use too then? Especially if I play intensive games or watch HD video. I would reckon the temperatures for the first minutes (30 or so) after booting the computer would be the lowest possible... they would rise only after some time the computer has been powered on or using it for CPU/GPU intensive stuff. So I'm not sure if the temps are responsible for the crashes since I get the crashes only soon after the first daily booting up off the computer.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.
___________________________________________

BugCheck 119, {1, 1a8, 299, 298}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+3a783 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 00000000000001a8
Arg3: 0000000000000299
Arg4: 0000000000000298

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x119

PROCESS_NAME:  System

CURRENT_IRQL:  b

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

DPC_STACK_BASE:  FFFFF80000BA0FB0

LAST_CONTROL_TRANSFER:  from fffff8800183422f to fffff80002ec2ec0

STACK_TEXT:  
fffff800`00b9a468 fffff880`0183422f : 00000000`00000119 00000000`00000001 00000000`000001a8 00000000`00000299 : nt!KeBugCheckEx
fffff800`00b9a470 fffff880`0410eec5 : fffff800`0304dcc0 00000000`000001a8 00000000`00000000 00000000`00000299 : watchdog!WdLogEvent5+0x11b
fffff800`00b9a4c0 fffff880`0410f131 : fffffa80`06945000 fffff800`00b9a5d0 00000000`000011ac fffffa80`05448040 : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
fffff800`00b9a4f0 fffff880`0410ef82 : 00000000`000001a8 fffff800`00b9a568 fffffa80`0693b000 00000000`000001a8 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x19d
fffff800`00b9a540 fffff880`0401513f : fffffa80`05e52480 fffffa80`05805000 fffffa80`05249060 00000000`00000003 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff800`00b9a570 fffff880`03e3a783 : 00000000`00000000 00000000`00000180 fffff800`00b9a620 00000000`00000001 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff800`00b9a5a0 00000000`00000000 : 00000000`00000180 fffff800`00b9a620 00000000`00000001 00000000`00000202 : atikmpag+0x3a783


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmpag+3a783
fffff880`03e3a783 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  atikmpag+3a783

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  546e9eb6

FAILURE_BUCKET_ID:  X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_atikmpag+3a783

BUCKET_ID:  X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_atikmpag+3a783

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x119_1_driver_reported_invalid_fence_id_atikmpag+3a783

FAILURE_ID_HASH:  {3394e43e-7046-c9b0-b82a-73ed6afa0f3e}

Followup: MachineOwner
---------

0: kd> lmvm atikmpag
start             end                 module name
fffff880`03e00000 fffff880`03e96000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri Nov 21 07:38:54 2014 (546E9EB6)
    CheckSum:         00093077
    ImageSize:        00096000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

No crashes or artifacts while burn testing my GPU. Here's the screenshot after 5 min of testing:

 

[Arc]

Very nicely documented reply.

53º for CPU means it is tending to be hot, though. But your logic is valid. Still, it will be under mark.
And, apparently all the sides of the display environment is checked.

Now we have to wait and see if it BSODs again with 14.4 WHQL installed.

 

[MarsMoon]

Thank you.

I know, the CPU temps are on the high side. That's why I'm in the process of buying a new CPU cooler.

Let's hope it'll work although I have my doubts.

 

[Arc]

Let's hope it'll work although I have my doubts.

The the problem persists, troubleshooting will be continued.

 

[MarsMoon]

Aaaaaaand it happened again today. Booted up the PC, logged into Windows, started a torrent client and freeze. Needed to restart the computer and then it worked without a problem.

I'm attaching the created dump file in this post.

 

[Arc]

Torrenting is a gray area, mate. I hope you are aware of it that whatever you are doing there is at your own risk and responsibility.

 

[MarsMoon]

I am well aware. Let's just say I'm downloading a couple of Linux distributions and few online distributed free documentaries. But I am well aware nonetheless.

PS: I don't think opening the torrent client is the issue though, because the same happens if I open Firefox too. So I don't think it's directly connected to the program. Especially since it only happens after the log in into Windows and never after the computer being turned on for a while (regardless of closing and opening before mentioned programs).

 

[Arc]

PS: I don't think opening the torrent client is the issue though, because the same happens if I open Firefox too. So I don't think it's directly connected to the program. Especially since it only happens after the log in into Windows and never after the computer being turned on for a while (regardless of closing and opening before mentioned programs).

Again there is sound logic in your statement as previous, and the crash dump supports it.

PROCESS_NAME:  System

This field reports the running program during the BSOD, and it doesn't say anything about torrents.

Still, we should be aware while torrenting. That is a great source of malware in cases.

But mate, as always, this crash dump is also not very informative as to what may be the failing thing. In general, a stop 0x124 is said to be a hardware related error; but it may be anything and everything included in the computer's overall environment. A factory bloatware or a hackers activation exploit may also cause this issue, beside hardware or hardware drivers.

In this situation, I would suggest you to read this guide: http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696
You will understand what is what, and why it is mysterious.
Follow it, let us positively hope that you will be able to discover the failing thing.
For any assistance during those tests, give us a shout.

 

[MarsMoon]

It was good for a couple of days, then it started happening again. Weirdly though, no BSODs, just random restarts and freezes (with sound "artifacts" coming from speakers).

I did a 38 hour Memtest86+ and no errors at all, so RAM sticks are probably fine.

And today something even weirder happened. After the freeze, Windows wasn't able to boot up. At the boot up logo there would be a split second that showed the BSOD (like 1/10 of a second, only the blue color is visible) and then restart.

Managed to get into safe mode to start checking the disks with chkdsk. Tested all three drives with no errors. Was able to boot up into Windows without problems. What the hell!?! Did the sfc /scannow just to be sure too and no problems here either.

Every damn test comes up with no errors... Cmon!

And when it finally looked it started to work again, another freeze. This time with graphic artifacts too (first time with this computer). Restarted and again not able to go past the Win boot up screen. So I shut down the computer, removed the graphics card (AMD) and installed the old one (Nvidia). Booted up into safe mode, ran the DDU to uninstall and delete AMD drivers. Rebooted into Windows without problems and installed Nvidia drivers.

Now im on about 20 min of usage with the old graphics card. Let's see if it will happen again. Judging from the past it will since it did when I was using this card (Nvidia) years ago - all the same symptoms too.

 

[Arc]

If it happens again, you need to think about moisture and dust too.

 

[MarsMoon]

It sure did happen again this morning. I still cant grasp why is it more prevalent in the mornings or after the computer was off for many hours.

I can conclude that the graphic card definitely isn't the problem as it happened with both of them (like it did in the past). HDDs and SSD are almost certainly fine to. SMART ok, chkdsk ok, temps ok.

Now I'm back to AMD graphics card. I removed half of the RAM (2x1 GB stick) and I'll wait for another freeze. Then I'll repeat with other two sticks and so on until I'll check all of them with process of elimination - although Memtest results were ok.

Regarding the dust. I regularly clean my computer. Even between the fans and all so it's pretty clean. Humidity is around 50 % during this season. But I'll check it more thoroughly when I get the battery for the hygrometer.

 

[Arc]

I will suggest you to open the computer, clean the edges of the RAM, graphics card and SATA ports with clean cotton cloth and then re-seat them.

Then wait for the next morning. See what happens.