Cheat Engine

Johner1261 · Cheater Reputation: 0 Joined: 09 Aug 2013 Posts: 44

Is there a way to see if anything is interfering with DBVM that might be causing my BSODs and what that interference is?

Thank you.

Dark Byte · Posted: Fri Nov 15, 2013 10:09 pm Post subject:

If your system has a serial port (preferably native) then you can use the debug build which will show data and crash reports when it fails and gives a interface for querying stuff

If it is a BSOD (and not the timer timout bsod), then upload a crash dump somewhere so I can check it out(preferably full memory crash dump)

Besides that the usual culprits:
Other virtual machines running (vmware, avast av, bluestacks, etc...)
Using Windows 8 and ultimap (the released version does not do ultimap on w Cool

Not enough contiguous ram (needs 8MB of nonpaged memory)

Johner1261 · Cheater Reputation: 0 Joined: 09 Aug 2013 Posts: 44

I PM'd you the memdumps.
You'll see VM sys files but the VMs were off.

Thank you.

Dark Byte · Posted: Mon Nov 18, 2013 7:51 pm Post subject:

those are timeout bsod's so don't contain any information on what is going wrong, and since they are minidumps there's no memory of dbvm to examine

The problem is in loading dbvm. Really make sure nothing is interfering.

Also, what cpu do you use ?

Johner1261 · Cheater Reputation: 0 Joined: 09 Aug 2013 Posts: 44

I use an AMD x6 1090t.

I tried closing all nonessential programs by stopping their services, killing the Windows through task manager, and anything left that wasn't a necessary process I killed, even explorer.exe.

I still crashed, before this I had tried and safemode but I still crashed.

I think it's my CPU that's causing these problems.

EDIT: I also have plenty of RAM, 8gb. I run Windows 8 x64 and I did some research and found about PatchGuard. Do you think that might be the problem?

Dark Byte · Posted: Tue Nov 19, 2013 6:06 pm Post subject:

it's possible it's the cpu yes. Only a handful of AMD's have been tested to work (I only have one AMD system to test with)

I don't think it's windows 8 x64, as the AMD system I tested it on also ran windows 8 x64

Also, do you launch dbvm using the about screen? If not, try that. It's the most stable method (make sure no games are running)

And what feature do you need of dbvm? Ultimap doesn't work on AMD systems, even with dbvm working.

Johner1261 · Cheater Reputation: 0 Joined: 09 Aug 2013 Posts: 44

I use DBVM via the about screen.
I need kernel debug and all of it's options but as soon as I accept the risks of DBVM my computer freezes up and then I get the BSoD a second or so later.

DannyFl · How do I cheat? Reputation: 0 Joined: 07 Mar 2013 Posts: 6

Try running DBVM just after Windows starts. And do it as soon as possible, because at Windows start, there is a lower probability of a BSOD. (at least in my system)

Johner1261 · Cheater Reputation: 0 Joined: 09 Aug 2013 Posts: 44

Johner1261 · Cheater Reputation: 0 Joined: 09 Aug 2013 Posts: 44

Uhh sorry for bumping and I know you do a lot but is your lack of replying due to business or am is it just because I'm doomed?

Dark Byte · Posted: Tue Nov 26, 2013 6:08 pm Post subject:

You're basically doomed yes. There's nothing I can do at the moment to fix compatibility with your system

Johner1261 · Cheater Reputation: 0 Joined: 09 Aug 2013 Posts: 44

Do you think you'll be able to improve compatibility in the next update?

Dark Byte · Posted: Wed Dec 04, 2013 7:27 pm Post subject:

I doubt it. Right now I can't see why your system crashes. So it's unlikely i'll figure out the problem

Johner1261 · Cheater Reputation: 0 Joined: 09 Aug 2013 Posts: 44

Dark Byte · Posted: Thu Dec 05, 2013 8:48 pm Post subject:

My debugging method is really annoying and isn't really suitable for other people without constant guidance and specialized hardware (these days a serial port with a nulmodem cable and another system with a serial port as well is categorized as 'specialized hardware')

In short: I make a build version that outputs all possible data and check if it at least gets through the initial stage.
If not, then I use that data to figure out what could be wrong, build a new version that outputs even more data. Confirm my theory, or not. Then build a new version with a fix or repeat.

If it does get through the initial stage then build a list of events that work correctly, so they don't output data again, and build it.
Then test it till I have pinpointed where it goes wrong.
According to the bug description it's a total system halt, so that should be a clear indication. The last outputted message will then show where it went wrong

But yes, you'll need some knowledge about dbvm's code (it's in the svn), be able to compile it (64-bit linux) and read out debugging data (serial port/nulmodem cable)

What you could try is raw-writing dbvm to a usb disk and boot off that. Perhaps it goes bad before it even launches, and might show what goes wrong on the display. (e.g: if your system doesn't support virtualization after all it will say that)
Note though: dbvm doesn't really support AMD booting. Only the first cpu core will be virtualized, but it may be enough to gather data