Page 1 of 2 12 LastLast
  1.    23 Mar 2016 #1
    Join Date : Jan 2016
    Posts : 47
    Win 10

    BSOD 32 bit memory related


    I'm getting a BSOD predictably, but not every single time. I'm using an audio recording program - Sonar Platinum. It has a 32 bit and a 64 bit version. I'm in the process of shifting over to 64 bit, yet sometime I still need to open a project in 32 bit. The BSOD never happens with the 64 bit only 32 bit. 32 bit can only access 4 gig of Mem and I have 16 Gigs of Mem. So it appears that it's Mem related.

    When the 32 bit program opens I can watch the memory from the TaskManager and watch it go from about 1,.2 to 3.5 and eventually settle to 3.1. The BSOD always happens when it gets very close to 3.5. But it doesn't happen every single time.

    Yesterday it did it crashed 4x in a row, each time I rebooted and waited for the hour glasses to go away and then open the program - it crashed. Then I turned off and turned back on my MOTO AVB audio interface, which stays on all the time normally. I then booted the computer 3x and each time opening the program - no crashes. So it seems to be related to the AVB.

    When I open this program I have it programed to open to the template, if I try to change this, it changes for both 32 and 64 bit. I did find out if I open to a template with less memory use, it doesn’t crash.

    What I'm hoping is how can I make Win 10 less fickle about memory like Win 8.1 was. With Win 8.1 this never happened. No crashes on opening the 32 bit program. I think this is memory related. I tried to optimize my system to reduce memory and feel I['m about as low as I can go form what I understand.
      My ComputerSystem Spec
  2.    23 Mar 2016 #2
    Join Date : Jun 2015
    Posts : 12,952
    Windows 10 Pro

    Please locate in %SystemRoot%\System32\drivers\ a file called motuavbuac2_x64.sys, right click > properties > tab details, make a screenshot of this tab and post it.
    All the crashes are caused by this driver, but I cannot find anything about it at all.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {ffffffff8bee0000, 2, ffffd00023486531, 2}
    
    *** WARNING: Unable to verify timestamp for motuavbuac2_x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for motuavbuac2_x64.sys
    
    Could not read faulting driver name
    Probably caused by : motuavbuac2_x64.sys ( motuavbuac2_x64+28a48 )
    
    Followup:     MachineOwner
    
    2: kd> lmvm motuavbuac2_x64
    Browse full module list
    start             end                 module name
    fffff800`35910000 fffff800`35952000   motuavbuac2_x64 T (no symbols)           
        Loaded symbol image file: motuavbuac2_x64.sys
        Image path: \SystemRoot\System32\drivers\motuavbuac2_x64.sys
        Image name: motuavbuac2_x64.sys
        Browse all global symbols  functions  data
        Timestamp:        Thu Oct 09 15:22:50 2014 (54368C2A)
        CheckSum:         00048C62
        ImageSize:        00042000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My ComputersSystem Spec
  3.    23 Mar 2016 #3
    Join Date : Jan 2016
    Posts : 47
    Win 10
    Thread Starter

    Quote Originally Posted by axe0 View Post
    Please locate in %SystemRoot%\System32\drivers\ a file called motuavbuac2_x64.sys, right click > properties > tab details, make a screenshot of this tab and post it.
    All the crashes are caused by this driver, but I cannot find anything about it at all.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {ffffffff8bee0000, 2, ffffd00023486531, 2}
    
    *** WARNING: Unable to verify timestamp for motuavbuac2_x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for motuavbuac2_x64.sys
    
    Could not read faulting driver name
    Probably caused by : motuavbuac2_x64.sys ( motuavbuac2_x64+28a48 )
    
    Followup:     MachineOwner
    
    2: kd> lmvm motuavbuac2_x64
    Browse full module list
    start             end                 module name
    fffff800`35910000 fffff800`35952000   motuavbuac2_x64 T (no symbols)           
        Loaded symbol image file: motuavbuac2_x64.sys
        Image path: \SystemRoot\System32\drivers\motuavbuac2_x64.sys
        Image name: motuavbuac2_x64.sys
        Browse all global symbols  functions  data
        Timestamp:        Thu Oct 09 15:22:50 2014 (54368C2A)
        CheckSum:         00048C62
        ImageSize:        00042000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    Attachment 71119
      My ComputerSystem Spec
  4.    23 Mar 2016 #4
    Join Date : Jun 2015
    Posts : 12,952
    Windows 10 Pro

    That is not the driver
    The driver is 3 files above the motuusb64.sys
      My ComputersSystem Spec
  5.    23 Mar 2016 #5
    Join Date : Jan 2016
    Posts : 47
    Win 10
    Thread Starter

    Sorry here's the correct one
    Attachment 71128
      My ComputerSystem Spec
  6.    23 Mar 2016 #6
    Join Date : Apr 2014
    Space coast of Florida
    Posts : 5,369
    Windows 10 Pro X64 16299.19

    Did you see this on the MOTO web site: MOTU.com - MOTU and Windows 10
      My ComputersSystem Spec
  7.    23 Mar 2016 #7
    Join Date : Jan 2016
    Posts : 47
    Win 10
    Thread Starter

    Quote Originally Posted by Ztruker View Post
    Did you see this on the MOTO web site: MOTU.com - MOTU and Windows 10
    I didn't see that, but yet I have the very latest software adn firmware. I'll certainly send them all this info, since this looks like a software bug. Yet I'm still wondering if there's any way I can prevent this BSOD for now.
      My ComputerSystem Spec
  8.    23 Mar 2016 #8
    Join Date : Jan 2016
    Posts : 47
    Win 10
    Thread Starter

    Also when I look at the contents of that zip file I sent this forum. Is there a file in there that gives the info for Bug Check analysis? Which axe0 posted. in the 2nd post here? I think if I read that I would have gone straight to MOTU. Thanks for everyone's excellent, as usual, help.
      My ComputerSystem Spec
  9.    24 Mar 2016 #9
    Join Date : Jun 2015
    Posts : 12,952
    Windows 10 Pro

    Yet I'm still wondering if there's any way I can prevent this BSOD for now.
    You need to update the drivers of Motu to prevent it in the future or remove them. The drivers are too old for Windows 10.

    Is there a file in there that gives the info for Bug Check analysis? Which axe0 posted. in the 2nd post here?
    The .dmp files are the onces that show it, but I can tell you that it isn't always this easy.
    A guide for proper configuring Windbg
    WinDBG - Install Configure - Windows 10 Forums
      My ComputersSystem Spec
  10.    24 Mar 2016 #10
    Join Date : Jan 2016
    Posts : 47
    Win 10
    Thread Starter

    I am using the latest MOTU software 1.5. Today I just uninstalled it and then reinstalled it - same BSOD
      My ComputerSystem Spec

 
