TechSpot

Brand New Dell, Minidump

By tide1
Apr 10, 2008
  1. Hey all. I'm new to this forum. I believe I have read all the qualifying threads about minidump procedures.

    The machine is a Dell 530s thin client, only 2 months old, tops. It has received BSOD since day one. I have done just about as much as I know to do, before calling Dell. This is my dad's machine and it has everything "Dell stocked", Windows Updates, and an HP AiO...

    I can't post links yet so here is the written out link with zipped *.dmp files:

    www(dot)shtyndall(dot)com/mini

    Anyway. Thanks a bunch! I hope someone can tell me the driver/hardware culprit.
     
  2. Matthew

    Matthew TechSpot Staff Posts: 5,268   +92

    Minidump 030208-01:

    BugCheck 40000080, {8a35d958, 89d39b48, ba4dbbb8, 1}
    Probably caused by : e1e5132.sys ( e1e5132+21f8 )

    ----------------------------------------------------------------------
    Minidump 030308-01:

    BugCheck 40000080, {8a34dad0, 89d28cd8, 805502b8, 1}
    Probably caused by : e1e5132.sys ( e1e5132+21f8 )

    ----------------------------------------------------------------------
    Minidump 030408-01:

    BugCheck 40000080, {8a390130, 89e281e8, 805502b8, 1}
    Probably caused by : e1e5132.sys ( e1e5132+21f8 )
    ----------------------------------------------------------------------
    Minidump 030408-01:

    BugCheck 40000080, {8a36e130, 89e11058, ba4dfe5c, 1}
    Probably caused by : e1e5132.sys ( e1e5132+21f8 )

    ----------------------------------------------------------------------
    Minidump 030508-01:

    Unable to load image e1e5132.sys, Win32 error 0n2
    Probably caused by : e1e5132.sys ( e1e5132+21f8 )

    ----------------------------------------------------------------------
    Minidump 030608-01:

    BugCheck 40000080, {8a383330, 89e15828, 805502b8, 1}
    Probably caused by : e1e5132.sys ( e1e5132+21f8 )
    ----------------------------------------------------------------------
    Minidump 030708-01:

    BugCheck 40000080, {8a38a4c8, 89e06b48, 805502b8, 1}
    Probably caused by : e1e5132.sys ( e1e5132+21f8 )

    ----------------------------------------------------------------------
    Minidump 030808-01:

    BugCheck 40000080, {8a369130, 89e1ae68, ba4dbbb8, 1}
    Probably caused by : e1e5132.sys ( e1e5132+21f8 )

    ----------------------------------------------------------------------
    Minidump 0301108-01:

    BugCheck 40000080, {8a35e130, 89c959b8, 805502b8, 1}
    Probably caused by : e1e5132.sys ( e1e5132+21f8 )

    ----------------------------------------------------------------------
    Minidump 032408-01

    BugCheck 40000080, {8a3695d8, 89e02e68, ba4dbbb8, 1}
    Probably caused by : e1e5132.sys ( e1e5132+21f8 )

    ----------------------------------------------------------------------
    Minidump 033008-01

    BugCheck 40000080, {8a34da68, 89e03058, ba4dbbb8, 1}
    Probably caused by : e1e5132.sys ( e1e5132+21f8 )

    ----------------------------------------------------------------------
    Minidump 041008-01

    BugCheck 40000080, {8a364998, 89e0b378, ba4dfe5c, 3}
    Probably caused by : e1e5132.sys ( e1e5132+21f8 )

    ----------------------------------------------------------------------

    :D Excessive, yes, but I'm bored at work. If you haven't gathered it - e1e5132.sys is to blame. It belongs to your Intel NIC. Update those drivers and if that doesn't solve the BSOD's, disable that device and go buy a new NIC for $9.99 ;).
     
  3. Bobbye

    Bobbye Helper on the Fringe Posts: 16,335   +36

    I don't know Zenosincks. If this Dell is only 2 months old and this has been happening 'since day one' Dell should handle it since the machine will be under the warranty.
     
  4. Matthew

    Matthew TechSpot Staff Posts: 5,268   +92

    Lol, I don't know Bobbye, on one hand you can wait two weeks for Dell to "fix" your PC, or, on the other hand, you can download updated drivers and/or spend <$10 and be good to go within a few minutes to an hour.

    I guess if they'll reimburse him without waiting ages to send the PC to Dell, go for it. I'm not bathing in money, far from it, believe me. However, <$10 isn't worth two weeks of waiting to me :).
     
  5. Bobbye

    Bobbye Helper on the Fringe Posts: 16,335   +36

    I know the time interval is important, but if I had a major problem like this on a new computer, I would hold the manufacturer responsible. There may even be additional hardware problems come up.
     
  6. tide1

    tide1 TS Rookie Topic Starter

    Ok. So I installed the newest driver build for the Intel NIC (9.12.13.0, 12.4, Feb 2008). The current driver was 9.8.20.0 (May 2007).

    So far so good. The PC has been on for 12 straight hours with no dumps.

    I'll post long term results later.
    Thanks for your time Zeno!
     
  7. Matthew

    Matthew TechSpot Staff Posts: 5,268   +92

    You're welcome, tide1.

    Bobbye, I would definitely agree in a more fatal or complicated situation. However a NIC is hardly worth the effort or wait (to me). I guess maybe if you just want to "stick it to the man" for some emotionally related gain, it's worthwhile. Sometimes, though, bending over and grabbing your ankles works out better for you in the long run.

    :) Anyway, the argument is irrelevant now, as the updated drivers appear to of worked.
     
  8. tide1

    tide1 TS Rookie Topic Starter

    Dammit! BSOD, Happened again this weekend?

    Zeno - Would you tell me if it's the same file, or something else?

    Thanks!

    www(dot)shtyndall(dot)com/mini

    If so, this b*tch is going back to Dell!!
     
  9. Matthew

    Matthew TechSpot Staff Posts: 5,268   +92

    Yep, same old deal:

    Minidump 041308-01:

    BugCheck 40000080, {8a2b1ad0, 89dfaf10, 805502bc, 1}
    Probably caused by : e1e5132.sys ( e1e5132+21f8 )


    If you're definitely sending it back to Dell (might be the best choice, now), okay. However, if you're interested in troubleshooting, you can begin by testing your RAM with Memtest86. If that is clean, I'd purchase a new NIC.
     
  10. Bobbye

    Bobbye Helper on the Fringe Posts: 16,335   +36

    Something told me that there would be more problems!
     
  11. Matthew

    Matthew TechSpot Staff Posts: 5,268   +92

    ...It's the same problem.
     
  12. Bobbye

    Bobbye Helper on the Fringe Posts: 16,335   +36

    Then the driver update didn't work. I can't open the dmp files so I can't check them. I use the Event Viewer instead.
     
  13. Matthew

    Matthew TechSpot Staff Posts: 5,268   +92

    Yes, that is true. Sadly the driver update didn't work. However, with that, it's the same problem that hasn't been fixed. It's not a new problem, nor a problem that has resurfaced again.
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...