hi
i installed the driver (runtime + axoloti core) on win7 64bit
when i plug in the axoloti, windows gives green arrows on the core and bulk
Then, if i launch the Axoloti software, i get a blue screen error: Bad_Pool_Header
please help!
(on my first try, the bulk driver did not install correctly (red arrow) and when i started the axoloti software,
i got a blue screen error, then my mouse + keyboard did not work anymore. there was no solution for this except reinstalling windows 
)
this is odd...
Axoloti uses standard windows supplied drivers, it does not have any special drivers drivers (it uses winusb drivers, that supply a midi and bulk interface)
this is why when you first plug in the axoloti board, windows downloads drivers from Microsoft (assuming you have not already got devices already using them)
similar the UI is java, so does not have any low level access, to cause blue screens
(other than accessing above drivers)
When you say the first time, the bulk driver did not install correctly ... were there any errors?
some things I would try :
I can only assume you have a clash with some other device(s) you have installed, that are causing the windows drivers issues, and could well be related to out of date drivers.
Hopefully the above, might help spot which two devices are conflicting...
Its possible to switch the usb driver used by Axoloti, but the WinUSB driver by Microsoft, should be the least likely to cause issues...
one thing you could look at is running Zadig:
C:\Program Files (x86)\axoloti_runtime\platform_win\zadig_2.1.2.exe
and look to see which driver is currently selected for axoloti
(more details here: https://sebiik.github.io/community.axoloti.com.backup/t/win-7-no-usb-found-with-matching-pid-vid/117)
BUT don't change anything... yet... better to get some info first rather than switching things around, when we are unsure of the issue.
the first time, the windows driver popup told me that the bulk core was not correctly installed
This was the with previous driver btw
(then came the reinstall)
then:
download the new driver + runtime
installed both
inserted board
same error, bulk not installed correcty
i ran zadig, no luck there (i read the other post about the pid/vid thing)
then did an uninstall, reinstalled
got 3 green arrows on the windows driver popup window (everything installed correctly)
(zadig might have done some good after all)
so i thought.. finally!
then ran the app.. same blue screen error.
Luckely, my mouse and keyboard kept working this time
now i'm updating windows (because of the win reinstall) hope this will solve it.
(i admit that my computer had not updated in a while before this crash)
I've done most of the development of Axoloti in Windows 7 64bit. Even during development - when experimenting with all sorts of things - I have never ever seen a blue screen.
Really reinstalling windows or "just" restarting windows?
The application runs in userland, and userland applications can't bluescreen normally (unless via a driver). The WinUSB driver is used, and this is made by Microsoft and not supposed to ever bluescreen. I'm really puzzled.
really reinstalling.
with the mouse + keyboard not working, i tried almost all internet solutions
tried safe mode,resetted the bios, went back to a previous stored point, nothing worked.
then i tried restoring windows, replacing usb driver .sys files while booting for the windows CD.
no luck there. So then i had to reinstall. that did work (but sucked)
the bluescreen error said : bad_pool_header. does that mean anything to you?
in zadig , i see this in the list:
axoloti core (interface 0)
driver: usbaudio (v6.1.7601.18208) --> WinUSB(v6.1.7600.16385
usb id 16C0 0442 00
wcid: X
axoloti bulk interface (interface 2)
driver: usbaudio v6.1.7600.16385 --> WinUSB(v6.1.7600.16385
usb id 16C0 0442 02
wcid: V WINUSB
log:
Zadig 2.1.2.677
Windows 7 SP1 64-bit
ini file 'zadig.ini' not found - default parameters will be used
default driver set to 'WinUSB'
0 devices found.
8 devices found.
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_046D&PID_C246&REV_7002&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_01&Prot_02
libwdi:debug [wdi_create_list] Driver version: 6.1.7601.18199
libwdi:debug [wdi_create_list] HidUsb USB device (8): USB\VID_046D&PID_C246&MI_00\6&11157928&0&0000
libwdi:debug [wdi_create_list] Device description: 'Gaming Mouse G300 (Interface 0)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_046D&PID_C246&REV_7002&MI_01
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_00&Prot_01
libwdi:debug [wdi_create_list] Driver version: 6.1.7601.18199
libwdi:debug [wdi_create_list] HidUsb USB device (9): USB\VID_046D&PID_C246&MI_01\6&11157928&0&0001
libwdi:debug [wdi_create_list] Device description: 'Gaming Mouse G300 (Interface 1)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_046D&PID_C31D&REV_6600&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_01&Prot_01
libwdi:debug [wdi_create_list] Driver version: 6.1.7601.18199
libwdi:debug [wdi_create_list] HidUsb USB device (11): USB\VID_046D&PID_C31D&MI_00\6&3AD08B7B&0&0000
libwdi:debug [wdi_create_list] Device description: 'USB Keyboard (Interface 0)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_046D&PID_C31D&REV_6600&MI_01
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_00&Prot_00
libwdi:debug [wdi_create_list] Driver version: 6.1.7601.18199
libwdi:debug [wdi_create_list] HidUsb USB device (12): USB\VID_046D&PID_C31D&MI_01\6&3AD08B7B&0&0001
libwdi:debug [wdi_create_list] Device description: 'USB Keyboard (Interface 1)'
libwdi:debug [wdi_create_list] Hardware ID: USB\Vid_05AC&Pid_12AA&Rev_0510
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_06&SubClass_01&Prot_01
libwdi:debug [wdi_create_list] Driver version: 6.0.9999.67
libwdi:debug [wdi_create_list] USBAAPL64 USB device (13): USB\VID_05AC&PID_12AA\08BFF7ABB35429270023B160CD7D2EDB500F167C
libwdi:debug [wdi_create_list] Device description: 'iPod'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_0BDA&PID_0181&REV_8197
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_08&SubClass_06&Prot_50
libwdi:debug [wdi_create_list] Driver version: 6.1.7601.17577
libwdi:debug [wdi_create_list] USBSTOR USB device (14): USB\VID_0BDA&PID_0181\20060413092100000
libwdi:debug [wdi_create_list] Device description: 'USB2.0-CRW'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_16C0&PID_0442&REV_0200&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_01&SubClass_03&Prot_00
libwdi:debug [wdi_create_list] Driver version: 6.1.7601.18208
libwdi:debug [wdi_create_list] usbaudio USB device (16): USB\VID_16C0&PID_0442&MI_00\6&1E0B4EBA&0&0000
libwdi:debug [wdi_create_list] Device description: 'Axoloti Core (Interface 0)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_16C0&PID_0442&REV_0200&MI_02
libwdi:debug [wdi_create_list] Compatible ID: USB\MS_COMP_WINUSB
libwdi:debug [wdi_create_list] Driver version: 6.1.7600.16385
libwdi:debug [wdi_create_list] WinUSB USB device (17): USB\VID_16C0&PID_0442&MI_02\6&1E0B4EBA&0&0002
libwdi:debug [wdi_create_list] Device description: 'Axoloti Bulk Interface (Interface 2)'
I have never used safe mode, reinstalled windows, reset the bios or a restore point during development, and I do not think they are relevant. Even a bluescreen should not result in the need to reinstall windows.
bad_pool_header does not ring a bell here. Take care with the "solutions" you find on the internet, a lot of them are irrelevant.
You have the usbaudio driver installed for "axoloti bulk interface (interface 2)", this is wrong, replace that with the WinUSB driver in Zadig. I do not understand how you got that there.
(While the usbaudio driver is correct for "Axoloti Core (Interface 0)").
i changed the bulk interface driver.
started axoloti (with my fingers crossed)
it started!
firmware log: (might have some relevance)
USB device found
connected
Authentic Axoloti Core
search path : objects
Firmware version: 1.0.0.1, crc=0x800A5D63, entrypoint=0x20011000
Firmware CRC mismatch! Please flash the firmware first! Hardware firmware CRC = 800A5D63 <> Software CRC = 2B8D2015
C:\Program Files (x86)\Axoloti\app\objects\gpio\in\button2.axo
i updated this when requested
loaded test patch.. it works!!
Thanks for the help!
That's a relief!
I have no explanation for the bluescreen you have seen.
It is strange that the usbaudio was associated with the "Axoloti bulk interface (interface 2)".
If someone else encounters this pattern, please report immediately!
i got the same problems with the new 1.03 version.
fixed it by reinstalling and running zadig, reinstalling the bulk driver
a blue screen again? (the firmware upgrade is to be expected for each software update)
I cannot see why changing the runtime/axoloti app would alter your driver setup.
I (still) think you have some conflicting driver/device/software... and you should follow the steps i detailed in my earlier post to try to determine the cause of conflict. its telling (to me), no other users have reported the issue, again pointing to a particular aspect of your setup.
I don't know what you use the machine for... but if its not 'mission critical', perhaps now is a good time to think about the windows 10 upgrade, and do it as a completely fresh install. (i.e don't preserve settings, this always carried over loads of rubbish and usually issues).
I don't run windows (except in VMs) these days, but when I did, I used to do fresh installs every 12-18 months, because of the mess windows into... and i see little evidence its got any better 
Note: Im only a volunteer/contributor to Axoliti, so this is just what I would do... and not any kind of 'official' response or recommendation on whats necessary, as I recognise this might be seen as an 'extreme' action - but personally I loathe unstable systems.
proper recommendations can only come from Johannes, who obviously knows Axoloti inside out.
yes, i think that my windows is causing this problem, too.
i'll test this with other pc's this week.
for info: i've got a AMD FX 8120 eight-core processor, 12 gb ram, 64bit OS
yeah, id assume its more devices or drivers... rather than the PC.. unless you have had issues with the PC and other devices before.
the windows 10 thing, is mainly as it looks like Microsoft are going to push people into upgrading pretty hard, and it actually has a few nice things for musicians. so its likely many are going to have/want to upgrade anyway.
(though usually I wait on these things, but Win 10 seems to be working ok for me at present, and nicer than 7 and 8!)
will be good to hear how it goes on another PC though.
i ran into more problems. (blue screens )
i repaired axoloti drom the control menu, then it worked again.
noticed something else too:
when i connect with an usb3 port, i get this:
USB device found
org.usb4java.LibUsbException: USB error 5: Unable to claim interface: Entity not found
at axoloti.USBBulkConnection.connect(USBBulkConnection.java:252)
at axoloti.MainFrame.(MainFrame.java:245)
at axoloti.Axoloti$1.run(Axoloti.java:299)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:75)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
search path : objects
search path : d:\axolotipatches\AXO
finished loading objects
USB device found
not accesseable : busy?
USB device found
not accesseable : busy?
No available USB device found with matching PID/VID
when i connect with the usb2 , it works normally.
What's the brand of your USB3 controller?
I have tested extensively with a Intel(R) USB 3.0 eXtensible Host Controller, and have not found problems.
Could you try a different USB cable, to exclude that from the equation?
i tried another cable
same error
USB device found
not accesseable : busy?
No available USB device found with matching PID/VID
the usb3 driver brand = Etron Technology Inc.