BSOD on startup, next boot is normal


  1. Posts : 37
    Windows 7 Enterprise 64bit
       #1

    BSOD on startup, next boot is normal


    Hello. Today when computer started automatically to run windows update, I had found it in BSOD state with message "REFERENCE BY POINTER" or something like that. I tried three following reboots but it always happened again. So I booted to safe mode (with networking) and than back to normal mode and it somehow fixed it.

    Also there were other BSOD without any useful message. These usually happens after fresh reboot, before the desktop is shown. Than another reboot directly to normal mode is ok and works fine for a like time. I use hibernation most of the time and it recovers fine from it pretty fine.
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    The BSODs were caused by SbieDrv.sys which is the Sandboxie kernel driver, uninstall this program.

    Code:
    BugCheck 1000008E, {c0000005, 8c000000, a6e3fb11, 0}
    
    Unable to load image \??\C:\Program Files\Sandboxie\SbieDrv.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for SbieDrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for SbieDrv.sys
    Probably caused by : SbieDrv.sys ( SbieDrv+1a028 )
      My Computer


  3. Posts : 37
    Windows 7 Enterprise 64bit
    Thread Starter
       #3

    Thank you for reply. I uninstalled it, rebooted and it worked fine. I will wait for couple more days before closing this. Although it's weird, friend of mine is using Sandboxie and has no issues. Is it possible to trace somehow if there are some possible conflicts that can cause it ?
      My Computer


  4. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #4

    FredyC said:
    Thank you for reply. I uninstalled it, rebooted and it worked fine. I will wait for couple more days before closing this. Although it's weird, friend of mine is using Sandboxie and has no issues. Is it possible to trace somehow if there are some possible conflicts that can cause it ?
    You could try contacting Sanboxie for a system-specific fix. Here the issue lies in their kernel driver, anything at this level cannot be fixed easily. It's a known issue and a lot of people have reported that on the Sanboxie forums, only they can provide answers.
      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 20:57.
Find Us