Niani

Member
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Niani

  • Rank
    Member

Recent Profile Visitors

2091 profile views
  1. Everything went back to normal with the last update of macrium. Thank you to everyone. Good day
  2. it's not about the antimalware i can launch reflect with emsisoft along antimalware but not when OA is on. so OA is the problem and i made all the execptions already. still not solved.
  3. i'm setup like this user already for EAM, i'll wait a few days for an OA update. Thank you Elise
  4. i just reinstalled OA to make sure everything was OK. but OA is working perfectly beside this reflect problem
  5. i dont get any alert that's the weird thing. no history lo log. i can only execute reflect when OA is shutdown. both this programs worked perfectly for the last two years or so. so some recent update is messing with reflect or a macrium update may be. from the event viewer : Faulting application name: Reflect.exe, version: 5.3.7134.0, time stamp: 0x53e3799b Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x000007fe007a0000 Faulting process ID: 0x213c Faulting application start time: 0x01cfb7b1d8654c67 Faulting application path: C:\Program Files\Macrium\Reflect\Reflect.exe Faulting module path: unknown Report ID: 167b4a44-23a5-11e4-8321-c860008a5c33 Faulting package full name: Faulting package-relative application ID:
  6. yes even in learning mode reflect cant be executed
  7. i cant launch the main exe file and the scheduled task are also blocked as soon as i shut OA it's ok and i can execute reflect. all exceptions are maid on OA to let reflect go through but no luck.
  8. Hello friends; i have Reflect v5 blocked for two days despite exception in OA. as soon as i shut down the firewall it's ok. Good day
  9. Hello, Exactly once a week every wednesday i have a BSOD when my PC resume from sleep. The mini dump reveal the following : ================================================== Dump File : 052913-17375-01.dmp Crash Time : 29/05/2013 06:16:10 Bug Check String : Bug Check Code : 0x00000139 Parameter 1 : 00000000`00000003 Parameter 2 : fffff880`0dca81e0 Parameter 3 : fffff880`0dca8138 Parameter 4 : 00000000`00000000 Caused By Driver : a2ddax64.sys Caused By Address : a2ddax64.sys+c4b31e0 File Description : Product Name : Company : File Version : Processor : x64 Crash Address : ntoskrnl.exe+5a440 Stack Address 1 : Stack Address 2 : Stack Address 3 : Computer Name : Full Path : C:\WINDOWS\Minidump\052913-17375-01.dmp Processors Count : 8 Major Version : 15 Minor Version : 9200 Dump File Size : 165 112 ================================================== I think EMSISOFT DIRECT DISK ACCESS SUPPORT DRIVER is causing me a little trouble. Good day
  10. Hello, I'm Having the exact same issue with the kernel security check once a week also.