Blue screen: c000021a 0xc000001d (0x00000000 0x00000000)

Similar Questions

• Blue screen: c000021a autochk program not found

  original title: program autochk not found - skipping AUTOCHK "Followed by BSOD" STOP: c000021a {fatal system error} Session Manager initialization of the system responding ended unexpectedly with the status of 0xc000003a (0x00000000 0x00000000)

  Hello everyone I am desperately need assistance. I'm running under Windows Vista Home Premium 32 bit SP2. The computer is a HP Pavilion Media Center TV PC m7680n.   About 5 days ago my antivirus software, Avira, picked up a malware infection at the site of Windows/System32/drivers/mountmgr.sys. Like a fool, I decided to delete the file and call it a day, but the second that I made my computer immediately deleted and I was forced to close. When I started again, I was greeted with this error message 'autochk program not found - skipping AUTOCHK', which was then followed by a container BSOD:

  STOP: c000021a {fatal system error}
  The Session Manager initialization system process ended unexpectedly with the status of 0xc000003a (0x00000000 0x00000000)

  Since then, I tried to boot from any available including the last known configuration safe mode options but I am confronted with the same BSOD and error message and am not able to access the desktop. I also tried all of my drive to Installation of Vista startup repair options, but it says it cannot determine the cause of the problem.

  I also tried to use system restore but it is said that "no restore points were created on your computer's system disk.

  I also tried using the command prompt and enter the command chkdsk with all the options available, but it cannot detect errors or problems. I also tried to use the Bootrec command with all available options, including the reconstruction of the BCD from scratch, but that no longer works. I also tried to use the sfc/SCANNOW command but it cannot start because I get an error message indicating that "Windows Resource Protection could not preform the requested operation." I also tried to replace the file mountmgr.sys since a separate installation of vista through the command prompt by using a floppy disk, but alas it does not solve my situation.

  There are a lot of files and personal information about this computer that I consider valuable for me so please give as much advice and guidance as you possibly can which can help save my OS without having to wipe everything. Also, it's my first time in this forum post, so if I've left out any important information so please let me know and I'll try to give it too you. By the way, I am also what you would call an extreme novice with these sorts of things so be as complete with your descriptions as possible. Thank you.

  Hello

  Go back and use the troubleshooting guide I posted above - top to bottom. And indeed will need you
  technical help in a real store of the computer (no leeks and glances at a BestBuy or other BigBox
  stores) or system manufacturer support.

  Startup Repair can help.

  I hope this helps.

  Rob Brown - MS MVP - Windows Desktop Experience: Bike - Mark Twain said it right.

• Blue screen with STOP error 0x0000007B (0xBA4CF524, 0xC0000034, 0x00000000, 0x00000000)

  I have my Acer 5920 laptop, 2 GB of RAM and 160 hard drive, last stop system time correctly with all the files to day, but when I restart then comes windows XP Jean-Christophe and then a blue screen with the error. Nor I have install new software or remove something in the laptop. My system was perfect, and that was before the last stop.
  I have Windows XP SP2-teacher-pack. I have the original CD of this package.
  But when I use the CD then nothing is happen and come same messgae of error. I do not have any other CD bootable for windowXP except your originalCD.
  Please suggest me what I should do to fix my probem. I'm not to much expert for the formatting and other things computer.

  After reading your following suggession:
  Here are a few things to try:
  The first thing to do is to boot your system and start pressing F8 as soon as it starts booting.  You will get the Windows startup options screen.  Select "Disable automatic restart in the event of system failure" and let it restart.  When it starts, it can now stop with an error screen and give an error message and code.

  Disconnect all external devices (printers, USB Hub, drives external, etc.) and try to start.

  I got the result of the error that comes on a blue screen after you follow your process-blue screen with STOP error 0x0000007B (0xBA4CF524, 0xC0000034, 0x00000000, 0x00000000)

  Thanks in advance for help
  What about nice Rajneesh

  Just one quick response for others...

  Go to your bios to change the mode of training of your s - ata AHCI or IDE Compatible mode or all that apply :) Windows XP is not like SATA, because it has no native support for it. At the start of the second phase of a Setup program, it would fail with this BSOD.

  Also read the following Microsoft article that describes many other causes (including file system damage):Troubleshooting of errors "Stop 0x0000007B" in Windows XP Advanced

  Sometimes, your BIOS will provide its default settings after a system crash or a configuration. Should not happen, but it is...

  For BIOS-discussions, see: 0x0000007B 0xBA4cf524 - Forum of Support PC - Free Computer help , XP installation: * STOP: 0x0000007B (0xF78D2524, 0xC0000034, 0x00000000, 0x00000000)? - Page 4 - Cyber Tech Help Support Forums , 0x0000007B (0xBA4CF524 - Google zoeken .)

  Have fun, and... Peace!

  Devvie

  ~ ~ ~ * E-mail address is removed from the privacy * ~ ~ ~

  CONARE nullius momenti videri fortasse missilibus careant
  ------
  All the spelling mistakes are my own and may not be distributed under the GNU General Public License! -(© 95 1 by Coredump; 2-10 by DevNullius)

