Windows 10: wireless wifi is not working in my coputer optiplex 3040

have a Dell Vostro 15 that I've had just under a year, for some reason the wireless WiFi function isn't working and in Driver it's saying windows have stopped it because it isn't working, but I don't know how to fix that. I've tried reseting the network, going onto command prompt and flushing the dns and reseting winsock, but nothing is working longer than a few days to a week. I have also paid someone to look at it and they deleted the drive for wireless WiFi connection intelr Wireless AC 9462 and reinstall the drive via the Internet using an ethernet cable, but that is also not wor

:)

 

Dell Optiplex 3040 SFF

So I recently picked up a Dell Optiplex 3040 Small form factor PC for quite a good deal. It Came with an i5 6500, 1TB HDD and a Single stick of 8GB DDR3L. I've been checking Dell's website regarding the specs of the Optiplex 3000 series and i've noticed that they originally only came with Skylake i5's. I'm planning on making it my living room gaming PC. Since I have an Extra i7 6700 non K lying around, I was just wondering if I can just switch out the CPU and reinstall Windows 10. I'm also planning on adding an MSI GTX 1050Ti Low Profile. I'm pretty sure the 180W PSU that came with it is not going to work. Anyone can recommend a TFX PSU? Thank you for the answers.

 

Windows 10 Optiplex 3040 USFF - Error PNP DRIVER WATCHDOG infinite loop

I have Ultra Small Form Factor Dell Optiplex 3040.

There were serious issues with previous installation, so reinstalled WIndows 10 from USB I created using Microsoft Tool. Installed fine, worked good, so plugged a WIFI dongle TP-Link TL-WN422G. Unfortunately all it has are WIndows 8 drivers (however it installed fine). Regardless, the dongle worked for an hour and I've updated drivers ...

Or rather I left it to update drivers. I had to go out for a bit.

Upon return computer is locked in endless reboot loop - restart, automatic repair, error PNP DRIVER WATCHDOG, restart... Exactly same thing happens when trying to boot from installer USB again.

I explicity choose USB from Boot menu list (tried with Legacy and UEFI, same result), wait for reaction several minutes, but it goes to either PNP DRIVER ERROR or Automatic Repair. Factory reset is out of question as drive was cleaned.

There is a Data wipe option in Bios, but the drive is 500GB 2.5" spinner, so it will take tiiiiiimmme to complete. Last time i did it it took 11 hours. Thus reluctant, also don't want to use another activation on that key.

Basically the only interactive moment in the whole loop is BIOS - I can enter BIOS, can enter Boot Menu and that's about it.

First time see something like this. Can this be hardware fault? Dell Diagnostics are a PASS. But no way to break the loop. What would be the next step?

 

February 14th update breaks mouse keyboard on Dell Optiplex 3040 SFF models

The windows update last Tuesday has been causing issues with ONLY our Dell Optiplex 3040 SFF units.



The mouse and keyboards drop off.



If we unplug the mouse or keyboard and plug it in it appears to install BUT they do not. They show up as unknown devices.



We have tried all the usual suggestions. Uninstalling the USB hub and the devices and the same issue the mouse and keyboard will not install.

We have tuend off USB sleep have tried various BIOS settings.



We have done rollbacks that work but a few days later the issue has come back.



We have seen this ONLY on our 3040s about 10 so far. Our 3010, 3020, and 3050s do not demonstrate this bug.



When we try to manually reinstall the mouse and KB; windows states NO DRIVERS FOUND. The devices show as unknown devices with the right names wired dell keyboard and HID compliant mouse.



As another workaround we have the device drivers in a separate folder and we can manually update the mouse and KB that that way. BUT if the user moves the mouse or KB to another port we would have to do the manual install again.



Mouse and KB are the only items being affected. Printers are not and other USB devices.



Anyone else seen this issue and any solutions?