Random Restarts -- MiniDumps!

By Deanznet
Jul 13, 2007
  1. Hey Their!

    I get 2 errors at random..

    Stop 0x0000008E
    and STOP: 0x00000050 Page_Fault_In_Non-Paged_Area

    Alright not sure why but i got a feeling its something to do with my Video Card..

    So i Tried Uninstalling My Video Driver and Everything Went Okay.. But Now I When i go to Reinstall my Driver i get Zero Display Service error But after i click okay it goses..

    Alright.. So Now Im going to do some virus scans but doubt it will help..

    Here Some Pc Info.

    Operating System: Windows XP Professional
    Language: English (Regional Setting: English)
    Processor: AMD Athlon(TM) XP 2400+, MMX, 3DNow, ~2.0GHz
    Memory: 512MB RAM
    Windows Dir: C:\WINDOWS
    DirectX Version: DirectX 9.0c
    Display Devices
    Card name: RADEON 9200 SERIES
    Manufacturer: ATI Technologies Inc.
    Chip type: RADEON 9250/9200 Series AGP (0x5964)
    DAC type: Internal DAC(400MHz)
    Display Memory: 128.0 MB
    Current Mode: 1024 x 768 (32 bit) (75Hz)
    Monitor: Dell M781s
    Monitor Max Res: 1600,1200
    Driver Name: ati2dvag.dll
    Driver Version: 6.14.0010.6614 (English)

    Sound Devices
    Description: SoundMAX Digital Audio
    Driver Name: smwdm.sys
    Driver Version: 5.12.0001.3663 (English)

    Disk & DVD/CD-ROM Drives
    Model: TOSHIBA ODD-DVD SD-M1802
    Model: SAMSUNG CD-R/RW SW-252F

    I Did a Memory Scan using Windows Memory Diagnostic and it Passed 9

    Here some of the minidump that i debugged..

    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arg1: ff8f2000, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 804fe25f, If non-zero, the instruction address which referenced the bad memory
    Arg4: 00000000, (reserved)
    Debugging Details:
    Could not read faulting driver name
    READ_ADDRESS:  ff8f2000 
    804fe25f 668b17          mov     dx,word ptr [edi]
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    LAST_CONTROL_TRANSFER:  from b6bff641 to 804fe25f
    f67fbb74 b6bff641 ff8f1a46 b6bff5d4 f67fbc68 nt!wcsstr+0x4d
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f67fbb90 804de7ec 00000cd8 00000000 00000000 vdo_5557_5ab2+0x641
    f67fbb90 804dd221 00000cd8 00000000 00000000 nt!KiFastCallEntry+0xf8
    f67fbc34 ba1cfa5d 00000cd8 00000000 00000000 nt!ZwQueryDirectoryFile+0x11
    f67fbcb0 ba1cfdd2 f67fbccc f67fbcec f67fbcd4 Mpfp+0xea5d
    f67fbd00 ba1c475f f67fbd3c 820afd94 00000000 Mpfp+0xedd2
    f67fbd5c ba1d7317 820afd90 00000000 829bd3a8 Mpfp+0x375f
    f67fbdac 8057d0f1 00000000 00000000 00000000 Mpfp+0x16317
    f67fbddc 804f827a ba1d726e 00000000 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
    b6bff641 85c0            test    eax,eax
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: vdo_5557_5ab2
    IMAGE_NAME:  vdo_5557-5ab2.sys
    SYMBOL_NAME:  vdo_5557_5ab2+641
    FAILURE_BUCKET_ID:  0x50_vdo_5557_5ab2+641
    BUCKET_ID:  0x50_vdo_5557_5ab2+641
    Followup: MachineOwner
    I hope you can help Thanks again!
  2. peterdiva

    peterdiva TechSpot Ambassador Posts: 1,088

    That crash is caused by vdo_5557-5ab2.sys. It's most likely an infection, as it's dated July 12 2007. Go HERE.

    BugCheck 10000050, {ff8f2000, 0, 804fe25f, 0}
    Probably caused by : vdo_5557-5ab2.sys ( vdo_5557_5ab2+641 )
    b6bff000 b6c25200 vdo_5557_5ab2 vdo_5557-5ab2.sys Thu Jul 12 21:01:27 2007 (46962627)
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...