• A blue screen on laptop running XP: Stop: 0x0000006B (0xc0000102, 0x00000002, 0x00000000, 0 x 000000000)

  We have a six year XP old Dell laptop. We recently had an upgrade memory and it works very well.

  Yesterday, we got what I now know to be a BSOD (blue screen of death!). I'm unable to go beyond the blue screen and complete functions. I tried all of the advanced options, including the 3 security modes.

  The message is "Process1_Initialization_Failed.

  Stop: 0x0000006B (0xc0000102, 0x00000002, 0x00000000, 0 x 000000000). Is anyone aware of how to get back or if I can get all the files on the laptop without being able to boot windows?

  I have a cd Windows xp home edition reinstallaton, but if I put in the drive, it is not recognized and is the BSOD. Thank you

  Patty

  I knew that there is an AVG in here somewhere...  AVG is at least a part of your problem.

  Here's how to fix this error:

  If you see a message like this:

  PROCESS1_INITIALIZATION_FAILED
  STOP: 0x0000006B (0c 00000034), 0x00000002, 0x00000000, 0x00000000)

  That means that your c:\windows\system32\ntdll.dll file is missing.

  Of course, the file must never be missing, but it may have been quarantined (actually deleted) by your antivirus/antimalware software.

  There are other copies of the file that is missing on your system in other places, so you just need to replace it.

  You can replace the file from the XP Recovery Console.

  If you do not have a genuine XP bootable installation CD to boot into XP Recovery Console (or if you are unsure of what you have) you should make a CD of XP Recovery Console and don't forget (no support for XP not necessary).  If you need to know how to do this, just ask.

  Once started in the XP Recovery Console, that:

  A good idea before you start things must first verify the integrity of your file system by using the chkdsk command.

  In the command prompt window, run the chkdsk command on the drive where Windows is installed to try to fix any problems on the afflicted player.

  Running chkdsk is fine, even if he finds no problem.  It won't hurt anything to run it.

  Assuming your boot drive is C, run the following command:

  CHKDSK C: /r

  Let chkdsk finish to correct the problems, he could find.

  It may take a long time for chkdsk complete or they seem to be "stuck".  Be patient.  If the HARD drive led blinks always, chkdsk is something.  Keep an eye on the amount of the percentage to be sure that it is still making progress.  It may even seem to go back sometime.

  We know that XP keeps copies of critical system files in the following folder:

  c:\Windows\System32\dllcache

  Starting the XP Recovery Console prompt, enter the following command:

  Copy c:\windows\system32\dllcache\ntdll.dll c:\windows\system32

  Answered in the affirmative if invited to replace the existing file and then you should see a message that 1 file (s) has been copied.

  If the copy command is unable to find a copy of the file in the dllcache folder, this command may work depending on how your XP has been installed:

  Copy c:\windows\ServicePackFiles\i386\ntdll.dll c:\windows\system32

  Type "exit" to exit the Recovery Console and the system will restart.

  You will see then a menu of boot options so if you do, choose Start Windows normally.

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

