How to Fix a Kernel32.DLL Error? : BSOD 0x0000007E error with srvnet.sys reference upon bringing laptop out of standby Tech Support

BSOD 0x0000007E error with srvnet.sys reference upon bringing laptop out of standby

I went to open the lid of my compaq presario cq62 notebook pc when i was greeted instead by a BSOD with the number 0x0000007E and a reference to the srvnet.sys file.

What is going on?

I've now had maybe four BSODs in the past month, including this one, the others were completely different.

Memory and Hard disk tests, both Windows and BIOS based versions, indicate all is well hardware wise.

What should I do?

Thanks

David

Anwsers to the Problem BSOD 0x0000007E error with srvnet.sys reference upon bringing laptop out of standby

Download SmartPCFixer to Fix It (Free)

Hi,
Check these KB articles :
"Stop 0x0000007E" or "Stop 0x00000050" Stop error message in Windows 7 or Windows Server
2008 R2
http://support.microsoft.com/kb/979538
"Stop 0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" error when the GPU is under
heavy load conditions in Windows 7 or Windows Server 2008 R2
http://support.microsoft.com/kb/983615

---------------------------------------------------------------------------------------------

See this thread for information on using BlueScreenView, MyEventViewer, and other methods to
troubleshoot BlueScreens - top 3 replies (+1 other).
http://answers.microsoft.com/en-us/windows/forum/windows_7-system/sometimes-i-get-a-blue-screen-when-using-ie-8/c675b7b8-795f-474d-a1c4-6b77b3fcd990
We can analyze the minidumps if you make them available from the SkyDrive or other file

sharing sites (such as MediaFire).
If you have problems uploading the minidumps copy

them to the Desktop or the Documents folder and upload them from there.

Zip or upload the contents of C:\Windows\minidump
Use SkyDrive to upload collected files.
http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
---------------------------------------------------------------------------------------------
References to Vista also apply to Windows 7.

BCCode: 7E     0x0000007E which is also 0x1000007E
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-
spyware/security programs.

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
Cause
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:

0x80000002: STATUS_DATATYPE_MISALIGNMENT indicates an unaligned data reference was encountered.
0x80000003: STATUS_BREAKPOINT indicates a breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.
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 theinc 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
/DEBUG switch.
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.chkfiles 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.
BCCode: 7E    0x00000007E which is also 0x1000007E <-- read this link
http://www.faultwire.com/solutions-fatal_error/SYSTEM-THREAD-EXCEPTION-NOT-HANDLED-0x0000007E-*1141.html?order=votes
===============================================================

Look in the Event Viewer to see if anything is reported about those.
http://www.computerperformance.co.uk/vista/vista_event_viewer.htm
MyEventViewer - Free - a simple alternative to the standard event viewer of Windows.
TIP - Options - Advanced Filter allows you to see a time frame instead of the whole file.
http://www.nirsoft.net/utils/my_event_viewer.html

---------------------------------------------------------------

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.

As examples :

BCCode: 116
BCP1: 87BC9510
BCP2: 8C013D80
BCP3: 00000000
BCP4: 00000002
or in this format :
Stop: 0x00000000 (oxoooooooo oxoooooooo oxooooooooo oxoooooooo)
tcpip.sys - Address 0x00000000 base at 0x000000000 DateStamp 0x000000000

This is an excellent tool for posting Blue Screen Error Information

BlueScreenView scans all your minidump files created during 'blue screen of death'
crashes, and displays the information about all crashes in one table - Free
http://www.nirsoft.net/utils/blue_screen_view.html

Many BlueScreens are caused by old or corrupted drivers, especially video drivers however
there are other causes.

You can do these in Safe Mode if needed or from Command Prompt from Vista DVD or
Recovery Options if your system has that installed by the maker.

How to Boot to the System Recovery Options in Windows 7
http://www.sevenforums.com/tutorials/668-system-recovery-options.html

You can try a System Restore back to a point before the problem started if there is one.

How to Do a System Restore in Windows 7
http://www.sevenforums.com/tutorials/700-system-restore.html

-------------------------------------------------------------------------

Start - type this in Search Box -> COMMAND   find at top and RIGHT CLICK - RUN AS ADMIN

