Cheat Engine Forum Index Cheat Engine
The Official Site of Cheat Engine
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 


Cheat engine 6.7 DBVM causes BSOD

 
Post new topic   Reply to topic    Cheat Engine Forum Index -> Cheat Engine
View previous topic :: View next topic  
Author Message
Viloresi
Expert Cheater
Reputation: 0

Joined: 02 Feb 2017
Posts: 149

PostPosted: Thu Aug 01, 2019 11:08 am    Post subject: Cheat engine 6.7 DBVM causes BSOD Reply with quote

Hello I'm trying to use cheat engine 6.7 on:
Windows 10
Version 1903 (build SO 18362.267)

last updated today (1 august 2019)

unfortunately it keeps BSOD when I try to enable DBVM by clicking on Help-> About-> "Your system supports DBVM" .
With cheat engine 6.8.3 I don't have any problem, dbk64.sys loads correctly and I'm able to start DBVM, also I didn't use the version 6.7 for a long time (likely 2 years) but now I need to use that
Back to top
View user's profile Send private message
Dark Byte
Site Admin
Reputation: 458

Joined: 09 May 2003
Posts: 25296
Location: The netherlands

PostPosted: Thu Aug 01, 2019 11:21 am    Post subject: Reply with quote

important thing when it comes to DBVM is the cpu you use. AMD's are currently not functional with DBVM

Also what BSOD do you have ?

_________________
Do not ask me about online cheats. I don't know any and wont help finding them.

Like my help? Join me on Patreon so i can keep helping
Back to top
View user's profile Send private message MSN Messenger
Viloresi
Expert Cheater
Reputation: 0

Joined: 02 Feb 2017
Posts: 149

PostPosted: Thu Aug 01, 2019 11:23 am    Post subject: Reply with quote

Dark Byte wrote:
important thing when it comes to DBVM is the cpu you use? AMD's are currently not functional with DBVM

Also what BSOD do you have ?


I have a intel i7-3770k

