Share via

Help - Blue Screen of Death

Anonymous
2013-12-02T00:57:08+00:00

Twice within the past month and a half, I have received the dreaded blue screen of death with the most recent one happening last night. I'm unsure what to do and hoping bringing it to computer repair will not be necessary. The two times the bsod have occurred, my laptop was NOT in sleep/hibernate mode. I was lightly surfing the internet. I have noticed that it's getting quite hot and the fan goes on pretty often, which is kind of noisy. I am running Windows 7 Home Premium on a Dell XPS L502X with 8gb RAM. 

Any help would be greatly appreciated as I'm currently a university student with no spare money to pay a computer repair shop.

DMP file: http://sdrv.ms/18wL5VR

  

System
- Provider <br> --- --- <br><br><br><br> [ Name] Microsoft-Windows-Kernel-Power <br> --- --- <br><br><br><br><br> [ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4} <br> --- ---
EventID 41 <br> --- ---
Version 2 <br> --- ---
Level 1 <br> --- ---
Task 63 <br> --- ---
Opcode 0 <br> --- ---
Keywords 0x8000000000000002 <br> --- ---
- TimeCreated <br> --- --- <br><br><br><br> [ SystemTime] 2013-12-01T05:10:50.261655800Z <br> --- ---
EventRecordID 197325 <br> --- ---
Correlation <br> ---
- Execution <br> --- --- <br><br><br><br> [ ProcessID] 4 <br> --- --- <br><br><br><br><br> [ ThreadID] 8 <br> --- ---
Channel System <br> --- ---
Computer Michelle-Laptop <br> --- ---
- Security <br> --- --- <br><br><br><br> [ UserID] S-1-5-18 <br> --- ---
- EventData
BugcheckCode 0
BugcheckParameter1 0x0
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0
SleepInProgress false
PowerButtonTimestamp 0
Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

  1. Anonymous
    2013-12-02T01:59:56+00:00

    Hi,

    Do as Patrick says an uninstall AVG and run their Removal Tool to prevent trouble causing

    remnants.

    Check with your system maker's support, their on-line documentation and drivers, and ask

    in their forums (if any) about known issues. Update the BIOS, low level chipset drivers,

    and the major on-board and separate device drivers. Especially update the Synaptic

    Touchpad Drivers.

    Synaptic Touchpad Drivers

    http://www.synaptics.com/resources/drivers

    Rob - SpiritX

    Was this answer helpful?

    0 comments No comments

Answer accepted by question author

  1. Anonymous
    2013-12-02T01:47:02+00:00

    I've taken a look at the DMP file you added to your original post, it's of the DRIVER_POWER_STATE_FAILURE (9f) bug check.

    This bug check indicates that the driver is in an inconsistent or invalid power state.

    If we go ahead and run an !irp on the 4th parameter of the bug check (blocked IRP address):

    >[ 16, 2]   0 e1 fffffa800a4e6cd0 00000000 fffff8000306b710-fffffa800d78b110 Success Error Cancel pending          Unable to load image \SystemRoot\system32\DRIVERS*SynTP.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for SynTP.sys*** ERROR: Module load completed but symbols could not be loaded for SynTP.sys*

    ^^ Synaptic Touch Pad Driver

    Check for an update - http://www.synaptics.com/resources/drivers

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

    Remove and replace AVG with Microsoft Security Essentials for temporary troubleshooting purposes:

    AVG removal tool - http://www.avg.com/us-en/utilities

    MSE -  http://windows.microsoft.com/en-us/windows/security-essentials-download

    -----------------------------------------------------------------------------***If after the above you're still crashing, please go ahead and enable Driver Verifier for more info:*******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:

    Vista - START | type rstrui - create a restore point

    Windows 7 - START | type create | select "Create a Restore Point"

    Windows 8 - http://www.eightforums.com/tutorials/4690-restore-point-create-windows-8-a.html

    How to enable Driver Verifier:

    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
    1. Select  - "Select driver names from a list"
    2. Click on the "Provider" tab. This will sort all of the drivers by the provider.
    3. Check EVERY box that is [B]NOT[/B] provided by Microsoft / Microsoft Corporation.
    4. Click on Finish.
    5. Restart.

    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?

    They will be located in %systemroot%\Minidump

    Any other questions can most likely be answered by this article:

    http://support.microsoft.com/kb/244617

    Regards,

    Patrick

    Was this answer helpful?

    0 comments No comments

