Member Avatar for ps101

I have a MSI neo platinum 4 mb with 2 gig ram tested with memtest, updated all drivers including video and get random bsod errors irql_not_less_or_equal. The computer may go for days than all of a sudden the machin shuts down. I have reloaded windows xp 2 times and the problem still recurrs. I can not repeat or duplicate the problem. The machine may work fine for 1 hour or for 6 or 7 days then it happens. I am using windows xp professional have all the windows updates still random bsod as above. No new software or hardware added. But this machine has been doing this over and over even with the reinstallation of windows xp.

  • 3 Contributors
  • 4 Replies
  • 121 Views
  • 22 Hours Discussion Span
  • Latest Post Latest Post by caperjack

Dani AI

Generated

A quick, focused plan to get usable evidence and avoid chasing random symptoms.

IRQL_NOT_LESS_OR_EQUAL usually means a kernel-mode component tried to access memory at the wrong IRQL. The authoritative reference is Microsoft’s bugcheck note: . Collecting and analyzing the dump is the only way to point to the offending driver or module.

Capture and post dumps

  • As suggested, disable automatic restart so the stop code is visible.
  • Collect the small minidumps from C:\Windows\Minidump (zip them). Also export the System event log range around the crash and a msinfo32 text export.
  • has the dumps ready to post; post them zipped so they can be grabbed for analysis. offered to look — include the above files.

Quick analysis workflow (recommended tools)

  • Use NirSoft BlueScreenView for a quick look: BlueScreenView.
  • For definitive analysis use WinDbg (Debugging Tools for Windows). Set symbols and run !analyze -v. Example WinDbg start commands:
.symfix
.sympath SRV*C:\Symbols*https://msdl.microsoft.com/download/symbols
.reload /f
!analyze -v
lmvm <suspect_driver.sys>
k

What to look for: MODULE_NAME / IMAGE_NAME entries, stack trace pointing to a third-party .sys, or check for repeated failure buckets.

Next diagnostic steps if the dump is inconclusive

  • Run Driver Verifier on non-Microsoft drivers only (it will force a crash to reveal the bad driver) — see Microsoft’s Driver Verifier guide: Driver Verifier. Disable it from Safe Mode if needed.
  • If drivers are not implicated, test hardware: single RAM stick in different slots, try a different GPU (or onboard), and run stress tests while watching voltages/temps. Also check for bad motherboard capacitors and BIOS/chipset updates.

Post the zipped minidumps plus the msinfo32 and event log; that will allow concrete identification of the culprit rather than guesswork.

Recommended Answers

All 4 Replies

Member Avatar for jbennet

Try updating to Sp3.

Is it overheating?
Got enough power?

Member Avatar for ps101

Try updating to Sp3.

Is it overheating?
Got enough power?

As far as I know NO. I have the case open and it has 600 watt thermaltake power supply that is new. I could post the minidumps if someone would like to take a stab at looking at them to determine the cause of the BSOD. I have checked almost everything and have come up empty on the cause of this BSOD.

Member Avatar for jbennet

Go into system -> advanced -> startup and recovery

turn "automatically restart" off. Next time it BSODs makea note of the number which begins with 0x and post it here

Member Avatar for caperjack

I could post the minidumps if someone would like to take a stab at looking at them to determine the cause of the BSOD. .

post them and i will have a look see ,just learning all this ,but you never know i may see something !

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.