github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-22 21:51:37 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #3743] The Windows (preview) version causes Windows 11 crash with DPC_WATCHDOG_VIOLATION (133) #2307

New Issue
Closed
opened 2026-04-12 12:35:53 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-12 12:35:53 -05:00
Owner
Copy Link

Originally created by @binxie33 on GitHub (Apr 19, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/3743

Originally assigned to: @dhiltgen on GitHub.

What is the issue?

I am running the Windows (preview) version on Windows 11 with Nvidia 4070Ti (12GB GPU memory).

The Nvidia driver is latest version 552.22, and Cuda is latest version 12.4.1. When answering some questions with relative lengthy outputs, the whole computer hang / crash with the error DPC_WATCHDOG_VIOLATION (133) . I have tried different models like deepseek-coder / wizardlm2 and encountered the same problem.

OS

Windows

GPU

Nvidia

CPU

Intel

Ollama version

0.1.32

Originally created by @binxie33 on GitHub (Apr 19, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/3743 Originally assigned to: @dhiltgen on GitHub. ### What is the issue? I am running the Windows (preview) version on Windows 11 with Nvidia 4070Ti (12GB GPU memory). The Nvidia driver is latest version 552.22, and Cuda is latest version 12.4.1. When answering some questions with relative lengthy outputs, the whole computer hang / crash with the error DPC_WATCHDOG_VIOLATION (133) . I have tried different models like deepseek-coder / wizardlm2 and encountered the same problem. ### OS Windows ### GPU Nvidia ### CPU Intel ### Ollama version 0.1.32
GiteaMirror added the bugnvidiawindows labels 2026-04-12 12:35:54 -05:00
GiteaMirror commented 2026-04-12 12:35:55 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Apr 19, 2024):

This sounds like it may be an NVIDIA driver bug, or possibly hardware fault. Did you get a BSOD? Did it report which driver was hung?

<!-- gh-comment-id:2067288337 --> @dhiltgen commented on GitHub (Apr 19, 2024): This sounds like it may be an NVIDIA driver bug, or possibly hardware fault. Did you get a BSOD? Did it report which driver was hung?
GiteaMirror commented 2026-04-12 12:35:56 -05:00
Author
Owner
Copy Link

@binxie33 commented on GitHub (Apr 24, 2024):

Yes, it got BSOD after hanging for a while. The following is the bugcheck detail. It points to nvlddmkm.sys which is nvidia display driver. I already installed the latest nvidia driver and it did not help.
`10: kd> !analyze -v

  •                                                                         *

  •                    Bugcheck Analysis                                    *

  •                                                                         *

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff80069f1c340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:

BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80069f1c340

BUGCHECK_P4: 0

FILE_IN_CAB: 041824-8484-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Code.exe

STACK_TEXT:
ffffd2013256b9d8 fffff800694e3739 : 0000000000000133 0000000000000001 0000000000001e00 fffff80069f1c340 : nt!KeBugCheckEx
ffffd2013256b9e0 fffff800694e2884 : 0000be4794caa2e8 ffffd20132551180 00000000003bc48e 0000000000000000 : nt!KeAccumulateTicks+0x239
ffffd2013256ba40 fffff800694e453f : 000000000000001c 0000000000001388 00000000003bc400 0000000000239fd7 : nt!KiUpdateRunTime+0xf4
ffffd2013256bc00 fffff800694e08f8 : 0000000000000000 ffffd2013644da00 ffffd20132551180 0000000000000000 : nt!KiUpdateTime+0x63f
ffffd2013256bea0 fffff800694e01ba : fffff80069e5fe60 ffffd2013644dab0 ffffd2013644dab0 0000000000000002 : nt!KeClockInterruptNotify+0x228
ffffd2013256bf40 fffff80069467e5c : 0000008e7f62ee25 ffffe706d81528a0 ffffe706d8152950 fffff8006961a38b : nt!HalpTimerClockInterrupt+0x10a
ffffd2013256bf70 fffff8006961a5ea : ffffb98693716d10 ffffe706d81528a0 0000000000900494 0000000000000000 : nt!KiCallInterruptServiceRoutine+0x9c
ffffd2013256bfb0 fffff8006961aeb7 : 000000000090047c fffff8006961aec4 0000000000900490 ffffb98693716e38 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffb98693716c90 fffff800966dd510 : fffff800966dda4a ffffe706ea9c7000 fffff80096704fde ffffe706ea9c7bf0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffb98693716e28 fffff800966dda4a : ffffe706ea9c7000 fffff80096704fde ffffe706ea9c7bf0 ffffb98693716e60 : nvlddmkm+0xed510
ffffb98693716e30 ffffe706ea9c7000 : fffff80096704fde ffffe706ea9c7bf0 ffffb98693716e60 ffffe70600000000 : nvlddmkm+0xeda4a
ffffb98693716e38 fffff80096704fde : ffffe706ea9c7bf0 ffffb98693716e60 ffffe70600000000 fffff80000000020 : 0xffffe706ea9c7000 ffffb98693716e40 ffffe706ea9c7bf0 : ffffb98693716e60 ffffe70600000000 fffff80000000020 ffffb98693716ea0 : nvlddmkm+0x114fde ffffb98693716e48 ffffb98693716e60 : ffffe70600000000 fffff80000000020 ffffb98693716ea0 0000000000000000 : 0xffffe706ea9c7bf0
ffffb98693716e50 ffffe70600000000 : fffff80000000020 ffffb98693716ea0 0000000000000000 0000000000000000 : 0xffffb98693716e60 ffffb98693716e58 fffff80000000020 : ffffb98693716ea0 0000000000000000 0000000000000000 0000000000900494 : 0xffffe70600000000
ffffb98693716e60 ffffb98693716ea0 : 0000000000000000 0000000000000000 0000000000900494 0000000000000000 : 0xfffff80000000020 ffffb98693716e68 0000000000000000 : 0000000000000000 0000000000900494 0000000000000000 0000000000000000 : 0xffffb98693716ea0

SYMBOL_NAME: nvlddmkm+ed510

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys`

<!-- gh-comment-id:2073785381 --> @binxie33 commented on GitHub (Apr 24, 2024): Yes, it got BSOD after hanging for a while. The following is the bugcheck detail. It points to nvlddmkm.sys which is nvidia display driver. I already installed the latest nvidia driver and it did not help. `10: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Arguments: Arg1: 0000000000000001, The system cumulatively spent an extended period of time at DISPATCH_LEVEL or above. Arg2: 0000000000001e00, The watchdog period (in ticks). Arg3: fffff80069f1c340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding the cumulative timeout Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_CODE: 133 BUGCHECK_P1: 1 BUGCHECK_P2: 1e00 BUGCHECK_P3: fffff80069f1c340 BUGCHECK_P4: 0 FILE_IN_CAB: 041824-8484-01.dmp DUMP_FILE_ATTRIBUTES: 0x1808 Kernel Generated Triage Dump DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: Code.exe STACK_TEXT: ffffd201`3256b9d8 fffff800`694e3739 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`69f1c340 : nt!KeBugCheckEx ffffd201`3256b9e0 fffff800`694e2884 : 0000be47`94caa2e8 ffffd201`32551180 00000000`003bc48e 00000000`00000000 : nt!KeAccumulateTicks+0x239 ffffd201`3256ba40 fffff800`694e453f : 00000000`0000001c 00000000`00001388 00000000`003bc400 00000000`00239fd7 : nt!KiUpdateRunTime+0xf4 ffffd201`3256bc00 fffff800`694e08f8 : 00000000`00000000 ffffd201`3644da00 ffffd201`32551180 00000000`00000000 : nt!KiUpdateTime+0x63f ffffd201`3256bea0 fffff800`694e01ba : fffff800`69e5fe60 ffffd201`3644dab0 ffffd201`3644dab0 00000000`00000002 : nt!KeClockInterruptNotify+0x228 ffffd201`3256bf40 fffff800`69467e5c : 0000008e`7f62ee25 ffffe706`d81528a0 ffffe706`d8152950 fffff800`6961a38b : nt!HalpTimerClockInterrupt+0x10a ffffd201`3256bf70 fffff800`6961a5ea : ffffb986`93716d10 ffffe706`d81528a0 00000000`00900494 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c ffffd201`3256bfb0 fffff800`6961aeb7 : 00000000`0090047c fffff800`6961aec4 00000000`00900490 ffffb986`93716e38 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa ffffb986`93716c90 fffff800`966dd510 : fffff800`966dda4a ffffe706`ea9c7000 fffff800`96704fde ffffe706`ea9c7bf0 : nt!KiInterruptDispatchNoLockNoEtw+0x37 ffffb986`93716e28 fffff800`966dda4a : ffffe706`ea9c7000 fffff800`96704fde ffffe706`ea9c7bf0 ffffb986`93716e60 : nvlddmkm+0xed510 ffffb986`93716e30 ffffe706`ea9c7000 : fffff800`96704fde ffffe706`ea9c7bf0 ffffb986`93716e60 ffffe706`00000000 : nvlddmkm+0xeda4a ffffb986`93716e38 fffff800`96704fde : ffffe706`ea9c7bf0 ffffb986`93716e60 ffffe706`00000000 fffff800`00000020 : 0xffffe706`ea9c7000 ffffb986`93716e40 ffffe706`ea9c7bf0 : ffffb986`93716e60 ffffe706`00000000 fffff800`00000020 ffffb986`93716ea0 : nvlddmkm+0x114fde ffffb986`93716e48 ffffb986`93716e60 : ffffe706`00000000 fffff800`00000020 ffffb986`93716ea0 00000000`00000000 : 0xffffe706`ea9c7bf0 ffffb986`93716e50 ffffe706`00000000 : fffff800`00000020 ffffb986`93716ea0 00000000`00000000 00000000`00000000 : 0xffffb986`93716e60 ffffb986`93716e58 fffff800`00000020 : ffffb986`93716ea0 00000000`00000000 00000000`00000000 00000000`00900494 : 0xffffe706`00000000 ffffb986`93716e60 ffffb986`93716ea0 : 00000000`00000000 00000000`00000000 00000000`00900494 00000000`00000000 : 0xfffff800`00000020 ffffb986`93716e68 00000000`00000000 : 00000000`00000000 00000000`00900494 00000000`00000000 00000000`00000000 : 0xffffb986`93716ea0 SYMBOL_NAME: nvlddmkm+ed510 MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys`
GiteaMirror commented 2026-04-12 12:35:57 -05:00
Author
Owner
Copy Link

@mtavenrath commented on GitHub (May 3, 2024):

How much system RAM do you have? How big is the model you've been loading in to ollama?

<!-- gh-comment-id:2092484370 --> @mtavenrath commented on GitHub (May 3, 2024): How much system RAM do you have? How big is the model you've been loading in to ollama?
GiteaMirror commented 2026-04-12 12:35:58 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (May 21, 2024):

@binxie33 our current theory is you ran low on system memory trying to load a large model, possibly with VRAM paging taking place on the GPU. If you can repro this failure, can you run nvidia-smi to see if the GPU's VRAM is ~full, and systeminfo | find "Virtual Memory" may also help shed some light on what's going on. We'd also like to understand how much physical RAM you have in the system.

<!-- gh-comment-id:2123179253 --> @dhiltgen commented on GitHub (May 21, 2024): @binxie33 our current theory is you ran low on system memory trying to load a large model, possibly with VRAM paging taking place on the GPU. If you can repro this failure, can you run `nvidia-smi` to see if the GPU's VRAM is ~full, and `systeminfo | find "Virtual Memory"` may also help shed some light on what's going on. We'd also like to understand how much physical RAM you have in the system.
GiteaMirror commented 2026-04-12 12:35:59 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (May 31, 2024):

If you're still having problems, please share the information above and I'll re-open.

<!-- gh-comment-id:2143023688 --> @dhiltgen commented on GitHub (May 31, 2024): If you're still having problems, please share the information above and I'll re-open.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label bug nvidia windows
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#2307
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?