• Blue screen Windows XP start STOP: 0x0000000A (0x000000FF, 0x00000000, 0x006CED36, 0x805302F2)

  Guru of any kind

  I turn on my computer, and then after the already loaded windows logo, with the fact that I found a blue screen said
  STOP: 0X0000000A (0X000000FF, 0X00000000, 0X006CED36, 0X805302F2)
  So, what should I do to solve this problem I have a bootable DVD, I could start in DOS now.
  For more details of this symtom.
  1. I installed NOD32 antivirus and use it for 2 days, already update the anti-virus databases, already sweeping the entire system, drive
  2. I found the GET bigger and bigger quarantine folder, so I try to remove (Ctrl + A, Del)
  then NOD32 program to happen does not not but the other program can still use
  can I use the Task Manager to end NOD32 but cannot, it has been protected.
  If I click on start/turn off computer/Turn off shutdown of windows then
  3 after I turn on my computer, then after the already loaded windows logo, with the fact that I found a blue screen said

  STOP: 0X0000000A (0X000000FF, 0X00000000, 0X006CED36, 0X805302F2)

  Thank you very much
  Sabrina C

  Take a look at the section "Error occurs after Windows XP is already installed" of this article in the Microsoft Knowledge base.

  I recommend the boot without failure and then research on the issue.

  To start in Safe Mode, until the small logo of Windows with a progress bar appears, press the F8 key. In the list of options, choose Safe Mode.

  Now that the first troubleshooting step, uninstall ESET NOD32 using the NOD32 removal tool (download the file via a work computer, save it to a USB drive and take it to your affected PC booted without failure).

  Once uninstallation is successful, restart the PC to see if the BSOD persists.

  If the BSOD persists, try to boot mode safe again. Now click on the Start button, select all programs > Accessories > system tools > system restore. Select "Restore my computer to an earlier time" and click Next. Choose a restore point before the installation of ESET NOD32, usually it will be a created restore point automatically named "Installed ESET NOD32 Antivirus" or something similar. After choosing a suitable restore point, click Next. Click Next again to confirm the restore operation.

  If only NOD32 UN-installing the problem you can try to re - install it or contact the ESET Support.

• I have blue screen & a Kernel_Stack_Inpage_Error & Stop message (0xc0000185, 0xc0000185, 0x00000000, 0x01e1600)

  original title: I get the blue screen of death & a Kernel_Stack_Inpage_Error & Stop message (0xc0000185, 0xc0000185, 0x00000000, 0x01e1600)

  This sometimes happens once a day & sometimes repeatedly, he spent 2 days without crashing.  I ran registry fix on that, but always seens to crash.  Help

  Hello

  · Were there any changes made on the computer before the show?

  Follow the steps from the link and check if it helps: you receive an error message on a Windows XP-based computer: "Stop 0 x 00000077" or "KERNEL_STACK_INPAGE_ERROR": http://support.microsoft.com/kb/315266

• Blue screen - UNMOUNTABLE_BOOT_VOLUME STOP: 0x000000ED (0x8A93D590, 0xC0000006, 0x00000000, 0x00000000)

  Original title: I'm trying to start Windows XP after getting the Blue Screen of Death

  Here are the specifics on the BSOD:
  UNMOUNTABLE_BOOT_VOLUME STOP: 0X000000ED (0X8A93D590, 0XC0000006, 0X00000000, 0X00000000)

  I started on the boot CD after changing the order in the BIOS.  Run the test fast and got this error:
  0F00:1344 error code
  MSG: Block 413906: error impossible to correct data or media is write protected
  Any suggestions on what to do next?

  First, store the boot CD.

  Secondly, because we know nothing on your system, you could tell us about it.

  Third, follow the directions in this thread:
  http://answers.Microsoft.com/en-us/Windows/Forum/windows_xp-system/unmountable-boot-volume-stop-0x0000000ed/570c7f90-5869-E011-8dfc-68b599b31bf5

