View previous topic :: View next topic |
Author |
Message |
ShadingVaz How do I cheat? Reputation: 0
Joined: 27 Mar 2015 Posts: 4
|
|
Back to top |
|
|
jgoemat Master Cheater Reputation: 22
Joined: 25 Sep 2011 Posts: 252
|
Posted: Fri Mar 27, 2015 5:55 pm Post subject: |
|
|
For your error I'm not sure. Do you have an intel processor? I don't know if DBVM supports others. Having Hyper-V installed makes CE say that your system doesn't support DBVM so you can't even try, but that's on Intel.
I only get the CLOCK_WATCHDOG_TIMEOUT bsod and I know that's due to the number of cores, apparently there's chance when offloading any single core to DBVM to get this error so the more cores you have the more likely you'll get the bsod. With a quad-core (hyperthreaded so 8 logical cores) it almost always causes the error. I change the number of processors that windows will use in system settings to '2' and I don't crash very often. This also only occurs the first time you use DBVM after rebooting so once you use it you're safe until you reboot. I don't know if it could be a different error on AMD.
|
|
Back to top |
|
|
hhhuut Grandmaster Cheater Reputation: 6
Joined: 08 Feb 2015 Posts: 607
|
Posted: Fri Mar 27, 2015 6:41 pm Post subject: |
|
|
Do you activate DBVM with the CE-AboutBox or do you even boot up your computer with DBVM?
|
|
Back to top |
|
|
ShadingVaz How do I cheat? Reputation: 0
Joined: 27 Mar 2015 Posts: 4
|
Posted: Sat Mar 28, 2015 7:05 am Post subject: |
|
|
hhhuut wrote: | Do you activate DBVM with the CE-AboutBox or do you even boot up your computer with DBVM? |
I activate with the CE about box. Where can I download the file to burn to a CD?
Quote: | For your error I'm not sure. Do you have an intel processor? I don't know if DBVM supports others. Having Hyper-V installed makes CE say that your system doesn't support DBVM so you can't even try, but that's on Intel.
I only get the CLOCK_WATCHDOG_TIMEOUT bsod and I know that's due to the number of cores, apparently there's chance when offloading any single core to DBVM to get this error so the more cores you have the more likely you'll get the bsod. With a quad-core (hyperthreaded so 8 logical cores) it almost always causes the error. I change the number of processors that windows will use in system settings to '2' and I don't crash very often. This also only occurs the first time you use DBVM after rebooting so once you use it you're safe until you reboot. I don't know if it could be a different error on AMD. |
As for you I have an Intel Processor with Core Two Duo, and I never get CLOCK_WATCHDOG_TIMEOUT. It only comes up with KMODE_EXCEPTION_NOT_HANDLED. Does this mean my laptop doesn't support it?
_________________
need help dbvm |
|
Back to top |
|
|
hhhuut Grandmaster Cheater Reputation: 6
Joined: 08 Feb 2015 Posts: 607
|
Posted: Sat Mar 28, 2015 7:44 am Post subject: |
|
|
Ok, with only 2 cores you shouldn't have a problem.
As for the file, it's located in the CE-installation direcotry and is called "vmdisk.img"
|
|
Back to top |
|
|
ShadingVaz How do I cheat? Reputation: 0
Joined: 27 Mar 2015 Posts: 4
|
Posted: Sat Mar 28, 2015 2:10 pm Post subject: |
|
|
hhhuut wrote: | Ok, with only 2 cores you shouldn't have a problem.
As for the file, it's located in the CE-installation direcotry and is called "vmdisk.img" |
The vmdisk.img couldn't be burned lol but I found a DBVM iso and it works perfectly!
_________________
need help dbvm |
|
Back to top |
|
|
jgoemat Master Cheater Reputation: 22
Joined: 25 Sep 2011 Posts: 252
|
Posted: Tue Mar 31, 2015 12:38 am Post subject: |
|
|
ShadingVaz wrote: | hhhuut wrote: | Ok, with only 2 cores you shouldn't have a problem.
As for the file, it's located in the CE-installation direcotry and is called "vmdisk.img" |
The vmdisk.img couldn't be burned lol but I found a DBVM iso and it works perfectly! |
Where did you find the ISO? I was able to burn the image but it crashes every time I try to boot with it. I'd love to be able to use all my cores and DBVM at the same time... The error I get is a windows one and happens when different cores are in VM mode and not at the same time, starting the VM before loading windows should fix that...
|
|
Back to top |
|
|
|