Stop error BCCode: 124

Similar Questions

• Blue screen error BCCode: 124.

  OT: How to fix the blue screen?

  Separated from this thread.

  How can I solve this blue screen?

  PC is 64-bit Win 7 Pro

  PC goes into about 3 - 4 times blue screen.

  Error logs:

  Problem signature: problem event name: BlueScreen OS Version:
  6.1.7601.2.1.0.768.3 locale ID: 1033 additional information about the problem:
  BCCode: 124 BCP1: 0000000000000000 BCP2: FFFFFA800365C038 BCP3: 00000000B 6000000
  BCP4: the Version of the OS 0000000000010015: 6_1_7601 Service Pack: 1_0 product: 768_1
  Files that help describe the problem: C:\Windows\Minidump\051215-14788-01.dmp
  C:\Users\John\AppData\Local\Temp\WER-30357-0.SysData.XML read our privacy
  online reporting:
  http://go.Microsoft.com/fwlink/?LinkId=104288 & clcid = 0 x 0409 if online
  Privacy statement is not available, please read our offline privacy statement:
  C:\Windows\system32\en-US\erofflps.txt---signature of the problem:
  Problem event name: BlueScreen OS Version: 6.1.7601.2.1.0.768.3 locale ID: 1033
  More information about the problem: BCCode: 124 BCP1: 0000000000000000
  BCP2: FFFFFA800369D038 BCP3: 00000000B 6000000 BCP4: 0000000000010015 OS Version:
  6_1_7601 Service Pack: 1_0

  We need the log files themselves (called a DMP files) because they contain the only record of the sequence of events that led to the accident, what drivers have been loaded, and what has been loaded.
  
  
  
  
  Please follow our instructions to find and download the files, we need to help you fix your computer. They can be found at here

  If you have any questions regarding the procedure, please ask
  
  

• What is the origin of Windows 7 BSOD BCCode: 124

  Hello

  I'm trying to understand what is the source of my BSOD. I had this problem for several weeks. It not always plant, but when that happens, it's usually after I shot recently on my computer. It shows the Blue error screen stop, try to restart it, shows a page of quick bios that is not the same one that shows at startup and then stops again. If I hit the power button it will usually be back on and start working a little bit. I've had the computer for about 2 years. I have the specs and details of the error below.

  Please let me know if I can post anything that might help.

  Thanks for your help!

  Update:
  Card mother-GA-Z77X-UD5H
  Corsair Vengeance 32 GB DDR3 1600
  EVGA GeForce GTX670 2048 MB
  Intel i7 - 3770 k Quad Core 3.5 GHz
  Western Digital Caviar Black 2 TB

  
  Windows 7 Blue Screen Of Death

  Signature of the problem:
  Problem event name: BlueScreen
  OS version: 6.1.7601.2.1.0.256.1
  More information about the problem:
  BCCode: 124
  BCP1: 0000000000000000
  BCP2: FFFFFA801EA3E028
  BCP3: 00000000B 2000000
  BCP4: 0000000081000402
  OS version: 6_1_7601
  Service Pack: 1_0

  TSM

  This is called BCC124 and is linked to the material.  Since Genuine Intel is referenced, I'd start by running a cpu stress 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.

  Stop 0 x 124 is a hardware error

  If you are overclocking try to reset your settings to standard processor and see if that helps.

  If you keep getting the BSOD here are things more than you may want.
  This is usually hardware related, defective heat, memory or processor even if it is "possible" he is associated (rare) driver.
  
  Stop 0 x 124 - what it means and what to try
  Synopsis:
  A "stop 0 x 124" is fundamentally different from many other types of bluescreens because it arises from a complaint of material.
  Stop 0 x 124 minidumps contain very little concrete information, and it is therefore necessary to address the problem as a case of material in an unknown state of distress.
  

  Generic troubleshooting ' Stop 0 x 124 ":

  1) to ensure that none of the hardware components are overclocked. Material which is pushed beyond its design specifications - by overclocking - may malfunction in unpredictable ways.
  (2) ensure that the machine is sufficiently cooled.
  If there is doubt, open the side of the case (be aware of all the relevant conditions guaranteed!) PC and direct an electric fan squarely to the motherboard. Who will rule on most cooling problems (lack of).
  3) update all drivers related to materials: video, sound, RAID (if applicable), NIC... anything that interacts with a piece of hardware.
  It is best to run the latest drivers anyway.
  (4) update the BIOS of your motherboard according to the manufacturer's instructions and clear CMOS.

  
  Their website should provide detailed instructions on the brand and model-specific procedure.
  (5) rarely, bugs in the operating system may cause "false positives" 0 x 124 events where the hardware wasn't complaining, but Windows thought otherwise (because of the bug).
  At the time of writing, Windows 7 does not have to suffer from a defect, but it is nevertheless important to keep Windows up-to-date.
  6) trying (stress) test these hardware components that can be put to the test artificially.
  The most obvious examples are the RAM and HDD (s).
  For the RAM, use the 3 rd-party memtest86 utility to run several hours a test value. (6-8 passes to stress the ram)
  For hard drives, verify if CHKDSK /R finds any problems on (s), including "bad sectors".
  Unreliable RAM, in particular, is mortal, as well as software, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result the diagnostic utilities does not guarantee that the RAM is free of any defect - only that none have been encountered during the test passes.
  7) as the last of the non-invasive troubleshooting steps, perform a "Vanilla" Windows reinstallation: just the OS itself without additional applications, games, utilities, updates, new drivers - or ANYTHING that does not come from the Windows 7 disc.
  Who stops working mitigate the problem of the 0 x 124, jump to the next step.
  If you run the "Vanilla" installation long enough to convince yourself that not a single 0 x 124 accident occurred, start installing applications and updates slowly, always stopping between successive additions long enough to get an idea of the question if the machine is still free of 0 x 124 breaks down.
  Smash back, obviously the latest addition of software may be somehow connected to the root cause.
  If the stop error 0 x 124 persist despite the above steps, and the equipment is under warranty, consider to go back and ask for a replacement that does not suffer periodic MCE events.
  Be aware that want to perform the subsequent hardware troubleshooting steps can, in some cases, void your warranty:
  (8) clean and carefully remove the dust inside the machine.
  Reinstall all memory modules and connectors.
  Use a can of compressed air to clean the RAM DIMM supports as much as possible.
  (9) If all else fails, start removing items of hardware one by one in the hope that the culprit is something non-essential that can be eliminated.
  Obviously, this type of testing is much easier if you have access to equivalent components in order to perform swaps.

  If you are in the situation to have completed all the steps above without a resolution of the symptom, unfortunately the most likely reason is that the error message is literally correct - something is fundamentally wrong with the hardware of the machine.

  
  
  More advanced reading can be found here from a MS MVP IT PRO
  http://captaindbg.com/bug-check-0x124-whea_uncorrectable_error-how-to-troubleshoot/

