8000 [CD] Windows CUDA 13.0 binaries : Windows fatal exception: access violation · Issue #162333 · pytorch/pytorch · GitHub
[go: up one dir, main page]

Skip to content

[CD] Windows CUDA 13.0 binaries : Windows fatal exception: access violation #162333

@atalman

Description

@atalman

🐛 Describe the bug

torch 2.9.0 nightly CUDA 13.0 build, Python 3.10
Windows CPU or GPU machine.
Failing on:

>>> torch._C._cuda_getDeviceCount()

Reproducer:

>>> import torch
>>> import faulthandler
>>> faulthandler.enable()
>>> torch.cuda.is_available()
Windows fatal exception: access violation

Current thread 0x00001980 (most recent call first):
  File "C:\Jenkins\Miniconda3\envs\py310\lib\site-packages\torch\cuda\__init__.py", line 182 in is_available
  File "<stdin>", line 1 in <module>

Expected output:

>>> import torch
>>> torch.cuda.is_available()
False

Windows Event log crash:

Faulting application name: python.exe, version: 3.10.18150.1013, time stamp: 0x6841977c
Faulting module name: c10_cuda.dll, version: 0.0.0.0, time stamp: 0x68baa4b4
Exception code: 0xc0000005
Fault offset: 0x00000000000015d3
Faulting process id: 0x1908
Faulting application start time: 0x01dc1e9d4857191a
Faulting application path: C:\Jenkins\Miniconda3\envs\py310\python.exe
Faulting module path: C:\Jenkins\Miniconda3\envs\py310\lib\site-packages\torch\lib\c10_cuda.dll
Report Id: 98017187-f664-4643-9a6e-5bbd05d1084c
Faulting package full name: 
Faulting package-relative application ID: 

Reference PR: pytorch/test-infra#7080

Versions

2.9.0

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @seemethere @malfet @peterjc123 @mszhanyi @skyline75489 @nbcsm @iremyux @Blackhex @ptrblck @eqy @jerryzh168
cc @ptrblck @tinglvv @nWEIdia @malfet

Metadata

Metadata

Assignees

Labels

high prioritymodule: binariesAnything related to official binaries that we release to usersmodule: cudaRelated to torch.cuda, and CUDA support in generalmodule: windowsWindows support for PyTorchoncall: relengIn support of CI and Release EngineeringtriagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate module

Type

No type

Projects

Status

Done

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0