here is what the bsod says: (I've opened the MEMORY.dmp file that gets generated inside Windows folder, with WinDbg)

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffa3000445f180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.




Debugging details:
Code:

Debugging Details:
------------------


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  MSI

SYSTEM_PRODUCT_NAME:  MS-7758

SYSTEM_SKU:  To be filled by O.E.M.

SYSTEM_VERSION:  1.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  V2.4

BIOS_DATE:  06/19/2012

BASEBOARD_MANUFACTURER:  MSI

BASEBOARD_PRODUCT:  Z77A-G43 (MS-7758)

BASEBOARD_VERSION:  1.0

DUMP_TYPE:  1

BUGCHECK_P1: 18

BUGCHECK_P2: 0

BUGCHECK_P3: ffffa3000445f180

BUGCHECK_P4: 2

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT

FAULTING_PROCESSOR: 2

PROCESS_NAME:  cheatengine-x86_64.exe

CPU_COUNT: 8

CPU_MHZ: d40

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3a

CPU_STEPPING: 9

CPU_MICROCODE: 6,3a,9,0 (F,M,S,R)  SIG: 20'00000000 (cache) 20'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  KEV-PC

ANALYSIS_SESSION_TIME:  08-01-2019 19:20:13.0248

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8047cfedab4 to fffff8047cfbfcc0

STACK_TEXT: 
ffffa300`04998af8 fffff804`7cfedab4 : 00000000`00000101 00000000`00000018 00000000`00000000 ffffa300`0445f180 : nt!KeBugCheckEx
ffffa300`04998b00 fffff804`7ce1f1a4 : 00000000`00000000 00000000`00000000 00000000`0000416f ffffa300`04940180 : nt!KeAccumulateTicks+0x1cb7b4
ffffa300`04998b60 fffff804`7d8b64b2 : 00000000`00000000 fffffc03`37adedb0 fffffc03`37adee30 00000000`0000000c : nt!KeClockInterruptNotify+0x6c4
ffffa300`04998f30 fffff804`7ce029e5 : 00000000`9c18521e ffffd782`982a6c00 ffffd782`982a6cb0 00000000`00000000 : hal!HalpTimerClockInterrupt+0xf2
ffffa300`04998f60 fffff804`7cfc175a : fffffc03`37adee30 ffffd782`982a6c00 00000000`00000000 ffffd782`982a6c00 : nt!KiCallInterruptServiceRoutine+0xa5
ffffa300`04998fb0 fffff804`7cfc1cc7 : 00000000`82616f9d fffffc03`37adee30 ffffd782`982a6c00 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffc03`37adedb0 fffff804`7ceb3536 : 00000000`00000000 ffffa300`04940180 00000000`00000000 fffff97c`0178cce0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffc03`37adef40 fffff804`7ceb153c : fffff804`7d266a40 00000000`00000000 fffffc03`37adf190 00000000`00000000 : nt!MiFlushTbList+0x3a6
fffffc03`37adf090 fffff804`7cec2062 : 80000001`9bb7f963 00000000`00000000 00000000`00000000 fffff97c`0178cce8 : nt!MiTerminateWsleCluster+0x38c
fffffc03`37adf230 fffff804`7ce57940 : ffffd782`a04ab790 00000000`00000004 00000000`00000000 ffffd782`98293850 : nt!MiRemoveMappedPtes+0x202
fffffc03`37adf2f0 fffff804`7d3fa763 : fffff804`7d2647e0 00000000`00001001 00000000`00000001 ffffba84`00000000 : nt!MiRemoveFromSystemSpace+0x328
fffffc03`37adf420 fffff804`7d3fa6a5 : ffffba84`27690050 fffffc03`00000000 ffffba84`27690050 ffffba84`1e613420 : nt!MmUnmapViewInSystemSpace+0x23
fffffc03`37adf450 fffff804`7d3fa1c4 : ffffd782`a1361b10 ffffba84`2751f010 00000000`63f20000 00000000`00000000 : nt!MiUpdateCfgSystemWideBitmapWorker+0x285
fffffc03`37adf530 fffff804`7d41dfb0 : ffffd782`a1361940 fffff951`80033e88 00000000`63f20000 00000000`00000000 : nt!MiUpdateCfgSystemWideBitmap+0x70
fffffc03`37adf570 fffff804`7d41daee : 00000000`63f20000 fffffc03`37adf840 ffffd782`a1269080 00000000`00000000 : nt!MiRelocateImageAgain+0x10c
fffffc03`37adf600 fffff804`7d41d586 : 00000000`00000002 fffffc03`00000000 ffffd782`a1710a20 fffffc03`37adf840 : nt!MiValidateExistingImage+0x66
fffffc03`37adf6a0 fffff804`7d3d82b3 : ffffd782`a1710a20 fffffc03`37adf840 ffffd782`a1269080 ffffd782`a1710a20 : nt!MiShareExistingControlArea+0xc2
fffffc03`37adf6d0 fffff804`7d3d86e4 : ffffd782`a1361940 00000000`00000000 ffffd782`a1710a20 00000000`00000000 : nt!MiCreateImageOrDataSection+0x1a3
fffffc03`37adf7c0 fffff804`7d3d7d3f : 00000000`01000000 fffffc03`37adfb80 00000000`00000001 00000000`00000010 : nt!MiCreateSection+0xf4
fffffc03`37adf940 fffff804`7d3d7ad0 : 00000000`0fe3e458 00000000`0000000d 00000000`00000000 00000000`00000001 : nt!MiCreateSectionCommon+0x1ff
fffffc03`37adfa20 fffff804`7cfd1515 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtCreateSection+0x60
fffffc03`37adfa90 00007ffe`299dc9a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`0fe3e3b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`299dc9a4


THREAD_SHA1_HASH_MOD_FUNC:  fc266d5b7cde156fa3d8cf724f4eb60cf181aa9b

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  9d7be940657e6d3e4f20065c7d95d42cb3cb4f08

THREAD_SHA1_HASH_MOD:  c679893896b7ac49f728be5210ad6454910d2317

FOLLOWUP_IP:
nt!KeAccumulateTicks+1cb7b4
fffff804`7cfedab4 cc              int     3

FAULT_INSTR_CODE:  cb8b48cc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KeAccumulateTicks+1cb7b4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  74da155a

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1cb7b4

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

PRIMARY_PROBLEM_CLASS:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

TARGET_TIME:  2019-08-01T17:02:03.000Z

OSBUILD:  18362

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  2032-02-15 10:16:10

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  33e9

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:clock_watchdog_timeout_invalid_context_nt!keaccumulateticks

FAILURE_ID_HASH:  {95498f51-33a9-903b-59e5-d236937d8ecf}

Followup:     MachineOwner
Back to top
View user's profile Send private message
Dark Byte
Site Admin
Reputation: 458

Joined: 09 May 2003
Posts: 25296
Location: The netherlands

PostPosted: Thu Aug 01, 2019 12:56 pm    Post subject: Reply with quote

watchdog timeout is dbvm freezing on a state it doesn't recognize.

Make sure no other hypervisor is running at the time (no vmware running, no hyper-V)

_________________
Do not ask me about online cheats. I don't know any and wont help finding them.

Like my help? Join me on Patreon so i can keep helping
Back to top
View user's profile Send private message MSN Messenger
Viloresi
Expert Cheater
Reputation: 0

Joined: 02 Feb 2017
Posts: 149

PostPosted: Thu Aug 01, 2019 1:01 pm    Post subject: Reply with quote

there shouldn't be a hypervisor running, I don't have vmware and hyper-v installed anyway I'm having this problem only with CE 6.7 , not with 6.8.3 sorry for my lack but the cheat engine driver is similar it should work on both right?
Back to top
View user's profile Send private message
Dark Byte
Site Admin
Reputation: 458

Joined: 09 May 2003
Posts: 25296
Location: The netherlands

PostPosted: Thu Aug 01, 2019 11:48 pm    Post subject: Reply with quote

6.8.3 is very different from 6.7.
e.g 6.7 dbvm can not be loaded by 6.8.3 driver and same the other way around (you'll crash)

but what you can do is load dbvm with 6.8.3 and then close ce and run the kernelmodule unloader

then try 6.7

also why do you wish to use 6.7 ? it has many bugs and doesn't even have cloaking support and invisible find what access breakpoints

_________________
Do not ask me about online cheats. I don't know any and wont help finding them.

Like my help? Join me on Patreon so i can keep helping
Back to top
View user's profile Send private message MSN Messenger
Viloresi
Expert Cheater
Reputation: 0

Joined: 02 Feb 2017
Posts: 149

PostPosted: Fri Aug 02, 2019 3:56 am    Post subject: Reply with quote

Dark Byte wrote:
6.8.3 is very different from 6.7.
e.g 6.7 dbvm can not be loaded by 6.8.3 driver and same the other way around (you'll crash)

but what you can do is load dbvm with 6.8.3 and then close ce and run the kernelmodule unloader

then try 6.7

also why do you wish to use 6.7 ? it has many bugs and doesn't even have cloaking support and invisible find what access breakpoints


ok then I've tried what you suggested, but when I try to use the kerneldebugger an error pops up "the driver couldn't be loaded" ... "dbvm is enabled ... do you want to force load the driver" and after I press yes I get a BSOD.

anyway to answer your last question it's becaue I've downloaded a cheat engine with all the strings modified to make it undetected, it was compiled with the 6.7 source.

anyway my PC might have secureboot enabled and I can't find a way to disable it from the bios...
Back to top
View user's profile Send private message
Dark Byte
Site Admin
Reputation: 458

Joined: 09 May 2003
Posts: 25296
Location: The netherlands

PostPosted: Fri Aug 02, 2019 4:04 am    Post subject: Reply with quote

The driver that comes with CE releases won't talk to modified CE versions. You need to compile the driver yourself and boot windows in testsigning mode, or sign it yourself with EV codesigning certificate

and forceload only works on windows 7

But wht you could do in 6.8.3 is hook the windows kernel functions that are used for detecting CE. E.g openprocess, readmemory, window caption enum

_________________
Do not ask me about online cheats. I don't know any and wont help finding them.

Like my help? Join me on Patreon so i can keep helping


Last edited by Dark Byte on Fri Aug 02, 2019 4:07 am; edited 1 time in total
Back to top
View user's profile Send private message MSN Messenger
Viloresi
Expert Cheater
Reputation: 0

Joined: 02 Feb 2017
Posts: 149

PostPosted: Fri Aug 02, 2019 4:07 am    Post subject: Reply with quote

alright I've made a mistake, I should've used cheat engine 6.7 (official) to do the test lol... anyway I've decided to use the 7.0 beta and leave the 6.7!
Thank you anyway your answers are always helpful.
I'm gonna explore the new functionalities too
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    Cheat Engine Forum Index -> Cheat Engine All times are GMT - 6 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group

CE Wiki   IRC (#CEF)   Twitter
Third party websites