• BCCode: 124

  My computer has been restarted recently about once a week during the night when it is idling. I'll wake up and notice that it has restarted, at first I thought he was just updated. I know realize there is something wrong, however! I started playing Starcraft II: Heart of the swarm today and it stopped after the first game. Hoping that it was just a fluke I started my computer again and after the first game, the same thing, full stop. Except this time I was met with a message 'windows has recovered from an error' when I started upward. Here's the message as follows:

  Signature of the problem:

  Problem event name: BlueScreen

  OS version: 6.1.7601.2.1.0.256.1

  Locale ID: 1033

  More information about the problem:

  BCCode: 124

  BCP1: 0000000000000000

  BCP2: FFFFFA8002C52038

  BCP3: 0000000000000000

  BCP4: 0000000000000000

  OS version: 6_1_7601

  Service Pack: 1_0

  Product: 256_1

  Files helping to describe the problem:

  C:\Windows\Minidump\031213-21484-01.dmp

  C:\Users\Robert\AppData\Local\Temp\WER-133796-0.SysData.XML

  Read our privacy statement online:

  http://go.Microsoft.com/fwlink/?LinkId=104288&clcid=0x0409

  If the online privacy statement is not available, please read our offline privacy statement:

  C:\Windows\system32\en-US\erofflps.txt
  What should I do?
  Stop 0 x 124 is a hardware error
  If you are overclocking try to reset your settings to standard processor and see if that helps.
  If you keep getting the BSOD here are things more than you may want.
  This is usually hardware related, defective heat, memory or processor even if it is "possible" he is associated (rare) driver.
  
  Stop 0 x 124 - what it means and what to try
  Synopsis:
  A "stop 0 x 124" is fundamentally different from many other types of bluescreens because it arises from a complaint of material.
  Stop 0 x 124 minidumps contain very little concrete information, and it is therefore necessary to address the problem as a case of material in an unknown state of distress.
  

  Generic troubleshooting ' Stop 0 x 124 ":

  1) to ensure that none of the hardware components are overclocked. Material which is pushed beyond its design specifications - by overclocking - may malfunction in unpredictable ways.
  (2) ensure that the machine is sufficiently cooled.
  If there is doubt, open the side of the case (be aware of all the relevant conditions guaranteed!) PC and direct an electric fan squarely to the motherboard. Who will rule on most cooling problems (lack of).
  3) update all drivers related to materials: video, sound, RAID (if applicable), NIC... anything that interacts with a piece of hardware.
  It is best to run the latest drivers anyway.
  (4) update the BIOS of your motherboard according to the manufacturer's instructions.
  Their website should provide detailed instructions on the brand and model-specific procedure.
  (5) rarely, bugs in the operating system may cause "false positives" 0 x 124 events where the hardware wasn't complaining, but Windows thought otherwise (because of the bug).
  At the time of writing, Windows 7 does not have to suffer from a defect, but it is nevertheless important to keep Windows up-to-date.
  6) trying (stress) test these hardware components that can be put to the test artificially.
  The most obvious examples are the RAM and HDD (s).
  For the RAM, use diagnostics from built-in memory (run MDSCHED) or the utility memtest86 3rd - party to run plenty of evidence of hours of testing.
  For hard drives, verify if CHKDSK /R finds any problems on (s), including "bad sectors".

  
  Unreliable RAM, in particular, is mortal, as well as software, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result the diagnostic utilities does not guarantee that the RAM is free of any defect - only that none have been encountered during the test passes.
  7) as the last of the non-invasive troubleshooting steps, perform a "Vanilla" Windows reinstallation: just the OS itself without additional applications, games, utilities, updates, new drivers - or ANYTHING that does not come from the Windows 7 disc.
  Who stops working mitigate the problem of the 0 x 124, jump to the next step.
  If you run the "Vanilla" installation long enough to convince yourself that not a single 0 x 124 accident occurred, start installing applications and updates slowly, always stopping between successive additions long enough to get an idea of the question if the machine is still free of 0 x 124 breaks down.
  Smash back, obviously the latest addition of software may be somehow connected to the root cause.
  If the stop error 0 x 124 persist despite the above steps, and the equipment is under warranty, consider to go back and ask for a replacement that does not suffer periodic MCE events.
  Be aware that want to perform the subsequent hardware troubleshooting steps can, in some cases, void your warranty:
  (8) clean and carefully remove the dust inside the machine.
  Reinstall all memory modules and connectors.
  Use a can of compressed air to clean the RAM DIMM supports as much as possible.
  (9) If all else fails, start removing items of hardware one by one in the hope that the culprit is something non-essential that can be eliminated.
  Obviously, this type of testing is much easier if you have access to equivalent components in order to perform swaps.

  If you are in the situation to have completed all the steps above without a resolution of the symptom, unfortunately the most likely reason is that the error message is literally correct - something is fundamentally wrong with the hardware of the machine.

