Member Avatar for skinner72

Hi Folks

This above error has just started to occur and it only happens when I try to play battlefield 2142 for some reason.

From what little I can gather this is usually a hardware driver issue so, on that basis I updated all my drivers tonight. Unfortuantely this had no effect and it happened again.

I read on a thread somewhere that it may be something to do with devices sharing the same channel (sorry I am not very tech minded I'm afraid)

Can anyone help as it seems that this could be a multitude of things ranging from the above, to bad RAM (I recently added 2x512mb)

As this error only occurs when I try to play Battlefield (which is an online registration) I don't theink the RAM is to blame so, I have a feeling it's to do with this device sharing dealy but I am unsure how I can check and then rectify this

Apologies for the long winded post, but I'm pulling my hair out here, Please Help!!!!

I will add to the post the exact content of the blue screen error message in the hope that it may shed some light on it
TIA
Skin

  • 4 Contributors
  • 4 Replies
  • 358 Views
  • 1 Year Discussion Span
  • Latest Post Latest Post by bigbill20176

Dani AI

Generated

Brief summary and where to focus

posted a 0xD1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL) crash that names D24WDM.SYS. Replies from , and rightly explored RAM and drivers, but the presence of a specific .SYS name is useful: it lets you target diagnostic work instead of guessing. Below is a short, prioritized troubleshooting checklist that moves from information-gathering to safe, reversible tests.

Collect and analyse the dumps first

  • Locate small/full dumps in C:\Windows\Minidump (or set Small Dump in System > Advanced > Startup and Recovery).
  • Use a lightweight analyzer first (BlueScreenView or WhoCrashed) to get a readable driver/module and stack; use WinDbg if you want full detail and symbols. These tools save a lot of time vs guessing. See Microsoft on the 0xD1 bugcheck and basic dump analysis, and tool pages for BlueScreenView/WhoCrashed.
    • Microsoft: Bug Check 0xD1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL).
    • BlueScreenView (NirSoft).
    • WhoCrashed (Resplendence).
    • WinDbg / Debugging Tools (Microsoft).

Identify the D24WDM.SYS owner and path

  • Find the file and vendor before changing it: check Properties in Explorer, or run a driver inventory to locate it and any duplicates. Example commands:
    driverquery /v /fo list | findstr /i "D24WDM"
  • Use Sysinternals Sigcheck to inspect publisher/signature and timestamp; Autoruns (Drivers tab) or Device Manager → Driver Details can show which service/device owns the .sys file. (Sigcheck and Autoruns docs linked below.)

Targeted, cautious remediation

  • If the file is from a third‑party (non‑Microsoft) vendor, try a clean uninstall + vendor/OEM driver reinstall (use the OEM site for chipset/video drivers if the file is OEM-specific — ’s VIA update is a good example of that working).
  • If the crash persists and the file looks suspect, enable Driver Verifier for that driver only to force a deterministic failure (this will likely cause BSODs so do it with a plan to disable: verifier /reset). Microsoft’s Driver Verifier docs explain risks and usage.
  • If you need to isolate software interaction, boot Safe Mode / perform a clean boot to rule out overlays, anti‑cheat or background hooks that only run during games.

If nothing pins down the fault, save the minidump and the exact D24WDM.SYS file (and its Properties output) and share them with the vendor or post them in a technical forum — people can often identify the vendor from the file metadata. Useful references: Microsoft 0xD1 doc, Driver Verifier guide, BlueScreenView, WhoCrashed, Sigcheck, and Autoruns.

Recommended Answers

All 4 Replies

Member Avatar for skinner72

Hi Skin again,

The blue screen says the following

Stop: and then a series of numbers followed by

D24WDM.SYS Address Ba68DCFB base at BA68C0000
Datestamp 403f091B
Beginning dump of physical memory
Physical memory dump complete
Contact your systems admin for more info

Not sure if that helps or muddies the water further

TIA
Skin

Member Avatar for Kn10

DRIVER_IRQL_NOT_LESS_OR_EQUAL is usually bad ram. This article should help as it shows you how to diagnose bad RAM. It actually specifically mentions that error in the article as being a RAM issue:

http://www.technibble.com/how-to-diagnose-bad-ram/

Member Avatar for mechbas

gaming is video, CPU, and RAM intensive.
The error codes after the STOP msg. would be most revealing.
D24WDM.SYS appears to be a VGA driver. check for correct path statement in registry (Image statements in reg. IS NOT the same as a path statement, DO NOT edit registry w/out instruction from OEM), check to see IF the file (& correct ver.) IS where it's supposed to be, check system for duplicate incorrect ver. copies of the same file, contact OEM.

Member Avatar for bigbill20176

Emachine with VIA chipset-ran memtest ok tried fresh instal w2000 no problem but balked on xp pro install - played with ram no help finally updaded via with 4 in 1 from Emachine site and cleared up problem

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.