Constant BSOD

Similar Questions

• Constant BSOD! Help, please!

  Get the constant BSOD stops. More than 5 - 10 times a day! I have no idea, and also my knowledge, everything is up-to-date. Help, please! :(

  Here is a link to my most recent minidumps.

  Current Minidumps link

  http://www.mediafire.com/download/76d7v7z904d6o46/CrashMinidumps.7z

  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.

  
  Don't forget to download any other DMP files (especially those running auditor)

  If you are overclocking reset all default before running these tests.
  In other words STOP!   If you don't know what it means that you're probably not

  1 - Memtest.
  Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Get it here
  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.
  
  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).
  
  Here is the procedure:
  Click Start and type "auditor" (without the quotes) and press enter
  Select 'Create a custom settings (for code developers)' and click 'Next' (or Type "check/standard/all" (without the quotes) If you want to check each of them (this will slow down your computer))

  Choose "Select custom settings from a full list" and click "Next".
  Select the entire document except for "Low resource Simulation" to win 8 do not check concurrency stress test and the verification of the conformity of DDI, 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.
  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.

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

  Words of driver verifier
  
  Information check driver driver Windows Vista - Microsoft Search Verifier
  Questions of Verifier within Vista / Windows 7 http://support.microsoft.com..default.aspx?+verifier1&res=20
  Pilot feature pool http://support.microsoft.com/kb/188831

• Constant BSoD, corrupt files, preventing a Win7 installation, no known recent driver updates

  From 4 days ago, my wife (Vista Home Premium) laptop started BSoD repeatedly.  We have not updated all the drivers recently (but who knows what performed auto-updates).  It restarted 4 times that night and each time it seemed to come as soon as she tried to access any URL in IE or Firefox.  She brought home for me and I had no problem with him in a browser, but the next day, he began to die again.

  Common mistakes are 7th and 8th, and it continues to hang, even after a system restore to a point of recovery two weeks ago (although it took 6 trials to actually restore - BSoD kept killing the process).  Repair of the system does not work either, it crashes, as well.  I remember at least three messages on the BS itself: CACHE_MANAGER and IRQL_NOT_LESS_OR_EQUAL BAD_POOL_HEADER.  I suspect a problem with the map NETWORK, but Windows says its pilots are underway (2008), especially as the most recent accident has been when I tried to connect to my wireless network.

  I was hoping a custom to Win7 Setup would fix it, but it continues to crash during the installation (at different points of the installation, as a bonus).  When trying to install, it is usually said of a file (usually a different each time) is corrupted.  I tried to run windows setup, and also start from the disc, or what allows me to complete the installation.  Is there a way to just reformat the hard disk during the installation as the back with Windows XP?

  Also, can someone tell me why "Contact Microsoft Support" says there is a problem with the ID of the product on the website?  It is said to put it in the right format, but it already is.  If I go back and choose a different product, it recognizes that the product key is wrong for the selected product, but for some reason, it doesn't let me continue to the next step.

  Thank you much for the help!

  Thanks for the answer, it turns out it was a bad stick of RAM.  I finally got to the point where I could boot from my CD of Windows, so I formatted the drive, but I still have bluescreened, so I thought it must be a problem with the hardware at its base.  I pulled one of the sticks and it crashed immediately, if I swapped out and it installed fine.  Thanks again for the interest, morality is to check things easy before going deep into the software!

• Constant BSOD, "WHEA_UNCORRECTABLE_ERROR."

  Hey guys,.

  Lately, my computer has been crashing all playing games on it and I do not know what to do. The time that I am able to use my computer before it crashes varies, but it tends to occur more quickly on most demanding games. For example, I could play Dark Souls 2 for a few hours and be well, while it will crash within 20 minutes on GTA V. I don't know what the problem is and was hoping that someone can help you. Here's the info from my last BSOD:

  Problem event name: BlueScreen
  OS version: 6.1.7601.2.1.0.768.3
  Locale ID: 1033
  BCCode: 124
  BCP1: 0000000000000000
  BCP2: FFFFFA800EA68638
  BCP3: 0000000000000000
  BCP4: 0000000000000000
  OS version: 6_1_7601
  Service Pack: 1_0
  Product: 768_1

  I used WhoCrashed trying to find out what the problem was, and he told me that ntoskrnl.exe broke and WHEA_UNCORRECTABLE_ERROR was the error.

  If we need more information, let me know what you need and how to get it!

  MU

  The results tend to point to the CPU, but it could also be the heat, POWER or else block.  It's probably the processor but I would continue to do other tests to eliminate other things as the source of the problem.

