7/27/2023 0 Comments Asus aura keeps crashing![]() I can obtain the requested information, using a debug build, via: Having an Arduino attached (with its COM port) is hopefully a "core" scenario that PulseView would want to support. ![]() Later attempts to launch PulseView just crashed, but it's possible I had attached an Arduino variant that exposed a COM port. I caught a first trace using a USB-attached Rigol DS1054z. I've been able to successfully load PulseView once.Īfter reading this thread, and hearing it may be a COM port for others, may have been a useful comment! I am happy to carry out further testing to provide more detail if that is of interest - time allowing. Although where the fault lies is another matter. ![]() In my case at least, there would seem to be a clash between the USB drivers. I have also tested with a FTDI virtual coms port (RS422 dongle) and have no problems. I have tested this a couple of times and it seems to be repeatable. If PulseView is already running, I can plug in the Microchip kit and PulseView continues to run. If I unplug the Microchip development kit, PulseView starts normally. Reinstalling the latest PulseView version did not help. I see a search progress bar reach about 3 or 4% and then it closes. With this device connected (it appears as a USB Microchip Virtual Coms Port) I experienced it for the first time today. I may be able to add some information to this bug. The device seems similar but not identical to the ARMFLY mini-logic shown on the wiki, I'll add a page for it, if I can. The device works, if I set a trigger on the D0 pin, and then touch that pin on and off the CLK output pin, I do get a capture. I'm a little surprised it believes the device is a Saleae Logic, I was expecting it to show up as and use the fx2lafw firmware, but I see no sign of that, should that be the case? Sr: std: fx2lafw: std_opts_config_list: sdi/cg != NULL: not handling. Libusb: debug allocating new device for session Libusb: debug cached config descriptor 0 (bConfigurationValue=1, 25 bytes) Libusb: debug found 1 configurations (active conf: 1) Libusb: info libusbK DLL is not available, will use native WinUSB Libusb: debug Will use CancelIoEx for I/O cancellation Some selections from the verbose log output are below Which gives me time to unplug the KVM, wait a while and then plug it back in with pulseview working. What I would like to know is does this mean the RAM maybe faulty or will I have to look at maybe adjusting the voltage to see it I can get it to run at 3600 speeds?ĮDIT - It just froze again (23:00 25/04/21), though this is the first time since I lowered the RAM frequency.I am now stumped as to what it is.To avoid frantic typing and unplugging of USB devices, I now start pulseview from a command like such as This is the first PC that I have built myself as I usually buy a Custom built one so don't have much experience with these issues. I have checked the the Asus website and these modules are not shown on the supported list for the motherboard. I have a Z590-F Gaming, 10900K (not currently overclocked) and Corsair CMW32GX4M2Z3600C18 RAM. Since I have done this Windows has not crashed once. I went into bios (XMP is enabled) and lowered the RAM frequency to 3400. I then googled 3600 memory and Asus motherboards and have seen on previous revisions (Z390 and Z490) that some people had trouble running RAM at those speeds. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly." Which I assume is related to me having to reset the PC with the power button. The only errors in Event Viewer at the times of the crashes was "The system has rebooted without cleanly shutting down first. In that time I have taken everything out of the case to check it all for any signs of damage, used new thermal paste etc, reinstalled windows numerous times, moving the M.2 drive to different slots on the board, having just the M.2 or the SSD as the only drives in the system. Last week I built a new PC and since then Windows has constantly been freezing meaning I have had to press the power button to reboot the PC.
0 Comments
Leave a Reply. |