TechSpot

BSOD 10e - Maybe faulty Video?

By lowridaah
Jun 13, 2008
  1. After playnig for a while (psychonauts), i decided to quit ... and B000m - B S O D (10e) & Restart !!
    Brand new laptop Dell XPS M1530 - GC GF 8600 GT driver version is 169.09 , OS Vista 32 bit etc...
    Never had problems before...
    Here is the most important part of minidup file ...

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
    The video memory manager encountered a condition that it can't recover from. By crashing,
    the video memory manager is attempting to get enough information into the minidump such that
    somebody can pinpoint what lead to this condition.
    Arguments:
    Arg1: 00000002, Process heap being destroyed isn't empty.
    Arg2: 00000001
    Arg3: 00000000
    Arg4: 00000000

    Debugging Details:
    ------------------

    *** WARNING: Unable to verify timestamp for SASKUTIL.sys
    *** ERROR: Module load completed but symbols could not be loaded for SASKUTIL.sys


    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x10E

    PROCESS_NAME: Psychonauts.exe

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from 8b33e22f to 81cd8681

    STACK_TEXT:
    a07ebb30 8b33e22f 0000010e 00000002 00000001 nt!KeBugCheckEx+0x1e
    a07ebb58 8b8374f2 00000000 0000010e 00000002 watchdog!WdLogEvent5+0x12f
    a07ebb88 8b807c8f a8317b98 a07ebba8 8b837426 dxgkrnl!VIDMM_PROCESS_HEAP::~VIDMM_PROCESS_HEAP+0x62
    a07ebb94 8b837426 00000001 8b807c44 a6b0f940 dxgkrnl!VIDMM_PROCESS_HEAP::`scalar deleting destructor'+0xd
    a07ebb9c 8b807c44 a6b0f940 a07ebbd8 8b837662 dxgkrnl!VIDMM_PROCESS::~VIDMM_PROCESS+0x50
    a07ebba8 8b837662 00000001 fe45772c fe45772c dxgkrnl!VIDMM_PROCESS::`scalar deleting destructor'+0xd
    a07ebbd8 8b8372f7 81c5430f fe4576b0 00000000 dxgkrnl!DXGPROCESS::Destroy+0x132
    a07ebc10 8faa6858 fe45772c 8fbcdf28 00000000 dxgkrnl!DxgkProcessCallout+0x108
    a07ebc24 8faa67bc fe45772c 00000000 fe4576b0 win32k!DxDdProcessCallout+0x1b
    a07ebc4c 8fabbfbb fe4576b0 00000001 94d00ac8 win32k!GdiProcessCallout+0x170
    a07ebc68 81e1bb42 98ea3b60 00000000 a07e0794 win32k!W32pProcessCallout+0x5d
    a07ebcd4 81e1ad7a 00000000 00000000 94d31030 nt!PspExitThread+0x484
    a07ebcf4 81e1b265 94d31030 00000000 00000001 nt!PspTerminateThreadByPointer+0x5b
    a07ebd24 8cb45fc0 ffffffff 00000000 00000000 nt!NtTerminateProcess+0x1e0
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a07ebd54 81c8caaa ffffffff 00000000 0022fea8 SASKUTIL+0x8fc0
    a07ebd54 771a0f34 ffffffff 00000000 0022fea8 nt!KiFastCallEntry+0x12a
    0022fea8 00000000 00000000 00000000 00000000 0x771a0f34


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    dxgkrnl!VIDMM_PROCESS_HEAP::~VIDMM_PROCESS_HEAP+62
    8b8374f2 c745fc6effffff mov dword ptr [ebp-4],0FFFFFF6Eh

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: dxgkrnl!VIDMM_PROCESS_HEAP::~VIDMM_PROCESS_HEAP+62

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: dxgkrnl

    IMAGE_NAME: dxgkrnl.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 46a94569

    FAILURE_BUCKET_ID: 0x10E_dxgkrnl!VIDMM_PROCESS_HEAP::_VIDMM_PROCESS_HEAP+62

    BUCKET_ID: 0x10E_dxgkrnl!VIDMM_PROCESS_HEAP::_VIDMM_PROCESS_HEAP+62

    Followup: MachineOwner



    -----------


    So ... what do u guys think , is it harware related or no? If it is a hardware problem i'll try to return it.
     
  2. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    According to MS this bug check is usually caused by a video driver behaving improperly. Try updating your drivers.
     
  3. lowridaah

    lowridaah TS Rookie Topic Starter

    Let me draw your attention to this :

    "
    "

    SASKUTIL? WTF?

    After some research i've some doubts...
    I'm using SUPERAntiSpyware now , and that file "saskutil.sys" is in the same folder of the detection tool.

    What could cause interaction between SASKUTIL.SYS and video driver?


    Thaks 4 your time :)
     
  4. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Do your BSODs only occur with Psychonauts? It could very well be that this game conflicts with your system and it is being expressed via your video.

    I have seen this happen may times. If it only occurs with psychonauts then I would say it is the game drivers causing the conflicts.

    As for SASKUTIL.sys (a SUPERAntispyware driver; I use it myself) it appears it is blocked from loading when this conflict occurs. At this point i would say it is the symptom of the issue and not the issue itself. Or SAS and Psychonauts may conflict.

    Then again, all that may be needed is updated graphics drivers.
     
  5. lowridaah

    lowridaah TS Rookie Topic Starter

    Yes only there but ... after this i went mad and deinstalled it fast as possible.

    So , In Conclusion ...

    no hardware issue 4 sure right? :)
     
  6. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    I don't know, we'll see. Notice in your minidump how the process Psychonauts.exe is in the mix.

    If you have stability from here on out then it was this game causing the conflict that might have been resolved with updated graphic drivers. But if your graphics drivers have been working well otherwise then leave as is and bury Psychonauts. :D

    However, it there are updates from Dell in the future you may want to give it a shot.

    Get back to us and let us know if you have continue to have stability.
     
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...