• Constant BSOD/crash on Windows 8

  Hi I just did a clean install of windows 8 pro last week. Since then, I have had several accidents. It is random when it happens, sometimes it will happen as soon as I start, sometimes a few hours later. I tried to find me a solution, but were unsuccessful. So now, I hope that someone here may be able to help me. I am blue screen reader, and every time it crashes it is because of ntoskrnl.exe any help would be greatly appreciated. I am also attaching a SkyDrive link with all the files of dump C:\Windows\Minidump.

  Minidump link: http://sdrv.ms/125t7Ga

  Thanks in advance,

  Dennis

  DJH

  It's all related material.  There is a small chance that your Kaspersky remains may be the cause so I remove it and using Mse instead

  Kaspersky is a common cause of BSOD.

  
  

  I remove and replace it with Microsoft Security Essentials at LEAST FOR TESTER.

  http://support.Kaspersky.com/downloads/utils/kavremover10.zip
  http://www.Microsoft.com/security_essentials/

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

• Constant BSOD, even after the restoration.

  I recently bought a HP a6554f computer.  Here's the specs: Intel Core 2 Quad Q6600 / 2.4 GHz 64-bit processor, 5 GB DDR2 SDRAM and I put in a GeForce 8500 gt when buying with a 550w PSU. I'm running on Vista Home Premium 64-bit.

  For several weeks it worked fine until one day I got my first blue screen.  After all initially that I would get one here and there, but I don't mind really until they began to become one every day, sometimes several times a thing of the day.  After a while, he was several times a day, so I started running memory tests that showed no problem, updated my drivers, attached to the top of my registry, updated my BIOS and done everything I could find on the internet.  I decided to restore the settings by default, and as soon as the operating system reinstalled, I got another blue screen.  I constantly closing the different host process and the windows update does not work.  Everytime I try to update downloads updates again and gets stuck their installation.  My next step is installing a copy of Vista Ultimate to see if a clean, new operating system will work.

  Any ideas on whether changing the operating system works, or if there is nothing else I could possibly do to solve these problems?

  Certainly a bad memory. You should test each of them separately. Time to call HP and have them send more or send in for repair.

  Please check your private messages.

  Message edited by dmhoo29 on 03/16/2009 20:27

• Constant BSOD in one pc brand new

  Hi, I have a new pc (acer e5 - 511 g) who came without OS, so I installed windows 7 x 32. the thing is that, since it first started, I constantly bs (0 x 00000124). I try to update the drivers and BIOS and continues in the same way, if someone can read the minidumps to see what is wrong with the computer?

  https://www.dropbox.com/s/nfh8no56pq6cm5y/minidumps.zip?DL=0

  Thanks in advance.

  They are called BCC124 and are related to the material.  Read how to diagnose and, hopefully, correct in this wiki

• Constant BSOD Windows 7 pro 64-bit

  I get a blue screen several times a day for the past month. I have not changed any hardware since I built my system about a year ago. IE 11 began to break up when opening. It don't crash in SafeMode.  I read another post about this, so I've included the link for my minidump files.

  Link: http://1drv.ms/1vFBQNm

  This is a link to the zip on OneDrive.

  James

  2 most recent accidents have been associated with memory management but have no active auditor.  What result did you get when you run check/query?

  I would like to start memtest as well.

