FAQ  •  Register  •  Login

Crash isbox

Moderator: MiRai

<<

jirza

Posts: 2

Joined: Sat Jun 29, 2013 5:56 pm

Post Fri Jul 11, 2014 1:24 pm

Crash isbox

From today I cant use isbox. When I try open it crash.

Software: Inner Space Kernel 1.13 Build 6016 (Fri Jul 04 20:04:51 2014)
Current time: Fri Jul 11 18:24:11 2014
Crash: 0x770F32CD: Exception 0xc0000005 reading from address 0x037144C0 in module ntdll.dll
Additional information: VirtualInput device init 'Uživatelské zařízení standardu HID' 10011 01-0C {DEEFFEEB-0000-0000-0000-504944564944}

Registers:
-----------------------------------
eax=00005A00 ebx=036E74C0 ecx=000000D3 edx=000007FF
edi=00620000 esi=037144C0 ebp=0018BD58 esp=0018BD30

Stack:
-----------------------------------
00620000 036E74C0 00000000 000000C0 0000000A 0018BD24 00000000 0018BE40
771371F5 0004CCBE 0018BE50 770F35B7 00620000 037144C0 0018BE20 00000000
7712A2CE 00000000 00620000 036E74C8 00001000 0018BD6C 00001000 0018BE14
03112040 6ED5078A FFFFFFFE 03123E8A 0311C03A 00620000 00623960 031E4E70
00000013 031E4E70 031E4E70 0000000C 00000000 0018BDD0 03128B58 006FD958
00000003 0312292C 00000013 0018BE18 03114DD0 031E4E70 03114DC3 6DD0476A
036E64C0 031E4E70 02CBB230 0000000C 0018BDEC 00000000 0018C35C 031E4E70
000000C0 00693430 031E4E70 0000000A 00005A00 00000000 0100B156 0312B15E
6DD0472A 010100C0 0018BD70 0018B77C 0018BEE8 771371F5 0004D4EE 00000000
0018BE70 770F34A2 036E74C0 036E74C8 031E4E70 00000000 031813A0 036E74C0
0018BE84 74DC14AD 00620000 00000000 036E74C8 0018BE98 0311309C 00620000
00000000 036E74C8 0018BEA8 03122983 036E74C8 031E4E70 0018BEC0 03113597
031E4E70 031E4E70 FFFFFFFF 031E4E70 0018BEF8 03113621 031E4E70 6DD0478A
036E64C0 00000000 031813A0 FFFFFFFF 0018BECC 0018B778 0018C35C 03112040
6ED50032 00000000 00001000 031048C7 031E4E70 031E4E70 031E4E70 0318F21C
031813A0 0018C8D4 02B917A8 02B570D8 02B2FA28 031E4E70 030B6D3D 0018BF58
03181301 00000000 00000000 6DD04632 031FFEC8 0018D1C0 02B2FA28 0317E06C
031FB7A8 02B7AA01 003A0043 0050005C 006F0072 00720067 006D0061 00460020
006C0069 00730065 00280020 00380078 00290036 0049005C 006E006E 00720065
00700053 00630061 005C0065 006E0049 00750070 00440074 00760065 00630069
00730065 0058002E 004C004D 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
<<

jirza

Posts: 2

Joined: Sat Jun 29, 2013 5:56 pm

Post Mon Jul 21, 2014 11:44 am

Re: Crash isbox

thx for reply :lol:
<<

bob

User avatar

League of Extraordinary Multiboxers

Posts: 4591

Joined: Sat Feb 15, 2014 11:14 am

Location: In the dining room, with the lead pipe.

Post Mon Jul 21, 2014 2:54 pm

Re: Crash isbox

To be fair, a simple stack trace is not all that useful without a memory dump and a bunch of debug files.

But it does give you most of the information you need to look into the problem.

0x000000005 is an exception code for Access Violation. This generally means that something attempted to access memory it was not entitled too. this normally happens when you have buggy drivers.
The second part is VirtualInput device init 'Uživatelské zařízení standardu HID' <- which is directing at some kind of interface device, e.g. Mouse/Keyboard/Footboard.

If you remove the device, the problem may go away. You may need to update drivers for the device and the problem may go away (or downgrade - perhaps the last thing you changed was an update to drivers??)
You could also try deleting/renaming the InputDevices.xml file in the Innerspace folder (default is normally C:\Program Files (x86)\InnerSpace - but it depends on your installation).

Failing that, try providing a diagnostics.. http://isboxer.com/wiki/Diagnostics it may be possible to spot something in there, but so far it is pointing to some input device/driver as the issue.
<<

bob

User avatar

League of Extraordinary Multiboxers

Posts: 4591

Joined: Sat Feb 15, 2014 11:14 am

Location: In the dining room, with the lead pipe.

Post Mon Jul 21, 2014 3:06 pm

Re: Crash isbox

BTW, to find out which HID device, if you don't know already, you may need to search the registry to find what DEEFFEEB-0000-0000-0000-504944564944 references.

Return to General discussion

Who is online

Users browsing this forum: No registered users and 0 guests

cron