6 additional answers

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Anonymous
    2013-12-02T01:16:26+00:00

    Hi,

    Are you using any Roxio or Nero programs? These have been known to cause this problem even

    if they were working well for a long period of time. If so check with their support.


    Check these :

    Error message when you try to resume a Windows 7-based or a Windows Server 2008 R2-based

    computer from hibernation: "Stop 0x0000009F"

    http://support.microsoft.com/kb/977186 

    Stop error when you put a computer that is running Windows 7 or Windows Server 2008 R2 to

    sleep or into hibernation, or when you restart the computer: "0x9F"

    http://support.microsoft.com/kb/975599 

    "0x0000009F" Stop error message when a computer enters and resumes from hibernation in

    Windows 7 or Windows Server 2008 R2

    http://support.microsoft.com/kb/981848 

    This one is possible if BlueScreenView OR MyEventViewer (or EventViewer) shows the appropriate code.

    Windows Kernel event ID 41 error in Windows 7 or in Windows Server 2008 R2: “The system has

    rebooted without cleanly shutting down first”

    http://support.microsoft.com/kb/2028504 

    And :

    "Stop 0x9F" or "Stop 0xFE" error on a Windows 7-based or Windows Vista-based computer that

    uses certain AMD USB EHCI host controllers

    http://support.microsoft.com/kb/982091 

    KB Search 0x0000009F with the above and a few other articles (check this as there may be new articles

    added to the KB)

    http://support.microsoft.com/search/default.aspx?mode=a&query=0x0000009F&spid=14019&catalog=LCID%3D1033&res=10 

    KB Search 0x9F with the above (check this as there may be new articles added to the KB)

    http://support.microsoft.com/search/default.aspx?mode=a&query=0x9F&spid=14019&catalog=LCID%3D1033&res=10 


    Resolving stop (blue screen) errors in Windows 7 - has a section for if you can or can't start Windows.

    http://windows.microsoft.com/en-us/windows7/Resolving-stop-blue-screen-errors-in-Windows-7 

    Check this thread for information using BlueScreenView, MyEventViewer and other methods

    to troubleshoot BlueScreens - top 3 replies.

    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 and post screen shot/picture.

    http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

    ===========================================================

    Check with these utilities to see if any information can be gathered : (Be sure to run this since there

    may well be other Bug_Check codes.)

    This is an excellent tool for posting Blue Screen Error Information

    BlueScreenView - Free - scans all your minidump files created during 'blue screen of death' crashes,

    and displays the information about all crashes in one table.

    http://www.nirsoft.net/utils/blue\_screen\_view.html


    MyEventViewer can be checked at the time of the BlueScreen (BSOD) to within a second or so of the

    time of the BSOD to provide more information as to possible cause - see TIP.

    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 -

    set it to a bit before and after the time of the BSOD.

    http://www.nirsoft.net/utils/my\_event\_viewer.html


    AppCrashView - Free - a small utility for Windows Vista and Windows 7 that displays the details of all

    application crashes occurred in your system. The crashes information is extracted from the .wer

    files created by the Windows Error Reporting (WER) component of the operating system every

    time that a crash is occurred. AppCrashView also allows you to easily save the crashes list to

    text/csv/html/xml file.

    http://www.nirsoft.net/utils/app\_crash\_view.html

    ================================

    ================================

    **References to Vista also apply to Windows 7.**This "could" be a power supply problem though it is not the most common cause.

    9f is likely a driver issue. Antivirus/antispware/security programs can also cause these issues.

    Have you added devices lately or updated drivers - be sure to check in Windows Updates to see

    if a driver was updated prior to this occurring. This could also be caused by a loose card or cable

    and even a weak power supply.

    That error means a driver is not handling the power state properly. Check in Control Panel - Device

    Manager to be sure major drivers are not shut off during sleep - double click Display Adapter - NIC

    and WIFI - Sound and others - Power Management tab - uncheck Allow computer to turn off power.

    Maybe only one has an issue.

    Start - type in Search box - MSCONFIG  find at top - Right Click - RUN AS ADMINGeneral Tab - check Diagnostic Start  - APPLY / OK  -  REBOOTTry it now. If it still blue screens think Video Driver. If not think NIC, Wifi, Sound, or......(and it still could be video interacting with something else). See troubleshooter linkabove for my generic driver update methods.MSDN - Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE <-- read this linkhttp://msdn.microsoft.com/en-us/library/ff559329(v=VS.85).aspx

    BCCode: 9F  0x0000009F  <-- read this linkhttp://www.faultwire.com/solutions-fatal\_error/DRIVER-POWER-STATE-FAILURE-0x0000009F-\*1167.html?order=date


    Driver Verifier can help find some BSOD issues :

    Using Driver Verifier to identify issues with Windows drivers for advanced users

    http://support.microsoft.com/kb/244617 

    How To Troubleshoot Driver Problems in Windows Vista or 7.

    http://www.winvistaclub.com/t79.html 

    Using Driver Verifier

    http://msdn.microsoft.com/en-us/library/ff554113(v=VS.85).aspx 

    How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issueshttp://www.youtube.com/watch?v=\_VwIDD9xngM

    Driver Verifier

    http://www.techsupportforum.com/2110308-post3.html

    Using Driver Verifier

    http://www.faultwire.com/solutions/using\_driver\_verifier.php 

    How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issues

    http://www.youtube.com/watch?v=\_VwIDD9xngM 

    You can disable Driver Verifier

    http://support.microsoft.com/kb/244617 

    Start - type in Search box -> verifier /reset      hit enter to disable

    Use BlueScreenView to see if there is a driver specified in the error message. Also check with

    MyEventViewer at the time of the BlueScreen.

    If DriverVerifier creates a minidump upload it and post the link here so we can analyze it.


    This is my generic how to for proper driver updates : (update your major drivers and BIOS)

    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

    each installation.

    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

    needed.

    Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER - check

    manually by model.

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

    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.

    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/

    Hope this helps.


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

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-12-02T01:12:34+00:00

    Hi,

    In order to assist you, we will need the DMP files to analyze what exactly occurred at the time of the crash, etc.

    If you don't know where DMP files are located, here's how to get to them:

     1.    Navigate to the %systemroot%\Minidump folder.

     2.    Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.

     3.    Upload the zip containing the DMP files to Skydrive or a hosting site of your choice and paste in your reply.

    If you are going to use Skydrive but don't know how to upload to it, please visit the following:

    http://www.wikihow.com/Use-SkyDrive

    Please note that any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, by default will delete DMP files upon use.

    If your computer is not generating DMP files, please do the following:

    1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
    2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.
    3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

    1. Double check that the WERS is ENABLED:

    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

    If you cannot get into normal mode to do any of this, please do this via Safe Mode.

    Regards,

    Patrick

    Was this answer helpful?

    0 comments No comments