• Constant BSOD with the new laptop computer

  I bought a laptop Dell L521X are three or four weeks ago, and since then have had difficulties with the projection of thing regularly blue on me at arbitrary points. Those initial seemed to result from McAfee LiveSafe who settled on the laptop so I uninstalled this and these people arrested. However, since then he has been giving me an error called DRIVER_POWER_STATE_FAILURE he says is caused by ntoskrnl.exe. Blue screens seem to happen arbitrarily and not because of anything specific I'm doing on the laptop. It will almost always crash when it is in "standby", however, and a few times he broke down while I'm closing. I updated both drivers and BIOS, hoping that would solve the problem but neither helped. I thought that it could be a hardware problem but all the Dell diagnostics, I came back with nothing. I've been futzing with the thing for a while now trying to figure out what it is but I'm stumped. If someone wants to look at the crash dump files I the downloaded in a zip here: [x]

  I really want to fix this because I don't want to take over the laptop. I bought the thing because I had problems with my old, and here I will once more in trouble with the new! I hope you guys can help me. Thank you!

  DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

  This indicates that a kernel-mode driver attempted to access pageable memory with a high IRQL.

  A driver tried to access a pageable (or that is completely invalid) address while the IRQL was too high. This bug check is usually caused by drivers who used a wrong address.

  STACK_TEXT:
  fffff880 '099013f8 fffff880' 018d636f: fffffa80 '13-57040 fffffa80' 118ac174 fffff880'09901460 00000000 00000000': 0 x 0
  "fffff880 ' 09901400 fffff880'd 018 7128: fffff880 ' 00000000 fffffa80 ' 100f5520 00000000' fffffa80 00000000' 00000000: ndis! ndisMSendCompleteNetBufferListsInternal + 0x10f
  fffff880 '099014-0 fffff880' 1009da83: fffffa80'132 ca 010 fffffa80 '132c88d0 00000000 00000000' fffffa80' 132bcb00: ndis! ndisMSendCompleteX + 0 x 188
  fffff880 '099014f0 fffffa80' 132ca 010: fffffa80'132c88d0 00000000 00000000' fffffa80 '132bcb00 fffffa80' 10eba1a0: SBFWIM + 0x2a83
  fffff880 '099014f8 fffffa80' 132c88d0: 00000000 00000000' fffffa80 '132bcb00 fffffa80' 10eba1a0 00000000' 00000000: 0xfffffa80'132 ca 010
  fffff880'09901500 00000000 00000000': fffffa80'132bcb00 fffffa80 '10eba1a0 00000000 00000000' fffffa80' 13f706b0: 0xfffffa80'132c88d0

  Gah... I suspected that this software to be a problem, but I wanted to be sure before recommending removal. Sunbelt Firewall is originally NETBIOS conflicts, I see quite often. It is quite problematic software (IMO), so I would remove as soon as POSSIBLE.

  Kind regards

  Patrick

• Kernel_security_check_failure frequent bsod

  I get these all the time. Usually the start or stop. It sometimes takes 2 or 3 attempts before Windows starts, and I don't remember the last time I had a closed own. I think it has something to do with one of my external hard drives. I currently have a LaCie 1 TB and a 2 to Seagate. The LaCie currently has a single partition ExFAT, while the Seagate has 2 partitions HFS + and a NTFS. If I try to 'remove' LaCie, it works very well. If I try with the Seagate, he always says that the device is in use, and not to remove it. If I ignore the warning, I get a BSOD instant.

  I would like to blame the HFS drivers that apple provides for the reading of the OS X partition. They suck no doubt. My proof is that I wanted to keep the Seagate as a pure GPT drive, so I have set up with 3 partitions HFS + disk utility, but Windows won't format the third partition to NTFS until I disabled the HFS driver. I guess I could disable the drivers again for a few days and see if the BSOD happen again, but I would still be able to see all HFS partitions, so I'm posting here in the hope of some sort of solution. And I was wondering if anyone else has had problems using external hard drives with HFS partitions.

  sfc/scannow says everything is fine, and a virus scan found nothing.

  And why using a partition for Time Machine makes it unreadable under Windows?

  I disabled the HFS drivers, and the amount of BSOD has dropped dramatically. I'll leave this unresolved even if for now, because I want a solution that allows me to see my OS X partition and not yet constant BSOD.

• BC BSOD Code 124 hall.dll accident pilot

  I did a lot of research and testing on this problem. Sometimes I use my computer for almost 2 weeks with no problems at all... play for hours every day.

  In this topic, I have all my info and the crash of the http://windowsforum.com/threads/constant-bsod-while-gaming-bc-code-124-hall-dll-driver.182451/#post-590033 reports
  The last thing I did was reinstall Windows fast and for 2 weeks, I had no problem... but 2 days ago I had another accident with driver hall.dll collection BC 124.
  A way to solve this problem? I lose all hope now... after my quick reinstalled, I thought that the problem disappeared... but 2 days ago, she came back.
  Any help would be really appreciated
  Thanks in advance

  Marco

  According to Ferdinand that it is hardware related.  A re - install will not solve the issue.  Given that the majority of the 124 genuine intel I suggest you run prime 95.

  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.

