Protect Yourself From Tech Support Scams
July 29, 2020
Protect Yourself From Tech Support Scams
Tech support scams are an industry-wide issue where scammers trick you into paying for unnecessary
technical support services. You can help protect yourself from scammers by verifying that the contact is a
Microsoft Agent or
Microsoft Employee and that the phone number is an
Microsoft global customer service number.
Driver_power_state_failure after upgrade to Windows 8.1 x64
Since upgrading to Windows 8.1, my network connection is continually dropping. Running the Network troubleshooting wizard causes the Broadcom Gigabit Ethernet Adaptor to hang/become disabled.
Rebooting either before or after the network connection drops fixes the connection but if the troubleshooting wizard was run, the reboot results in a BSOD with DRIVER_POWER_STATE_FAILURE error.
I downloaded the latest Broadcom drivers but Windows insists that the default driver is current and won't allow installation of the vendor driver (which is an earlier version number, but has a more recent date than default WIndows driver).
I've uploaded the latest two minidumps and a full dump to Skydrive. (http://sdrv.ms/17WIvSD)
Any help would be appreciated.
This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.
2. 3rd party antivirus or firewall software causing network conflicts (i.e NETBIOS ports).
Do you have any antivirus or firewall software installed and/or enabled? If not, let's go ahead and enable Driver Verifier:
What is Driver Verifier?
Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode
components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
Start > type "verifier" without the quotes > Select the following options -
1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is [B]NOT[/B] provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
Important information regarding Driver Verifier:
- If Driver Verifier finds a violation, the system will BSOD.
- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause /
force a BSOD.
If this happens, do not panic, do the following:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > type "system restore" without the quotes.
- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:
- Start > Search > type "cmd" without the quotes.
- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・ Restart and boot into normal Windows.
How long should I keep Driver Verifier enabled for?
It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.
My system BSOD'd, where can I find the crash dumps?