Forum Replies Created
November 5, 2017 at 1:45 pm in reply to: Network Adapter PCI\VEN_14E4&DEV_43A0&SUBSYS_061914E4&REV_03 #2267
I thought I’d be helpful and install the driver in the link I gave. After installing, my network card wasn’t updated, so I went to update it and set it to search my hard drive for an update (prior to installing from the CD there was no driver available), after installing the driver and searching the C: drive, it found a new driver and updated my Network Adapter, so I’d say that link to the driver software is probably the right one.
October 27, 2017 at 7:37 am in reply to: A Delegation For This DNS Server Cannot Be Created – Windows Server 2012 R2 #2263
If you get the delegation for this DNS server cannot be created error, you might want to double check that there’s a record for your domain name pointing to the IP address of the server you just promoted to a DC.
Thought I’d just do an update to my review of Trend Micro’s Web Reputation software.
Basically, after using it for a year and a half, I can quite comfortably say that it’s terrible. It would be adequate for some uses as my former review stated, were it not for the fact that half the time the URL whitelisting system doesn’t work.
I highly DON’T recommend it.
❗ I didn’t realise that I’d already encountered this problem, so I worked out how to solve it and wrote this article. I just noticed that I’d already wrote an article, but I’ll share what I’d written up because it looks at the problem from a different perspective, shares more info on why the database can’t be deleted and also a different solution.
Here’s how to delete a PostgreSQL database, to get around an annoying message telling you that you cannot drop / delete the database.
First the problem: You open PG Admin, right click the database you want to delete and click drop / delete database. It then gives you an error message saying that the database is in use and there is an active connection. You check for running processes and all you can see is possibly an autovacuum, which you kill and try again. You still cannot delete the database.
You also try deleting the PostgreSQL database using drop database databaseName; which doesn’t work.
The solution: Rather ingeniously PostgreSQL has a clever interface that specifies that you must connect to the database to do things to it, but when you click delete / drop, it doesn’t work because you’re connected to it. Brilliant.
To get around this, create another database (if you don’t already have another database other than the one you want to delete), then restart the PostgreSQL service. Load up PG Admin and WITHOUT CLICKING ON THE DATABASE YOU CANNOT DELETE, click on the database you just created and run the SQL Query interface. Run drop database databaseName; and the database should now be deleted.
June 28, 2017 at 10:52 am in reply to: The Letter 'L' (And Other Lines) In PDFs Is Too Thick / Bold #2143
The “Enhance Thin Lines” setting can be found under Edit -> Preferences in the menu.
❗ Update: I have contacted SonicWall support who have suggested that I should update my firmware to the latest as there is no evidence in my SonicWall logs of having crashed. I updated my firmware yesterday and the SonicWall hasn’t crashed since. As before, I’ll message again if it crashes again, otherwise you can assume that this fixed it.
… looks like this didn’t fix it. I’ll take this to SonicWall’s support and let you know how I get on.
❗ UPDATE: My SonicWall crashed again yesterday and I think I’ve managed to fix it this time.
I think what was happening is that the CPU on the SonicWall was overutilized and the SonicWall was becoming completely unresponsive. I think this was due to the Gateway Anti-Virus scanning incoming packets from the internet as usage (or hack attempts) increased throughout the day.
To fix this, I turned off outgoing HTTP scanning, and scanning of both outgoing and incomming TCP streams. My SonicWall has not crashed since making this change. Fingers crossed 🙂
If I don’t update this thread after today, you can assume that this fixed it!
January 30, 2017 at 10:03 am in reply to: Volume Shadow Copy Service: Error calling routine on Shadow Copy Provider #2045
Today I had some issues with Chromecast going slow, and it was because the Chromecast was too hot.
I put it in the freezer for 30 seconds which fixed it. If I get around to it, I might buy a heatsink for it. Maybe an old CPU one might be small enough, or the heatsinks you can get for “performance” RAM might be suitable.
This issue is perhaps only one that you get in hot countries.
Today I discovered that sometimes Chromecast’s audio can be kind of jittery if the Chromecast connection to the TV isn’t great (wiggle the USB and HDMI cables going into the TV). Sometimes jitter in audio can be fixed by stopping the cast and casting the Chrome browser again. Also, rebooting the TV, computer and router can fix this 🙁
December 21, 2016 at 9:12 am in reply to: PCI To PCI Bridge PCI\VEN_8086&DEV_A119&SUBSYS_50011458&REV_F1 #2011
Update: The PCI to PCI Bridge turned out to be an Intel(R) 100 Series/C230 Series Chipset PCI Express Root Port #100 – A119. The driver was available on Windows Updates, eventually!
The above link is correct for the SM Bus controller with hardware ID “”, but the link below makes it easier to find:
It’s actually an Original AMD Chipset Driver.
That’s the correct website for the Ethernet Controller with hardware ID “”, it’s listed under the “Original Drivers” section and is a Original Realtek Network Controller Driver. The URL to that specific download is here:
November 10, 2016 at 6:17 pm in reply to: Windows Modules Installer Worker – High Disk Usage #1990
Now that I’ve mentioned how to fix the high CPU usage of the Windows Modules Installer Worker, since it’s such a common problem I thought I’d explain why the after mentioned things cause high CPU form the Windows Modules Installer Worker.
To do this, firstly I’ll explain what the Windows Modules Installer Worker is. The Windows Modules Installer Worker is a process of the Windows Modules Installer service. According to Microsoft, the Windows Modules Installer service is basically in charge of installing, updating or removing Windows Updates and Optional Updates.
So given this, the following causes were identified as culprits for causing high CPU due to the Windows Modules Installer Worker:
- You are running a disk repair
- Your PC is performing disk maintenance of some kind
- You are installing Windows Updates
- You have a hardware issue with your hard disk or hard disk controller
- You have a virus
As you can see, all are things that would suffer from high disk usage, which rather annoyingly causes the Windows Modules Installer Worker to use high CPU usage. Ultimately, the Windows Modules Installer service could have been coded to better deal with disk latency, but it hasn’t. So, the best way to fix the issue of high CPU usage, is strangely to upgrade to a faster disk – like an SSD disk.