• computer does not boot, blue screen with the message: Stop: 0 x 00000024 (0 x 00190203, 0 X 86949258, 0xC0000102, 0x00000000)

  computer does not boot, blue screen with the message: Stop: 0 x 00000024 (0 x 00190203, 0 X 86949258, 0xC0000102, 0x00000000)

  Hello

  1 how long have you been faced with this problem?
  2. don't you make changes on the computer before this problem?

  Start the computer by using the Microsoft Windows XP recovery console, and then perform a check disk on the file system.

  To do this, follow these steps:

  1. Insert the Windows XP CD in the CD-ROM or DVD - ROM drive, and then restart the computer. Select the required options to start the computer from the CD-ROM or DVD - ROM drive if you are prompted to do so.
  2. once the Welcome to Setup screen appears, press R to start the Recovery Console.
  3. If your computer is configured to dual-boot or multiple boot, select the appropriate installation of Windows XP.
  4. When you are prompted to do so, type the administrator password and press ENTER. NOTE: In Windows XP Home Edition, the administrator password is blank by default.
  5. at the command prompt, type the following command and press ENTER: cd system32
  6. type the following command and press ENTER: chkdsk /r /p
  7. remove the Windows XP CD in the disc drive.
  8. Type exit to restart your computer.

  Important: Running chkdsk on the drive if bad sectors are found on the disk hard when chkdsk attempts to repair this area if all available on which data may be lost

• Virus deleted and now the computer will not start... I get the blue screen with an error that says STOP: 0x0000007B (0xB84C3524, 0xC000000E, 0x00000000, 0x00000000) what is the problem? !!

  Virus deleted and now the computer will not start... I get the blue screen with an error that says STOP: 0x0000007B (0xB84C3524, 0xC000000E, 0x00000000, 0x00000000) what is the problem? !!

  Hi ipitedafoo,

  You can check if this article helps.

  Advanced troubleshooting of errors "Stop 0x0000007B" in Windows XP

  See also:

  Error message "STOP 0x0000007B" when you restart your Windows XP-based computer

• When you try to Watch youtube videos, get the blue screen error: 0x0000008E (0xE0000001, 0BA460925, 0xA8919820, 0x00000000)

  I can't view videos such as youtube without my computer locking with a blue screen and error message: 0x0000008E (0xE0000001, 0BA460925, 0xA8919820, 0x00000000) how correct this and what it means? I am running windows XP. Thank you

  Hello

  · You receive this error message only when you watch videos online?

  · Do you remember any changes made on the computer before the show?

  · What is the number and the model of the computer?

  · What is the service pack installed?

  Check the status of the card/video display adapter installed on your computer.

  a. click on start

  b. click Run, in the Run dialog box type devmgmt.msc

  (c) in the Device Manager window, look for the screen reader and expand the drive, double-click the sub element to check if an error message or error code is listed.

  You can also check out the link below: general troubleshooting for an error message that you receive randomly in Windows XP: "Stop 0x0000008E": http://support.microsoft.com/kb/945658