• I get an error with an error code 124 blue sreen.

  Original title: blue screen of death help

  I get the dreaded BSOD and I was wondering if anyone had any ideas what's happening?  This is a new installation on a new computer, Lenovo.

  I loaded my files of information system and dmp... http://sdrv.Ms/YjFbBk Can someone take a look?
  Thanks in advance

  Signature of the problem:

  Problem event name: BlueScreen

  OS version: 6.1.7601.2.1.0.768.3

  Locale ID: 1033

  More information about the problem:

  BCCode: 124

  BCP1: 0000000000000000

  BCP2: FFFFFA80065AF028

  BCP3: 00000000F6002000

  BCP4: 000000001D 000136

  OS version: 6_1_7601

  Service Pack: 1_0

  Product: 768_1

  Files helping to describe the problem:

  C:\Windows\Minidump\012113-12495-01.dmp

  C:\Users\Heath Stake\AppData\Local\Temp\WER-35599-0.sysdata.xml

  Read our privacy statement online:

  http://go.Microsoft.com/fwlink/?LinkId=104288&clcid=0x0409

  If the online privacy statement is not available, please read our offline privacy statement:

  C:\Windows\System32\en-US\erofflps.txt
  Stop 0 x 124 is a hardware error
  If you are overclocking try to reset your settings to standard processor and see if that helps.
  If you keep getting the BSOD here are things more than you may want.
  This is usually hardware related, defective heat, memory or processor even if it is "possible" he is associated (rare) driver.
  
  Stop 0 x 124 - what it means and what to try
  Synopsis:

  A "stop 0 x 124" is fundamentally different from many other types of bluescreens because it arises from a complaint of material.
  Stop 0 x 124 minidumps contain very little concrete information, and it is therefore necessary to address the problem as a case of material in an unknown state of distress.
  

  Generic troubleshooting ' Stop 0 x 124 ":

  1) to ensure that none of the hardware components are overclocked. Material which is pushed beyond its design specifications - by overclocking - may malfunction in unpredictable ways.

  (2) ensure that the machine is sufficiently cooled.
  If there is doubt, open the side of the case (be aware of all the relevant conditions guaranteed!) PC and direct an electric fan squarely to the motherboard. Who will rule on most cooling problems (lack of).

  3) update all drivers related to materials: video, sound, RAID (if applicable), NIC... anything that interacts with a piece of hardware.
  It is best to run the latest drivers anyway.

  (4) update the BIOS of your motherboard according to the manufacturer's instructions.
  Their website should provide detailed instructions on the brand and model-specific procedure.

  (5) rarely, bugs in the operating system may cause "false positives" 0 x 124 events where the hardware wasn't complaining, but Windows thought otherwise (because of the bug).
  At the time of writing, Windows 7 does not have to suffer from a defect, but it is nevertheless important to keep Windows up-to-date.

  6) trying (stress) test these hardware components that can be put to the test artificially.
  The most obvious examples are the RAM and HDD (s).
  For the RAM, use diagnostics from built-in memory (run MDSCHED) or the utility memtest86 3rd - party to run plenty of evidence of hours of testing.
  For hard drives, verify if CHKDSK /R finds any problems on (s), including "bad sectors".

  
  Unreliable RAM, in particular, is mortal, as well as software, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result the diagnostic utilities does not guarantee that the RAM is free of any defect - only that none have been encountered during the test passes.

  7) as the last of the non-invasive troubleshooting steps, perform a "Vanilla" Windows reinstallation: just the OS itself without additional applications, games, utilities, updates, new drivers - or ANYTHING that does not come from the Windows 7 disc.
  Who stops working mitigate the problem of the 0 x 124, jump to the next step.
  If you run the "Vanilla" installation long enough to convince yourself that not a single 0 x 124 accident occurred, start installing applications and updates slowly, always stopping between successive additions long enough to get an idea of the question if the machine is still free of 0 x 124 breaks down.
  Smash back, obviously the latest addition of software may be somehow connected to the root cause.
  If the stop error 0 x 124 persist despite the above steps, and the equipment is under warranty, consider to go back and ask for a replacement that does not suffer periodic MCE events.
  Be aware that want to perform the subsequent hardware troubleshooting steps can, in some cases, void your warranty:

  (8) clean and carefully remove the dust inside the machine.
  Reinstall all memory modules and connectors.
  Use a can of compressed air to clean the RAM DIMM supports as much as possible.

  (9) If all else fails, start removing items of hardware one by one in the hope that the culprit is something non-essential that can be eliminated.
  Obviously, this type of testing is much easier if you have access to equivalent components in order to perform swaps.

  If you are in the situation to have completed all the steps above without a resolution of the symptom, unfortunately the most likely reason is that the error message is literally correct - something is fundamentally wrong with the hardware of the machine.

• Computer freezes (no blue screen), but on reboot displays error code 124.

  More than 3 months my computer froze at random on 5 occasions, sometimes all this idle and sometimes browsing the internet.
  After reboot, windows tells me that he has recovered from an unexpected error.
  It's information:

  BCCode: 124
  BCP1: 0000000000000000
  BCP2: FFFFFA8007CD88F8
  BCP3: 0000000000000000
  BCP4: 0000000000000000
  OS version: 6_1_7601
  Service Pack: 1_0
  Product: 768_1

  I also downloaded the minidump file on my skydrive:

  https://SkyDrive.live.com/#CID=F3389EB25ED220A7

  No information about the cause of the problem would be highly appreciated.

  Thanks in advance,

  Elliot.

  Original title: Windows 7 freezes and the error code is: BCCode: 124

  There are two main problems. I am not sure of the third.

  Log name: System
  Source: Application Popup
  Date: 23/09/12 19:23:08
  Event ID: 1060
  Level: error
  Description:
  \SystemRoot\SysWow64\drivers\tandpl.sys has been blocked by a loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.

  It could be malicious.

  I recommend that you run Disk Cleanup or cCleaner to remove temporary files as this will reduce the time to scan security software.

  Start the computer in safe mode with network and download and install Malwarebytes (free version for individuals only), updated definitions and run in safe mode. Disable other security software while you do the analyses.

  http://www.computerhope.com/issues/chsafe.htm

  http://www.Malwarebytes.org/products/malwarebytes_free

  Download and run SuperAntiSpyware (Free Edition)
  http://www.SUPERAntiSpyware.com/download.html

  I suggest that we check if the two errors are still happening after that we dealt with the foregoing

  Log name: System
  Source: Service Control Manager
  Date: 23/09/12 19:23:15
  Event ID: 7000
  Level: error
  Description:
  The AODDriver4.1 service failed to start due to the following error:
  The system cannot find the specified file.

  Log name: System
  Source: bowser
  Date: 23/09/12 19:24:13
  Event ID: 8003
  Level: error
  Description:
  The master browser has received a server announcement from VICTORIA-PC computer that believes it is the master browser for the domain of transport NetBT_Tcpip_ {CB46FB47-59D5-4BC9-A10A-C4E6EC721082}. The master browser stops or an election is forced.
      \Device\LanmanDatagramReceiver
      VICTORIA-PC
      NetBT_Tcpip_ {CB46FB47-59D5-4BC9-A10A-C4E6EC721082}

