How to Fix Windows Update Errors?: How to Resolve - BSOD during shutdown or when entering sleep mode?

BSOD during shutdown or when entering sleep mode

Hello,
I'm in need of a little assistance, my system started crashing (BSOD) or freezing approx 2 weeks ago when a shutdown was initiated or when entering sleep.
I've run checkdisk and it came back clean, I ran a full virus scan, 5 were found and cleaned from the
system but the problem persists.
I've zipped and uploaded the minidump and the system information to Skydrive, here's the link:

https://skydrive.live.com/redir.aspx?cid=0825ebfe0628dae1&resid=825EBFE0628DAE1!103&authkey=XT6xxAGu2zE%24
I'm running Windows 7 64 bit on an HP Pavilion Slimline s5150t
If additional information is needed just let me know
Thanks much.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 39
BCP1: FFFFF8800445EF50
BCP2: FFFFFA8006B98550
BCP3: FFFFFA80051B1F50
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\111111-26738-01.dmp
C:\Users\Jim\AppData\Local\Temp\WER-83242-0.sysdata.xml

Anwsers to the Problem BSOD during shutdown or when entering sleep mode

Download Error Fixer (Free)

Hi,
Results verified by WinDBG, DumpCHK, and BlueScreenView.

The Bug_Check was 39 CAUSE ks.sys which is a Windows component which means something else drove
it into Fault.

BugCheck 39, fffff8800445ef50, fffffa8006b98550, fffffa80051b1f50, 0
Probably caused by : ks.sys ( ks+2bf50 )
MODULE_NAME: ks
IMAGE_NAME: ks.sys
FAILURE_BUCKET_ID: X64_0x39_ks+2bf50
BUCKET_ID: X64_0x39_ks+2bf50
1.
Run DriverVerifier as indicated in the next message.

--------------
2.
Check with HP Support, their on-line documentation and drivers, diagnostics, and ask in their forums
about known issue.
Check for updates to the BIOS, low level chipset drivers, and the other major on-board
drivers.
Also update the major separate device drivers - run DriverView and set VIEW to Hide Microsoft
drivers - update those without Dump in their name.
See the methods in the next message.

BiosVersion = 5.05
BiosReleaseDate = 06/04/2009 <-- check for updates to the BIOS, low level chipset drivers, and the other
major on-board and separate device drivers.
SystemManufacturer = HP-Pavilion
SystemProductName = NY806AV-ABA s5150t
SystemFamily = 103C_53316J
SystemVersion =
SystemSKU = NY806AV#ABA
BaseBoardManufacturer = PEGATRON CORPORATION
BaseBoardProduct = Eureka3
BaseBoardVersion = 1.01

------------
3.
Use the other methods in the troubleshooters below.

===========================================================================
BCCode: 39   0x00000039
The most common cause of this Bug_Check is a driver.
If there is nothing referenced by the ln command
run DriverVerifier as indicated in the next message.
Bug Check 0x39: SYSTEM_EXIT_OWNED_MUTEX

The SYSTEM_EXIT_OWNED_MUTEX bug check has a value of 0x00000039.
This indicates that the worker routine returned without releasing the mutex object that it owned.
Important Information If You Have Received a STOP Code
If you have received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss.
A hardware device, its driver, or related software might have caused this error.
If your copy of Windows came with your computer,
call the manufacturer of your computer.
If you purchased Windows separately from your computer, Microsoft provides support.
To find contact information for Microsoft or your computer manufacturer,
Contact Support.
If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft article
Resolving STOP (Blue Screen) Errors in Windows.
The following actions might prevent an error like this from happening again:
Download and install updates and device drivers for your computer from Windows Update.
Scan your computer for computer viruses.
Check your hard disk for errors.
SYSTEM_EXIT_OWNED_MUTEX Parameters
The following parameters are displayed on the blue screen.
Cause
The worker routine returned while it still owned a mutex object.
The current worker thread will proceed to run other unrelated work items, and the mutex will never be released.
Resolution
A debugger is required to analyze this problem.
To find the driver that caused the error, use the
ln (List Nearest Symbols) debugger command:
kd> ln address
Where address is the worker routine given in Parameter 1.
BCCode: 39   0x00000039   <-- read this link
http://www.faultwire.com/solutions-fatal_error/SYSTEM-EXIT-OWNED-MUTEX-0x00000039-*1072.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

How To Disable Automatic Driver Installation In Windows Vista - Drivers
http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
http://technet.microsoft.com/en-us/library/cc730606(WS.10).aspx

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

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.

To check for Windows updates

Open Windows Update by clicking the Start button Picture of the Start button, clicking All Programs, and then clicking Windows Update.
In the left pane, click Check for updates, and then wait while Windows looks for the latest updates for your computer.
If any updates are found, click Install updates. Administrator permission required If you are prompted for an administrator password or confirmation, type the password or provide confirmation.

Another Safe way to Fix the Problem: BSOD during shutdown or when entering sleep mode:

How to Fix BSOD during shutdown or when entering sleep mode with SmartPCFixer?

1. Click the button to download Error Fixer . Install it on your system. Open it, and it will scan your computer. The errors will be shown in the list.

2. After the scan is done, you can see the errors and problems need to be repaired. Click Fix All.

3. The Repair part is finished, the speed of your computer will be much higher than before and the errors have been removed. You can also use other functions in SmartPCFixer. Like dll downloading, junk file cleaning and print spooler error repair.

How to Fix Windows Update Errors?

Thursday, August 25, 2016

How to Resolve - BSOD during shutdown or when entering sleep mode?

BSOD during shutdown or when entering sleep mode

Anwsers to the Problem BSOD during shutdown or when entering sleep mode

To check for Windows updates

Another Safe way to Fix the Problem: BSOD during shutdown or when entering sleep mode:

How to Fix BSOD during shutdown or when entering sleep mode with SmartPCFixer?

No comments:

Post a Comment