Help for Minidumps BSOD on toshiba laptop

By Gabbon ยท 9 replies
Mar 8, 2006
  1. Hi,
    Would anyone be able to give an accurate reading of the attached minidumps?
    Previous tech guys thought it might be the drive. The OS has been re-installed by them, but that didn't help.

    Attached Files:

  2. altheman

    altheman TS Rookie Posts: 425

    im no expert, but it seems some system files may be corrupted. minidump 012906 was caused by memory corruption, 020306 and 021706 were caused by ntfs.sys.

    dumps 021906 was caused by mouhid.sys, which is some sort of input driver, 022306 was caused by symevent.sys, a file that belongs to symantec, dump 030206 wa caused by win32k.sys.

    the first thing you should do is run sfc/scannow from command prompt to check ur system file integrety, and then download and run memtest to check ur ram condition. hope this helps
  3. Gabbon

    Gabbon TS Rookie Topic Starter Posts: 23

    Toshiba minidump question

    thanks for your reply.
    Any further clues as to what could be causing the BSOD's?
    win XP has been re-installed, and it continues
    memtest86 tests out just fine
    & I tried sfc/scannow too.
  4. altheman

    altheman TS Rookie Posts: 425

    if sfc and memetest passed, it could be some other hardware problem. try running a SMART scan on your hd, manufacturers ususally supply downloadable tools to do this. other then that im not too sure, some1 else here might be able to help more :).
  5. Gabbon

    Gabbon TS Rookie Topic Starter Posts: 23

    reading Toshiba minidump ???

    Hmmm, yes, Toshiba have no HDD diagnostic tools as far as I know.
    Can anyone read a little more detail into the minidump files I posted?
    That'd be great.
  6. cpc2004

    cpc2004 TS Evangelist Posts: 1,994


    I find the footprint of the Norton AV at the stack trace of three minidump. You had better upgrade Norton AV to latest patches. If it still crashes, reseat the memort module to another slot and make sure your PC is not overheated.

    Mini012906-01.dmp BugCheck 10000050, {f00018f5, 0, f00018f5, 3}
    Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+3b ) <-- maybe caused by hardware but not sure ??

    Mini020306-01.dmp BugCheck 24, {1902fe, efa646ec, efa643e8, 8057dc88}
    Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCleanup+2271 ) <- Stack trace has footprint of Norton AV

    Mini021706-01.dmp BugCheck 24, {1902fe, ef8f01dc, ef8efed8, 8057dc88}
    Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCleanup+2271 ) <- Stack trace has footprint of Norton AV

    Mini021906-01.dmp BugCheck 100000D1, {408b0c45, 2, 1, f79f583b}
    Probably caused by : hardware ( mouhid!MouHid_ReadComplete+5 ) <-- hardware problem (ram, m/b, psu or overheat)

    Mini022306-01.dmp BugCheck 1000008E, {c000001d, f0a49839, f07a2968, 0}
    Probably caused by : SYMEVENT.SYS ( SYMEVENT+a839 ) <-- caused by hardware problem (ie ram or motherboard) or software error of Norton AV

    Mini030206-01.dmp BugCheck 1000008E, {c0000005, bf80197a, efc90920, 0}
    Probably caused by : win32k.sys ( win32k!HMAssignmentLock+26 ) <-- caused by hardware problem (ie faulty ram)
  7. Gabbon

    Gabbon TS Rookie Topic Starter Posts: 23

    Hi cpc2004,
    thanks for your input.
    I'll do the updates & post again if it does not solve the problem.
  8. Gabbon

    Gabbon TS Rookie Topic Starter Posts: 23

    How to narrow down BSOD causer more...

    I wondered if anyone could give some further clues on the cause of the Toshiba laptop crashes. cpc2004 gave some input on the first minidumps I posted. since then, I've had 8 more BSODs (narrowing this down would help alot).
    I'll post the latest 6 minidumps following:
  9. Gabbon

    Gabbon TS Rookie Topic Starter Posts: 23

    Well, It's been a long long time since I've posted, but the problem seems to have remained...

    I did a clean install from a WinXP disk, and it has possibly made the system more stable, but the blue screens keep coming.

    Would anyone be able to suggest anything from the lastest five minidumps?

    Thanks... I'll attach them.
  10. Route44

    Route44 TechSpot Ambassador Posts: 11,984   +72


    A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues.

    The driver cited is wdmaud.sys which belongs to the Windows Wave/Midi API mapper. It is a sound driver and a core Windows driver.

    The other three are 0x8E errors and these are basically due to hardware issues. The problem is it only lists win32.sys as the problem which is too general as well as too broad to help much.

    * Toshiba harddrives will work with Seagate Tools harddrive diagnostic utility. I suggest downloading and running the Long DST.
Topic Status:
Not open for further replies.

Similar Topics

Add your comment to this article

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