• Windows XP Stop error, blue screen.

  Hello moderators,

  I am running Windows XP SP3. My Info system is as follows:-

  Name of the operating system Microsoft Windows XP Professional
  Version 5.1.2600 Service Pack 3 Build 2600
  Manufacturer of operating system Microsoft Corporation
  System name USER-364DED4B8D
  System manufacturer MSI
  System model MS-7597
  System Type X 86-based PC
  Processor x 86 family 16 model 5 Stepping 3 Mhz-AuthenticAMD ~ 3013
  BIOS Version/Date American Megatrends Inc. V10.2, 14/03/2011
  SMBIOS 2.5 version
  Windows C:\WINDOWS directory
  System directory C:\WINDOWS\system32
  Boot Device \Device\HarddiskVolume3
  The local United States
  Hardware Abstraction Layer Version = "5.1.2600.5512 (xpsp.080413 - 2111).
  User name USER-364DED4B8D\user
  HIS Western time zone standard time
  Total physical memory 096,00 MB 4
  2.28 GB available physical memory
  Total virtual memory 2.00 GB
  Available virtual memory 1.96 GB
  Page file space 4.81 GB
  Paging file C:\pagefile.sys

  I was playing music on Windows Media Player. Visualizations was running. When all of a sudden system crashed "Stop error". I restarted the system and received the error message. The details are as follows: -.

  BCCode: 1000008e BCP1:c0000005 BCP2: B3E96EZ56E25 BCP3: B27DE118 BCP4: 00000000

  BONE, 51_2600 SP3_0 worm produces 256_1

  I checked the system tools and looked into the system the only thing I could find was a warning that my web cam created an error about 2-3 days before today.

  A further check revealed that the webcam and its software was not spent by the Microsoft Logo and was therefore inconsistent to run under XP.

  I have experienced this type of problem before crash and recently did a clean install of the operating system. I'm afraid that if I folds music or run that DVD system stops again.

  What can I do to prevent it happening again.

  I will be grateful for any assistance to resolve the problem.

  Thanking you.

  standeb.

  http://xpdrivers.com/hardware/cameras/resolving-Webcam-driver-issues-for-Windows-XP/

  read this.

  If it corrects the problem return post, otherwise it would be logical to uninstall the software from your webcam and then see if the error occurs again all while listening to music and watching visualizations.

  post results back please.

• Screen blue - Stop error 0x8E

  Here is my blue screen error: BCCode: 1000008e BCP1: C0000005 BCP2: BF83D79B BCP3: B6DD0830 BCP4: 00000000 OSVer: 5_1_2600 SP: 3_0 product: 256_1
  It is an old Acer running Windows XP. I've recently updated the hard drive and video card (new G-Force, 512 MB DDR2 DVI TV 620). This replaced a G - force 4 MX4408X 64 MB DDR TV Out.  It wasn't great before the updates to work but works worse now.

  HAL

  These accidents were caused by the corruption of memory (probably a driver).  Run these two tests to check your memory and find which driver is causing the problem.

  If you are overclocking reset all default before running these tests.
  In other words STOP!

  1 - Memtest.

  * Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. "http://www.memtest.org/#downiso"] Memtest86 + - Advanced Memory Diagnostic tool

  * Boot from the CD and let it run at least 5 or 6 passes.

  Remember, anytime Memtest reports errors, it can be bad RAM or a bad motherboard slot.

  Test the sticks individually and if you find a good, test it in all slots.

  Any error is indicative of a memory problem.

  If a well-known stick fails in a slot of motherboard, it's probably the slot.

  http://www.SevenForums.com/tutorials/105647-RAM-test-Memtest86.html

  2. Driver Verifier

  Using Driver Verifier is a dubious proposition. Most of the time it will crash and it will tell you what is the driver. But sometimes it will crash and will not tell you the driver. Sometimes it will crash until you can connect to Windows. If you can't mode without failure, then you will have to resort to editing the registry offline to disable driver verifier.

  I suggest that you first back up your data and make sure you have access to another computer so you can contact us in case of problems. Then do a system restore point (so you can restore the system using the functionality of Vista/Win7 Startup Repair).

  In Windows 7, you can do a startup repair disk by clicking Start... All programs... Maintenance... Create a system - with Windows Vista repair disc, you need to use your drive installation or from the "Repair your computer" option at the top of the Safe Mode menu.

  So, here is the procedure:
  -Go to start and type "auditor" (without the quotes) and press enter
  -Select 'Create a custom settings (for code developers)' and click 'Next '.
  -Select "Select individual settings from the list complete" and click "Next".
  -Select the entire document except for "Low resource Simulation" and click "next".
  -Select "Select driver names from a list", then click "next".
  Select all drivers that are NOT provided by Microsoft, and then click "Next".
  -On the next page, select "Finish".

  Restart the system and wait as he crashed to blue screen. Continue to use your system normally and if you know what are the causes of the crash, do it several times. The objective here is to get the system crash because Driver Verifier is stressing out the drivers. If it is not planted for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

  If you are unable to Windows because it crashes too early, try safe mode.
  If you can't mode without fail, try to use the system from the installation DVD restore to bring the system back to the previous point of restoration that you created.
  http://www.SevenForums.com/tutorials/101379-Driver-Verifier-enable-disable.html

  Further reading
  "http://support.microsoft.com/kb/244617"] using Driver Verifier to identify issues with Windows drivers for users advanced

• Error BCCode: 1000008e and cannot print using Microsoft word or excel

  Original title: I have 2 questions.

  (1) error message (BCCode: 1000008e - BCp1:c000005 - BCP2:BF9472FD - BCP3:AB6A91D4 - BCP4:0000000 - OSVer:5_1_2600 - SP:3_0 - product: 256_1)?

  (2) I have HP LaserJet 6 L printer and it will print the test page put not print other pages to print such as word or Excel.... etc? Note that the test page didn't print that from the printer not your PC

  Hi TurmanTurman,

  1. Did you the latest changes on the computer?
  2. Exactly when you receive the error message? You are able to boot into Windows after the error message?
  3. You are able to print using WordPad or Notepad?
  4. What happens when you try to print using Microsoft word or excel?

  The stop error 0x0000008E occur mainly due to the following:

  • Drive hard damage
  • Problems of material General configuration with the BIOS, memory, hard drive, or with other devices
  • Incompatible device driver
  • Incompatible software

  Check out the articles below and try the steps mentioned, check if it helps.

  General troubleshooting for an error message that you receive randomly in Windows XP: "Stop 0x0000008E"

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

  You may receive an error message on a Windows-based computer: "STOP 0 x 00000050" or "STOP 0x0000008e"

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

  I suggest that you see if you can print using WordPad or Notepad on the computer.

  If you are unable to print only when you use the Microsoft office application then I suggest that you post your question in the forums of Microsoft Office.

  http://answers.Microsoft.com/en-us/Office/Forum

