Question windows hard reboot

[sauravnsu]

I was in half life 2 and there was a salad setup running on the background while my windows stuck and hard rebooted. In the event viewer, it shows the following error :

error bug check event id 1001

The computer has rebooted from a bug check. The bugcheck was: 0x00000119 (0x000000000000a000, 0xffff9a04674937a0, 0x0000000000000000, 0x0000000000000001). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: bf273e86-64fa-4563-803d-d8c6ee4ccc50.


I am uploading the memory.dmp file link....

https://drive.google.com/file/d/1oFPwoxfwqJZIR7hBKcHyDvdpLpnN0ywl/view?usp=sharing

 

[jojesa]

Could you post your system components or specs.
That bug check is related to outdated or corrupted graphics drivers.

 

[sauravnsu]

Could you post your system components or specs.
That bug check is related to outdated or corrupted graphics drivers.

motherboard: asrock b360 pro
processor: intel i5 8400
gpu: msi rtx 3060 12 gb
ram: geil 8*2= 16gb
psu: bitfinix 750w wispher 80+ gold

 

[ubuysa]

As above, the 0x119 bugcheck is a VIDEO_SCHEDULER_INTERNAL_ERROR, but the argument 1 value of 0xA000 indicates that the error was caused by bad hardware, possibly RAM.

I'm downloading the kernel dump as I type and will come back if it reveals anything else, but for now I'd suggest the following...

1. Ensure you're running the latest driver for your RTX3060 via the Nvidia website. The latest version is dated 22nd August 2023.
2. Remove and re-seat your graphics card.
3. Remove and re-seat the RAM cards.
4. Download Memtest86 and use that to test your RAM.

 

[sauravnsu]

As above, the 0x119 bugcheck is a VIDEO_SCHEDULER_INTERNAL_ERROR, but the argument 1 value of 0xA000 indicates that the error was caused by bad hardware, possibly RAM.

I'm downloading the kernel dump as I type and will come back if it reveals anything else, but for now I'd suggest the following...

1. Ensure you're running the latest driver for your RTX3060 via the Nvidia website. The latest version is dated 22nd August 2023.
2. Remove and re-seat your graphics card.
3. Remove and re-seat the RAM cards.
4. Download Memtest86 and use that to test your RAM.

ram tested with memtest and no error

 

[ubuysa]

Memtest can't guarantee that your RAM is good, no memory tester can, but if it's not RAM then it's likely to be the graphics card itself. The full description of the argument 1 value 0f 0xA000 is...

This is an internal OS state error, typically caused by a memory corruption or bad hardware.

To be certain that it's not RAM remove one stick of RAM and just run on the other for a while. Then swap sticks. See whether it BSODs on one stick but not the other.

Once you're 100% certain that the RAM is good (ie. it BSODs on either stick on its own) then you have to suspect the graphics card. To check that, download DDU and the most recent three driver versions for your 3060 from the Nvidia website. Use DDU to fully uninstall the current driver and (on reboot) install the latest driver version. If that BSODs use DDU again to uninstall it and (on reboot) install the previous driver version. If that BSODs then use DDU again to uninstall it and finally install the two-level back driver version.

If it BSODs on all three of the latest driver versions using DDU in between each, then it's most likely to be a graphics card issue.

BTW There was nothing new in the kernel dump, though you can see how the error unfolded...

5: kd> knL
 # Child-SP          RetAddr               Call Site
00 fffff880`0db3f638 fffff801`1cbb3ad0     nt!KeBugCheckEx
01 fffff880`0db3f640 fffff801`2a04becb     watchdog!WdLogEvent5_WdCriticalError+0xe0   <=== generate the bugcheck
02 fffff880`0db3f680 fffff801`2a0e105e     dxgmms2!VidSchiResetHwEngine+0x6ab   <=== reset the graphics driver
03 fffff880`0db3f830 fffff801`2a0ab61f     dxgmms2!VidSchiResetEngines+0xaa   <=== reset the graphics card
04 fffff880`0db3f880 fffff801`2a0781e2     dxgmms2!VidSchiCheckHwProgress+0x3340f   <=== detect that the graphics command has hung
05 fffff880`0db3f8f0 fffff801`2a01a11a     dxgmms2!VidSchiWaitForSchedulerEvents+0x372   <=== wait for the card to respond
06 fffff880`0db3f9c0 fffff801`2a09d7d5     dxgmms2!VidSchiScheduleCommandToRun+0x2ca   <=== send a graphics command to the card (via the nvlddmkm.sys driver)
07 fffff880`0db3fa80 fffff801`2a09d78a     dxgmms2!VidSchiRun_PriorityTable+0x35
08 fffff880`0db3fad0 fffff801`0390e6f5     dxgmms2!VidSchiWorkerThread+0xca   <=== start a graphics operation
09 fffff880`0db3fb10 fffff801`03a05878     nt!PspSystemThreadStartup+0x55
0a fffff880`0db3fb60 00000000`00000000     nt!KiStartSystemThread+0x28

You read these call stacks from the bottom up. I've annotated it so you can see what happened.