• help - Fusion 7.1.2 causes BSOD

  Summary:

  I have problems under Windows XP SP2 under Fusion. Everything works with Fusion 7.1.1 but I get constant BSOD with Fusion 7.1.2.

  Details:

  I have some software I use locally and don't care if XP is precarious since I don't leave it up to the Internet. Here's what I did to test and debug:

  (1) I installed Fusion 7.1.1 .dmg. I'm on OS X 10.8.5 on a Macbook Pro with 8 GB of RAM.

  (2) I installed XP Pro SP2 full retail copy of DVD. activated (via the internet). Works very well. My software works.

  (3) after activation of XP, I spend my "Private to my Mac" VM network to keep XP away from the Internet

  (4) merger offers me 7.1.2 update

  (5) I have stop my VM. I'm hosting Fusion update to 7.1.2

  (6) when I restart XP, Fusion will automatically update VMware tools

  (7) all goes haywire

  (8) XP gets repeated BSOD and restarts sometimes as quickly as within 20 seconds, even as I connect

  (9) the BSOD error is STOP c000021a with status 0xc0000005 (sorry I should have taken a screenshot, but did not)

  (10) what can I do?

  More information:

  (11) that I removed the merger, including preferences, Application, library, etc. I rebooted 7.1.1. Everything works again. It is with a copy saved my XP VM I installed under 7.1.1 with the virtual machine that had 7.1.2 VMware tools installed.

  (12) I authorize update to 7.1.2 XP starts to become again BSOD

  (13) I am back on 7.1.1 and won't go again just to get a BSOD 7.1.2 perforated Cap. There is apparently no way to keep 7.1.1 and 7.1.2 on the computer at the same time.

  
  

  Anyone having problems with 7.1.2?

  
  

  Merge only supports XP SP3 (although the workstation supports XP SP2). I don't want to go to SP3 because I don't want all the hassles out XP Activation to the Internet to make its periodic recording of 'windows genuine advantage' with Microsoft. As I said earlier, my software doesn't have Internet so I won't leave XP to the Internet. I just use a shared folder to move data back and forth between OS X and XP.

  I made a mistake trying to stay with XP SP2? I'm fighting a losing battle?

  Should I move my computer to OS X 10.9 or 10.10? Is there a chance that helps?

  Thanks for any help or suggestion.

  
  

  We are aware of a problem with versions of Windows XP before SP3, affecting the installation of the latest tools in VMware Fusion 7.1.2 and Workstation 11.1.2 of.  This thread has more details: regression tools VMware Workstation 11.1.2

  You may be able to install the Microsoft hotfix for article KB921337 solve the problem.

  See you soon,.

  --

  Darius

• Blue screen after Windows Vista SP2 installed on my TouchSmart IQ770

  
  

  All, I came across this thread, after having the same problem (constant BSOD after Vista SP2) installed.  The fix referenced by MS that contains a placeholder file.  However, this most recent patch http://support.microsoft.com/kb/975163/ contains even more recent versions of all the files in question.

  For this installation, I went to safe mode and disabled the wireless network card.  I copied the fix of a usbstick on the desktop.  After the reboot of the machine was stable enough to install this fix (before it would break before the fix might get installed).  After the restart, yet once again, I have reactivated the wireless card.

  The system seems to be stable again (its place for over an hour now, the previous record was 5 minutes approximately from SP2)

  I hope this helps someone to another Google search for Vista SP2 IQ770 BSOD USB

• Windows 10 that requires new activation after motherboard change

  My X 1 carbon (2nd generation) has problems with memory (constant BSOD) and bootloop so endless, so my motherboard has been changed (with the CPU and memory welded) by a subcontractor to Lenovo.

  After turning the computer for the test that I noticed that my Windows 10 license is now uncommitted, and there need a new product key.

  Is there an easy fix for this?

  
  

• LeAPC_INDEX_MISMATCHErreur accident

  "Problem reports" and Solutions tells me that to do with Norton.
  I am not or have never used Norton on this PC?

  Try to run the Memory Diagnostic tool to check your RAM for errors.

  Memory diagnostic tool
  http://www.vista4beginners.com/Windows-Memory-Diagnostics-tool

  How old is your machine?  Everything left as collateral?

  Constant BSOD of various denominations which makes me suspect a hardware problem type.

  Drive manufacturers will have free software diagnostic bootable carefully check the State of the hard drive.

  You have overclocked the machine at all? Setting the Bios to "Safe Defaults", or looking for an update of the available Bios might resolve it?