• HOW CAN I FIX A SCREEN BLUE, WITH STOP ERROR CODE: 0X0000007E (0XC0000005, 0X89F24OAE, 0X8A953BA0, 0X8A95389C)

  HOW CAN I FIX A SCREEN BLUE, WITH STOP ERROR CODE: 0X0000007E (0XC0000005, 0X89F24OAE, 0X8A953BA0, 0X8A95389C)

  Hello

  Please do not type in capital letters because it's difficult to read and considered to be shouting.

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

  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.

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

  Use SkyDrive download collected files and after shot/screenshot.
  http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65

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

  Also this, so you can see the probable bluescreens.

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

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

  The system has RAID? If so, it's also very suspicious.

  This error is usually a driver problem and display adapter (video) driver is the most suspicious if she
  may be others. Antivirus/antispyware/security programs, equipment (heat) and major software problems
  can also cause the error. When you get to the section of the driver to use the Troubleshoot utility my generic
  methods in the next message and then return to the if necessary troubleshooting tool.

  Have you recently added hardware or drivers updated? Don't forget to look in Control Panel - Windows
  Updates to see if all drivers have been updated it. Other donor opportunities include the antivirus/anti-
  spyware/security programs.

  When you get to the pilot and sections of the memory of the troubleshooter check the following message to
  update drivers and memory test and then return to the troubleshooter if necessary.

  BCCode: 7F 0x0000007E which is also 0x1000007E

  Cause

  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug control is a very common bug control. TO
  interpret, you must identify which exception has been generated.

  Common exception codes are:

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

  For a complete list of exception codes, see the Ntstatus.h file located in theinc directory
  the Microsoft Windows Driver Kit (WDK).

  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
  • Reference of 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) must identify the driver or function that caused the problem.

  If the exception code 0 x 80000003 occurs, a hard-coded breakpoint or assertion was hit, but the system
  has been launched with the /nodebug. switch. This problem should occur infrequently. If it occurs repeatedly,
  Make sure that a kernel debugger is connected and the system is booted with the Switch/DEBUG .

  In case of exception code 0 x 80000002, the trap frame provides additional information.

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

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

  If a driver is listed by name in the bug check message, disable or remove that driver. Disable
  or remove drivers or services that have been recently added. If the error occurs during 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 system startup procedure
  in Safe Mode, you must start the computer by using the Recovery Console to access the file.

  If the problem is associated with Win32k.sys, the source of the error may be a third remote
  control program. If this software is installed, you can remove the boot of the computer service
  by using the Recovery Console, and then 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 the driver that generated the bug check 0x7E.

  You can also disable memory cache BIOS may try to resolve the error. You should 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
  Once the installation is complete. A possible cause of the error is lack of disk space for installation and system
  BIOS incompatibilities. For problems during the installation of Windows that are associated with the absence of disc
  space, reduce the number of files on the disk drive hard target. Find and delete any temporary
  the files that you do not have to have files hidden Internet, backup application and.chkfiles files that
  contain fragments of file saved to disk scans. You can also use another hard drive with more drive
  free space for the installation. You can solve the problems of BIOS by upgrading the version of the system BIOS.

  BCCode: 7F 0x00000007E who is also a 0x1000007E<-- read="" this="">
  * 1141.html? order = votes http://www.faultwire.com/solutions-fatal_error/System-thread-exception-not-HANDLED-0x0000007E-

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

  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 event viewer
  Windows. TIP - Options - Advanced filter allows you to see a time rather
  of the entire file.
  http://www.NirSoft.NET/utils/my_event_viewer.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 the.
  death ' crashes and displays information about all accidents of a table.
  Free
  http://www.NirSoft.NET/utils/blue_screen_view.html

  BlueScreens many are caused by drivers of old or damaged, in particular the video 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.

  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. (Does not work
  tell all possible driver issues).

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

• Recurring blue screen error BCCode: c5 BCP1: 00000000 BCP2: 00000002 BCP3: 00000000 BCP4: 828EE4A2 OS

  Hi all and I want to thank you in advance
  I get this non-stop error and my computer stops and restarts all the hours
  and that's the exact blue screen. I checked against viruses and malware and my laptop is clean, so I don't know what else to do
  Thanks in advance :)

  Signature of the problem:
  Problem event name: BlueScreen
  The system version: 6.0.6002.2.2.0.768.3
  Locale ID: 4105

  More information about the problem:
  BCCode: c5
  BCP1: 00000000
  BCP2: 00000002
  BCP3: 00000000
  BCP4: 828EC4A2
  OS version: 6_0_6002
  Service Pack: 2_0
  Product: 768_1

  Files helping to describe the problem:
  C:\Windows\Minidump\Mini011012-01.dmp
  C:\Users\Shima\AppData\Local\Temp\WER-62915-0.SysData.XML
  C:\Users\Shima\AppData\Local\Temp\WERD0A6.tmp.version.txt

  Hello

  See this thread for more information on using BlueScreenView, MyEventViewer and other methods of
  Troubleshoot BlueScreens - answers top 3 (+ 1 more).

  http://answers.Microsoft.com/en-us/Windows/Forum/windows_vista-system/blue-screen-plug-and-play-detected-an-error-most/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

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

  BCCode: C5 0x000000C5

  This error is most often a driver, thinks the video and other BIOS. Antivirus/antispyware/security
  programs are also suspected.

  BCCode: C5 0x000000C5

  Bug Check 0xC5: DRIVER_CORRUPTED_EXPOOL

  Value of 0x000000C5 DRIVER_CORRUPTED_EXPOOL bug control a. This indicates that the system attempted to access invalid memory at IRQL level too high.

  Important information if you have received a STOP Code

  If you have received a blue screen error, or stop code, the computer stopped abruptly to protect against data loss. A hardware device, its driver or software might have caused this error. If your copy of Windows is shipped with your computer, contact your computer manufacturer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact information for Microsoft or the manufacturer of your computer connect with Support.

  If you have experience with computers and try to recover from this error, follow the steps in the Microsoft article solution STOP (blue screen) errors in Windows.

  The following actions could prevent a mistake like this does not happen:

  1. Download and install updates for your computer from Windows Update device drivers.
  2. Scan your computer for computer viruses.
  3. Check your hard drive for errors.

  DRIVER_CORRUPTED_EXPOOL parameters

  The following settings are displayed on the blue screen.

  Parameter	Description
  1	Memory referenced
  2	IRQL at time of reference
  3	0: Read 1: To write
  4	Memory address

  Cause

  The kernel attempted to access pageable memory (or may be completely invalid memory) when the IRQL was too high. The ultimate cause of this problem is almost certainly a driver that has damaged the system pool.

  In most cases, this bug results if checking a driver corrupts a small amount (less than PAGE_SIZE). Allowances cause more bug check 0xD0 (DRIVER_CORRUPTED_MMPOOL).

  Resolution

  If you have recently installed new software, check if it is properly installed. Check the updated drivers on the manufacturer's website.

  To debug this error, use special pool of driver verifier. Failure to reveal the driver that caused the error, use the global flags utility to enable the special pool by pool tag.

  BCCode: C5 0x000000C5<-- read="" this="">
  * 1198.html http://www.faultwire.com/solutions-fatal_error/A-Device-Driver-has-pool-0x000000c5-

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

  Driver Verifier can help find some BSOD problems:

  Using Driver Verifier to identify issues with Windows drivers for users advanced
  http://support.Microsoft.com/kb/244617

  How to solve the problems of driver 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 drivers check Manager to solve problems and identify the Driver questions
  http://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 drivers check Manager to solve problems and identify the Driver questions
  http://www.YouTube.com/watch?v=_VwIDD9xngM

  You can disable the driver verifier
  http://support.Microsoft.com/kb/244617

  Start - type in the box search-> auditor/Reset hit enter to disable

  BlueScreenView lets you know if there is a driver specified in the error message. Also check with
  MyEventViewer at the blue screen.

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

  I hope this helps.

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

