[SOLVED] Win10pro 64bit camera server crashing several times per week stop 0x124 and 0xc9. FIX: I replaced the CPU (it was under warranty).

R

rgibson

Member
Joined
Oct 12, 2020
Posts
12
Random freezing on win10 Pro 64bit.

I have a windows10 Pro 64bit system that has ran for six months or more without fail. It is a camera server, so nobody is using it for daily use, internet browsing, office work, Etc. Other than the camera recording software, and a camera config utility or two. it is a simple win10 pro64 install, hardware drivers, and recording software. until the crashing, there were NO other software or utilities installed.
Crashing started once or twice then daily with nothing other than the bugcheck of 0xC9 or 0x127, after the fact. No events, appear to point to problem beforehand, Scans for Viri, Malware, turn up nothing.
the system just freezes. Display is there but frozen, no mouse, no keyboard. System is locked so hard, that pressing and holding the case power button will not power down.
Only the power supply switch will cause a power off state (obviously). Flip the switch, press power, system boots up without a problem. Only the "Shutdown was unexpected" event
recorded on powerup.
Here is what has been done so far.

SFC /Scannow Shows NO problems
DISM.exe /Online /Cleanup-image /Scanhealth Shows NO Problems
Online and Offling Virus scan of Entire HDD show NO problems
Malware scan both Online and Offline show NO problems
System Restore to prior point does NOT fix problems


Thanks in advance

Randy
 

Attachments

Answers to the support questions:

System Manufacturer= Me

Laptop or Desktop?= Desktop
Exact model number (if laptop, check label on bottom)= Gigabyte B365M DS3H
OS = Windows 10 Pro x64, version 2004 (OS Build 19041.508)
Bitness = 64Bit
Original OS= Windows 10 Pro x64, version 1903
OS type= Full retail
hardware age= Aprox. 18 months
OS install age= 18 months
reinstalled= yes
CPU= Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz Socket 1151 LGA
RAM = Crucial Technology Model CT8G4DFS8266.M8FD, ChannelA-DIMM1 & ChannelB-DIMM1
Video Card= NVIDIA GeForce GTX 1650 4096 MBytes
MotherBoard= Gigabyte B365M DS3H
Power Supply= Silverstone ET-500, 500W
driver verifier = disabled
What security software are you using?= Windows Defender
Are you using proxy, vpn, ipfilters= NO
Are you using Disk Image tools? = NO
Are you currently under/overclocking?= NO
 
I'm seeing x0124 WHEA uncorrectable error which is a hardware error usually related to heat.
Have you checked the CPU temps?
 
Wrench97 said:
I'm seeing x0124 WHEA uncorrectable error which is a hardware error usually related to heat.
Have you checked the CPU temps?
Click to expand...
Hello Wrench97,
Yes, and logged those temps with CoreTemp.
The attached log is a 10/10/2020 .CSV of those temps in Fahrenheit. the CPU MAX is 212 Fahrenheit.
as of this writing, 8:27am Sunday Oct 18, 2020, there was a new crash at 12:18am this morning, stop 0xc9 with NO dump file generated, crash screen hung at 0%.
I had changed the dump type to complete and made sure the paging file was set to a large enough size to cover 16GB , but alas, no file. changing it back to automatic.
At one point I connect to the problem computer with KD over network. I do NOT know how to properly use windbg, but thought I could grab a log of the error or something.
Again, I can log right up to the point of halt.

just to refresh, I have ran
Intel CPU diag= NO problem found
Crucial Nvme diag= NO problem found
Win10 Mem Test and Memtest86+= No problem
The MRI utility from BestBuy (Hardware Tester?)= No problem found
Boot and Run a Ubuntu Live CD for DAYS= No issues

I do not believe the problem is hardware, so I ran
SFC /scannow= No problems
DISM /Online /Check-Image /CheckHealth= No problem
DISM /Online /Check-Image /ScanHealth= No problem

Please let me know if there is any other info needed

Thank you

Randy
 

Attachments

Wrench97 said:
x09c DRIVER_VERIFIER_IOMANAGER_VIOLATION so you have driver verifier running?

How do you have it set up?
Click to expand...
It was at one point, but not now.
I selected all non MS drivers. ran for several days, then crashed with 0x09c,,,,, disabled verifier, rebooted. eight days later, I think crashed with same 0x0c9
I've been grasping at straws for several months now.
I can't seem to get a full "complete" dump though. also sometimes the system hangs as though frozen in time... nothing works, case power button , reset button, nothing, yet video is still on the screen as though i'm looking at a photograph. Other times a reboot will happen.
attached is a zipped .PNG of the desktop now 10:35am , showing GPU temp at 54 C and at 54% utilization. CPU temps. the big 6 is just a looping video so I can see at a distance if the system is frozen or not.

