BSOD running 3rd party SDK in in-house software


  1. Waf
    Posts : 1
    Windows 7 Professional 32bits
       #1

    BSOD running 3rd party SDK in in-house software


    Hello,

    Back story (feel free to skip):
    I'm one of the devs for my company's main product. During our testing we've discovered that we blue-screen on some particular model of laptop (got it to happen on 3 different machines) that we have here.
    We can reproduce it easily but not deterministically. Based on our testing so far it happens only when we use some 3rd party SDK to deal with multimedia operations (Can't do without it). We don't have access to the internals of that SDK and their support team is not exactly keen to help.

    I therefore come to you guys for help in the hope that we can at least get more information out of the blue screen.

    What I've tried so far:
    I then proceeded to follow this: dump-files-configure-windows-create-bsod to configure the system for a minidump and this: blue-screen-death-bsod-posting-instructions
    but SFDT popped an unhandled exception (Could not find file "C:\Winsows\EventApp.txt"). and didn't produce any output directory on the desktop.

    I've tried to look at the minidump file (attached) with Blue Screen Viewer. It seemed to believe that hal.dll was to blame.

    I then tried to configure verifier so it would produce more informative dumps but I was then unable to create any because of a lock-up during the BSOD at the "Initializing disk for crash dump" step.

    And now I've got no idea what to do...
    Any help on this would be greatly appreciated.
    Many thanks

    Some more details:
    Running on a fully updated win7 Pro 32bit
    Proc: Q740 i7
    Ram: 4GB (Ram is not likely the source of the pb given we've replicated the issue on 3 separate machines)
    Avast is not installed but McAfee is.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    It is stop 0x124, a hardware related crash.
    Code:
    BugCheck 124, {4, 86ed0024, 0, 0}  
    Probably caused by : GenuineIntel  
    Followup: MachineOwner
     ---------
    Follow the guide Stop 0x124 - what it means and what to try.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 14:15.
Find Us