• Bluescreen error: bccode 116; computer turns off on the reboot screen everything seems fine.

  Original title: while using the computer turns off on the reboot screen, everything seems fine. received message the last time. Signature of the problem: any suggestions?

  While using the computer turns off on the reboot screen, everything seems fine. received message the last time.

  Signature of the problem:

  Problem event name: BlueScreen

  The system version: 6.0.6002.2.2.0.768.3

  Locale ID: 1033

  More information about the problem:

  BCCode:                                               116

  BCP1:                                                    863A52A0

  BCP2:                                                    8DC1C152

  BCP3:                                                    C000009A

  BCP4:                                                    00000004

  OS version: 6_0_6002

  Service Pack: 2_0

  Product:                                               768_1

  any suggestions?

  Hello

  Try the procedure described in the following article.

  How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart unexpectedly?

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

  In addition, update the drivers for graphics cards and check if it helps.

  http://Windows.Microsoft.com/en-us/Windows7/update-a-driver-for-hardware-that-isn ' t-work correctly

• Stop error code blue screen: STOP: 0x000000F5

  I am a student and I take 2 of my classes online.  As soon as I decided to take my classes online my computer starts to work again. I can't afford to take it to the cause of Squad of geek I'm behind in my classes. It happened already, blue screens, and I was about to start my classes then instead of he sends to a diagnosis, I thought I could solve the problem by simply installing a new hard drive. If that's what I did. About a week later, I got another blue screen and since I had just put the new hard drive and a warranty, I got and they fixed, does not really enter in what the problem was. Now about a month has passed and the dreaded blue screen is back. This time that I wrote all the error codes and everything I did to try to solve the problem. I guess only through diagnostic tests, and to install a new hard drive was a mistake, given that I spent $260 and the problem is not resolved. In any case, I'm sorry I got carried away with the details, but I'm desperate! Last night, I had the first blue screen and read it.  The usual "a problem has been detected and windows were shut down to prevent damage to your computer.

  Then he said (and this was the first and only time I've seen this message) "run a system diagnostic utility supplied by your hardware manufacturer. In particular, to achieve a memory check, and check memory faulty or incompatible. Try to change your video card. "And then the usual"disable any hardware or drivers and software, etc... Technical information: STOP: 0x0000007F (0x00000000, 0x00000000, 0x00000000, 0x00000000).  Then, I started it in safe mode w/network, ran windows memory diagnostic tool and it found nothing. Then I tried Microsoft fix google and I change video card. Ending me upgoing in the properties of my video card to find out information about the pilot. Somehow, I ended up on Intel' support and found a newer driver for my video card, so I downloaded it. But then I got the blue screen again. This time it read; "A problem has been detected etc..  FLTMGR_FILE_SYSTEM with Tech Info STOP: 0x000000F5 (0x0000006E, 0x87AD62F8, 0x87AD62C8, 0x00000000). Can you please tell me what is happening so I can solve this problem once and for all! Or should I just invest in a new computer?   Thank you for your time.

  Hello

  Since this has happened material suspect in particular hard drive and anything
  report (such as the motherboard and wiring) - also, malware or same antivirus/anti -.
  spyware/security programs.

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

  You have ZoneAlarm or any 3rd party firewall installed? If so, this could be the cause.
  Other antivirus/security programs could be at least partially responsible.

  This fix "could" apply however do not use if you are quite safe.

  Two drivers of platform using WFP (Windows Filtering) causes a computer crash when the
  computer running Windows Vista, Windows 7 or Windows Server 2008
  http://support.Microsoft.com/kb/979278

  Check also:

  The General causes of errors "STOP 0x0000007F" (applies to Vista and Windows 7 as well)
  http://support.Microsoft.com/kb/137539

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

  Pick up the pieces after a computer breakdown - see what to do if Windows won't start correctly
  http://Windows.Microsoft.com/en-us/Windows-Vista/picking-up-the-pieces-after-a-computer-crash

  For the methods of troubleshooting blue screen using BlueScreenView and MyEventViewer see my answers
  If this thread - top 3 RESPONSES (+ 1 other).

  http://answers.Microsoft.com/en-us/Windows/Forum/windows_vista-system/blue-screen-plug-and-play-detected-an-error-most/3deab2fa-4000-4136-8c78-a3d22b1db009

  We can analyze the minidumps if make you it available the onedrive 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.

  Adding files to your OneDrive
  http://Windows.Microsoft.com/en-us/Windows-8/getting-started-onedrive-tutorial

  A disk - sharing files and folders and change the permissions
  http://Windows.Microsoft.com/en-us/onedrive/share-file-folder

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

  Use OneDrive to upload collected files

  http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65

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

  BCCode: 0x0000007f 7F

  Have you added a hardware or drivers updated recently? Check Control Panel - Windows
  Updates to see if all drivers have been updated it just before what is going on has begun.

  For 7f - this could be a problem of material such as uncomfortable cards or memory, while there are
  other causes. Power electric low could also lead to this. Use the troubleshooters above and below
  and when you get to the drivers and memory sections refer to my next message below and then
  return if necessary troubleshooting services

  If a PC remove ALL power. Opening the case, remove and reinstall all memory cards and ALL
  cable (try not just to close) on both ends if they are accessible and on the device ends if not
  (remove the cables and the resettlement of help them to eliminate minor corrosion).

  If a laptop or a PC, you will need to take a shop (not BestBuy or other BigBox stores) or your
  Support of the machine system.

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

  BCCode: 7F 0x0000007F which is the same as 0x1000007F

  UNEXPECTED_KERNEL_MODE_TRAP bug control has a value of 0x0000007F. This bug check indicates that the Intel CPU generated a trap and the kernel could not catch this trap.

  This trap might be a bound trap (a trap the kernel is not allowed to capture) or adouble foul(an error occurred during the processing of an earlier fault, which always results in a failure of the system).

  Parameters

  The first parameter that is displayed on the blue screen indicates the number of trap.

  The most common trap codes are the following:

  • 0x00000000 or division by zero error, indicates that a DIV instruction is executed and the divisor is zero. Memory corruption, other hardware problems or software failures can cause this error.
  • 0 x 00000004, or overflow, occurs when the processor executes a call to an interrupt handler when the overflow (OF) is flag set.
  • 0x00000005, or limits check fault, indicates that the processor, then executing a BOUND instruction, determines that the operand exceeds the specified limits. A BOUND instruction ensures that a signed array index is within a certain range.
  • 0 x 00000006 or Opcode not valid, indicates that the processor attempts to execute an invalid instruction. This error occurs generally when the instruction pointer is corrupted and point to the wrong address. The most common cause of this error is hardware memory corruption.
  • 0x00000008 or Double fault, indicates that an exception occurs during a call to the previous exception handler. In general, two exceptions are handled in series. However, there are several exceptions that cannot be handled serially, and in this case, the processor signals a double fault. There are two common causes of a double fault

  CAUSE

  0x7F bug check occurs after the installation of a faulty or incompatible hardware (including memory) or if installed hardware fails.

  A double fault can occur when the kernel stack overflows. This overflow occurs if multiple drivers are attached to the same battery. For example, if two file system filter drivers are associated to the same stack and then again the recursively of file system, the capacity of the battery.

  Solve the problem

  Troubleshooting: If you have recently added the material to the computer, remove to see if the error recurs. If the hardware failure existing, remove or replace the faulty component. Run the diagnostics of material that does not have the system manufacturer supplies to determine which hardware component.

  The scanner memory is particularly important. Faulty or incompatible memory can cause this bug check. For more information on these procedures, see the manual of your computer. Check that all the cards in the computer are well calibrated. Use an ink eraser or electrical contact treatment, available in electronic supply stores, to ensure the adapter card contacts are clean.

  If the error appears on a newly installed system, check the availability of updates for BIOS, SCSI, or card network controller. These updates are generally available on the Web site or the hardware manufacturer BBS.

  Confirm that all hard drives, hard disk controllers and SCSI adapters are listed in the list of the products tested Microsoft Windows market.

  If the error occurred after the installation of a new or updated device driver, you should remove or replace the driver. If, in this circumstance, the error occurs during the startup sequence and the system partition is formatted with NTFS, 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 in order to access the file.

  Also to restart your computer and press F8 to character-based menu that displays the choice of operating system. In the menuof Advanced Options , select thelast known good Configuration option. This option is most effective when you add a single driver or service at a time.

  Overclocking (setting of the CPU to run at a speed higher than the nominal specification) can cause this error. If you have overclocked to the computer that is experiencing the error, return the CPU to default clock speed setting.

  Check the system log in Event Viewer for additional error messages that might help identify the device or driver that generated the error. You can also disable caching memory BIOS to try to resolve the problem.

  If you have encountered this error during the upgrade to a new version of the Windows operating system, the error can be caused by a device driver, system service, an anti-virus or a backup tool that is not compatible with the new version. If possible, remove all third-party device drivers and system services and disable all antivirus before upgrade you. Contact the software manufacturer for updates of these tools. Also, make sure that you have installed the latest Windows Service Pack.

  Finally, if all of the steps above do not resolve the error, take the system motherboard to a repair for the diagnostic facility. A crack, a scratched trace, or a defective component on the motherboard can also cause this error.

  BCCode: 7F 0x0000007F which is the same as 0x1000007F<-- read="" this="">
  * 1304.html http://www.faultwire.com/solutions-fatal_error/Run-a-System-diagnostic-Utility-supplied-by-your-0x1000007F-

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

  BCCode: F5 0x000000F5

  The most common cause of this problem is a problem of hard disk or hardware connected to the drive
  as the mother/controller card and cabling. Other possible causes include antispyware/antivirus/security programs.

  Bug Check 0xF5: FLTMGR_FILE_SYSTEM

  Bug FLTMGR_FILE_SYSTEM control has a value of 0x000000F5. This indicates that a fatal error has occurred in the Filter Manager.

  Important information if you have received a STOP Code

  If you have received a blue screen error, or stop code, the computer stopped abruptly to protect against data loss. A hardware device, its driver or software might have caused this error. If your copy of Windows is shipped with your computer, contact your computer manufacturer. If you purchased Windows separately from your computer, Microsoft provides support.
  To find contact information for Microsoft or the manufacturer of your computer, Contact Support.

  If you have experience with computers and try to recover from this error, follow the steps in the Microsoft article solution STOP (blue screen) errors in Windows.

  The following actions could prevent a mistake like this does not happen:

  1. Download and install updates for your computer from Windows Update device drivers.
  2. Scan your computer for computer viruses.
  3. Check your hard drive for errors.

  FLTMGR_FILE_SYSTEM settings

  The following settings are displayed on the blue screen. Parameter 1 indicates the type of violation. The meaning of the other parameters depends on the value of parameter 1.

  See this link for the parameters or the Faultwire link below.
  http://msdn.Microsoft.com/en-us/library/ff560383 (v = VS. 85) .aspx

  Cause

  The cause of the problem is indicated by the value of parameter 1. See the table in the settings section.

  
  Resolution

  If parameter 1 is 0 x 66, you can debug this problem by checking that your minifilter driver recorded a reminder after the operation for this operation. The current operation are in the structure of recall data. (See parameter 2). Use of the ! fltkd.cbd the debugger extension.

  If parameter 1 is 0 x 67, you must verify that you do not have a leak pool unpaginated somewhere in the system.

  If parameter 1 is equal to 0x6A, make sure that your minifilter driver does not refer to this file object (see parameter 2) to get a handle at any time during the processing of your minifilter of this operation.

  If parameter 1 is equal to 0x6B or 0x6C, then a State internal unrecoverable error has occurred causing the operating system bug control.

  If parameter 1 is equal to 0x6D, make sure that your minifilter driver does not call FltReleaseContext too many times the specific context (see parameter 2).

  If parameter 1 is equal to 0x6E, make sure your minifilter driver does not call FltReferenceContext after the context has been removed (see parameter 2).

  BCCode: F5 0x000000F5<-- read="" this="">
  http://www.faultwire.com/solutions-fatal_error/FLTMGR-file-system-0x000000F5-* 1242.html

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

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

• BCCode: 124 on a new generation of system, please help! __

  I have a new generation system, and keep getting a bbc that I fight for the difficulty and I am in desperate need of assistance.  Thanks in advance for any help that you can provide to fix this problem.

  Signature of the problem:
  Problem event name: BlueScreen
  OS version: 6.1.7600.2.0.0.768.3
  Locale ID: 1033

  More information about the problem:
  BCCode: 124
  BCP1: 00000000
  BCP2: 864C78FC
  BCP3: 00000000
  BCP4: 00000000
  OS version: 6_1_7600
  Service Pack: 0_0
  Product: 768_1

  Files helping to describe the problem:
  C:\Windows\Minidump\091410-17640-01.dmp
  C:\Users\Marshall\AppData\Local\Temp\WER-31734-0.SysData.XML

  Read our privacy statement online:
  Privacy statement for Windows 7 - Microsoft Windows

  If the online privacy statement is not available, please read our offline privacy statement:
  C:\Windows\system32\en-US\erofflps.txt

  ==================================================
  Dump file: 091410-17640 - 01.dmp
  Crash time: 2010-09-14 23:32:29
  Bug Check String:
  Bug check code: 0 x 00000124
  Parameter 1: 0x00000000
  Parameter 2: 0x864c78fc
  Parameter 3: 0x00000000
  Parameter 4: 0x00000000
  Caused by the driver: ntoskrnl.exe
  Caused by the address: ntoskrnl.exe + 322493
  File description: NT kernel & system
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 6.1.7600.16617 (win7_gdr.100618 - 1621)
  Processor: 32-bit
  Computer name:
  Full path: C:\Windows\Minidump\091410-17640-01.dmp
  Number of processors: 3
  Main version: 15
  Minor Version: 7600
  ==================================================

  ==================================================
  Dump file: 091410-18703 - 01.dmp
  Crash time: 2010-09-14 23:25:48
  Bug Check String:
  Bug check code: 0 x 00000124
  Parameter 1: 0x00000000
  Parameter 2: 0x85afc8fc
  Parameter 3: 0x00000000
  Parameter 4: 0x00000000
  Caused by the driver: ntoskrnl.exe
  Caused by the address: ntoskrnl.exe + 322493
  File description: NT kernel & system
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 6.1.7600.16617 (win7_gdr.100618 - 1621)
  Processor: 32-bit
  Computer name:
  Full path: C:\Windows\Minidump\091410-18703-01.dmp
  Number of processors: 3
  Main version: 15
  Minor Version: 7600
  ==================================================

  ==================================================
  Dump file: 27187 091110 - 01.dmp
  Crash time: 2010-09-11 17:21:14
  Bug Check String: PAGE_FAULT_IN_NONPAGED_AREA
  Bug check Code: 0 x 00000050
  Parameter 1: 0xffffff8b
  Parameter 2: 0x00000001
  Parameter 3: 0x92a956d5
  Parameter 4: 0x00000000
  Caused by the driver: tcpip.sys
  Caused by the address: tcpip.sys + f9438
  Description of the file: TCP/IP Driver
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 6.1.7600.16385 (win7_rtm.090713 - 1255)
  Processor: 32-bit
  Computer name:
  Full path: C:\Windows\Minidump\091110-27187-01.dmp
  Number of processors: 3
  Main version: 15
  Minor Version: 7600
  ===============================================

  I use a triple-core processor AMD Athlon II 440, MSI NF750-G55 mainboard, Corsair xms 2 gig memory, Hitachi Desktar 1 TB disk sata hard.

  Once again, thank you for your help in advance.

  You have a fatal hardware problem :

  Bug Check 0 x 124: WHEA_UNCORRECTABLE_ERROR - This bug check indicates that a fatal hardware error occurred.

  Please copy the files of the dmp to the C:\Windows\Minidump folder first on your desktop, zip dmp all in 1 zip file and download the zipfile to your Skydrive [1] and post a link here, so that I can look at landfills.

  André

  http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65 [1]

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

  André,

  Thanks for your reply, but I think that I have fixed my problem.  When I built the system, I never could the 2nd strip of memory to work.  It would not just start my system at all.  I thought all along that I had a problem of memory based on my last sentence.  I finally went out and bought another brand memory and did not have a BSOD on the last 2 days.

  Thanks again for trying to help me.

• Help blue screen Stop error

  If it received Blue error screen and auto restart past since I did the sp1 update. I have Windows Vista-32 and the error I get is:

  Stop: 0x0000008E (0xc0000005, 0x93F042F9, 0X92CD3C50, 0x00000000)

  Win32k.sys - address 93F042F9 base at 93E00000, DateStamp 4549aea2

  I need help here. I'm going nuts trying to figure this out. I would appreciate your help. Thank you.

  Hello

  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
  You must identify which exception has been generated.

  Common exception codes are:

  • 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
  • Reference of 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) must 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. Make sure that all new equipment installed is listed in the
  • List of Microsoft Windows Marketplace tested products.
  • Service driver or defective peripheral system. A service driver or defective peripheral system can be
  • responsible for this error. Hardware problems, such as the incompatibilities of the BIOS, memory, conflicts
  • 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. Also, clear or
  remove drivers or services that have been recently added. If the error occurs during 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 system startup
  Mode process without failure, you must start the computer by using the Recovery Console to access to the
  file.

  If the problem is associated with Win32k.sys, the source of the error may be a third remote
  control program. If this software is installed, you can remove the service from the system startup of
  using the recovery and then Console by removing the system service file incriminated.

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

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

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

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

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

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

  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' crashes, 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, drivers particularly video drivers but it
  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 - bicycle - Mark Twain said it is good.