Enter this at the prompt - sfc /scannow
How to Repair Windows 7 System Files with System File Checker
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program
generates in Windows Vista cbs.log (and Windows 7)
http://support.microsoft.com/kb/928228

The log might give you the answer if there was a corrupted driver.
(Does not tell all the possible
driver issues).

Also run CheckDisk so we can rule out corruption as much as possible.

How to Run Check Disk at Startup in Windows 7
http://www.sevenforums.com/tutorials/433-disk-check.html

-------------------------------------------------------------------------

Often updating drivers will help, usually Video, Sound, Network Card (NIC), WiFi, 3rd party
keyboard and mouse, as well as other major device drivers.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.
http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm
Installing and updating drivers in Windows 7 (updating drivers manually using the methods above
is preferred to ensure the latest drivers from System maker and Device makers are found)
http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html

Stop Windows 7 from Automatically Installing Device Drivers
http://helpdeskgeek.com/windows-7/stop-windows-7-from-automatically-installing-device-drivers/

How To Disable Automatic Driver Installation In Windows 7 / Vista
http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/

Disable Windows Update Device Driver Search Prompt In Windows 7 / Vista (for Professional,
Ultimate, and Enterprise)
http://www.addictivetips.com/windows-tips/disable-windows-update-device-driver-search-prompt/

-------------------------------------------------------------------------

How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart
unexpectedly
http://support.microsoft.com/kb/958233

Troubleshooting Vista Blue Screen, STOP Errors (and Windows 7)
http://www.chicagotech.net/vista/vistabluescreen.htm

Understanding and Decoding BSOD (blue screen of death) Messages
http://www.taranfx.com/blog/?p=692

Windows - Troubleshooting Blue Screen Errors
http://kb.wisc.edu/page.php?id=7033

-------------------------------------------------------------------------

In some cases this might be required.

StartUp Repair from Recovery Options or Windows 7 disk

How to Run a Startup Repair in Windows 7
http://www.sevenforums.com/tutorials/681-startup-repair.html
How to Boot to the System Recovery Options in Windows 7
http://www.sevenforums.com/tutorials/668-system-recovery-options.html
How to Create a Windows 7 System Repair Disc
http://www.sevenforums.com/tutorials/2083-system-repair-disc-create.html
How to Do a Repair Install to Fix Windows 7
http://www.sevenforums.com/tutorials/3413-repair-install.html

Hope this helps.

Rob Brown -
Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle - Mark Twain said it right.

Check Windows System Requirements

Microsoft Windows Requirements :

1 gigahertz (GHz) or faster 32-bit (x86) or 64-bit (x64) processor
1 gigabyte (GB) RAM (32-bit) or 2 GB RAM (64-bit)
16 GB available hard disk space (32-bit) or 20 GB (64-bit)

This error can be due to some configuration requirements for you system. If your PC hardware is not up to par, then make sure you update where necessary before continuing.

Another Safe way to Fix the Problem: BSOD 0x0000007E error with srvnet.sys reference upon bringing laptop out of standby:

How to Fix BSOD 0x0000007E error with srvnet.sys reference upon bringing laptop out of standby with SmartPCFixer?

1. Download SmartPCFixer . Install it on your system. Click Scan, and it will perform a scan for your computer. The junk files will be shown in the scan result.

2. After the scan is done, you can see the errors and problems which need to be fixed.

3. When the Fixing part is done, your computer has been speeded up and the errors have been fixed

How to Fix a Kernel32.DLL Error?

Thursday, August 25, 2016

BSOD 0x0000007E error with srvnet.sys reference upon bringing laptop out of standby Tech Support

BSOD 0x0000007E error with srvnet.sys reference upon bringing laptop out of standby

Anwsers to the Problem BSOD 0x0000007E error with srvnet.sys reference upon bringing laptop out of standby

Check Windows System Requirements

Another Safe way to Fix the Problem: BSOD 0x0000007E error with srvnet.sys reference upon bringing laptop out of standby:

How to Fix BSOD 0x0000007E error with srvnet.sys reference upon bringing laptop out of standby with SmartPCFixer?

No comments:

Post a Comment