Page 1 of 2 12 LastLast


Similar Threads
Thread Forum
Driver related BSOD
Was having a lot of BSODs on my computer, so I completely formatted and reinstalled windows 10 - not a few days into the fresh reinstall, the bsods started coming again. So today I had a random bsod, which named ndis.sys as the problem. I then...
BSOD Crashes and Debugging
Solved BSOD audio/video related?? Please help!
Hi there, Desktop PC, WIn10 64 bit, no problems until yesterday. A series of BSOD which often occurr when watching some videos/listenings to some music/playing some games; so I think they could be related to the video or audio card. If I don't do...
BSOD Crashes and Debugging
Occasional Random BOSD, related to the kernal -potential memory issue?
I ran dm_log_collector.exe, and I think it grabbed all of my BSODs (some I think I fixed). But if you look at the most recent one (and similar ones) -- that is the type of error I'm talking about. According to BSOD Viewer, my error occurs at...
BSOD Crashes and Debugging
Random BSOD always related to ntoskrnl.exe
Hi, Having these BSOD happen almost once a week. It never happens when gaming or doing anything demanding. It seems to happen alot when either watching Twitch or Netflix. I have already ran a memtest with 7 passes with no errors. Could...
BSOD Crashes and Debugging
BSOD related to Memory & Flash Player (I think)
Since up loading to 10, I have had a few BODS some with or without a warning message that there is insufficient memory space, but memory diagnostics show no issues. Here are the dumps from two of the latest incidents: 29213 29212
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:10.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums