KERNEL_MODE_EXCEPTION_NOT_HANDLED

Got BSOD with this message. Bug check code: 0x1000008e

Will add the link of the minidump below file.
Also I tested it using boot from Hiren's cd: memtest86 +, video stress test - not mistakes.
So, what's the problem?

SGM

Often difficult to diagnose with a dmp because you can't spot trends or confirm the diagnosis.  This is the case here, it seems to be a hardware problem

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: material

Nom_image: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: SINGLE_BIT_CPU_CALL_ERROR

I ran Prime95 cpu test

Try this free stress test: http://www.mersenne.org/freesoft/


Prime95 Setup program;
-Extract the contents of the zip file into a directory of your choice
-Double-click on the executable file
-Select "all stress testing.
-Select the test of 'Blend '.  If you have already run MemTest overnight, you can run the test of "Small FFFS" instead.
"Number of threads of torture test run" must equal the number of processors multiplied by 2 (if you use hyperthreading).
The best way to do this is to go to the Manager of the tasks of the figure... The performance tab - and see the number of boxes that appear under the CPU usage history
Then run the test of 6 to 24 hours - or until you get errors [b](whichever comes first)
The selection of Test and the file stress.txt box describes the components that insists on the program.

Tags: Windows

Similar Questions

  • BSOD KERNEL_MODE_EXCEPTION_NOT_HANDLED on developers preview WIndows

    Original title: BSOD KERNEL_MODE_EXCEPTION_NOT_HANDLED
    Hello world.

    I have a problem with my copy of Windows Developer Preview.
    I get about 3 - 4 times on the day a Blue Screen Of Death with "BSOD KERNEL_MODE_EXCEPTION_NOT_HANDLED" whenever I wake the computer from sleep mode. It happened when I randomly wake press a key on my keyboard. I didn't try to wake up the power button, but I think that the problem is not resolved in this way.
    What should I do?
    Thanks in advance

    Hello

    As the question is about an excerpt from Windows developers, I would say that you post the question on the link provided below for assistance.
    http://social.msdn.Microsoft.com/forums/en-us/windowsdeveloperpreviewgeneral/threads

  • Error 0x0000008E (KERNEL_MODE_EXCEPTION_NOT_HANDLED) in the Windows XP machine code.

    Original title: KERNEL_MODE_EXCEPTION_NOT_HANDLED.

    Yes im receiving a blue error screen indicating the following:

    Mini033111 - 01.dmp 31/03/2011-14:10:42 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008E 0xc0000047 0x804fcf44 0xb84e7a24 0x00000000 Ntoskrnl.exe Ntoskrnl.exe + 25f44 NT kernel & system Microsoft® Windows® operating system Microsoft Corporation 5.1.2600.6055 (xpsp_sp3_gdr.101209 - 1647) 32 bit   C:\WINDOWS\Minidump\Mini033111-01.dmp 1 15 2600

    I havnt a clue what is causeing this help and all would be greatly appreciated

    Hello

    ·         You did it of any material changes or software on the computer before this problem?

    ·         Exactly when you receive this error message?

    You can follow this link and check if it helps.

    You receive a random "0x0000008E" error message on a blue screen in Windows XP

    Hope the helps of information.

    Please post back and we do know.

  • Error blue screen: STOP: 0x0000008E KERNEL_MODE_EXCEPTION_NOT_HANDLED

    original title: blue screen with the error: "STOP: 0x0000008E (0xC000001D, 0 x 82850572, 0x9E204038, 0x00000000)"»

    Hello everyone,

    It has been more than a week I tried to re - install my computer: ACER9802AWKMi after several months of support with blue screen apearing errors whenever there is more than one program open :-(
    So I started with a recovery disk, but the problem was still there.  The computer came with XP Home Edition and I got an upgrade to Vista (all original stuff) with all updates (SP1 and 2 and everything else updates)
    Now, every time I go on the internet: especially no problem, but if I want to play a game (online) full screen, after a few minutes:
    Yes: blue screen with messages such as
    STOP: 0X0000008E (0XC000001D, 0 X 82850572, 0X9E204038, 0X00000000)
    STOP: 0x0000007F (0x00000008, 0x8013F000, 0 x 00000000, 0 x 00000000) or
    PFN_LIST_CORRUPT or
    something with the memory of the BIOS (which I have to remove cache or mirror) witch I tried to do, but not found in the BIOS SetUp (when start PC press F2)

    Whenever I get another message :-(

    I tried with FixIt, fact CHKDSK - CHKDSK F + CHKDSK F R
    I have also run Everest to have all the necessary stuff... so if you need it...

    If anyone has a sollution, I would be very happy to hear it.

    TX much

    In the mean time brands more than 13,000,000 errors:(et toujours obtient plus élevé.)  Of course I'm not every minute in front of my screen (sometimes I work too: the job from 9 to 5, you know)

    Hi Sabine,.

    This means that the RAM is broken or damaged. If you receive error messages, you can stop the execution of memtest86 +.

    Ask someone who knew a little technical to open the laptop and check out how many RAM modules there. If it has a single module, buy a new RAM module.

    If she has more modules, remove other modules, so that you don't have 1 module of RAM left. Now run the test for each RAM module again (only install 1 module at the same time) to check if all are damaged or 1.

    If you have discovered how many RAM modules is broken, buy new RAM

    André

    "A programmer is just a tool that converts the caffeine in code" Deputy CLIP - http://www.winvistaside.de/

  • Error Stop: 0X0000008E (0XC0000005, 0X820371A7, 0X9F10E91C, 0 x 0000000).

    I have error Stop: 0X0000008E (0XC0000005, 0X820371A7, 0X9F10E91C, 0 x 0000000). I did the F9 Diagnostics and no error found. Also, I tried to remove the DVD and replace the video card, but no improvement. However, Windows starts normally in SafeMode only. Thanks for supporting.

    Product ID: 89578-OEM-7332157-00061

    Hello

    Specifying your version of Windows and other information would help help us to you.

    How to ask a question
    http://support.Microsoft.com/kb/555375

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

    Check this thread for more information using BlueScreenView, MyEventViewer and other methods
    to troubleshoot the BlueScreens - top 3 responses (+ 1 other).

    http://social.answers.Microsoft.com/forums/en-us/w7repair/thread/c675b7b8-795f-474d-a1c4-6b77b3fcd990

    We can analyze the minidumps if make you it available to the SkyDrive or another file
    sharing sites.

    ZIP or download the content of the C:\Windows\minidump

    Use SkyDrive to upload collected files.
    http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65

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

    BCCode: 8th 0x0000008E is the same as 0x1000008E

    Two main causes of these blue screen video drivers and BIOS - check with the system manufacturer
    Site for graphics (Video) card and BIOS, then on site of the manufacturer of the device for the last video. It may be
    other pilots to check there. Disable the installation of self as those who are older and if
    Updates Windows suggests a pilot just HIDE. Antivirus is another possibility.

    See the methods of update driver generic and verify the implementation of driver verifier in the next
    Message.

    BCCode: 8th 0x0000008E is the same as 0x1000008E

    Cause

    Bug KERNEL_MODE_EXCEPTION_NOT_HANDLED control is a very common bug control. To interpret it, you must identify which exception has been generated.

    Common exception codes are:

    • 0 x 80000002: STATUS_DATATYPE_MISALIGNMENT indicates that an unaligned data reference was encountered.

    • 0 x 80000003: STATUS_BREAKPOINT indicates that a breakpoint or ASSERTION was met when no kernel debugger was attached to the system.

    • 0xc0000005: STATUS_ACCESS_VIOLATION indicates that a memory access violation has occurred.

    Solve the problem

    If you do not have to debug this problem, you must use certain 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 cards.
    • Check with your hardware vendor for updates to the BIOS.
    • Disable the BIOS memory options such as implementing caching or shading.

    If you plan to debug this problem, you may find it difficult to get a stack trace. Parameter 2 (the address of the exception) should identify the driver or function that caused the problem.

    If you do not know the specific cause of the exception, consider the following:

    • Hardware incompatibility. Ensure that all new equipment installed is listed in the list of the products tested Microsoft Windows market.
    • Service driver or defective peripheral system. A chauffeur service or defective peripheral system could be responsible for this error. The hardware problems, such as BIOS incompatibilities, conflicts of memory and IRQ conflicts can also generate this error.

    If the verification of the message bug list a driver by name, disable or remove that driver. In addition, disable or remove drivers or services that have been recently added. If the error occurs during the startup sequence and the system partition is formatted with the NTFS file system, you may be able to use Safe Mode to rename or to delete the faulty driver. If the driver is used as part of the start-up procedure of the system 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 may be a third-party remote control program. If this software is installed, you can remove the system startup service using the recovery and then Console by removing the offending system service file.

    Check the system log in Event Viewer for additional error messages that might help identify the device or driver responsible for control of bug 0x1E. You can disable the cache in memory of the BIOS to try to resolve the error. You must also run the diagnostics of material, especially the scanner memory, which provides the manufacturer of the system. For more information about these procedures, see the manual of your computer.

    The error that generates this message may occur after the first reboot during Windows Setup, or after installation is complete. A possible cause of the error is lack of disk space for installation and the system BIOS incompatibilities. For any problems during the installation of Windows that are associated with lack of disk space, reduce the number of files on the hard disk drive target. Search and delete temporary files that you do not have to have, files hidden Internet, application backup files and files saved.chk, which contain fragments of files on disk scans. You can also use an another hard disk drive with more free space for the installation.

    You can solve the problems of BIOS by upgrading the version of the system BIOS

    BCCode: 8th 0x0000008E is the same as 0x1000008E<-- read="" this="">
    * 1151.html? order = date http://www.faultwire.com/solutions-fatal_error/kernel-mode-exception-not-HANDLED-0x0000008E-

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

    Look in the Event Viewer to see if something is reported on those.
    http://www.computerperformance.co.UK/Vista/vista_event_viewer.htm

    MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
    TIP - Options - Advanced filter allows you to see a period of time instead of the entire file.

    http://www.NirSoft.NET/utils/my_event_viewer.html

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

    Also this, so you can see the probable bluescreens.

    Windows Vista restarts automatically if your computer encounters an error that requires him to plant.
    http://www.winvistatips.com/disable-automatic-restart-T84.html

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

    Here are a few ways to possibly fix the blue screen issue. If you could give the blue screen
    info that would help. Such as ITC and 4 others entered at the bottom left. And all others
    error information such as codes of STOP and info like 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: 0 x 00000000 (oxoooooooo oxoooooooo oxoooooooo oxooooooooo)
    Tcpip.sys - address blocking 0 x 0 00000000 000000000 DateStamp 0 x 000000000

    It is an excellent tool for displaying the blue screen error information

    BlueScreenView scans all your minidump files created during 'blue screen of death '.
    hangs and displays information about all accidents of a table - free

    http://www.NirSoft.NET/utils/blue_screen_view.html

    BlueScreens many are caused by old or damaged, in particular the video drivers drivers however
    There are other causes.

    You can do mode if necessary safe or the Vista DVD command prompt or
    Options recovery if your system is installed by the manufacturer.

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

    You can try a system restore to a point before the problem started when one exists.

    How to do a system restore in Windows 7
    http://www.SevenForums.com/tutorials/700-system-restore.html

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

    Start - type this in the search box-> find COMMAND at the top and RIGHT CLICK – RUN AS ADMIN

    Enter this at the command prompt - sfc/scannow

    How to fix the system files of Windows 7 with the 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 cbs.log Windows Vista (and Windows 7)
    http://support.Microsoft.com/kb/928228

    The log can give you the answer if there is a corrupted driver. (Says not all possible
    driver problems).

    Also run CheckDisk, so we cannot exclude as much as possible of the corruption.

    How to run the check disk at startup in Windows 7
    http://www.SevenForums.com/tutorials/433-disk-check.html

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

    Often drivers up-to-date will help, usually video, sound, network card (NIC), WiFi, part 3
    keyboard and mouse, as well as of other major device drivers.

    Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
    http://pcsupport.about.com/od/driverssupport/HT/driverdlmfgr.htm

    Installation and update of drivers to 7
    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
    quit unexpectedly
    http://support.Microsoft.com/kb/958233

    Troubleshooting Vista Blue Screen, error of JUDGMENT (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, it may be necessary.

    Startup Options recovery or Windows 7 disk repair

    How to run a startup repair in Windows 7
    http://www.SevenForums.com/tutorials/681-startup-repair.html

    How to start on 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 installation to repair Windows 7
    http://www.SevenForums.com/tutorials/3413-repair-install.html

    I hope this helps.

    Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle="" -="" mark="" twain="" said="" it="">

  • Blue screen... STOP: 0x0000008E (0xC0000005, 0xBF8B6C11, 0xA9538368, 0x00000000) win32k.sys - address BF8B6C11 base address BF800000 DateStamp 4C7d06ce

    I have a Dimension 3000 bought in 2005, upgraded to 2 GB of RAM.

    I recently implemented almost from scratch, because Opera program and profile would be repeatedly corrupted, making me lose the email. (This reappeared even after reinstall opera clean, do not use old messages or other profile files). Therefore, I restored a backup of the C: partition Ghost (there are others for my data and downloads) I did shortly after the purchase, after which I had installed only Ghost and two games (I uninstalled the games). I installed SP3 and ran Microsoft Update. I was trying to reinstall other programs that I use now. It's Rhapsody; one of my kids 'synchronize' a player MP3 Sansa Fuze with Rhapsody.

    A few days ago when closing Internet Explorer, I got a message that should be closed and I could send a report to Microsoft. It is also used to happen before, from time to time.

    Then, more recently, when I closed Rhapsody, I got a blue screen with a message that there was a problem. He said I could try to change some settings in the BIOS. I remember what happens before I restored the ghost of 2005 BU. I looked in the BIOS and not able to find the parameters referred to in (something like memory cache). I wish it were possible to print these messages on a blue screen. I didn't copy the entire message, but I write these references:

    STOP: 0X0000008E (0XC0000005, 0XBF8B6C11, 0XA9538368, 0X00000000)

    Win32k.sys - address BF8B6C11 base address BF800000 DateStamp 4C7d06ce

    This means almost nothing to me. I hope that someone on the forum knows what this means and can suggest what could be the problem.

    So far, I have not had more wrong with Opera, so there may be two distinct problems. OTOH, I reinstalled only Opera on 10/12/10; I can still have problems with it.

    Hello

    Here is more information on the bug 0x8E control: http://support.microsoft.com/kb/945658/

    The 0x8E KERNEL_MODE_EXCEPTION_NOT_HANDLED can be caused by a faulty service/driver, damaged hard drive or defective display card not enough space, or memory, Hardware/software incompatibility and third-party remote control software. So to get started:

    1. test your memory. Run Memtest you can download from http://www.memtest.org/#downiso. Download the ZIP file, extract the ISO and write on CD. Once written to CD, boot your PC with the CD and run Memtest. Allow the test to run by at least 3 passes or until it gives errors. If you have more than 1 memory module, run the test on each module separately. Try running Memtest from a cold - start unplug your PC for an hour to cool down, then immediately run memtest again when you next turn on the. This way memtest will run when the memory is cool and after the 3rd pass when the memory is hottest.

    2. update your display driver. Reference Dell seems to have highlighted 3 different models of Dimension 3000 and so there is 3 different Intel display drivers. See if you can find an updated driver on the Intel Web site. If you use a graphics add-on card try to find an updated driver from the manufacturer's website. If you have any trouble finding a driver let us know what brand and model of graphics card you have.

    3. update the Rhapsody software. (I think it's the software you using http://www.rhapsody.com/-software ?). If it's Rhapsody software I think it seems to integrate into your Web browser and it's perhaps why Opera and now IE are mistakes? You can uninstall Rhapsody for a while just to see if it is the reason for your BSOD.

    4. when the 0x8E BSOD is caused by win32k.sys, yours, is it then possible, it is caused by control software remote third. It can include programs such as VNC, PCAnywhere, etc. of Teamviewer, RAdmin.  If you use one of these programs, uninstall it and see if the PC stops mistakes.

    5 run a scan on your hard drive. You can check your hard disk for errors by going toStart ->Run -> type chkdsk c: /r -> clickOk . When asked if you want to force a sayNodisassembly. When asked to plan the audit at the next startup, Yes. Reboot your PC to allow running chkdsk.

    Alternatively, you can run a diagnostic on your hard drive. This by downloading the diagnostic program from your hard disk manufacturer. A list of manufacturers and their diagnostic tools can be found here: http://www.tacktech.com/display.cfm?ttid=287. Once more, download the ZIP file, extract the ISO and write to CD. A time written on CD, boot your PC with the CD and run the test Advanced/extended.

    Also make sure you have enough hard disk space. It is always recommended, if possible, to have at least 15% of your free hard disk capacity.

    6. Finally, take a look in your event viewer when the BSOD for possible errors. You want to look especially in the system and Application logs (and maybe Internet Explorer connects). You can run Event Viewer by going toStart ->Run -> type eventvwr.msc -> pressOk -> event viewer screen opens. If there are errors listed in one of the newspapers type them in your next post if you are not right.

    Reading your post I see 3 specific issues, that you might want to focus:

    -The memory you added (run Memtest) and hard drive (run Chkdsk)

    -The Rhapsody program - try to update or uninstall.

    -The software was initially corrupted until you make the first image after the purchase. So you just ghost the problem on.

    I hope this helps. Good luck.

  • Vista windows desktop HP oxoooooo8E Stop

    my hp desktop computer always freezes last BSOD said STOP OXOOOOOO8E please help

    Hello

    Check with HP, their drivers support and documentation online and ask in the forums of HP on known issues.

    Support HP & drivers
    http://welcome.HP.com/country/us/en/support.html

    Contact HP
    http://welcome.HP.com/country/us/en/contact_us.html

    HP forums
    http://h30434.www3.HP.com/PSG/

    ========

    Check this thread for more information using BlueScreenView, MyEventViewer and other methods
    to troubleshoot the BlueScreens - top 3 responses (+ 1 other).

    http://social.answers.Microsoft.com/forums/en-us/vistarepair/thread/3deab2fa-4000-4136-8c78-a3d22b1db009

    We can analyze the minidumps if make you it available to the SkyDrive or another file
    sharing sites (such as MediaFire). If you have problems to download the copy of minidumps
    for the office or in the Documents folder and download them from there.

    ZIP or download the content of the C:\Windows\minidump

    Use SkyDrive to upload collected files
    http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65

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

    Two main causes of this blue screen video drivers and BIOS - check with the system manufacturer
    Site for graphics (Video) card and BIOS, then on site of the manufacturer of the device for the last video. It may be
    other pilots to check there. Disable the installation of self as those who are older and if
    Updates Windows suggests a pilot just HIDE. Antivirus is another possibility.

    See methods of update driver generic in the next message.

    BCCode: 8th 0x0000008E is the same as 0x1000008E

    Cause

    Bug KERNEL_MODE_EXCEPTION_NOT_HANDLED control is a very common bug control. To interpret it, you must identify which exception has been generated.

    Common exception codes are:

    • 0 x 80000002: STATUS_DATATYPE_MISALIGNMENT indicates that an unaligned data reference was encountered.

    • 0 x 80000003: STATUS_BREAKPOINT indicates that a breakpoint or ASSERTION was met when no kernel debugger was attached to the system.

    • 0xc0000005: STATUS_ACCESS_VIOLATION indicates that a memory access violation has occurred.

    Solve the problem

    If you do not have to debug this problem, you must use certain 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 cards.
    • Check with your hardware vendor for updates to the BIOS.
    • Disable the BIOS memory options such as implementing caching or shading.

    If you plan to debug this problem, you may find it difficult to get a stack trace. Parameter 2 (the address of the exception) should identify the driver or function that caused the problem.

    If you do not know the specific cause of the exception, consider the following:

    • Hardware incompatibility. Ensure that all new equipment installed is listed in the list of the products tested Microsoft Windows market.
    • Service driver or defective peripheral system. A chauffeur service or defective peripheral system could be responsible for this error. The hardware problems, such as BIOS incompatibilities, conflicts of memory and IRQ conflicts can also generate this error.

    If the verification of the message bug list a driver by name, disable or remove that driver. In addition, disable or remove drivers or services that have been recently added. If the error occurs during the startup sequence and the system partition is formatted with the NTFS file system, you may be able to use Safe Mode to rename or to delete the faulty driver. If the driver is used as part of the start-up procedure of the system 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 may be a third-party remote control program. If this software is installed, you can remove the system startup service using the recovery and then Console by removing the offending system service file.

    Check the system log in Event Viewer for additional error messages that might help identify the device or driver responsible for control of bug 0x1E. You can disable the cache in memory of the BIOS to try to resolve the error. You must also run the diagnostics of material, especially the scanner memory, which provides the manufacturer of the system. For more information about these procedures, see the manual of your computer.

    The error that generates this message may occur after the first reboot during Windows Setup, or after installation is complete. A possible cause of the error is lack of disk space for installation and the system BIOS incompatibilities. For any problems during the installation of Windows that are associated with lack of disk space, reduce the number of files on the hard disk drive target. Search and delete temporary files that you do not have to have, files hidden Internet, application backup files and files saved.chk, which contain fragments of files on disk scans. You can also use an another hard disk drive with more free space for the installation.

    You can solve the problems of BIOS by upgrading the version of the system BIOS

    BCCode: 8th 0x0000008E is the same as 0x1000008E<-- read="" this="">
    * 1151.html? order = date http://www.faultwire.com/solutions-fatal_error/kernel-mode-exception-not-HANDLED-0x0000008E-

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

    Look in the Event Viewer to see if something is reported on those.
    http://www.computerperformance.co.UK/Vista/vista_event_viewer.htm

    MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
    TIP - Options - Advanced filter allows you to see a period of time instead of the entire file.

    http://www.NirSoft.NET/utils/my_event_viewer.html

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

    Also this, so you can see the probable bluescreens. (If necessary)

    Windows Vista restarts automatically if your computer encounters an error that requires him to plant.
    http://www.winvistatips.com/disable-automatic-restart-T84.html

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

    It comes to my convenience store generic bluescreen:

    Here are a few ways to possibly fix the blue screen issue. If you could give the info to blue screen
    This would help. Such as ITC and 4 others entered at the bottom left. And another error
    information such as the STOP codes and info like 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: 0 x 00000000 (oxoooooooo oxoooooooo oxoooooooo oxooooooooo)
    Tcpip.sys - address blocking 0 x 0 00000000 000000000 DateStamp 0 x 000000000

    It is an excellent tool for displaying the blue screen error information

    BlueScreenView scans all your minidump files created during 'blue screen of death '.
    hangs and displays information about all accidents of a table - free
    http://www.NirSoft.NET/utils/blue_screen_view.html

    BlueScreens many are caused by old or damaged, in particular the video drivers drivers however
    There are other causes.

    You can do without if needed fail or the Vista DVD or recovery command prompt mode
    Options if your system was installed by the manufacturer.

    This tells you how to access the System Recovery Options and/or a Vista DVD
    http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

    You can try a system restore to a point before the problem started when one exists.

    How to make a Vista system restore
    http://www.Vistax64.com/tutorials/76905-System-Restore-how.html

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

    Start - type this into the search-> find COMMAND to top box and RIGHT CLICK-
    RUN AS ADMIN

    Enter this at the command prompt - sfc/scannow

    How to analyze the log file entries that the Microsoft Windows Resource Checker
    (SFC.exe) program generates in Windows Vista cbs.log
    http://support.Microsoft.com/kb/928228

    The log can give you the answer if there is a corrupted driver. (Says not all possible
    driver problems).

    Also run CheckDisk, so we cannot exclude as much as possible of the corruption.

    How to run the check disk at startup in Vista
    http://www.Vistax64.com/tutorials/67612-check-disk-Chkdsk.html

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

    Often drivers up-to-date will help, usually video, sound, network card (NIC), WiFi, part 3
    keyboard and mouse, as well as of other major device drivers.

    Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
    http://pcsupport.about.com/od/driverssupport/HT/driverdlmfgr.htm

    How to install a device driver in Vista Device Manager
    http://www.Vistax64.com/tutorials/193584-Device-Manager-install-driver.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
    quit unexpectedly
    http://support.Microsoft.com/kb/958233

    Troubleshooting, STOP error blue screen Vista
    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, it may be necessary.

    The Options or Vista recovery disk Startup Repair

    How to do a startup repair
    http://www.Vistax64.com/tutorials/91467-startup-repair.html

    This tells you how to access the System Recovery Options and/or a Vista DVD
    http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

    I hope this helps.

    Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle=""><- mark="" twain="" said="" it="">

  • Blue screen of death (Minidump) - several stop codes.

    Hello

    ==================================================
    Dump file: Mini101911 - 02.dmp
    Crash time: 2011-10-19 14:22:12
    Bug Check String: KERNEL_MODE_EXCEPTION_NOT_HANDLED
    Bug check code: 0x1000008e
    Parameter 1: 0xc0000005
    Parameter 2: 0xbf80124b
    Parameter 3: 0xba127a48
    Parameter 4: 0x00000000
    Caused by the driver: win32k.sys
    Caused by the address: win32k.sys + 124 b
    Description of the file: multi-user Win32 Driver
    Product name: Microsoft® Windows® Operating System
    Company: Microsoft Corporation
    File version: 5.1.2600.6149 (xpsp_sp3_gdr.110906 - 1620)
    Processor: 32-bit
    Plant address: win32k.sys + 124 b
    Stack address 1: win32k.sys + 831d0
    Stack address 2: win32k.sys + b8fa7
    Battery 3 address: win32k.sys + 1142
    Computer name:
    Full path: C:\windows\Minidump\Mini101911-02.dmp
    Number of processors: 2
    Main version: 15
    Minor Version: 2600
    Size of the dump file: 94 208
    ==================================================

    ==================================================
    Dump file: Mini101911 - 01.dmp
    Crash time: 19/10/2011-12:01:17
    Bug Check String: DRIVER_CORRUPTED_EXPOOL
    Bug check code: 0x100000c5
    Parameter 1: 0 x 00000004
    Parameter 2: 0x00000002
    Parameter 3: 0x00000001
    Parameter 4: 0x8054bfd2
    Caused by the driver: sr.sys
    Caused by the address: sr.sys + 4bbf
    Description of the file: System Restore filesystem filter driver
    Product name: Microsoft® Windows® Operating System
    Company: Microsoft Corporation
    File version: 5.1.2600.5512 (xpsp.080413 - 2108)
    Processor: 32-bit
    Plant address: ntoskrnl.exe + 74fd2
    Stack address 1: ntoskrnl.exe + 19eb1
    Stack address 2: ntoskrnl.exe + aca58
    Battery 3 address: ntoskrnl.exe + e44aa
    Computer name:
    Full path: C:\windows\Minidump\Mini101911-01.dmp
    Number of processors: 2
    Main version: 15
    Minor Version: 2600
    Size of the dump file: 94 208
    ==================================================

    ==================================================
    Dump file: Mini101811 - 02.dmp
    Crash time: 2011-10-18 12:45:15
    Bug Check String: DRIVER_CORRUPTED_EXPOOL
    Bug check code: 0x100000c5
    Parameter 1: 0x00076e14
    Parameter 2: 0x00000002
    Parameter 3: 0x00000001
    Parameter 4: 0x8054bfd2
    Caused by the driver: Ntfs.sys
    Caused by the address: Ntfs.sys + 575 b
    Description of the file: NT File System Driver
    Product name: Microsoft® Windows® Operating System
    Company: Microsoft Corporation
    File version: 5.1.2600.5512 (xpsp.080413 - 2111)
    Processor: 32-bit
    Plant address: ntoskrnl.exe + 74fd2
    Stack address 1: ntoskrnl.exe + 19eb1
    Stack address 2: ntoskrnl.exe + aca58
    Battery 3 address: ntoskrnl.exe + e44aa
    Computer name:
    Full path: C:\windows\Minidump\Mini101811-02.dmp
    Number of processors: 2
    Main version: 15
    Minor Version: 2600
    Size of the dump file: 94 208
    ==================================================

    ==================================================
    Dump file: Mini101811 - 01.dmp
    Crash time: 2011-10-18 12:23:39
    Bug Check String: IRQL_NOT_LESS_OR_EQUAL
    Bug check code: 0x1000000a
    Parameter 1: 0x005c003a
    Parameter 2: 0x0000001c
    Parameter 3: 0x00000001
    Parameter 4: 0x80502cd6
    Caused by the driver: ntoskrnl.exe
    Caused by the address: ntoskrnl.exe + 2bcd6
    File description: NT kernel & system
    Product name: Microsoft® Windows® Operating System
    Company: Microsoft Corporation
    File version: 5.1.2600.6055 (xpsp_sp3_gdr.101209 - 1647)
    Processor: 32-bit
    Plant address: ntoskrnl.exe + 2bcd6
    Stack address 1: ntoskrnl.exe + 2bf2f
    Stack address 2: ntoskrnl.exe + 230d9
    Battery 3 address: ntoskrnl.exe + 2316c
    Computer name:
    Full path: C:\windows\Minidump\Mini101811-01.dmp
    Number of processors: 2
    Main version: 15
    Minor Version: 2600
    Size of the dump file: 94 208
    ==================================================

    So, I'm wondering for corrupted files, I can just remove or repair? For example, I got a blue screen of death before, so I remove the source of the blue screen of death which is

    ==================================================
    Dump file: Mini070811 - 01.dmp
    Crash time: 08/07/2011-18:28:31
    Bug Check String: IRQL_NOT_LESS_OR_EQUAL
    Bug check code: 0x1000000a
    Parameter 1: 0 x 00000016
    Parameter 2: 0x0000001c
    Parameter 3: 0x00000000
    Parameter 4: 0x80502eb4
    Caused by the driver: adasprot32.sys
    Caused by the address: adasprot32.sys + 1440
    Description of the file:
    Product name:
    Company:
    Version of the file:
    Processor: 32-bit
    Plant address: ntoskrnl.exe + 2beb4
    Stack address 1: ntoskrnl.exe + 2329e
    Stack address 2: adasprot32.sys + b31
    Battery 3 address: ntoskrnl.exe + 1819f
    Computer name:
    Full path: C:\WINDOWS\Minidump\Mini070811-01.dmp
    Number of processors: 2
    Main version: 15
    Minor Version: 2600
    Size of the dump file: 94 208
    ==================================================

    This is an example for you to understand the process. The essential 'Address', what is more important than 'address crash' and ' address 1-3' of the battery. I delete the corrupt of this show. So I wonder is that files that are displayed as blue screen of death appear as new files or has been corrupted (not new, but the changes) so that files is important, it is not good to remove it but just fix it? In this case, it is program file, so that files can be removed, but for above I'll list five blue screen of death (at the top of this page and recently), is files computer, more important than the program files. So I can delete files, but it would affect the entire computer? Or fix it? Another thing that is feature computer sank black and can't restart for some time. Thus, the program can cause corrupted files or delete files that is corrupt to become new and separate, which means that it can be? Are there two types of files? SE do not become like nine files can you repair files, but changes or files that become like new but bad files, it can therefore be removed. Thus, since the site Web who say it is the right program or files, but it is good to scan files that can cause of spyware, malware, virus or a program? So, do you know what could be cause of the last blue screen of death to connect to black on computer screen. It's as if I hard harddirve, but this isn't like that. This is exactly the same process of result with old hard drive causing the computer screen black, but this case is different departure process. If you tell me to use the cd, to solve the problem, tell me what cd and if it is a restore cd that say recovery on the cd for xp or more. It is large and clear a word that mean the recovery? If this is the case, I don't have it. Well, don't have no possible, but in case I did not.

    Hello Khalif Foster,

    It may be a problem with the Table of master files on the hard drive that does not, however, another option is to use the tool in the mentionted Knowledge Base article.

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

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

    To verify exactly which driver may be the cause of this problem. (if you don't believe the issue is the hard drive).

    Hope this information helps.

  • That means the closing blue screen problem down in WinXP? DMP attached.

    Received the blue screen error and need help to interpret .dmp file. Having read the advice here and don't understand the error.

    DMP link here. Can someone please help?
    https://SkyDrive.live.com/redir.aspx?CID=5de3dc24cafcbc7c&RESID=5DE3DC24CAFCBC7C! 136 & authkey = TPC026azOCU % 24

    The dump file suggests that Hitman Pro is the culprit.  They just released a new version last week.

    Here's what the dump file has to say:

    ==================================================
    Dump file: Mini100311 - 01.dmp
    Crash time: 03/10/2011 15:38:19
    Bug Check String: KERNEL_MODE_EXCEPTION_NOT_HANDLED
    Bug check code: 0x1000008e
    Parameter 1: 0xc0000005
    Parameter 2: 0x806048f9
    Parameter 3: 0xa6d6baf0
    Parameter 4: 0x00000000
    Caused by the driver: hitmanpro35.sys
    Caused by the address: hitmanpro35.sys + 1ab5
    Description of the file:
    Product name:
    Company:
    Version of the file:
    Processor: 32-bit
    Computer name:
    Full path: C:\WINDOWS\Minidump\Mini100311-01.dmp
    Number of processors: 1
    Main version: 15
    Minor Version: 2600
    Size of the dump file: 65 536
    ==================================================

    You only install only recently?  You can uninstall, reboot and see what things look like.  If things look better without it, you can be sure that you use the latest version.

    I used BlueScreenView to interpret the dump file and so you can next time.

    Download BlueScreenView here:
    Unzip it and run it (BSV installs nothing) and let him complete the digitization of all your crash dump files.
    If you double-click on depressed, you will get information on it (including the field caused by the driver) and you should be able to spot the problem right away - especially if you see a model in landfills where Caused by field pilot is the same (beginning with this driver).
    BlueScreenView tries to find the right driver or module that caused the blue screen by looking inside the stack of the accident. However, be aware that the driver detection mechanism is not 100% reliable, and you should also look in the lower pane, that display all drivers/modules found in the stack.
    Select (highlight) one or more of the most recent dump files by clicking on them and hold down the CTRL key to select multiple files.  Try to select only the most recent links that relate to your problem (perhaps five or six to start dump files).
    Click on file, save selected items and save information from the dumps to a text file on your desktop called BSOD.txt.

    Open BSOD.txt with a text editor, copy the text and paste it in your next reply.

    You can always put stuff on your SkyDrive of course if you need another set of eyeballs - BSV is not perfect - sometimes you have to dig deep with the windows debugging tools.

  • BSoD after updating drivers

    Mini092811 - 07.dmp 28/09/2011-14:59:23 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xe0000001 0xb83d8925 0xb2c30e9c watchdog.sys 0 x 00000000 watchdog.sys + 925 Watchdog Driver Microsoft® Windows® operating system Microsoft Corporation 5.1.2600.5512 (xpsp.080413 - 2108) 32-bit watchdog.sys + C:\WINDOWS\Minidump\Mini092811-07.dmp 2 15 2600 94 208 925

    Mini092811 - 06.dmp 28/09/2011-14:40:10 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0xbd09b7f0 0xb2678bb8 0 x 00000000 nv4_disp.dll nv4_disp.dll + 897f0 NVIDIA Windows XP Display driver, Version 280.26 NVIDIA Windows XP Display driver, Version 280.26 NVIDIA Corporation 6.14.12.8026 32-bit nv4_disp.dll + 897f0 C:\WINDOWS\Minidump\Mini092811-06.dmp 2 15 2600 94 208
    Previous error DIRECTLY above was due to obsolete Nvidia drivers

    Current error must be due to defective drivers... Please advise on what could be the problem, because I always get the BSoD when I watch Youtube videos.

    SPEX system: Microsoft Windows XP... SP3... /4gig 1.80 GHz RAM Dual Core 4300 / PCI Geforce 8500GT Graphix

    Hello Vic_007,

    If this started after updating Nvidia drivers, you can reinstall the previous drivers series that you were using for the moment, keep an eye on new Nvidia drivers in the meantime.

    Also, can you zip the contents of the C:\windows\minidumps folder and post it in a public folder on http://skydrive.live.com?

    After that, post the link on this thread so that we can look at landfills.

    Best regards

    Matthew_Ha

  • Dimension E521 win xp; stop: 0x1000008e (0xc0000005 0xf757bc21 0xb85dfbb0 0x00000000)

    My original/factory disk hard get burn, gone, finito, died on my, so I I buy all new hard drive, loaded with every drive him come with the pc, everything was looking fine until the blue screen appears.
    and now, at this point one haven't a clue what driver do that!
    so far I did step by step each unique method the I get this forum and because of that I'm updating some of the drivers, but UNFORTUNATELY I still have the blue screen!
    In the lines below, you will find all the accidents I n up to now, I hope that someone my give some news of how to solve this problem. :

    Mini082911 - 01.dmp KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0xf757bc21 0xb85dfbb0 29/08/2011-21:33:12 0 x 00000000 stdriver32.sys stdriver32.sys + 4c21 stdriver.sys stdriver.sys NCH Software 1.13:14:30:54 32-bit stdriver32.sys + 4c21 stdriver32.sys + 1815 stdriver32.sys + 680b ntoskrnl.exe + 1819f C:\WINDOWS\Minidump\Mini082911-01.dmp 2 15 2600 90 112
    Mini082711 - 07.dmp 27/08/2011 19:08:03 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0xf752bc21 0xb8137bb0 0 x 00000000 stdriver32.sys stdriver32.sys + 4c21 stdriver.sys stdriver.sys NCH Software 1.13:14:30:54 32-bit stdriver32.sys + 4c21 stdriver32.sys + 1815 stdriver32.sys + 680b ntoskrnl.exe + 1819f C:\WINDOWS\Minidump\Mini082711-07.dmp 2 15 2600 90 112
    Mini082711 - 06.dmp 27/08/2011-15:26:42 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0xf76ebc21 0xb8087bb0 0 x 00000000 stdriver32.sys stdriver32.sys + 4c21 stdriver.sys stdriver.sys NCH Software 1.13:14:30:54 32-bit stdriver32.sys + 4c21 stdriver32.sys + 1815 stdriver32.sys + 680b ntoskrnl.exe + 1819f C:\WINDOWS\Minidump\Mini082711-06.dmp 2 15 2600 90 112
    Mini082711 - 05.dmp 27/08/2011-13:55:40 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0xf76ebc21 0xb785ebb0 0 x 00000000 stdriver32.sys stdriver32.sys + 4c21 stdriver.sys stdriver.sys NCH Software 1.13:14:30:54 32-bit stdriver32.sys + 4c21 stdriver32.sys + 1815 stdriver32.sys + 680b ntoskrnl.exe + 1819f C:\WINDOWS\Minidump\Mini082711-05.dmp 2 15 2600 90 112
    Mini082711 - 04.dmp 27/08/2011-13:39:31 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0xf76fbc21 0xb7b1ebb0 0 x 00000000 stdriver32.sys stdriver32.sys + 4c21 stdriver.sys stdriver.sys NCH Software 1.13:14:30:54 32-bit stdriver32.sys + 4c21 stdriver32.sys + 1815 stdriver32.sys + 680b ntoskrnl.exe + 1819f C:\WINDOWS\Minidump\Mini082711-04.dmp 2 15 2600 90 112
    Mini082711 - 03.dmp 27/08/2011-12:43:56 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0xf7528fc6 0xb877f570 0 x 00000000 stdriver32.sys stdriver32.sys + 1fc6 stdriver.sys stdriver.sys NCH Software 1.13:14:30:54 32-bit stdriver32.sys + 1fc6 stdriver32.sys + 6767 ntoskrnl.exe + 1819f sysaudio.sys + 2c75 C:\WINDOWS\Minidump\Mini082711-03.dmp 2 15 2600 90 112
    Mini082711 - 02.dmp 27/08/2011-12:30:51 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0xf752bc21 0xb8607bb0 0 x 00000000 stdriver32.sys stdriver32.sys + 4c21 stdriver.sys stdriver.sys NCH Software 1.13:14:30:54 32-bit stdriver32.sys + 4c21 stdriver32.sys + 1815 stdriver32.sys + 680b ntoskrnl.exe + 1819f C:\WINDOWS\Minidump\Mini082711-02.dmp 2 15 2600 90 112
    Mini082711 - 01.dmp 27/08/2011 11:59:56 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0xf7598fc6 0xf7686570 0 x 00000000 stdriver32.sys stdriver32.sys + 1fc6 stdriver.sys stdriver.sys NCH Software 1.13:14:30:54 32-bit stdriver32.sys + 1fc6 stdriver32.sys + 6767 ntoskrnl.exe + 1819f sysaudio.sys + 2c75 C:\WINDOWS\Minidump\Mini082711-01.dmp 2 15 2600 90 112
    Mini082611 - 02.dmp 27/08/2011-01:51:14 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0xf751bc21 0xb79e6bb0 0 x 00000000 stdriver32.sys stdriver32.sys + 4c21 stdriver.sys stdriver.sys NCH Software 1.13:14:30:54 32-bit stdriver32.sys + 4c21 stdriver32.sys + 1815 stdriver32.sys + 680b ntoskrnl.exe + 1819f C:\WINDOWS\Minidump\Mini082611-02.dmp 2 15 2600 90 112
    Mini082611 - 01.dmp 2011-08-26 18:26:50 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0xf76fbc21 0xf6254bb0 0 x 00000000 stdriver32.sys stdriver32.sys + 4c21 stdriver.sys stdriver.sys NCH Software 1.13:14:30:54 32-bit stdriver32.sys + 4c21 stdriver32.sys + 1815 stdriver32.sys + 680b ntoskrnl.exe + 1819f C:\WINDOWS\Minidump\Mini082611-01.dmp 2 15 2600 90 112
    Mini080711 - 01.dmp 08-07-2011 19:24:55 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0xf7518fc6 0xb6e448ac 0 x 00000000 stdriver32.sys stdriver32.sys + 1fc6 stdriver.sys stdriver.sys NCH Software 1.13:14:30:54 32-bit stdriver32.sys + 1fc6 stdriver32.sys + 6767 ntoskrnl.exe + 1819f sysaudio.sys + 218th C:\WINDOWS\Minidump\Mini080711-01.dmp 2 15 2600 90 112
    Mini080611 - 06.dmp 06/08/2011-18:34:31 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0xf76f8fc6 0xb726c570 0 x 00000000 stdriver32.sys stdriver32.sys + 1fc6 stdriver.sys stdriver.sys NCH Software 1.13:14:30:54 32-bit stdriver32.sys + 1fc6 stdriver32.sys + 6767 ntoskrnl.exe + 1819f sysaudio.sys + 2c75 C:\WINDOWS\Minidump\Mini080611-06.dmp 2 15 2600 90 112
    Mini080611 - 05.dmp 06/08/2011-14:21:41 UNEXPECTED_KERNEL_MODE_TRAP 0x0000000d 0x1000007f 0x00000000 0x00000000 0 x 00000000 stdriver32.sys stdriver32.sys + 4c21 stdriver.sys stdriver.sys NCH Software 1.13:14:30:54 32-bit stdriver32.sys + 4c21 stdriver32.sys + 1815 stdriver32.sys + 680b ntoskrnl.exe + 1819f C:\WINDOWS\Minidump\Mini080611-05.dmp 2 15 2600 90 112
    Mini080611 - 04.dmp 06/08/2011-13:21:20 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0xf750bc21 0xb9ad6bb0 0 x 00000000 stdriver32.sys stdriver32.sys + 4c21 stdriver.sys stdriver.sys NCH Software 1.13:14:30:54 32-bit stdriver32.sys + 4c21 stdriver32.sys + 1815 stdriver32.sys + 680b ntoskrnl.exe + 1819f C:\WINDOWS\Minidump\Mini080611-04.dmp 2 15 2600 90 112
    Mini080611 - 03.dmp 06/08/2011-12:49:28 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0xf751bc21 0xb9a66bb0 0 x 00000000 stdriver32.sys stdriver32.sys + 4c21 stdriver.sys stdriver.sys NCH Software 1.13:14:30:54 32-bit stdriver32.sys + 4c21 stdriver32.sys + 1815 stdriver32.sys + 680b ntoskrnl.exe + 1819f C:\WINDOWS\Minidump\Mini080611-03.dmp 2 15 2600 90 112
    Mini080611 - 02.dmp 06/08/2011-12:38:58 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0xf7518fc6 0xb9626570 0 x 00000000 stdriver32.sys stdriver32.sys + 1fc6 stdriver.sys stdriver.sys NCH Software 1.13:14:30:54 32-bit stdriver32.sys + 1fc6 stdriver32.sys + 6767 ntoskrnl.exe + 1819f sysaudio.sys + 2c75 C:\WINDOWS\Minidump\Mini080611-02.dmp 2 15 2600 90 112
    Mini080611 - 01.dmp KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0xf751bc21 0xb9aaebb0 06/08/2011-12:02:22 0 x 00000000 stdriver32.sys stdriver32.sys + 4c21 stdriver.sys stdriver.sys NCH Software 1.13:14:30:54 32-bit stdriver32.sys + 4c21 stdriver32.sys + 1815 stdriver32.sys + 680b ntoskrnl.exe + 1819f C:\WINDOWS\Minidump\Mini080611-01.dmp 2 15 2600 90 112
    Mini080511 - 01.dmp 06/08/2011-12:45:58 AM KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0xf753bc21 0xb975ebb0 0 x 00000000 stdriver32.sys stdriver32.sys + 4c21 stdriver.sys stdriver.sys NCH Software 1.13:14:30:54 32-bit stdriver32.sys + 4c21 stdriver32.sys + 1815 stdriver32.sys + 680b ntoskrnl.exe + 1819f C:\WINDOWS\Minidump\Mini080511-01.dmp 2 15 2600 90 112

    System: Microsoft Windows XP
    Media center Edition
    Version 2002
    Service Pack 3
    Computer: AMD Athlon (TM) 64 x 2 Dual
    Processor Core 3800 +.
    2.00 GHz, 1.00 GB of RAM
    Physical address extension

    P.D. Not to mention that I need to "restore point", or something like that, remember, «MY FACTORY HARD DRIVE IS GONE»
    Thank you.

    Hello

    1. when exactly you get the blue screen error?

    2 have you tried the steps by Joel S?

    3. are you able to boot to the desktop with success?

    4. the problem persists in safe mode?

    Read the following article which is useful.

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

  • Displaying the right information to get a BSOD error help

    When your computer crashes and displays a blue screen there are often very valuable information about the photo that will allow users to help you solve your problem and to know what is causing this blue screen appears.

    Looking at the image at the end of the article you will see two sections highlighted, you will always want to post this information in your forum thread when looking for help she will be the most critical part of troubleshooting. The top tells us what's happening and said background where it goes to. We have just responded to two of the most important issues when you try to solve a problem.

    What's not?

    Where is the problem isolated to?

    Most of the text is quite annoying, but if that's important to you then it may be important for us. We have all seen what looks like a BSOD, but we do not know what your BSOD.

    There are more important questions that you can answer that will help your troubleshoot BSOD error message.

    1. What is your system brand and model? We know that you have an HP computer, but there are tons of computers. We need to know your specific model to ensure you use the appropriate drivers and we recommend the proper drivers.
    2. What is your version of Windows and the Service pack?
    3. Are you running a 64 bit or 32 bit OS?
    4. What is your Internet browser and version?
    5. Does your system use IDE or SATA disk drives?
    6. What virus protection software and current malicious software do you use? Is up to date?
    7. The issue occurred after an interruption of the power supply as an abnormal termination or power failure?
    8. What has changed recently?
    9. Does this happen often you can effectively reproduce the problem? If you can easily reproduce what steps can you take to reproduce the problem.

    Here is a list of the most common mistakes of the BSOD you can see

    • Stop 0 x 00000003 UNSYNCHRONIZED_ACCESS
    • Stop 0x0000000A IRQL_NOT_LESS_OR_EQUAL
    • Stop 0x0000001E KMODE_EXCEPTION_NOT_HANDLED
    • Stop 0 x 00000023 FAT_FILE_SYSTEM
    • Stop 0 x 00000024 NTFS_FILE_SYSTEM
    • Stop 0x0000002E DATA_BUS_ERROR
    • Stop 0x0000003F NO_MORE_SYSTEM_PTES
    • Stop 0 x 00000044 MULTIPLE_IRP_COMPLETE_REQUESTS
    • Stop 0 x 00000050 PAGE_FAULT_IN_NONPAGED_AREA
    • Stop 0x0000006B PROCESS1_INITIALIZATION_FAILED
    • Stop 0 x 00000073 CONFIG_LIST_FAILED
    • Stop 0 x 00000074 BAD_SYSTEM_CONFIG_INFO
    • Stop 0 x 00000076 PROCESS_HAS_LOCKED_PAGES
    • Stop 0 x 00000077 KERNEL_STACK_INPAGE_ERROR
    • Stop 0 × 00000079 MISMATCHED_HAL
    • Stop 0x0000007A KERNEL_DATA_INPAGE_ERROR
    • STOP 0x0000007B INACCESSIBLE_BOOT_DEVICE
    • Stop 0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    • Stop 0x0000007F UNEXPECTED_KERNEL_MODE_TRAP
    • Stop 0x0000008E KERNEL_MODE_EXCEPTION_NOT_HANDLED
    • Stop 0x0000009C MACHINE_CHECK_EXCEPTION
    • STOP 0x0000009F DRIVER_POWER_STATE_FAILURE
    • Stop 0x000000BE ATTEMPTED_WRITE_TO_READONLY_MEMORY
    • Stop 0x000000C2 BAD_POOL_CALLER
    • Stop DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000C4
    • Stop 0x000000CA PNP_DETECTED_FATAL_ERROR
    • Stop 0x000000CB DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
    • Stop 0x000000CE DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
    • STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
    • Stop 0x000000D5 DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
    • Stop 0x000000D8 DRIVER_USED_EXCESSIVE_PTES
    • Stop 0x000000DA SYSTEM_PTE_MISUSE
    • STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER
    • Stop 0x000000ED UNMOUNTABLE_BOOT_VOLUME
    • Stop 0x000000F2 HARDWARE_INTERRUPT_STORM
    • Stop 0x000000F4 CRITICAL_OBJECT_TERMINATION
    • Stop 0x000000FC ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
    • STOP 0x000000FE BUGCODE_USB_DRIVER
    • Stop 0xC0000218 UNKNOWN_HARD_ERROR
    • STOP 0xC000021A STATUS_SYSTEM_PROCESS_TERMINATED
    • Stop 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH
    • STOP 0xC0000244 STATUS_AUDIT_FAILED

    This thread is purely an informative thread. If you are experiencing a BSOD error please create a new thread ensure you provide information that questions on this thread.

    While many BSOD errors may be troubleshooting-made the same way, there is an amount of many of them and they should be troubleshoot-carried out on their own.

    If you have anything else you want to add or general BSOD issues then you can post them here, but if you ask about anything that requires real troubleshooting it should be in its own thread.

  • Blue screen error during games

    It has happened so far in the two games and is always at a precise moment of each game.here the minidump... I hope that someone can 'read' and help :)

    http://CID-af248a311624c723.Office.live.com/self.aspx/.public/minidump.rar

    According to landfills, the problem is you video display NVIDIA driver.

    Video drivers are the first thing to look at when you see a BSOD while playing games or other video intensive operations.

    As the forums MS Answers does not prompt for any information system when a new question is asked, I can't see exactly what you have now or tell you exactly what you need to do.

    I would like to start here:

    Browse the NVIDIA site and let scan them online take a look at your video system and see what he suggests for drivers and consider their analysis if they offer a new driver.

    It is recommended to run the scan NVIDIA with Internet Explorer.

    Here is the address of the NVIDIA page:

    http://www.nvidia.com/download/Prescan.aspx?lang=en-us

    Read the instructions, and then click the GRAPHICS DRIVERS button to start the scan.

    If following their indications do not straighten things, then follow these steps:

    Describe your current antivirus and software anti malware situation: McAfee, Norton, Spybot, AVG, Avira!, Defender, ZoneAlarm, PC Tools, MSE, Comodo, etc..
     
    Click Start, run and enter in the box:

    Msinfo32

    Click on OK and when the system info summary appears, click on Edition, select all, copy, and then paste the information here.

    For information about video drivers, expand components, click view, click on edit, select all, copy and then paste the information.

    This will minimize back Q & A and eliminate guesswork.

    If you have a desire, you can learn to interpret the crash dump files yourself.  It is not to intimidate with some of the tools out there on the wide Wide World of the Web.

    There are some third-party tools that are good to use for a first look, so do not waste time with all the tools of Windows if you are not interested by it.

    Here's how to watch terrils you have and you can see the cause of the accidents is the NVIDIA driver and your BSOD has this 'advice' on the BSOD page:

    STOP: 0X1000008E (0XC0000005, 0XBD0B2494, 0XB2F14860, 0X00000000)

    Nv4_disp.dll - address 0xbd0b2494 base at 0xbd012000 DateStamp 0x4d9e7d6e

    The nv4_disp.dll is your video driver.

    To see if for yourself, follow these steps:

    Download BlueScreenView here:
    Unzip it and run it (BSV installs nothing) and let him complete the digitization of all your crash dump files.
    If you double-click on depressed, you will get information on it (including the field caused by the driver) and you should be able to spot the problem right away - especially if you see a model in landfills where Caused by field pilot is the same (beginning with this driver).
    BlueScreenView tries to find the right driver or module that caused the blue screen by looking inside the stack of the accident. However, be aware that the driver detection mechanism is not 100% reliable, and you should also look in the lower pane, that display all drivers/modules found in the stack.

    Here's an example of your BSOD where Caused by field is the NVIDIA driver (the driver is an older version):

    ==================================================
    Dump file: Mini052211 - 01.dmp
    Crash time: 22/05/2011-22:35:59
    Bug Check String: KERNEL_MODE_EXCEPTION_NOT_HANDLED
    Bug check code: 0x1000008e
    Parameter 1: 0xc0000005
    Parameter 2: 0xbd0b2494
    Parameter 3: 0xb2f14860
    Parameter 4: 0x00000000
    Caused by the driver: nv4_disp.dll
    Caused by the address: nv4_disp.dll + a0494
    File description: NVIDIA Compatible Windows 2000, Version 186.34 display driver
    Product name: NVIDIA Compatible Windows 2000, Version 186.34 display driver
    Company: NVIDIA Corporation
    File version: 6.14.11.8634
    Processor: 32-bit
    Computer name:
    Full path: C:\WINDOWS\Minidump\Mini052211-01.dmp
    Number of processors: 2
    Main version: 15
    Minor Version: 2600
    Size of the dump file: 98 304
    ==================================================

  • Blue Screen - Stop 0x8E

    Hi, someone who can help me with the following BSOD:
    I've unlocked just my PC with the password field, and after 3-4 then got the BSOD. I use the docking station. My pc is DELL Latitude D630.
    Mini051311 - 01.dmp 13/05/2011 11:12
    KERNEL_MODE_EXCEPTION_NOT_HANDLED
    0x1000008E
    0xc0000005
    0xbf8768f0 0xa844ec04
    0x00000000
    Win32k.sys
    Win32k.sys + 768f0
    Multi-user Win32 Driver
    Microsoft® Windows® operating system
    Microsoft Corporation
    5.1.2600.6046 (xpsp_sp3_gdr.101026 - 1628)
    32 bit
    C:\WINDOWS\MiniDump\Mini051311-01.dmp
    2
    15
    2600
    90.112
    Thank you for your help.

    Hello Karlihnos,

    I agree with AirOnSkin in the fact that it is probably a scenario "wait and see".

    Because this machine is on a domain, you may want to go ahead and post this question on the TechNet forums if it bluescreens again.  They have the resources for troubleshooting of clients in the domain we have here.

    Their forums are at the following link:

    http://social.technet.Microsoft.com/forums/en-us/itproxpsp/threads

    Best regards

    Matthew_Ha

  • Blue Screen iastor.sys, STOP; 0x0000008E (0xC0000005, 0x828490B8, 0xB96DA758, 0x00000000)

    iastor.sys - address 828490B 8 physical memory base to @8280B 000, Date Stamp 48054343 - Crash Dump, dump - the disk of 100 I can work only in Mode without failure, but I can't print or scan that I need to do. Someone can help me.

    Hello

    Looks like you need to update iastor.sys:

    iastor.sys = Intel Matrix Storage Manager driver - see System/card mother Maker and manufacturer of chipset.
    This driver could perhaps was pushed to the fault by other programs such as Symantec/Norton.

    This driver is extremely difficult to install if you need system or the manufacturer of the motherboard (for custom
    bed systems) help but you could also ask on their forums (if any).

    Also check the Intel downloads audit AFTER with the system/motherboard manufacturer...

    Intel downloads
    http://Downloadcenter.Intel.com/

    Intel Matrix Storage Manager - do not forget to check DATE and set for the version of Windows and chipset
    http://Downloadcenter.Intel.com/SearchResult.aspx?lang=eng&keyword=%22matrix+Storage+Manager%22

    More help on installing iastor.sys here (System Maker/card mother Maker first consult and use that as a last resort).

    http://social.technet.Microsoft.com/forums/en-us/itprovistadeployment/thread/98f123d4-9190-4169-A376-7a0caf0ffb2a/

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

    More troubleshooting if necessary:

    Pick up the pieces after a computer crash
    http://Windows.Microsoft.com/en-us/Windows-Vista/picking-up-the-pieces-after-a-computer-crash

    Check this thread for more information using BlueScreenView, MyEventViewer and other methods
    to troubleshoot the BlueScreens - top 3 responses (+ 1 other).

    http://social.answers.Microsoft.com/forums/en-us/vistarepair/thread/3deab2fa-4000-4136-8c78-a3d22b1db009

    We can analyze the minidumps if make you it available to the SkyDrive or another file
    sharing sites (such as MediaFire). If you have problems to download the copy of minidumps
    for the office or in the Documents folder and download them from there.

    ZIP or download the content of the C:\Windows\minidump

    Use SkyDrive to upload collected files
    http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65

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

    Two main causes of this blue screen video drivers and BIOS - check with the system manufacturer
    Site for graphics (Video) card and BIOS, then on site of the manufacturer of the device for the last video. It may be
    other pilots to check there. Disable the installation of self as those who are older and if
    Updates Windows suggests a pilot just HIDE. Antivirus is another possibility.

    See methods of update driver generic in the next message.

    BCCode: 8th 0x0000008E is the same as 0x1000008E

    Cause

    Bug KERNEL_MODE_EXCEPTION_NOT_HANDLED control is a very common bug control. To interpret it, you must identify which exception has been generated.

    Common exception codes are:

    • 0 x 80000002: STATUS_DATATYPE_MISALIGNMENT indicates that an unaligned data reference was encountered.

    • 0 x 80000003: STATUS_BREAKPOINT indicates that a breakpoint or ASSERTION was met when no kernel debugger was attached to the system.

    • 0xc0000005: STATUS_ACCESS_VIOLATION indicates that a memory access violation has occurred.

    Solve the problem

    If you do not have to debug this problem, you must use certain 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 cards.
    • Check with your hardware vendor for updates to the BIOS.
    • Disable the BIOS memory options such as implementing caching or shading.

    If you plan to debug this problem, you may find it difficult to get a stack trace. Parameter 2 (the address of the exception) should identify the driver or function that caused the problem.

    If you do not know the specific cause of the exception, consider the following:

    • Hardware incompatibility. Ensure that all new equipment installed is listed in the list of the products tested Microsoft Windows market.
    • Service driver or defective peripheral system. A chauffeur service or defective peripheral system could be responsible for this error. The hardware problems, such as BIOS incompatibilities, conflicts of memory and IRQ conflicts can also generate this error.

    If the verification of the message bug list a driver by name, disable or remove that driver. In addition, disable or remove drivers or services that have been recently added. If the error occurs during the startup sequence and the system partition is formatted with the NTFS file system, you may be able to use Safe Mode to rename or to delete the faulty driver. If the driver is used as part of the start-up procedure of the system 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 may be a third-party remote control program. If this software is installed, you can remove the system startup service using the recovery and then Console by removing the offending system service file.

    Check the system log in Event Viewer for additional error messages that might help identify the device or driver responsible for control of bug 0x1E. You can disable the cache in memory of the BIOS to try to resolve the error. You must also run the diagnostics of material, especially the scanner memory, which provides the manufacturer of the system. For more information about these procedures, see the manual of your computer.

    The error that generates this message may occur after the first reboot during Windows Setup, or after installation is complete. A possible cause of the error is lack of disk space for installation and the system BIOS incompatibilities. For any problems during the installation of Windows that are associated with lack of disk space, reduce the number of files on the hard disk drive target. Search and delete temporary files that you do not have to have, files hidden Internet, application backup files and files saved.chk, which contain fragments of files on disk scans. You can also use an another hard disk drive with more free space for the installation.

    You can solve the problems of BIOS by upgrading the version of the system BIOS

    BCCode: 8th 0x0000008E is the same as 0x1000008E<-- read="" this="">
    * 1151.html? order = date http://www.faultwire.com/solutions-fatal_error/kernel-mode-exception-not-HANDLED-0x0000008E-

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

    Look in the Event Viewer to see if something is reported on those.
    http://www.computerperformance.co.UK/Vista/vista_event_viewer.htm

    MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
    TIP - Options - Advanced filter allows you to see a period of time instead of the entire file.

    http://www.NirSoft.NET/utils/my_event_viewer.html

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

    Also this, so you can see the probable bluescreens. (If necessary)

    Windows Vista restarts automatically if your computer encounters an error that requires him to plant.
    http://www.winvistatips.com/disable-automatic-restart-T84.html

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

    It comes to my convenience store generic bluescreen:

    Here are a few ways to possibly fix the blue screen issue. If you could give the info to blue screen
    This would help. Such as ITC and 4 others entered at the bottom left. And another error
    information such as the STOP codes and info like 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: 0 x 00000000 (oxoooooooo oxoooooooo oxoooooooo oxooooooooo)
    Tcpip.sys - address blocking 0 x 0 00000000 000000000 DateStamp 0 x 000000000

    It is an excellent tool for displaying the blue screen error information

    BlueScreenView scans all your minidump files created during 'blue screen of death '.
    hangs and displays information about all accidents of a table - free
    http://www.NirSoft.NET/utils/blue_screen_view.html

    BlueScreens many are caused by old or damaged, in particular the video drivers drivers however
    There are other causes.

    You can do without if needed fail or the Vista DVD or recovery command prompt mode
    Options if your system was installed by the manufacturer.

    This tells you how to access the System Recovery Options and/or a Vista DVD
    http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

    You can try a system restore to a point before the problem started when one exists.

    How to make a Vista system restore
    http://www.Vistax64.com/tutorials/76905-System-Restore-how.html

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

    Start - type this into the search-> find COMMAND to top box and RIGHT CLICK-
    RUN AS ADMIN

    Enter this at the command prompt - sfc/scannow

    How to analyze the log file entries that the Microsoft Windows Resource Checker
    (SFC.exe) program generates in Windows Vista cbs.log
    http://support.Microsoft.com/kb/928228

    The log can give you the answer if there is a corrupted driver. (Says not all possible
    driver problems).

    Also run CheckDisk, so we cannot exclude as much as possible of the corruption.

    How to run the check disk at startup in Vista
    http://www.Vistax64.com/tutorials/67612-check-disk-Chkdsk.html

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

    Often drivers up-to-date will help, usually video, sound, network card (NIC), WiFi, part 3
    keyboard and mouse, as well as of other major device drivers.

    Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
    http://pcsupport.about.com/od/driverssupport/HT/driverdlmfgr.htm

    How to install a device driver in Vista Device Manager
    http://www.Vistax64.com/tutorials/193584-Device-Manager-install-driver.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
    quit unexpectedly
    http://support.Microsoft.com/kb/958233

    Troubleshooting, STOP error blue screen Vista
    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, it may be necessary.

    The Options or Vista recovery disk Startup Repair

    How to do a startup repair
    http://www.Vistax64.com/tutorials/91467-startup-repair.html

    This tells you how to access the System Recovery Options and/or a Vista DVD
    http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

    I hope this helps.

    Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle=""><- mark="" twain="" said="" it="">

Maybe you are looking for