BSOD using Unity Editor

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 7 64bit

    BSOD using Unity Editor

    My computer has BSOD'd 12 times in the past month; I think every time it has been while I have been developing in the Unity editor though I often have many things up at once: Chrome with 10+ tabs, Unity, FlashDevelop, Skype... I have a lenovo G780 laptop. I have disabled the virus protection stuff that comes preinstalled on the laptop and have run the hardware checks and virus checks manually with no issues found. I've also run HijackThis and haven't found anything strang. Any help would be greatly appreciated.

    - Will
      My Computer

  2. Posts : 3,056
    Windows 10

    Hello and welcome :)!

    The bugchecks are all the same pretty much in blaming an OEM Lenovo driver.

    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arg1: fffff8a012d4e000, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff800033909f3, If non-zero, the instruction address which referenced 
            the bad address.
    Arg4: 0000000000000000, (reserved)
    Probably caused by : fbfmon.sys ( fbfmon+330f )
    Two Lenovo drivers, please remove or update.
    lmvm fbfmon
    start             end                 module name
    fffff880`01be6000 fffff880`01bfa000   fbfmon   T (no symbols)           
        Loaded symbol image file: fbfmon.sys
        Image path: \SystemRoot\system32\drivers\fbfmon.sys
        Image name: fbfmon.sys
        Timestamp:        Thu Jan 27 17:35:42 2011

    lmvm DamageGuardX64
    Browse full module list
    start             end                 module name
    fffff880`013b5000 fffff880`013ec000   DamageGuardX64 T (no symbols)           
        Loaded symbol image file: DamageGuardX64.sys
        Image path: \SystemRoot\system32\DRIVERS\DamageGuardX64.sys
        Image name: DamageGuardX64.sys
        Browse all global symbols  functions  data
        Timestamp:        Thu Feb 09 07:36:21 2012

    We see that McAfee is also active in the stack interacting with fltmgr.

    0xfffff8800acc0268 : 0xfffff800033784e2 : nt!CcMapData+0xd2
    0xfffff8800acc02e8 : 0xfffff8800164285c : Ntfs!NtfsExtendedCompleteRequestInternal+0x11c
    0xfffff8800acc0328 : 0xfffff880016f3383 : Ntfs!NtfsReadUsnJournal+0xb52
    0xfffff8800acc0368 : 0xfffff80003077cae : nt!KiPageFault+0x16e
    0xfffff8800acc0370 : 0x0000000000000000 :  Trap @ fffff8800acc0370
    0xfffff8800acc0498 : 0xfffff880016f15cf : Ntfs!NtOfsPostNewLength+0x16b
    0xfffff8800acc04d8 : 0xfffff800033909f3 : nt!FsRtlNotifyFilterReportChange+0x3c7
    0xfffff8800acc0528 : 0xfffff880016df4ef : Ntfs!NtfsCommitCurrentTransaction+0x9f
    0xfffff8800acc05a8 : 0xfffff880016ab5e1 : Ntfs!NtfsRenameLcb+0xed
    0xfffff8800acc05e8 : 0xfffff880016ab0f0 : Ntfs!NtfsRenameLinkInDir+0xd4
    0xfffff8800acc0628 : 0xfffff8800164aad9 : Ntfs!NtfsReportDirNotify+0xe5
    0xfffff8800acc06f8 : 0xfffff880016a98e9 : Ntfs!NtfsSetRenameInfo+0xb59
    0xfffff8800acc0968 : 0xfffff8800acc0980 :  !du "tempFile"
    0xfffff8800acc0980 : 0x0070006d00650074 :  !du "tempFile"
    0xfffff8800acc09e8 : 0xfffff80003091891 : nt!FsRtlCheckOplockEx+0x5b1
    0xfffff8800acc09f8 : 0xfffff800031ade80 : nt!ExAllocatePoolWithTag+0x270
    Unable to load image \SystemRoot\system32\DRIVERS\DamageGuardX64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for DamageGuardX64.sys
    *** ERROR: Module load completed but symbols could not be loaded for DamageGuardX64.sys
    Unable to load image \SystemRoot\system32\drivers\mfehidk.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for mfehidk.sys
    *** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
    Unable to load image \SystemRoot\system32\drivers\mfeavfk.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for mfeavfk.sys
    *** ERROR: Module load completed but symbols could not be loaded for mfeavfk.sys
    0xfffff8800acc0ae8 : 0xfffff880016cd985 : Ntfs!NtfsCommonSetInformation+0x7d5
    0xfffff8800acc0b88 : 0xfffff8800164227e : Ntfs!NtfsInitializeTopLevelIrp+0x3e
    0xfffff8800acc0bc8 : 0xfffff8800163ff84 : Ntfs!NtfsFsdSetInformation+0x11c
    0xfffff8800acc0c48 : 0xfffff8800142cbcf : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
    0xfffff8800acc0c78 : 0xfffff800032ec800 : nt!IopOpenLinkOrRenameTarget+0x140
    0xfffff8800acc0cd8 : 0xfffff8800142b6df : fltmgr!FltpDispatch+0xcf
    *** WARNING: Unable to verify timestamp for fbfmon.sys
    *** ERROR: Module load completed but symbols could not be loaded for fbfmon.sys
    0xfffff8800acc0dd8 : 0xfffff80003359703 : nt!NtSetInformationFile+0x91f
    0xfffff8800acc0ef8 : 0xfffff80003078e13 : nt!KiSystemServiceCopyEnd+0x13
    0xfffff8800acc0f68 : 0xfffff80003078e13 : nt!KiSystemServiceCopyEnd+0x13
    0xfffff8800acc0f70 : 0xfffffa800f1a2060 :  Trap @ fffff8800acc0f70
    lmvm mfehidk
    Browse full module list
    start             end                 module name
    fffff880`0148a000 fffff880`01543700   mfehidk  T (no symbols)           
        Loaded symbol image file: mfehidk.sys
        Image path: \SystemRoot\system32\drivers\mfehidk.sys
        Image name: mfehidk.sys
        Browse all global symbols  functions  data
        Timestamp:        Wed Nov 07 00:47:12 2012

    lmvm mfeavfk
    Browse full module list
    start             end                 module name
    fffff880`0639d000 fffff880`063e6600   mfeavfk  T (no symbols)           
        Loaded symbol image file: mfeavfk.sys
        Image path: \SystemRoot\system32\drivers\mfeavfk.sys
        Image name: mfeavfk.sys
        Browse all global symbols  functions  data
        Timestamp:        Wed Nov 07 00:48:17 2012

    lmvm mfefirek
    Browse full module list
    start             end                 module name
    fffff880`0685d000 fffff880`068d8680   mfefirek   (deferred)             
        Image path: \SystemRoot\system32\drivers\mfefirek.sys
        Image name: mfefirek.sys
        Browse all global symbols  functions  data
        Timestamp:        Wed Nov 07 00:50:08 2012

    Please remove McAfee.
    I suggest using Microsoft Security Essentials as a reliable alternative.

    Here from a number of different 0xD1, the Dell wireless needs an update as well.
    lmvm bcmwl664
    Browse full module list
    start             end                 module name
    fffff880`05a87000 fffff880`05f11000   bcmwl664   (deferred)             
        Image path: \SystemRoot\system32\DRIVERS\bcmwl664.sys
        Image name: bcmwl664.sys
        Browse all global symbols  functions  data
        Timestamp:        Thu Oct 27 05:45:09 2011

    Post back with the results :).
      My Computer

  3. Posts : 7
    Windows 7 64bit
    Thread Starter

    OK Thanks SO much. Apparently McAfee has a hidden special tool that you are supposed to run to Uninstall McAfee more after you've already uninstalled it.... um yea. It's called MCPR if anyone else is looking. Running that tool removed all those weird driver files. Also updated the wifi driver and uninstalled the Lenovo Boot Optimizer which came preinstalled on this thing. So far so good but will keep yall posted if another bsod happens; it's not every day so it may take a while.
      My Computer

  4. Posts : 7
    Windows 7 64bit
    Thread Starter

    The computer BSOD'd again today under the same conditions Running Unity/Chrome/Skype/Notepad++. I've attached the latest dump files.
      My Computer

  5. Posts : 3,056
    Windows 10

    Thanks for the feed back :) .
    In this bugcheck similar to the first one where we see DamageGuardX64.sys causing problems
    which is a part of lenovo instant reset.
    damageguardsvc.exe    c:\program files\lenovo\instant reset\damageguardsvc.exe
    0xfffff8800656be58 : 0xfffff8000337f4e2 : nt!CcMapData+0xd2
    0xfffff8800656bed8 : 0xfffff8800166885c : Ntfs!NtfsExtendedCompleteRequestInternal+0x11c
    0xfffff8800656bf18 : 0xfffff88001719383 : Ntfs!NtfsReadUsnJournal+0xb52
    0xfffff8800656bf78 : 0xfffff8000307ecae : nt!KiPageFault+0x16e
    0xfffff8800656bf80 : 0x0000000000000000 :  Trap @ fffff8800656bf80
    0xfffff8800656c088 : 0xfffff880017175cf : Ntfs!NtOfsPostNewLength+0x16b
    0xfffff8800656c0b8 : 0xfffff88001717f9d : Ntfs!LfsResetUndoTotal+0x17d
    0xfffff8800656c0e8 : 0xfffff800033979f3 : nt!FsRtlNotifyFilterReportChange+0x3c7
    0xfffff8800656c118 : 0xfffff880017054ef : Ntfs!NtfsCommitCurrentTransaction+0x9f
    0xfffff8800656c148 : 0xfffff8800165c036 : Ntfs!NtfsUpdateCcbsForLcbMove+0x106
    0xfffff8800656c1d8 : 0xfffff8800177fb5e : Ntfs!NtfsMoveLinkToNewDir+0x3ad
    0xfffff8800656c238 : 0xfffff88001670ad9 : Ntfs!NtfsReportDirNotify+0xe5
    0xfffff8800656c2c8 : 0xfffff880016c8539 : Ntfs!NtfsUpdateFcbFromLinkRemoval+0x29
    0xfffff8800656c308 : 0xfffff880016cf8e9 : Ntfs!NtfsSetRenameInfo+0xb59
    0xfffff8800656c4c8 : 0xfffff88000c600c6 : "PSHED!PshedpGetInjectionCapabilities <PERF> (PSHED+0xc6)"
    0xfffff8800656c578 : 0xfffff8800656c590 :  !du "ASSEMB~1.MDB"
    0xfffff8800656c590 : 0x0045005300530041 :  !du "ASSEMB~1.MDB"
    0xfffff8800656c598 : 0x0031007e0042004d :  !du "MB~1.MDB"
    0xfffff8800656c5b8 : 0xfffff880014c3785 : fltmgr!FltpFreeIrpCtrl+0x145
    0xfffff8800656c5f8 : 0xfffff80003098891 : nt!FsRtlCheckOplockEx+0x5b1
    0xfffff8800656c608 : 0xfffff800031b4e80 : nt!ExAllocatePoolWithTag+0x270
    Unable to load image \SystemRoot\system32\DRIVERS\DamageGuardX64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for DamageGuardX64.sys
    *** ERROR: Module load completed but symbols could not be loaded for DamageGuardX64.sys
    0xfffff8800656c698 : 0xfffff88001660000 : Ntfs!NtfsReserveClusters+0x4f0
    0xfffff8800656c6f8 : 0xfffff880016f3985 : Ntfs!NtfsCommonSetInformation+0x7d5
    0xfffff8800656c798 : 0xfffff8800166827e : Ntfs!NtfsInitializeTopLevelIrp+0x3e
    0xfffff8800656c7d8 : 0xfffff88001665f84 : Ntfs!NtfsFsdSetInformation+0x11c
    0xfffff8800656c858 : 0xfffff880014c1bcf : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
    0xfffff8800656c8e8 : 0xfffff880014c06df : fltmgr!FltpDispatch+0xcf
    0xfffff8800656c948 : 0xfffff80003360703 : nt!NtSetInformationFile+0x91f
    0xfffff8800656c9f8 : 0xfffff880014e1b00 : fltmgr!FltpFastIoQueryStandardInfo
    0xfffff8800656ca68 : 0xfffff8000307fe13 : nt!KiSystemServiceCopyEnd+0x13
    0xfffff8800656cad8 : 0xfffff8000307fe13 : nt!KiSystemServiceCopyEnd+0x13
    0xfffff8800656cae0 : 0xfffffa800fd9fb50 :  Trap @ fffff8800656cae0
    The pickle is if you wish to remove instant reset the PC will force you restore back to the factory image
    meaning it will WIPE EVERYTHING! so be very careful with that!!!.

    Let's try to disable it and stop it from auto starting on Windows startup.

    locate damageguardsvc in the services list,
    (Start Menu> type services.msc and hit enter)
    Double click damageguardsvc and stop it (the Stop button),
    then this is the part it gets tricky it might not allow you to change the Startup type to Disabled.
    Post back if you're having issues.
      My Computer

  6. Posts : 7
    Windows 7 64bit
    Thread Starter

    Ironic, DamageGuard damaging my laptop...

    I ran HijackThis and did see:
    O23 Service: Lenovo Instant Reset Service (DamageGuardSvc) - Lenovo Beijing Limited - C:\Program Files\Lenovo\Instant Reset\DamageGuardSvc.exe

    And also came across another post with a similar issue:
    New Lenovo G580 BSOD error

    I found Lenovo Instant Reset in Services and stopped it but am unable to set it's startup to Manual (it's set to Automatic). It says access denied even though I ran as admin.

    I saw a post where someone recommended deleting DamageGuardSvc.exe here How to disable Lenovo Instant Reset so I can use the Windows System Restore? -

    What do you think about this idea? Will it trigger my laptop to try to reset to factory default? I can't see how it would trigger it but you never know...
      My Computer

  7. Posts : 3,056
    Windows 10

    Haha, sadly ironic .

    I don't think deleting the file would be wise, I don't think it will force you to wipe the machine
    but there's no knowing what it will break.

    What I would do is a clean install, not using the factory restore image.
    If that is something you can consider doing then backing up all of the important data first
    then trying to rename the file to "DamageGuardSvc.bak" and see how it behaves,
    worst case scenario you can follow this tutorial to get a clean OEM Windows 7.

      My Computer

  8. Posts : 7
    Windows 7 64bit
    Thread Starter

    So I stopped that Lenovo Instant Reset service and incredibly the laptop still BSODs... Always when Unity/TortoiseGit is running. I don't know why this laptop sucks so bad when my first Lenovo Thinkpad back in 2008 was so awesome.
      My Computer

  9. Posts : 3,056
    Windows 10

    I'm sorry to say that not much has changed in terms of the bugcheck / stack.
    What we are seeing is similar to before (even most of the same routines are being called):

    Debug session time: Tue Oct 22 20:27:25.242 2013 (UTC + 3:00)
    BugCheck 50, {fffff8a009245000, 0, fffff800033aa0d3, 0}
    Could not read faulting driver name
    Probably caused by : ntkrnlmp.exe ( nt!FsRtlNotifyFilterReportChange+3c7 )
    2: kd> !procdumpext.dpx
    Start memory scan  : 0xfffff8800967ee18 ($csp)
    End memory scan    : 0xfffff88009680000 (Stack Base)
    0xfffff8800967ee78 : 0xfffff80003391bc2 : nt!CcMapData+0xd2
    0xfffff8800967ef38 : 0xfffff88001713383 : Ntfs!NtfsReadUsnJournal+0xb52
    0xfffff8800967ef78 : 0xfffff80003092cee : nt!KiPageFault+0x16e
    0xfffff8800967ef80 : 0x0000000000000000 :  Trap @ fffff8800967ef80
    0xfffff8800967f0a8 : 0xfffff800030b0318 : nt!KeReleaseSemaphore+0x228
    0xfffff8800967f0e8 : 0xfffff800033aa0d3 : nt!FsRtlNotifyFilterReportChange+0x3c7
    0xfffff8800967f128 : 0xfffff8000308a28d : nt!ExpReleaseResourceForThreadLite+0x33d
    0xfffff8800967f1b8 : 0xfffff880016cb5e1 : Ntfs!NtfsRenameLcb+0xed
    0xfffff8800967f1f8 : 0xfffff880016cb0f0 : Ntfs!NtfsRenameLinkInDir+0xd4
    0xfffff8800967f238 : 0xfffff8800166aad9 : Ntfs!NtfsReportDirNotify+0xe5
    0xfffff8800967f2c8 : 0xfffff880016c2539 : Ntfs!NtfsUpdateFcbFromLinkRemoval+0x29
    0xfffff8800967f308 : 0xfffff880016c98e9 : Ntfs!NtfsSetRenameInfo+0xb59
    0xfffff8800967f578 : 0xfffff8800967f590 :  !du "ORIG_H~1.LOCORIG_HEAD.lock"
    0xfffff8800967f588 : 0xfffff8800967f5a8 :  !du "ORIG_HEAD.lock"
    0xfffff8800967f590 : 0x004700490052004f :  !du "ORIG_H~1.LOCORIG_HEAD.lock"
    0xfffff8800967f598 : 0x0031007e0048005f :  !du "_H~1.LOCORIG_HEAD.lock"
    0xfffff8800967f5a0 : 0x0043004f004c002e :  !du ".LOCORIG_HEAD.lock"
    0xfffff8800967f5a8 : 0x004700490052004f :  !du "ORIG_HEAD.lock"
    0xfffff8800967f5b0 : 0x004100450048005f :  !du "_HEAD.lock"
    0xfffff8800967f5f8 : 0xfffff800030ac891 : nt!FsRtlCheckOplockEx+0x5b1
    0xfffff8800967f608 : 0xfffff800031c8e80 : nt!ExAllocatePoolWithTag+0x270
    Unable to load image \SystemRoot\system32\DRIVERS\DamageGuardX64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for DamageGuardX64.sys
    *** ERROR: Module load completed but symbols could not be loaded for DamageGuardX64.sys
    0xfffff8800967f698 : 0xfffff88001660000 : Ntfs!NtfsFsdSetInformation+0x198
    0xfffff8800967f6f8 : 0xfffff880016ed985 : Ntfs!NtfsCommonSetInformation+0x7d5
    0xfffff8800967f798 : 0xfffff8800166227e : Ntfs!NtfsInitializeTopLevelIrp+0x3e
    0xfffff8800967f7d8 : 0xfffff8800165ff84 : Ntfs!NtfsFsdSetInformation+0x11c
    0xfffff8800967f858 : 0xfffff880014eebcf : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
    0xfffff8800967f8e8 : 0xfffff880014ed6df : fltmgr!FltpDispatch+0xcf
    0xfffff8800967f948 : 0xfffff80003372e03 : nt!NtSetInformationFile+0x91f
    0xfffff8800967f9f8 : 0xfffff8800150eb00 : fltmgr!FltpFastIoQueryStandardInfo
    0xfffff8800967fa68 : 0xfffff80003093e53 : nt!KiSystemServiceCopyEnd+0x13
    0xfffff8800967fad8 : 0xfffff80003093e53 : nt!KiSystemServiceCopyEnd+0x13
    We can see that one of the fore mentioned drivers are still present, and is appearing
    on the stack, a different driver on the loaded modules list is I think what is using fltmgr which is normally
    being used by an antivirus software, which I don't see you're using?.

    Browse full module list
    start             end                 module name
    fffff880`03083000 fffff880`0308c000   dgFltrX64   (deferred)             
        Image path: \SystemRoot\system32\drivers\dgFltrX64.sys
        Image name: dgFltrX64.sys
        Browse all global symbols  functions  data
        Timestamp:        Mon Dec 12 10:48:49 2011 (4EE5BFF1)
        CheckSum:         000150A8
        ImageSize:        00009000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    2: kd> lmDvmDamageGuardX64
    Browse full module list
    start             end                 module name
    fffff880`01d37000 fffff880`01d6e000   DamageGuardX64 T (no symbols)           
        Loaded symbol image file: DamageGuardX64.sys
        Image path: \SystemRoot\system32\DRIVERS\DamageGuardX64.sys
        Image name: DamageGuardX64.sys
        Browse all global symbols  functions  data
        Timestamp:        Thu Feb 09 07:36:21 2012 (4F335B55)
        CheckSum:         00041E45
        ImageSize:        00037000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Apart from on bugcheck that occurred when removing / using the Bluetooth module,
    are the bugchecks onlyhappening when you're using Unity / Git?

    I would like to run some tests if you were to comply.

    The Following Method Should NOT Be Performed On An SSD!

    Testing the HDD:

    1. Perform a Disk Check | Disk Check
    2. Then Post the results following | THIS METHOD
    3. Download SeaTools for DOS if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
    4. If SeaTools for Windows is unable to recognize your HDD visit HDDdiag and follow the instructions.

    If SeaTools For DOS does not recognize the drive;
    Boot into the BIOS using the *Fxkey.
    Look for an entry called SATA Mode (or something similar), it should be set to IDE / AHCI.
    It's probably set to AHCI which is why SeaTools doesn't recognize them in the DOS environment.
    Set it to IDE then save and exit usually by pressing the F10 key.
    Now boot into SeaTools and it should detect the drives.
    Start the Long Test and let it run.
    Upon completion don't try to boot into Windows as it will only result in a BSOD, go back into the BIOS
    and change the SATA setting back to what it was in the first place.

    Please scan for possible infection and file corruption.

    (*Kaspersky Rescue CD from a USB thumbdrive)

    Keep us posted :) .
      My Computer

  10. Posts : 7
    Windows 7 64bit
    Thread Starter

    Sorry for the long delay here. I've noticed some bsods lately with the computer when Unity isn't even running... I tried to run the chkdsk on the main drive (the option where you run it when the computer starts) but it just fails saying something about the system needs to be rolled back. I then ran sfc /scannow (I've attached the log from it) and a number of corrupt things were fixed. I then ran chkdsk in just read only mode and it said there were no errors:

    C:\Windows\system32>chkdsk C:
    The type of the file system is NTFS.
    Volume label is Windows7_OS.

    WARNING! F parameter not specified.
    Running CHKDSK in read-only mode.

    CHKDSK is verifying files (stage 1 of 3)...
    637952 file records processed.
    File verification completed.
    926 large file records processed.
    0 bad file records processed.
    0 EA records processed.
    50 reparse records processed.
    CHKDSK is verifying indexes (stage 2 of 3)...
    793918 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered.
    CHKDSK is verifying security descriptors (stage 3 of 3)...
    637952 file SDs/SIDs processed.
    Security descriptor verification completed.
    77984 data files processed.
    CHKDSK is verifying Usn Journal...
    35604536 USN bytes processed.
    Usn Journal verification completed.
    Windows has checked the file system and found no problems.

    440993791 KB total disk space.
    330526772 KB in 480317 files.
    235840 KB in 77985 indexes.
    0 KB in bad sectors.
    753643 KB in use by the system.
    65536 KB occupied by the log file.
    109477536 KB available on disk.

    4096 bytes in each allocation unit.
    110248447 total allocation units on disk.
    27369384 allocation units available on disk.

    Will try some of these other recommendations...
      My Computer

Page 1 of 2 12 LastLast

  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 12:39.
Find Us