Member Avatar for darthfarkus

Well, I only seem to get it while I'm playing a game, and it tends to happen in laggy areas or when a lot is going on in the game. I have removed the possibility or RAM as the problem and I know it is not the game. I have a Toshiba U305 with Intel Mobile 345 graphics so I know they aren't the best to begin with. I am using XP drivers (i downgraded from Vista to XP OS) and as far as I can tell I got the right ones. I am unsure if its a hardware problem or a drivers problem and if it can even be fixed? The stop message I get just lists numbers like 0X000000E blah blah blah. I can try to crash if the precise numbers would be helpful, but I google search them and got nothing and nothing else is identified in that stop message. Can anybody offer any suggestions? Thank you.

  • 2 Contributors
  • 3 Replies
  • 144 Views
  • 16 Hours Discussion Span
  • Latest Post Latest Post by Suspishio

Dani AI

Generated

As hinted, guessing from symptoms alone often points to the graphics driver — but a few short, targeted triage steps will quickly tell whether it’s a driver, firmware, or hardware problem.

First, capture the system crash data. Configure Windows to write minidumps, reproduce the crash, and collect the .dmp files from the Minidump folder. A full dump or minidump attached to the thread gives far more to work with than a handwritten stop code. See Microsoft’s guidance on analyzing crash dumps: .

Second, analyze the dump with WinDbg (part of the Debugging Tools). Set the symbol path to Microsoft’s symbol server and run !analyze -v to get the probable faulting module. Example symbol path:

SRV*c:\symbols*https://msdl.microsoft.com/download/symbols

Guide: Getting started with WinDbg.

Third, if the dump implicates a driver but not the OS kernel, use Driver Verifier to stress-test drivers. It will usually force a failing driver to trip while producing a useful stack trace. Driver Verifier can intentionally crash the system — document how to reset it (verifier /reset) before using it. Docs: Driver Verifier.

Practical checks while diagnosing: do a clean graphics-driver install from the vendor (use the vendor/PC-maker package rather than third-party packs), update chipset/BIOS, monitor temperatures during heavy load, and try conservative game settings to see if the problem changes. , attaching the minidump or the !analyze -v output will let helpers point to the exact module and next fix.

Recommended Answers

All 3 Replies

Member Avatar for Suspishio

Usually this sort of thing is the graphics drivers crashing into other areas of RAM. So try googling the Intel Mobile 345 PROBLEM search.

Member Avatar for darthfarkus

Okay Ill try that, also I screwed up, its the 945, not 345.

Member Avatar for Suspishio

Incidentally there are a good few posts in this forum about the Itel Graphics chipset and associated problems.

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.