• Blue Screen error code RQL_Less_or_Equal stop: 0X0000000A, C0xE10039F0, 0x000000FF, 0x00000000, 0x8056CA2E

  I came to doday to find that a blue screen on my pc .This is the error number.

  Blue Screen error code RQL_Less_or_Equal stop: 0X0000000A, C0xE10039F0, 0x000000FF, 0x00000000, 0x8056CA2E

  Please provide additional information on your system:
  What is your system brand and model?
  What is your version of XP and Servie Pack?
  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 here.
  There will be some personal information (such as the user name and the name of the system), and everything seems
  be personal information for you, just delete pasted information.
  This will minimize back Q & A and eliminate guesswork.
  Download BlueScreenView here:
  http://www.NirSoft.NET/utils/blue_screen_view.html
  Unzip it and run it (BSV installs nothing) and let him complete the digitization of all of your files to dump.
  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).
  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.
  Here's an example of report ASB to a single BSOD I initiated on purpose that indicates the cause of the accident as the pilot i8042prt.sys belonging to Microsoft Corporation:
  ==================================================
  Dump file: Mini062110 - 01.dmp
  Crash time: 21/06/2010-11:51:31
  Bug Check String: MANUALLY_INITIATED_CRASH
  Bug check code: 0x000000e2
  Parameter 1: 0x00000000
  Parameter 2: 0x00000000
  Parameter 3: 0x00000000
  Parameter 4: 0x00000000
  Caused by the driver: i8042prt.sys
  Caused by the address: i8042prt.sys + 27fb
  Description of the file: i8042 Port driver
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 5.1.2600.5512 (xpsp.080413 - 2108)
  Processor: 32-bit
  Computer name:
  Full path: C:\WINDOWS\minidump\Mini062110-01.dmp
  ==================================================
  Send information from 5 last memory dumps.
  While you wait for analysis, no matter what you use for protection against malware, please follow these steps:
  Download, install, update and do a full scan with these free malware detection programs:
  Malwarebytes (MMFA): http://malwarebytes.org/
  SUPERAntiSpyware: (SAS): http://www.superantispyware.com/
  It can be uninstalled later if you wish.

  Do not guess what the problem might be - understand and resolve it. I need YOUR voice and the points for helpful answers and propose responses. I'm saving for a pony!

• blue screen error STOP: 0X000000ED (OX86791240, 0XC000009C, 0x00000000, 0x00000000)

  When I try to start my dell inspiron 5100 laptop with windows xp I get a blue screen with the error UNMOUNTABLE_BOOT_VOLUME with the error code Stop: 0X000000ED (OX86791240, 0XC000009C, 0x00000000, 0x00000000) is there anyone to the solution?

  How your post is related to the Windows Update feature?

  Bug Check 0xED: UNMOUNTABLE_BOOT_VOLUME:
  http://msdn.Microsoft.com/en-us/library/ff560355 (vs.85) .aspx

  ~ Robear Dyer (PA Bear) ~ MS MVP (that is to say, mail, security, Windows & Update Services) since 2002 ~ WARNING: MS MVPs represent or work for Microsoft

• Blue screen with an error: process1_initialization_failed "stop: 0x0000006B (0xC0000020, 0 x 00000003, 0x00000000, 0x00000000).

  OT: Boot to Vista.

  Hello everyone,

  I have a laptop running Vista which is not booting to windows at all. I tried repair disk installation which stops at a blue screen with an error: process1_initialization_failed

  Lowest:

  Stop: 0x0000006B (0xC0000020, 0 x 00000003, 0x00000000, 0x00000000)

  Y at - there anyone who can help?

  Thanks in advance :)

  Hi Nikita,

  Try the following link that will help solve your problem:

  You receive "0x0000006B" and "0XC000021A" Stop error message after you uninstall McAfee Agent 4.6.2 in Windows Vista, Windows 7, Windows Server 2008 or Windows Server 2008 R2:

  I hope this helps. Please let us know if you need assistance.

• Blue screen STOP: 0 x 00000124 (0x00000000, 0x89BED028, 0xB2000040, 0 x 00000800)

  Hello

  This is my first post, please have mercy,
  I have a BSD at startup and this is the code that continues to show upward.  System Restore (from system repair and also safe mode) has not solved the teething problems.
  Blue screen STOP: 0 x 00000124 (0x00000000, 0x89BED028, 0xB2000040, 0 x 00000800)
  I think the code means some sort of failure hardware, is anyway to deduce which device has failed in assessing these codes?
  Please let me know if I'm on the wrong track with a hardware failure, I appreciate all the advice.
  Thank you

  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) 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) make sure 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 of the BIOS of the 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) attempt (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 troubleshooting no invasive steps, perform a reinstallation of Windows 'vanilla': 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.