BSoD: Unknown

Similar Questions

• I can't update of Windows security because of an unknown error. Also, I get frequent BSODS.

  Good, so like I said, when I try to get the security updates, I get a message saying "year error occurred while of updates for your computer." Errors found: Code 80072EFE Windows Update encountered an unknown error. "Code 0 x 80244015 appears when I try the update of Defender.

  I've had this laptop (it's a Toshiba Satellite L305, is told by the way) gave me down and it has a number of problems. Another problem taxing enough, it's that I had frequent dumps. Some programs that I want to uninstall used to uninstall because the uninstall file does not exist. I installed a free Revo Uninstaller Pro trial and that helped, but I still don't know what causes the dumps.

  One of my recent problems with laptop computer is my computer crash dumps whenever I try to open Chrome now. It was working fine, then I would get BSOD as I just described, so I tried to uninstall it and then put it back, and it worked well again for the day, and then it happens again. I think it could be a virus. I also learned that it might be a registry error and I can change my registry, but I know almost nothing about computers, so maybe I need to walk through this.

  I have AVG and I used it to scan the computer and I also scanned with the Defender, and both programs have only seen adware. I don't really think that could do much harm. I'm not sure. Right now, it looks like a big mess of problems.

  I think I should also add that the laptop has no trackpad software installed, or at least that's what it looks like. The former owners told me that the trackpad has never worked. I don't know if that has anything to do with it.

  Any advice will help, please leave as much as possible.

  Thank you

  Blue screens are caused by defective material or defective hardware drivers.

  To see if a fix is available

  In Control Panel (and select Classic discovered in the left pane) select reports on the problems and Solutions (problem of type in the START search box), go to historical problem, right-click of your error and choose check for the Solution. You can also right-click and choose Details for more information. Post the details here.

  To see if any recent system change caused it

  In Control Panel (and select Classic discovered in the left pane) choose Administrative Tools and then choose reliability and performance monitor and choose the monitoring tools then the reliability monitor (type reliability in research on Start). This list is a chart of the software installs, uninstalls, updated Windows and crashes by date (scroll left to see earlier dates). See if your plant has started to happen after you installed or uninstalled something.

  First to test we can the material.

   

  Standard hardware troubleshooting

   

  S.M.A.R.T

  Click Start - All Programs - Accessories - Right click Command Prmodel and choose run as administrator.

   

  Disk in Windows drives monitor for impending failure. The function is called S.M.A.R.T. It detects an imminent failure, 30% of the time. In a type elevated command prompt (it's a single line)

   

  WMIC PATH MSStorageDriver_FailurePredictStatus /namespace:\\root\wmi get active, predictfailure, reason List

   

  If it is on will be true, otherwise on enable in the BIOS of the computer.

   

  Predict the failure must be False if everything is ok.

   

  In Vista and later if SMART failure predicted Windows prompts the user to run the backup.

   

  Run chkdsk

  In computer discs right click and choose Properties, then the Tools tab, and then click check now. Check the TWO boxes and then start. Reset. This will take from one day to the next.

  SFC

  Check the alteration of the file by clicking on Start - All Programs - Accessories - right on command prompt and choose run as administrator. Type

  sfc/scannow

  Diagnosis of memory

  If you have not run a diagnosis of memory, please do. Click on Start - Control Panel - choose Classic view in the left pane - choose Administrative Tools - then memory diagnostic tool.

  For results of Chkdsk

  Click on Start - Control Panel (and select Classic view in the left pane) choose Administrative Tools and then Event Viewer , and then look at the Application and the System will connect (under Windows logs) for entries.

   

  Look for EventID is 7 and Source disk
  Look for EventID is 11 and the Source disk
  Look for EventID is 51 and Source disk
  Look for EventID is 52 and Source disk
  Look for EventID 55 and Source is NTFS
  Look for EventID is 130 and Source is NTFS
  Look for EventID 1001 and Source is Autochk
  Look for EventID 1001 and Source is Winlogon
  Look for EventID 1001 and Source is WinInit
  Look for EventID 1001 and Source is Chkdsk
  
  Look for EventID is 26212 and Source is Chkdsk
   
  Double-click the entry for more details on this entry.
   
  PS 7 and 55 are auto repair codes where windows repair disk errors silently on the fly. 52 is the SMART warning.
   
  For the results of the SFC
  Check the alteration of the file by clicking on Start - All Programs - Accessories - right on command prompt and choose run as administrator. Type
  findstr/c: "[SR] cannot" %windir%\logs\cbs\cbs.log|more "

   

  It will be able to see which files are corrupted. We may be able to copy it from another computer.

   

  For memory diagnostic results

  Click on Start - Control Panel (and select Classic view in the left pane) choose Administrative Tools and then Event Viewer , and then look at the Application and the System will connect (under Windows logs) for entries.

   

  Look for EventID is 1201 or 1101 and Source is MemoryDiagnostic-results

   

  Double-click the entry for more details on this entry.

   

  Analyze dump files

   

  If you want to analyze your own dump files. (C:\windows\Minidump).

  
  Download and install the debugging tools for Windows
  http://msdn.Microsoft.com/en-us/Windows/hardware/hh852363
  Install Windows SDK, but simply choose the debugging tools.

  Create a folder called symbols in C:\

  Start Windbg. Menu - symbol file path of the file and enter

   
  SRV * C:\symbols* http://msdl.microsoft.com/download/symbols

  Close, and then reopen WinDbg. File menu - Open Crash Dump

  It will analyze the crashdump. You must close and reopen WinDbg for each analyzed dump file. Because you download symbols from the internet WinDbg seems to be to do nothing. But it's the download. Be patient.

   
  Looking for a driver or a library system that the incident occurred at the end of the list. Find the file, do a right click then Properties - Details tab. You must update the driver identified.

  Type in the theWinDbg command prompt

   
  ! analyze - v

   

  -v means Verbose and if the accident was created by a program, as opposed to hardware or a driver, it will appear in the middle of the list.

  Or download files minidump to your Public SkyDrive folder and copy the link in the address bar, and I'm going to do an analysis.

   

  SkyDrive is the download file from Microsoft, Windows Live, at https://skydrive.live.com/site.  Read about it at http://explore.live.com/skydrive.

  If you have downloaded one of the Live applications or a website based Live
  e-mail, you already have access to your Skydrive account.

  Put your list of events in the Public folder and copy the link in the address bar.

• Satellite C660 stuck in an infinite loop of BSOD after upgrade to win 10

  Wow what a disaster, this is a machine under windows 7-32 bit Satellite C660 PSC1GA-01E01M stuck in an infinite loop of BSOD.

  The lappy said that it was ok to upgrade to windows 10 so... Yes, I did.
  Now its stuck in a loop without end of BSOD.

  So I decided to use the recover option and reinstall windows 7 and then move from there.
  After mega downloads updates and finally got to the stage where there was no update on the left to get, so I decided to upgrade to windows 10 even once.

  Now stuck in an endless loop of BSOD again.

  Can someone point me to the driver who is a failure, I can get into SafeMode ok, Device Manager has 2 problems

  (1) is under OTHER DEVICES is an unknown device
  (2) is generic pnp monitor

  I tried from Toshiba Web site for updates of drivers for 32-bit windows 8 thinking this could be the best step but the links are bad and the page Web said sorry loser at home...

  Also no network, if I try to logging for the safe mode with networking, he returned to the screens of BSOD...

  HELP PLEASE

  Toshiba has released a list with all Toshiba models supported for upgrading to Windows 10
  http://win10upgrade.Toshiba.com/swup...SPX?region=TEG

  Satellite C660 PSC1GA is not in the list, which means that this model is not supported to win 10 and will not get win 10 drivers.

  However the Win 10 must run on this device, because it meets the essential physical requirements.

  I guess the BSOD loop arise due to some drivers which are not entirely compatible Win 10 and probably these drivers must be removed before making the Win 10 update.

  To check the compatibility follow this procedure:

  • Right-click on the icon 'Get Windows 10' (on the right side of the taskbar), then click on "Check the status of your upgrade".
  • In the app to get Windows 10, click on the menu: (3 lines) and then click on "Check your PC.
  • Now you should see the list of compatibility issues

  Also this kind of problem could be fixed by Microsoft update, as mentioned in this article:
  http://www.Forbes.com/sites/amitchow...s-reboot-loop/

• Start the upgrade to Windows 7 BSOD

  Satellite L300 was running Vista 32 sweet as a nut, never any problems. Upgrading to 7 and twice in the last few weeks have had an error at startup 'Page in the nonpaged area failure'. The Startup Repair utility was not able to fix it, but ok after system startup.

  Journal displays all tests OK except:

  Root cause found:
  ---------------------------
  Unknown error checking: bugcheck 50. Parameters = 0 x 0, 0x931f2493, 0x9d789000, 0 x 0.

  Repair action: repair and checking the integrity of system files
  Result: failed. Error code = 0 x 490

  No change in hardware/software/updates or the failure of the system before the startup problem.

  I would normally think RAM may be suspect, but it seems more likely given the totality of the circumstances that it is Windows 7 that is at fault.

  Any thoughts?

  Hmm. It of always difficult to say what could be the reason for the BSOD
  Above all it s related to a software or hardware problem

  I google a bit and result: failure. Error code = 0 x 490 appears also running Vista OS.
  So it s not associated with Win 7 only

  Maybe it s RAM as you suggested you can try to use only a single module of RAM for test purposes

• Satellite P100: BSOD nv4_disp infinite loop playing a game

  Hello

  I hope you can see my details of my profiling system, but in case you can't, here are the basic details:

  Satellite P100-113; 2x2.0GHz; 2 GB of memory; XP Pro SP3. Go 7600 256 MB - factory core/mem speed 350 / 400 MHz - no overclocking.
  Out of warranty: purchased as a plant-reclamation in 2006. No problem at all until this - great machine!

  I tried for 2 weeks to resolve the formidable 'in nv4_disp infinite loop' blue screen of the problem of death, which occurs when playing company of Heroes Opposing Fronts (COHOF). Original COH has always run without any problem.

  I think I tracked down what is happening. Using RivaTuner, I took a log of data GPU, both in the general use of Windows and by practicing a COHOF game. I had just downloaded a "fix" claimed this infinite loop problem; referenced in the nvidia forum.
  I think it was the only reason that the game did not plant this time, so that I could look at the newspaper. But this has not yet resolved the problem.

  What is clear, according to the journal of Riva, it's the GPU speeds are usually 0/0 on Windows. Then, every few minutes, he crawls up to something like 198/135, for only 10-20 seconds and then again. This, in my opinion, has always happened, because it is accompanied by a rapid acceleration of the fan and a "sigh" to air for a few seconds. The machine has always done since I bought it, and it is not a problem in normal conditions (i.e. not game) use.

  But here'w what happened in the game. After playing about 30 minutes (I noted earlier), the game suddenly stuttered horribly, so I thought it might be breaking. FPS increased from typical of 30-40 something like 0.5 to 2 FPS. And this continued for another 15 minutes (I went to play, with gritted teeth, in order to obtain good log data).

  Looking at the newspaper of Riva, what happened at that time was one of these speed GPU rampdowns: down 351/398 expected 198/198 - just for about 15 seconds, then go back to the top to 351/398. Given that the "infinite loop" error includes a description "device driver entered an infinite loop waiting for the material to answer", I am fairly certain that it is the cause of the infinite loop BSOD: If the GPU suddenly decides to run at reduced speed in half, under heavy load (COHOF has often been described as the ultimate stress-test system) , you expect this kind of error occurs. I suspect that this is the point to which I would have had a crash "infinite loop" - but perhaps the 'fix', I downloaded caught the ball and prevented the usual total crash.

  Temperature: absolutely perfect. I use a Zalman cooler under the machine. Riva reports temperatures GPU 51 c (idle), maxing out at a constant C 66-68 without crampons (load, COHOF). So, my driver unless (I tried 84.4 - later, Toshiba or 91.33, 156.13, 164 something laptopvideo2go.com) is a misinterpretation of the temperature data and imagine that the card needs to be rested (because the driver thinks, it's hitting the ceiling of 115 HP.), is not an overheating problem.

  The fact that go up and down this rise has always happen, even with the original drivers installed at the factory from Toshiba (the regular intermittent fan 'sighs') makes me think that this is part of Toshiba design for integration of the Go 7600 in this machine. Perhaps something of the power management, or to extend the life of the chip. (I have all the settings of power-mgmt software I can find the value "grass of the battery, give me performance", since I usually use the machine plugged).

  Now, it of very well under Windows, does not cause problems. But he won't. The GPU is ramping down, without apparent reason, while COHOF is throwing a huge workload on it.

  Issues related to the:
  1. How can I disable this behavior ramp - at least temporarily to play COHOF? I've never heard of a GPU accelerates its speed goes up and down depending on the load, so I doubt it's problem of nVidia.
  2. can I get an updated driver for this machine? The most recent is 84.4.0. Of course, it is possible to download drivers from laptopvideo2go.com modded-, but I suspect that these pilots to leave out some specific Toshiba 'magical' that manages the specific details of this card in this machine. (p. ex. or SpeedFan and Riva can detect any fans in my system, which suggests that Toshiba took control of the fan "under the hood" somehow).
  3. where can I get an update BIOS/firmware for the Go 7600? You can find anything on the net, apart from that!

  Looks like I need to take this with a hardcore of Toshiba tech (I don't know if Toshiba supports log on this forum); But if someone reads this and has a time "click - I know that this", please post some ideas as to what I can do.

  Hey Buddy

  It seems that this Toshiba forum is only a user forum, and it seems there are only Toshiba users here and not technicians.

  In any case if I understand you problem described in your long ad, the graphic issue appears only this specific game (company of Heroes Opposing Fronts).

  In my opinion, the graphics driver is not fully compatible with this game or your game does not support the nVidia Driver
  So it s not a problem with the laptops hardware, but compatibility issues between the two parties game<->graphics driver software

  I think a graphics driver update (if available) might help.

  Here are my responses regarding the points:

  (1) as I said above, I think that the graphics driver update might help to
  (2) according to my experience, all the latest drivers graphics (and other drivers) are published on the Toshiba driver website
  (3) you can find only a Toshiba BIOS on the Toshiba driver page. BIOS or firmware update graphic card is unknown to me and to be honest I don t think it would exist.

  See you soon

• Satellite L300D - recovery BSOD error + imagex.exe application error

  Hello

  My laptop lost function a while back due to some unknown errors. I managed to get most of the data on safe mode and transferred them on my desk.

  The problem I have now is to fix my laptop. I have since lost my receipt and so unable to guarantee; but I thought that I could restore my computer to its factory condition with the recovery disk that I created. The original problem and I'm facing can be seen here-> http://forums.computers.toshiba-europe.com/forums/message.jspa?messageID=153146#153146<>

  As you can see on this thread, the recovery disk has failed. So, based on the advice I have received, I went to a computer retailer Toshiba Repair Center today and they replaced my hard drive with a SATA 120 GB Fujitsu. Then, I tried to use the recovery disk but ran into a few snags. (1) a BSOD happens randomly during the restoration, i.e. during the copy image it would pop up... sometimes he'd jump upward when it is finalizing the recovery. (2) sometimes, the BSOD will be bipassed, and instead, a mistake would come to 3% installation finalising saying that img could not be copied to the HARD disk in C /:! (3) sometimes a misapplication of image.exe would come saying 'the instruction at 0x77c45a20 referenced memory at 0x00000000. The memory could not be written. Click on OK to terminate the program. »

  NOTE: None of these problems occur in the same resumption of the trial. But they made it up randomly and when they do, I have to restart the computer and try again.

  My question is this. Since the last piece of advice was to replace my faulty HARD drive, and I did, why I am still unable to fix my computer? And if it is not one of the HARD drive, then what is the problem here? I'm desperate to fix my laptop as it is meant to be my 14 year old office replacement. Thank you all for your kind attention; I only hope that there is someone out there who has faced and overcome such a problem before.

  Hello!

  It's not easy to say what the reason is for this. It might be the motherboard, HARD disk or a faulty RAM again. So it could be bad luck that the new HARD drive is also down

  I think you should test something on your laptop with special diagnostics tools.

  http://www.HitachiGST.com/HDD/support/download.htm#DFT
  With the Drive Fitness Test, you can test your HARD drive. Download the CD image, burn it to a CD and boot from it. Then you can test the HARD drive.
  On the same site is a user's guide if you want to know more.

  http://Memtest86.com/
  Memtest86 is a diagnostic tool to check the RAM. Here, you can also download a CD image.
  It s easy to use. Run the test of 3-4 hours and then you will see if the RAM has some errors.

  After that, post your result. Maybe the test is a mistake.
  If this isn't the case, you should try it with a Microsoft installation disc. Maybe the recovery disk is noisy or so

  You can t find something you should go to the ASP again. Talk to the technicians and explain the situation. I think they'll try to help you as quickly as possible.

  Good bye

• On Safari error bsod 89940201

  unknown website "notwhileiameating.com" loading (I'm reasonably sure that's it). kick back, error message w/Safari icon at the top left, code 0 x 80040201 popped up WARNING not2shut / restarting the corruption of registry data. Call the 855-335-7619. I called, they were in need of remote access, I said no / hung up. But now I'm stuck w/2error messages on my screen, I'm afraid I'm going to that slab my iMac.

  BSOD: dllregistersetting detected 0 x 80040201

  Yosemite 10.10.5 OS

  iMac 21.5, end of 2012

  2.7 GHz Intel core i5

  8 GB 1600 MHz DDR3

  NVIDIA GeForce GT 640M 512 MB

  Help?

  It's a scam of javascript. Do not call the number.

  Force Quit Safari and revive all holding the SHIFT key.

• Error message: "Unknown software Exception" Oxc00000td - place: OX76f755ab

  Please:

  At the start: I get this error message: "Unknown software Exception" Oxc00000td

  as well as various slot numbers, for example: oxc00000td

  Thanks for your efforts on my behalf, I'm

  OCHARDON

  We need the DMP file because it contains the single record of the sequence of events that led to the accident, what drivers have been loaded, and what has been loaded.

  You may be able to get the DMP files without crashing by booting in SafeMode (F8) with networking.

  If you are overclocking stop.  (chances are that if you are unsure if you are, you are not)

  To allow us to help you with symptoms BSOD on your computer, download the contents of your folder "\Windows\Minidump".

  The procedure:

  * Copy the contents of \Windows\Minidump to another location (temporary) somewhere on your machine.
  * Zip up the copy.
  * Join ZIP archive to your message by using the button (attachments) "trombone".
  * Please download to a service like Skydrive or "Rapidshare" to share files and put a link to them in your answer.

  To ensure the minidumps are enabled:

  * Click Start, in the search box, type: sysdm.cpl, press ENTER.
  * On the Advanced tab, click Startup and recovery... Settings button.
  * Make sure that automatically restart is unchecked.
  * Under the writing debugging information header, select image partial memory (256 KB) in the list box drop-down (varies from 256kb).
  * Ensure to that small Dump Directory is listed as % systemroot%\Minidump.
  * OK your way out.
  * Reboot if changes have been made.

  Please also run MSinfo32 and download the output as well.

  To run MSinfo32 please go to start > run > MSinfo32
  Go to 'file', 'save' and download the PDF is saved with the DMP
  (Instructions for XP, Vista, Win 7, Win 8)

• BSOD: "a process or thread crucial to system operation has unexpectedly released or ended." Startup Repair does not solve the problem-

  I recently had a serious viral infection on my laptop Windows Vista SP2 Gateway.  After you run the antivirus AVG cleaner, who seemed to have had to quarantine or delete some files infected, System I couldn't Boot Windows to the top on this machine - even in the (all flavors of) Safe Mode.  When you try to start, I'd get

  a Blue Screen of Death with the msg of error in the title of this thread.  Before turning off the crash dump, the system indicated:

  ' * STOP: 0X000000F4 (0 X 00000003 0X85F22848 0X85F22694 0X82A26AB0).

  Other messages in the BSOD said I might have new HW causing the BSOD (I did not - but nevertheless I removed all external HW and tried again - got the same result).

  So one of the first things I did was to capture the startup log, so I could see what the pilots were hang up / does not.  Here's what I found:

  (1) the last driver to load (as indicated in ntbtlog.txt) was monitor.sys.  My understanding is that this indicates that when this driver loaded, the system crashed at this place - suggesting that there is 'something wrong' with this particular driver.  However, it seems likely, that I can use the screen/monitor (built-in) to the laptop without problem.

  (2) several drivers do NOT load: they are:

  1 NDProxy.sys

  2 Kvhfjgcv.sys

  3 Kbdhid.sys

  4 i8042prt.sys

  QUESTION 1: "Monitor.sys" being the last driver to load, should I assume this is the driver the system hung up on (that is, which caused the BSOD)?  And if so, that means I should replace this driver?  If so, how do I do that (how and where can I get a copy of 'Clean/good' of monitor.sys)?

  QUESTION 2: Is it possible to get "good versions" of drivers I listed above which was NOT loaded (I guess they didn't not load because they have been corrupted by the virus or the virus cleaner, or maybe just deleted by the virus cleaner because they were infected) to put into the Windows\System32\Drivers folder?  How?

  Here are the steps I took to try to fix the "corrupt system".  I inserted my Windows Vista DVD into the DVD drive and loaded Windows using that.

  Once that came, I then tried the following (and here are the results for all that I tried):

  (1) I selected the option "Repair", then choose "Microsoft Windows Vista" OS and press "next".  He tried to 'attempt to repair' for 15 minutes about, then finally stopped with a message: "Startup Repair cannot repair this computer automatically.  "Details of problem indicated: (a) the problem event name: StartupRepairV2." Signature 01: ExternalMedia; Signature 02: 6.0.6000.16386.6.0.6001.18000; Signed 03:6; Signature 04:131074. Signature 05: 0xF4; Signature 06: 0xF4; Signature 07:0; Signature 08:2; Signature 09: WrpRepair; Signature 10:5; OS version: 6.0.60090.2.0.0.256.1

  (2) I selected the option 'display diagnostic and repair details '.  He said that all tests successful (error code = 0 x 0), and

  then indicated the 'cause': ' unknown error checking: bugcheck f4, parameters = 0x3, 0x88607b80, 0x88607ccc, 0x82a78ab0. "

  - AND -

  Repair action: repair and checking the integrity of system files.  Result: failed.  Error code = 0 x 5

  (3) I checked that the restoration of the system, and even though I know I had some Restore Points created at the origin of this system, System Restore has indicated that there was no restore points to go back, (leading me to believe that the virus must have killed)

  (4) so I chose the selection "Command Prompt", which opens by default "X:\Sources >".  I'm in C: and then typed: "sfc/scannow".  The system has responded with the following messages:

  "Start system analysis.  This process will take time. " follow up 30 seconds later by the message:

  "Windows resource protection could not perform the requested operation".

  MAIN QUESTION: any reflection on what other tools and options I try to repair the windows installation / driver set?

  Hello

  I suggest you follow the steps below:

  Method 1:

  Follow the steps in the link and check if the problem persists:

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

  Method 2:

  Connect over winre and rename the driver files that he talked with *.old quick order. You can find these % system32%. Follow these steps:

  a. use the Windows 7 DVD to start the computer from Windows Recovery (WinRE).

  b. in WinRE, open a command prompt. To do this, follow these steps:

  On the screen to install Windows, select the appropriate language to install, time and

  currency format and keyboard or input method options and then click Next.

  c. click on repair your computer.

  d. click 7 installation you want to repair, and then click Next.

  e. click on command prompt.

  f. navigate to % system32% and rename old files 8.

  Method 3:

  After step above the computer restarts. Run the System File Checker tool to troubleshoot missing or corrupted system files. Follow the steps from the link:

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

• HP Pavilion DV7-1232nr XP Downgrade BSOD

  HP Pavilion DV7-1232nr

  During Downgrade XP, BSOD when it cannot load the RAID driver twice during install of FDD. He can run the F6 driver during the first part of the installation.

  I have of course there is this driver issue, but cannot get the unit up to install it. Even a Bart PE BSOD drive. Need to down grade to allow most of my business software to run. Custom in Vista.

  Thank you

  Have you tried my suggestion above for the ACPI\PNP0C32\1 of unknown devices?

  Try of BUS SM > South Bridge Driver, here

• Some rather illusory BSOD and crashes on windows 7.

  So for the past month I have been doing some strange crashes and BSOD that have been in every sense. I've been on Reddit and impossible to get a solution, I have reformatted, which does not set it. I've been on with the technical support of Microsoft support chat and can not get a definitive answer (they spend hours and a symptom of trouble then send me on my way). Accidents and the BSOD happen a crapton all in one day, it's good for several days, then it's a crapton while a new day. I just assumed it was graphics so I uninstalled and reinstalled. No solution. I assumed it was ram, so I change RAM, using just a single chip, get chips on other computers, including the chip switch is in what location, perform a test of memory, no solution.

  Apart from just BSOD I have therefore also get those pips weird screen that blur the screen and resemble a classic movie scene where a security monitor is hacked. Or sometimes I can be working away and suddenly the computer starts up without ever giving any warning or anything.

  Here are the BSOD logs that I have. He did TONS more than that, but more often it does not really give me a journal later.

  Crash Dump Analysis

  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

  Thursday, October 6, 2016 10:33:43 PM GMT crashed your computer
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: unknown (0xFFFFF80002D38344)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002D38344, 0xFFFFF880067AAD40, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  A third-party driver has been identified as the likely cause of the system error.
  Google search: SYSTEM_SERVICE_EXCEPTION

  Thursday, October 6, 2016 20:18:22 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\100616-25740-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0 x 70150)
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Monday, October 3, 2016 17:22:27 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\100316-48391-01.dmp
  This was probably caused by the following module: atikmpag.sys (atikmpag + 0x780C)
  Bug check code: 0 x 116 (0xFFFFF8800490080C, 0xFFFFFA8007F784E0, 0 x 2, 0 x 0)
  Error: VIDEO_TDR_ERROR
  file path: C:\Windows\system32\drivers\atikmpag.sys
  product: AMD driver
  company: Advanced Micro Devices, Inc..
  Description: multi-vendor AMD driver miniport
  Bug control description: This indicates that an attempt to reset display driver and recover a timeout failed.
  A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: atikmpag.sys (AMD several suppliers Miniport Driver, Advanced Micro Devices, Inc.).
  Google search: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR

  Saturday, September 24, 2016 9:53:06 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092416-62416-01.dmp
  This was probably caused by the following module: atikmpag.sys (atikmpag + 0x780C)
  Bug check code: 0 x 116 (0xFFFFF8800453A80C, 0xFFFFFA800D828010, 0 x 2, 0 x 0)
  Error: VIDEO_TDR_ERROR
  file path: C:\Windows\system32\drivers\atikmpag.sys
  product: AMD driver
  company: Advanced Micro Devices, Inc..
  Description: multi-vendor AMD driver miniport
  Bug control description: This indicates that an attempt to reset display driver and recover a timeout failed.
  A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: atikmpag.sys (AMD several suppliers Miniport Driver, Advanced Micro Devices, Inc.).
  Google search: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR

  Thursday, September 22, 2016 6:59:12 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092216-29250-01.dmp
  This was probably caused by the following module: tcpip.sys (tcpip + 0x52A73)
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  path to the file: C:\Windows\system32\drivers\tcpip.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: driver TCP/IP
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Tuesday, September 20, 2016 17:47:17 this computer crashed
  crash dump file: C:\Windows\Minidump\092016-62213-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0x5A88)
  Verification of error code: 0 x 24 (0xFFFFF8800A5E5A48, 0xFFFFF8800A5E52A0, 0x1904FB, 0xFFFFF880012A94E4)
  Error: NTFS_FILE_SYSTEM
  file path: C:\Windows\system32\drivers\ntfs.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT file system driver
  Bug control description: This indicates there is a problem in the NTFS file system.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Monday, September 19, 2016 5:38:40 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\091916-39905-01.dmp
  This was probably caused by the following module: unknown (0xFFFFF880013E86E4)
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  A third-party driver has been identified as the likely cause of the system error.
  Google search: KMODE_EXCEPTION_NOT_HANDLED

  Hello

  Although there may be other factors at play that video drivers ATI are involved as well
  Check with Support ATI, their drivers and documentation online and ask for their
  Forums about known problems.

  AMD/ATI - assistance and pilot - search
  http://support.AMD.com/us/psearch/pages/psearch.aspx?type=2.4.2&product=2.4.2.3.9&ContentType=GPU+download+detail&OSType=Windows+8+Preview+-+32-bit+Edition&keywords=&items=20

  Download the Catalyst Drivers here
  http://game.AMD.com/us-en/drivers_catalyst.aspx

  ATI - Forums
  http://forums.AMD.com/game/categories.cfm?CATID=260&forumid=11

  ATI - Support and drivers
  http://support.AMD.com/us/pages/AMDSupportHub.aspx

  However, given that you re-installed Windows there must be a hardware or BIOS.
  driver Chipset or other very low level driver problem. So anything you can update and
  use the other methods below.

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

  Resolution in Windows 7 stop errors (blue screen) - has a section because if you
  may or may not start Windows.
  http://Windows.Microsoft.com/en-us/Windows7/resolving-stop-blue-screen-errors-in-Windows-7

  Vista and Windows 7 updated drivers love then here's how update largest. References to the Vista also apply to Windows 7.

  It's my generic how updates of appropriate driver: (updating the video/display driver and BIOS)

  This utility, it is easy see which versions are loaded: run DriverView - see
  Hide Microsoft drivers - updated those without drain in their names. (Also update BIOS and drivers from the chipset.)

  -Free - DriverView utility displays the list of all device drivers currently loaded on your system. For each driver in the list, additional useful information is displayed: load address of the driver, description, version, product name, company that created the driver and more.
  http://www.NirSoft.NET/utils/DriverView.html

  For drivers, visit manufacturer of emergency system and of the manufacturer of the device that are the most common. Control Panel device - graphics card configuration-manager - note the brand and complete model of your graphics driver - double-click - tab - write version information. Now, click the driver update (this can do nothing as MS is far behind the certification of drivers) - then do a right click - Uninstall - REBOOT it will refresh the driver stack.

  Repeat for network - card (NIC), Wifi network, sound, mouse, and keyboard if 3rd party with their own software and drivers and the other main device drivers you have.

  Now go to the website of the manufacturer of system (Dell, HP, Toshiba as examples) (restoration), then site of the manufacturer of the device (Realtek, Intel, Nvidia, ATI, for example) and get their latest versions. (Review of the BIOS, Chipset and software updates on the site of the manufacturer of the system while there).

  Download - SAVE - go to where you put them - right click - RUN AD ADMIN - REBOOT after each installation.

  Always check in the Device Manager - tab drivers version you install actually shows up. This is because some restore drivers before the most recent is installed (particularly that audio drivers) so install a driver - reboot - check that it is installed and repeat if necessary.

  Repeat to the manufacturers - BTW on device at the DO NOT RUN THEIR SCANNER - manually check by model.

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

  Installation and update of drivers under Windows 7 (updated drivers manually using the methods above is preferable to ensure that the latest drivers from the manufacturer of system and device manufacturers are located)
  http://www.SevenForums.com/tutorials/43216-installing-updating-drivers-7-a.html

  If you update the drivers manually, then it's a good idea to turn off the pilot facilities in Windows updates, that leaves is to Windows Update, but it will not install the drivers who are generally older and cause problems. If updates offers a new driver and then hide it (right click on it), then go get new ones manually if you wish.

  How to stop Windows 7 automatically install drivers
  http://support.Microsoft.com/kb/2500967

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

  Tests of memory intercept all errors, such as memory do not match (possible even for poles that seem identical) and how faster memory is placed in system behind the slower memory. Also is it better to Exchange also sticks in and out to check for those, even if all the tests of memory do not show a problem.

  To test the RAM here control - run 4 + hours or so.<-- best="">
  www.memtest.org

  For the Windows Memory Diagnostic tool.

  Start - type in the search-> memory box - find top - right click - Memory Diagnostics tool follow RUN AS ADMIN instructions

  Windows Vista: How to scan / test your memory with Windows Vista memory or RAM
  Diagnostic tool
  http://www.shivaranjan.com/2007/11/01/Windows-Vista-how-to-scan-test-your-RAM-or-memory-with-Windows-Vista-memory-diagnostic-tool/

  How to run the diagnostic tool memory in Windows 7
  http://www.SevenForums.com/tutorials/715-memory-diagnostics-tool.html

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

  After doing ALL the updates you canand if the problem persists, run
  DriverVerifier.

  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. (8/8.1 and 10)
  are essentially the same).
  http://www.WinVistaClub.com/T79.html

  Using Driver Verifier
  https://msdn.Microsoft.com/en-us/library/Windows/hardware/ff545448%28V=vs.85%29.aspx?f=255&MSPPError=-2147217396

  WINDOWS key + X - RUN - type-> auditor/reset press ENTER to disable

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

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

  I hope this helps.
  --------------------------------------------------------------------------------------------
  Rob Brown - Microsoft MVP<- profile="" -="" windows="" and="" devices="" for="" it :="" bicycle="" -="" mark="" twain="" said="" it="">

• Serscan.sys ntoskrnl.exe BSOD

  I started having BSOD pointing to ntoskrnl.exe and serscan.sys. Before the accident, the system gets very insensitive. The Task Manager displays all the information Resource Monitor gets even worse. When I reboot I get BSOD. After a few resets the system up live. I scanned for malware and found nothing. Antivirus shows as well clean. HD Tune says Spin Retry count slightly exceeds threshold and an unknown attribute of a same drive on another more transferred sector Count. There is more than one drive, but HD Tune does not show health is probably that it is 2 TB. It would then be memory or maybe something else? BSOD SkyDrive here

  The accident was reported as being caused by DISK_HARDWARE_ERROR: a closer examination gives us a clue.

  Process of own fffffa800b83b380 Image: RapportService

  0: kd >! THREAD
  GetPointerFromAddress: unable to read from fffff800036ff000
  WIRE fffffa800a968640 Teb 13c8.1678 Cid: 00000000fff9e000 Win32Thread: 0000000000000000 PROCESSOR 0
  Borrow not identity
  GetUlongFromAddress: cannot read fffff8000363dbf0
  Owning process fffffa800b83b380 Image: RapportService
  Joint process s/o Image: n/a
  fffff78000000000: cannot get shared data
  Wait start TickCount 1985375

  You could do either of two things. Completely uninstall 'Trusteer report' and wait to see if the system crashes again, or you can force a crash by running the Driver Verifier, to help locate the faulty module, then post a link to the dump file here, resulting in the body of your next post.

  Driver Verifier - stalking a bad driver to behave.

  http://answers.Microsoft.com/en-us/Windows/wiki/windows_10-Update/Driver-Verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4B6D-95b3-c48669e4c983

• BSOD on shutdown associated ntoskrnl.exe

  Hello, today I got the BSOD when stop twice. I used the blue screen and it showed that this problem related to ntoskrnl.exe. I here enclose the direction in the dump file. Please help me solve this problem. https://onedrive.live.com/redir?RESID=7B7FCCC78623B4E2%21153

  The unknown device below, is your laptop free fall sensor driver. Please install the driver using the link below.

  [Peripheral problem]

  Error code of device device PNP ID
  Not available ACPI\SMO8810\1 the drivers for this device are not installed.

  ST Microelectronics free fall sensor driver.

  http://www.Dell.com/support/home/us/en/04/drivers/DriversDetails?driverId=CWHJC&FILEID=3201714739&osCode=W764&ProductCode=Alienware-17&LanguageCode=en&CategoryID=UT

  Uninstall Bitdefender, using the uninstall program following the link. Install Microsoft Security Essentials, at least temporarily, until what stabilize us your system.

  Uninstall tools for Bitdefender products.

  http://www.BitDefender.com/uninstall/

  Microsoft Security Essentials.

  http://Windows.Microsoft.com/en-us/Windows/Security-Essentials-download

  Then,.

  You sometimes have a GoFlex, FreeAgent or OneTouch Seagate external drive attached to this system. Please make sure that the drivers for this device are installed correctly, if you do.

  Installing software FreeAgent GoFlex, or OneTouch does not start automatically in Windows.

  http://knowledge.Seagate.com/articles/en_US/FAQ/205515en

• [BSOD] My PC crashed while multi-tasking DMP file Dump analysis required

  Hey everyone I need help trying to figure out why my computer freezes or faces BSOD...

  C:\Windows\Minidump\122514-14913-01.dmp

  Is recovered.

  Link to the dump is https://onedrive.live.com/redir?resid=4A2C6A8186FB95F9%21114

  I don't know how to analyze it but if someone can tell me what is needed to be useful

  ITZ

  This DMP has been altered and of little use.  It does not specify what related material but not that little material.  If you have other DMP files download them.  Meanwhile, 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.

  This is called a BCC124 and is linked to the material

  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" install Windows re: 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/

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