Vista Blue Screen RRS feed

  • Question

  • I created a MDI application in .NET VC++. I am using ALT+G to open a new window. In order to create new window I am using OnFileNew() function. While opening I am trying to open and play a sound file (It is an editing software).

    But it crashes in Windows Vista enterprise and businss version. It is working fine in all other Wiondows versions including XP and 2000.

    As a part of troubleshoot I installed DirectX 9.0 runtime (Since I am using DirectX to play sound) in Enterprise version.Then it started working fine. But this method did not help me in Vista business version.
    Friday, July 10, 2009 9:43 AM


All replies

  • I don't see how this is related to the Common Language Runtime. Perhaps you should try a C++ or DirectX forum.
    Mattias, C# MVP
    Friday, July 10, 2009 10:42 AM
  • .NET code cannot generate BSODs.  Update your drivers, start with the audio hardware.

    Hans Passant.
    Friday, July 10, 2009 10:52 AM
  • Athough trying upgrading random stuff could work, i suggest creating a memory dump and using windbg to analyze what caused the bsod.
    Friday, July 10, 2009 12:42 PM
  • Thanks for the info. I tried the same and here is the result:




    LAST_CONTROL_TRANSFER:  from 9532d9a2 to 9526a0d8

    WARNING: Stack unwind information not available. Following frames may be wrong.
    914f79fc 9532d9a2 d2010fa1 00000001 00000001 win32k+0x6a0d8
    914f7c78 952dab6d ff03b138 00000000 0000029e win32k+0x12d9a2
    914f7cd4 952dd0a2 ff03b138 00000101 00000012 win32k+0xdab6d
    914f7cec 952dd9b6 ff03b138 00000101 00000012 win32k+0xdd0a2
    914f7d08 952dceee ff03b138 00000101 00000012 win32k+0xdd9b6
    914f7d40 818461fa 00090508 00000101 00000012 win32k+0xdceee
    914f7d64 76fa0f34 badb0d00 0012f5dc 00000000 nt+0x461fa
    914f7d68 badb0d00 0012f5dc 00000000 00000000 0x76fa0f34
    914f7d6c 0012f5dc 00000000 00000000 00000000 0xbadb0d00
    914f7d70 00000000 00000000 00000000 00000000 0x12f5dc


    9526a0d8 ff4604          inc     dword ptr [esi+4]


    SYMBOL_NAME:  win32k+6a0d8

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  win32k.sys


    Followup: MachineOwner

    If you are getting any idea..please inform

    Friday, July 10, 2009 1:21 PM
  • setting up your symbols would definitly not hurt after you done that run !analyze -v. The crash originating in win32k.sys does not look hopefull though might as well just be a case of bad ram.
    Friday, July 10, 2009 1:31 PM
  • This is one of the best videos ever:

    It's Russinovich: Windows Hang and Crash Dump Analysis. Enjoy. :)

    Programming blog: http://nitoprograms.blogspot.com/
      Including my TCP/IP .NET Sockets FAQ
    MSBuild user? Try out the DynamicExecute task in the MSBuild Extension Pack source; it's currently in Beta so get your comments in!
    • Marked as answer by Zhi-Xin Ye Thursday, July 16, 2009 2:09 PM
    Friday, July 10, 2009 1:36 PM