Member Avatar for 14G_Tiger

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x80581e21, 0xba318bd8, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini080804-01.dmp.

I also have that same stop code, but I dont have an audigy card, I use the original nForce chipset sound. I ran the RAM test that was in another thread, but no errors were recorded. What you guys said and what Im getting is confusing.

  • 3 Contributors
  • 9 Replies
  • 226 Views
  • 1 Month Discussion Span
  • Latest Post Latest Post by kccomputerdr

Dani AI

Generated

Quick summary and what to do first (short checklist): gather the minidumps, run a quick dump viewer, then run targeted hardware checks. already has many minidumps in C:\Windows\Minidump — copy those files to a spare folder and run a lightweight analyzer (BlueScreenView or WhoCrashed) for an immediate, readable clue, or open the dump with WinDbg and run !analyze -v for a full trace. These tools will usually point to the driver or module on the stack so you know whether to look at drivers or hardware next. (nirsoft.net)

What the codes mean (brief): stop 0x8E maps to KERNEL_MODE_EXCEPTION_NOT_HANDLED (unhandled kernel exception) and 0x1A is MEMORY_MANAGEMENT (severe memory-management corruption). Either can be caused by bad drivers, corrupted pagefile/disk I/O, or failing RAM/board — the presence of many different stop codes over time increases the chance of hardware (memory, PSU, motherboard) being involved. Read the specific bugcheck pages to map the parameter values to likely causes. (learn.microsoft.com)

Practical hardware checks (do these before a reinstall): boot a Memtest86 USB and run multiple full passes (overnight; test each DIMM alone and in every slot); check the system drive with chkdsk /r; monitor temperatures and voltages or try a known-good PSU if available. If Memtest86 finds errors, that DIMM/slot is likely the culprit. (memtest.org)

Driver/OS isolation and final steps: update chipset/nForce, GPU and audio drivers (temporarily disable the onboard audio to rule it out), and enable Driver Verifier on non-Microsoft drivers to force a pinpointable crash if a driver is guilty — stop and disable Verifier after you capture the new dump. If none of the above finds the issue, then a clean OS install is reasonable but treat it as a last resort given 's point about time. When you post back, include one representative minidump analysis output (from BlueScreenView/WhoCrashed or the !analyze -v summary) and the Memtest log so responders can be concrete. (learn.microsoft.com)

WinDbg quick command (example):

windbg -y SRV*c:\symbols*http://msdl.microsoft.com/download/symbols -z C:\Windows\Minidump\MiniYYYYMMDD-01.dmp

then run:

!analyze -v

This will show the failing driver/module and the stack trace. (learn.microsoft.com)

Recommended Answers

All 9 Replies

Member Avatar for Bear

Have you checked Event Viewer?

Member Avatar for 14G_Tiger

Have you checked Event Viewer?

Yes thats where i found out the stop code...all it says it that it was from a bugcheck and pay Micro $30 for a chat.

I have a whole bunch of them...

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x00041284, 0x00003001, 0x00000000, 0xc0503000). A dump was saved in: C:\WINDOWS\Minidump\Mini060605-01.dmp.

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xf82e7f60, 0xf3abfbc4, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini060705-01.dmp.

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x8257e197, 0x00000002, 0x00000000, 0x804ead79). A dump was saved in: C:\WINDOWS\Minidump\Mini060705-02.dmp.

The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000000, 0x00000005, 0x00000001, 0xf617002d). A dump was saved in: C:\WINDOWS\Minidump\Mini060905-01.dmp.

I have 13 spanning 2 weeks

Member Avatar for 14G_Tiger

Yes thats where i found out the stop code...all it says it that it was from a bugcheck and pay Micro $30 for a chat.

I have a whole bunch of them...

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x00041284, 0x00003001, 0x00000000, 0xc0503000). A dump was saved in: C:\WINDOWS\Minidump\Mini060605-01.dmp.

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xf82e7f60, 0xf3abfbc4, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini060705-01.dmp.

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x8257e197, 0x00000002, 0x00000000, 0x804ead79). A dump was saved in: C:\WINDOWS\Minidump\Mini060705-02.dmp.

The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000000, 0x00000005, 0x00000001, 0xf617002d). A dump was saved in: C:\WINDOWS\Minidump\Mini060905-01.dmp.

I have 13 spanning 2 weeks

Anyone have ideas on this?? As stated, the RAM was stress tested and passed, and i cleaned the ram and the sockets. Ill put my comp specs up.

Athlon XP 2200+
512MB pc2700 RAM(2 sticks)
80 GB Hard Drive
nVidia GeForce FX 5200 w/ latest drivers
nForce1 motherboard w/ sound and NIC (which are both being used) and latest drivers.
Antec 430W PS
Win XP Home SP2

Member Avatar for 14G_Tiger

Anyone?? Ive cleaned the RAM and reseated still no fix

Member Avatar for kccomputerdr

Yes thats where i found out the stop code...all it says it that it was from a bugcheck and pay Micro $30 for a chat.

I have a whole bunch of them...

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x00041284, 0x00003001, 0x00000000, 0xc0503000). A dump was saved in: C:\WINDOWS\Minidump\Mini060605-01.dmp.

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xf82e7f60, 0xf3abfbc4, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini060705-01.dmp.

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x8257e197, 0x00000002, 0x00000000, 0x804ead79). A dump was saved in: C:\WINDOWS\Minidump\Mini060705-02.dmp.

The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000000, 0x00000005, 0x00000001, 0xf617002d). A dump was saved in: C:\WINDOWS\Minidump\Mini060905-01.dmp.

I have 13 spanning 2 weeks

Try downloading Spybot S&D from download.com, if that don't work, erase Windows & start from scratch. Much less hassle.

Member Avatar for 14G_Tiger

Try downloading Spybot S&D from download.com, if that don't work, erase Windows & start from scratch. Much less hassle.

I already did all the spyware checks im not that stupid...Redoing XP isnt an option too much info on it that I would have to reload.

Member Avatar for kccomputerdr

I already did all the spyware checks im not that stupid...Redoing XP isnt an option too much info on it that I would have to reload.

OK, was just trying to help. good luck.

Member Avatar for 14G_Tiger

sorry if that came off harsh..just really pissed off..switched out RAM with new, same problem.

Member Avatar for kccomputerdr

sorry if that came off harsh..just really pissed off..switched out RAM with new, same problem.

I know what you're saying. Sometimes computers are aggravating.

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.