Search results

Thanks again for your great support. Well appreciated. Let's keep the thread open for another couple of days, as I cannot yet say that the BSOD's have truly disappeared. Cheers, Armand

Defintely. But I found an alternative solution. Back in the days with XP and Vista I had a similar issue step 1! Go into another drive (d:, e:, ...) and create a folder called usbdriver step 2! Go into C:\WINDOWS\INF and copy the whole contents step 3! COPY ALL THAT INTO...

But I've already done every single step you've listed; no effect. The deleting entries from the enum key used to be a very efficient way of telling older versions of windows to rescan and re-attribute drivers to the system. Therefore my thinking.

Regarding the BSOD I'm not yet sure, but it looks promissing. Concerning the USB & chipset drivers, I reinstalled them, but it doesn't make any difference. Wouldn't it make sense to either rename the driver file to ".old" and/or go to the ENUM keys within the registry and delete the...

... hmm..... it's still running... No BSOD since I've deactivated the VirtualBox Network interface. Uptime of 15 hours (although a hibernation took place :think: But now the USB Mass Storage is no longer working.....:huh: ... since it's neither Friday 13th nor April 1st, I really start asking...

Thank you very much. I'm also off to bed; 1:15 here in Luxembourg Good night.

No, I'm not using any VPN connection. The virtual box is running a MacOS helping me to (sporadically) configure an midi merging device for which Windows driver do no longer exist, but I need to run my synthesizers. Wouldn't it be possible to just deactivate the networking layers of the VBox...

using windbg it still says the same thing. Couldn't it be the NETIO.SYS becoming corrupted? I've read some similar posts on the web and that Microsoft were onto a Bugfix that should'nt last long before general availability. ... DEFAULT_BUCKET_ID: LIST_ENTRY_CORRUPT BUGCHECK_STR: 0x139...

... :sleepy: ... It happened again.... I'm starting getting very frustrated.

No. I will wait for the powermanagement to take action..... hopefully without any BSOD

It seemed that the unknown device was referring to the old external firewire audio interface (1394) which somehow remained in the device manager list although no longer connected. I also re-installed the driver collection for the AMT and the Chipset although it told me that a newer version was...

But in this case I would have noticed it somewhere during my previous scans, wouldn't I ? I mean, sfc /scannow would have said something about and the intel driver utility would also have it listed ??? Anyway, I started a download of the complete Driver package from Fujitsu (1,5 GB). It'll be...

In fact I'd added this FireWire card as I had another external Audio interface I wanted to use. The Unibrain drivers WERE for that card. I'll remove it from the setup.

No, connected via RJ45 through a multi-layer switch to my router. This is my PC: ESPRIMO P920 0-Watt - Fujitsu CEMEA&I

That's what I've used. "Intel Driver Update Utility". When I go to "Auto Detect" it always only brings up the graphic driver: Intel Iris and HD Graphics Driver. But this one is already up-to-date (Ver 15.36.18.64.4156)......:sarc: While going for "manual", I have to select the mainboard...

Thanks softwaremaniac. I got rid of the Unibrain Firewire drivers, uninstalled McAfee and updated the Flashing Utility. Since the later one is from Fujitsu, I do not know whether or not the flashud.sys was now accordingly updated or not; I couldn't find anything related to my motherboard on the...

Hi Guys, This is my first entry to this forum upon which I stumbled by pure incident. My PC, purely used as Audio Workstation worked very fine and suddenly started to BSOD when getting into power save mode, e.g. when I was away for some minutes. The installation was a fresh Win 8.1 64bit...