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.
Bluescreen minidump error message - bc code: 1000007e
This forced shutdown only happens if my computer has been shut down for 5 or more hours and usually happens within 15 mins of start up if i restart after forced shutdown let every thing load shut down & start again it doesnt happen again until next time
its been off for 5 hrs or more. if if i dont do this it continues to crash &if its only shut down for a few hrs it doesnt happen at all ive tried reinstalling windows, updating drivers & bios nothing has worked, any suggestions Thanks 74dazaj
This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.
Since you have reinstalled Windows and it does not happen after 5 hours rest it just about has to
be hardware. Possibly also heat related so try adding a fan to blow into or across the vents. For
a PC remove all power then reseat all cards, memory, and cables (on both ends when possible)
- actually remove and replace - do not just snug.
Here is the troubleshooter for that error however you really need technical help from a real computer shop or your System maker's Support.
References to Vista also apply to Windows 7.
This error is usually a driver issue and display adapter (video) driver is the most suspect though it
could be others. Antivirus/antispyware/security programs, hardware (heat) and major software issues
can also cause the error. When you get to the driver section of the troubleshooter use my generic
methods in the next message and then return to the troubleshooter if needed.
Have you added hardware recently or updated drivers? Be sure to look in Control Panel - Windows
Updates to see if any drivers were updated there. Other lessor possibilities include antivirus/anti-
When you get to the driver and memory sections of the troubleshooter refer to the next message to
update drivers and test memory and then refer back to the troubleshooter if needed.
BCCode: 7E 0x0000007E which is also 0x1000007E
The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check is a very common bug check. To
interpret it, you must identify which exception was generated.
Common exception codes include the following:
0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.
For a complete list of exception codes, see the Ntstatus.h file that is located in the
inc directory of
the Microsoft Windows Driver Kit (WDK).
Resolving the Problem
If you are not equipped to debug this problem, you should use some basic troubleshooting techniques.
Make sure you have enough disk space.
If a driver is identified in the bug check message, disable the driver or check with the
manufacturer for driver updates.
Try changing video adapters.
Check with your hardware vendor for any BIOS updates.
Disable BIOS memory options such as caching or shadowing.
If you plan to debug this problem, you might find it difficult to obtain a stack trace. Parameter 2
(the exception address) should identify the driver or function that caused this problem.
If exception code 0x80000003 occurs, a hard-coded breakpoint or assertion was hit, but the system
was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly,
make sure that a kernel debugger is connected and the system is started with the
If exception code 0x80000002 occurs, the trap frame supplies additional information.
If you do not know the specific cause of the exception, consider the following issues:
Hardware incompatibility. Make sure that any new hardware that is installed is listed in the
Microsoft Windows Marketplace Tested Products List.
Faulty device driver or system service. A faulty device driver or system service might be
responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts,
and IRQ conflicts can also generate this error.
If a driver is listed by name within the bug check message, disable or remove that driver. Disable
or remove any drivers or services that were recently added. If the error occurs during the startup
sequence and the system partition is formatted with NTFS file system, you might be able to use Safe
Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process
in Safe Mode, you must start the computer by using the Recovery Console to access the file.
If the problem is associated with Win32k.sys, the source of the error might be a third-party remote
control program. If such software is installed, you can remove the service by starting the computer
by using the Recovery Console and then deleting the offending system service file.
Check the System Log in Event Viewer for additional error messages that might help identify the
device or driver that is causing bug check 0x7E.
You can also disable memory caching of the BIOS might to try to resolve the error. You should also
run hardware diagnostics, especially the memory scanner, that the system manufacturer supplies.
For more information about these procedures, see the owner's manual for your computer.
The error that generates this message can occur after the first restart during Windows Setup, or
after Setup is finished. A possible cause of the error is lack of disk space for installation and system
BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk
space, reduce the number of files on the target hard disk drive. Check for and delete any temporary
files that you do not have to have, Internet cache files, application backup files, and
.chk files that
contain saved file fragments from disk scans. You can also use another hard disk drive with more
free space for the installation. You can resolve BIOS problems by upgrading the system BIOS version.
Here are some methods to possibly fix the blue screen issue. If you could give the Blue Screen info
that would help. Such as the BCC and the other 4 entries on the lower left. And any other error
information such as STOP codes and info such as IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.
This is my generic how to for proper driver updates :
This utility makes it easy to see which versions are loaded :
DriverView - Free - utility displays the list of all device drivers currently loaded on your system.
For each driver in the list, additional useful information is displayed: load address of the driver,
description, version, product name, company that created the driver, and more. http://www.nirsoft.net/utils/driverview.html
For Drivers check System Maker as fallbacks and Device Maker's which are the most current.
Control Panel - Device Manager - Display Adapter - write down the make and complete model
of your video adapter - double click - Driver's tab - write down the version info. Now click UPdate
Driver (this may not do anything as MS is far behind certifying drivers) - then Right Click -
Uninstall - REBOOT this will refresh the driver stack.
Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard if 3rd party
with their own software and drivers and any other major device drivers you have.
Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and then Device
Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their latest versions. (Look for
BIOS, Chipset and software updates at System Maker's site while there.)
Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN - REBOOT after
Always check in Device Manager - Drivers tab to be sure the version you are installing actually
shows up. This is because some drivers rollback before the latest is installed (sound drivers
particularly do this) so install a driver - reboot - check to be sure it is installed and repeat as
Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER - check
manually by model.
If you update drivers manually then it is a good idea to disable Driver Installations in Windows
Updates, this leaves Windows Updates ON however it will not install drivers which will usually be
older and cause issues. If Updates suggests a new driver then HIDE it (Right Click on it) and then
go look for new ones manually if you wish.