racket / racket/drracket

Windows 10 BSOD When Using DrRacket

Open
#121 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Racket
Stars
516
Forks
103
PR merge metrics
No merged PRs in 30d

Description

I installed Racket v6.9 (x86_64) yesterday on my Windows 10 desktop. I can use it just fine, everything functions. But after opening it, Windows 10 will consistently BSOD after a random amount of time. I've had it BSOD after having DrRacket open only a few seconds and today I had it open a good 20 minutes or so before it BSOD'd. My computer does not BSOD with any other programs or tasks, it seems to only be DrRacket.

I have no clue if this is an issue with DrRacket or my PC. It could just be that my PC has an issue that is only triggered by something DrRacket does.

Here are my specs if it helps:

i7 2600k @ 4.3GHz (Overclocked, but stable with everything else)
16GB DDR3-1600 RAM (4 Modules)
2x 1TB HDD (7200rpm & 5200rpm)
Zotac AMP! GTX 1060 6GB (Not overclocked)

Windows 10 Home
Version 1703
OS Build 15063.296

BSOD Dump File

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by analyzing the linked BSOD Dump File against the reported Windows 10 and DrRacket setup. Try to reproduce the crash using the listed hardware and version details, then determine whether DrRacket is implicated; done means a confirmed cause or a reliably actionable reproduction.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.