Bugcheck 0x119 - new pc, frequent BSoD

Wednesday, December 11, 2019

Bleeping Computer



https://www.bleepingcomputer.com/forums/t/709482/new-pc-frequent-bsod/



Hi. . .

Your system parts link returns an HTTP 404 error (page not found) - https://pcpartpicker.com/list/YCLntp)

I know you said this is a new system and I see the words "custom build" listed. Exactly how old is it? i.e., a week. a moth, 6 months, etc...??

The reason that I ask is because depending in which state that you live in, you MAY be entitled to a brand new system versus the manufacturer/builder attempting to fix your current system.

I would demand a brand new system -- do not allow them to talk you into fixing this system otherwise I fear that you will be stuck with a system that you will have problems with for as long as you own it.

For info, I generally see 1 (one) NVIDIA BSOD for every 1,000 ATI video BSODs. NVIDIA writes some of the finest drivers in the world; ATI for whatever reason, does not.

The Sysnative zip file attachment contained just 3 dump files, yet a Windows app, executed by the Sysnative app -  msinfo32 - WERCON (Windows Error Reporting) section lists a total of 8 (eight) BSODs starting on 5 December 2019 through 9 December 2019. Any idea what happened to the missing 5 dumps?

The date of the BSOD is contained in the file name -
C:\Windows\Minidump\120919-6718-01.dmp
C:\Windows\Minidump\120919-6718-01.dmp
C:\Windows\Minidump\120819-6515-01.dmp
C:\Windows\Minidump\120819-6515-01.dmp
C:\Windows\Minidump\120619-6593-01.dmp
C:\Windows\Minidump\120619-6593-01.dmp
C:\Windows\Minidump\120519-6015-01.dmp
C:\Windows\Minidump\120519-6015-01.dmp

Per the Windows app systemunfo.exe, again, executed by the Sysnative app, shows your initial Windows boot date (the date when Windows was installed and/or first booted) to be:
Original Install Date:     02/12/2019, 01:32:42

That would equate to 2 December 2019, just 3 days prior to the first BSOD per the files that I have examined thus far.

Do you recall the exact date that you took delivery of the system? i.e., did you take delivery of the system between 2 December and 9 December 2019? I'm trying to figure out if the system builder had the system during the BSODs and therefore would have known that they were delivering a defective system to you or not. This would not be the first time where I have seen a systm builder deliver a new system to a client that they knew was BSOD'ing. Shameful if true!

Here are the bugchecks and "probably caused by" for the 3 dumps submitted - 
BugCheck 119, {1, 57d90, 57d92, ffffa604ae98d000}
Probably caused by : dxgmms2.sys ( dxgmms2!VidSchiProcessIsrCompletedPacket+1249f )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 119, {1, 45900, 45902, ffff9283125eb000}
Probably caused by : dxgmms2.sys ( dxgmms2!VidSchiProcessIsrCompletedPacket+1249f )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 119, {1, 3eb2, 3eb4, ffffac85e7c54000}
Probably caused by : dxgmms2.sys ( dxgmms2!VidSchiProcessIsrCompletedPacket+1249f )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Bugcheck 0x119 = The VIDEO_SCHEDULER_INTERNAL_ERROR bug check has a value of 0x00000119. This indicates that the video scheduler has detected a fatal violation. This is most likely a hardware failure problem.

"Probably caused by : dxgmms2.sys" =  dxgmms2.sys is a Microsoft DirectX component (driver) and is not the rel culprit here --- it just caught the blame because the real culprit could not be identified.

As I said earlier - contact the system builder immediately and report the fact that you are experiencing BSODs likely caused by something related to video or other unknown hardware failure.

Also mentioned in each of the 3 dumps - your ATI video driver.

I checked the timestamps (dates) on the ATI drivers as found in the BSOD dumps and the drivers are very new, so I doubt that the video drivers are the problem. Here are the two ATI video drivers currently loaded in your system:
atikmdag.sys Tue Nov 26 16:59:33 2019 (5DDDCA75)
atikmpag.sys Tue Nov 26 16:49:59 2019 (5DDDC837)
As you can see - they are just 15 days old.

Again - contact the system builder immediately.

Regards. . .

jcgriff2

Edited by jcgriff2, Today, 04:48 PM.



p.s. I checked the SYSTEM Event Viewer log and found evidence of 5 (five) BSODs starting on 5 December 2019.

Again - the date of system delivery to you is very important here.

Do you recall the date that you took delivery of the system?

To be honest, my curiosity is peaked right now as well! :)

Regards. . .

jcgriff2

0 comments:

Text

Powered by Blogger.

Follow by Email

Search This Blog

Popular Posts