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.
automatically restarting saying that "Your PC ran into problem"
I have installed windows 8.1 recently. I have been getting a blue screen automatically saying that " :( Your PC ran into problem and we will restart for you."
It is also showing that "search for IRQL_unexpected_value". This is happening very often recently for about 2 times a day. I am losing all my work. I have searched for it. But, that was showing something related to Wifi. I dont have any problem using my
Further, I also found that my windows defender was not able to update. It is showing an error code"0x8024402c". I dont know how these two are related. Please help me out in solving this.
This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.
If that's what you're connecting with, it's strange we're seeing a Conexant Modem Diagnostic Interface x86 Driver listed and loaded. Do you otherwise have a 3rd party modem or fax connected?
Have you visited your manufacturers website and ensured all network drivers are up to date?
Let's go ahead and enable Driver Verifier for more info as I am now curious:
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?