This system ran for over six months perfectly. Not one single error. with nobody doing anything. Now six months of nothing but random crashes.

Again Thanks for Helping

Randy
 

Attachments

rgibson said:
It was at one point, but not now.
I selected all non MS drivers. ran for several days, then crashed with 0x09c,,,,, disabled verifier, rebooted. eight days later, I think crashed with same 0x0c9
I've been grasping at straws for several months now.
I can't seem to get a full "complete" dump though. also sometimes the system hangs as though frozen in time... nothing works, case power button , reset button, nothing, yet video is still on the screen as though i'm looking at a photograph. Other times a reboot will happen.
attached is a zipped .PNG of the desktop now 10:35am , showing GPU temp at 54 C and at 54% utilization. CPU temps. the big 6 is just a looping video so I can see at a distance if the system is frozen or not.

This system ran for over six months perfectly. Not one single error. with nobody doing anything. Now six months of nothing but random crashes.

Again Thanks for Helping

Randy
Click to expand...

Wrench97 said:
x09c DRIVER_VERIFIER_IOMANAGER_VIOLATION so you have driver verifier running?

How do you have it set up?
Click to expand...
I would be happy to turn on , enable, setup, configure, and report back, Darn near ANYTHING you would like. just let me know what.
 
The x09c is a driver verfier bug check, it would have to be running for it to occur as far as I know.

Try turning Verifier Off. Running verifier on MS drivers can cause issues for some reason

Open the run box(winkey+r) type verifier and press Enter, Select ok to run Driver Verifier, in the verifier window select Delete Existing Settings then press finish.
Click to expand...
 
Wrench97 said:
The x09c is a driver verfier bug check, it would have to be running for it to occur as far as I know.

Try turning Verifier Off. Running verifier on MS drivers can cause issues for some reason
Click to expand...
I looked at the "Display current settings", and they were all NO.
I did as requested, and as I confirmed the choice, it stated no settings were changed.
Remember I "WAS" checking NON MS Drivers.
I was getting x09c errors before I ever knew anything about verifier, and I'm the only one to ever touch this computer, so if x09c is only a verifier bug check, then thats odd!

I wanna Cry now, but my grand kids would just laugh!
 
Well I was totally wrong on that, my reference material is wrong as it should not be x09c but 0x9c.
From the Microsoft site 0x9C: MACHINE_CHECK_EXCEPTION which falls in line with the 0x124: WHEA_UNCORRECTABLE_ERROR I saw in the dumps I read earlier.
Both are hardware errors, the 0x9c occurs very rarely on modern hardware as it has mostly been replaced with 0x124.
If the temps are good then it's usually a motherboard or rarely a cpu issue.
 
Wrench97 said:
Well I was totally wrong on that, my reference material is wrong as it should not be x09c but 0x9c.
From the Microsoft site 0x9C: MACHINE_CHECK_EXCEPTION which falls in line with the 0x124: WHEA_UNCORRECTABLE_ERROR I saw in the dumps I read earlier.
Both are hardware errors, the 0x9c occurs very rarely on modern hardware as it has mostly been replaced with 0x124.
If the temps are good then it's usually a motherboard or rarely a cpu issue.
Click to expand...
I've sort of muddled my way to this point. I can launch a recovery environment running a batch file I wrote, just launching and running everything i could think of, and it runs for weeks without fail.
i can run Linux Mint live CD and run utilities for weeks. I did Not think it was hardware.
So on the dump with the 0x124, what is it pointing to, where in the stack does it begin to fail.

This is so frustrating.

Thanks
 
 
Last edited:
Installed All listed Drivers on evening of 10/21. Setup a few things to monitor the system.
I found on 10/22 the system had hung during the night. No dump, no logs. a P/S power switch was required to power off and on.
Intel has replaced the CPU under warranty, which has now been installed.
Since Motherboard, RAM and NVMe have all been replaced already... What's that saying "When you have eliminated the impossible, whatever remains, however improbable, must be the truth."
Even though Intel's own CPU diagnostic show no errors, memtest shows no errors, MS Mem diagnostic shows no errors, Micron Crucial NVMe diagnostic shows no errors, motherboard diagnostic via several tools show no errors, OS reinstall continues to has errors.
This has kinda been like jacking up a radiator cap and pulling a new car under it.
I will let you know if we still have crashes!.
Randy
 

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

Back
Top