Windows 7 BSOD, minidumps uploaded to skydrive

Similar Questions

• Windows 7 BSOD when changing between LAN and Wifi network

  I have users to get BSODs during network between LAN and Wifi. There is not much information in the dump file.

  Any idea what could be causing this BSOD, and what can be done to correct?

  I can send the dump file if anyone is interested in looking at.

  Thank you

  Manish

  Hello

  1st thing I would do is update the card interface (wired) NETWORK and WiFI (wireless) drivers.

  Suspect also any 3rd party antivirus. Uninstall it and use MSE - free at least test.

  List of tools to clean/uninstall anti-malware programs
  http://answers.Microsoft.com/en-us/protect/wiki/MSE-protect_start/list-of-anti-malware-product-removal-tools/2bcb53f7-7ab4-4EF9-ab3a-6aebfa322f75

  Uninstallers (removal tools) for common antivirus software
  http://KB.eset.com/esetkb/index?page=content&ID=SOLN146

  MSE - free
  http://www.Microsoft.com/en-US/Download/details.aspx?ID=5201

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

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

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

  http://answers.Microsoft.com/en-us/Windows/Forum/Windows_7-system/sometimes-i-get-a-blue-screen-when-using-IE-8/c675b7b8-795f-474d-a1c4-6b77b3fcd990

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

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

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

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

  Also this, so you can see the probable bluescreens.

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

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

  Check out these utilities to see if information may be collected:

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

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

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

  MyEventViewer can be verified at the time of the blue screen (BSOD) to in a
  second or so time of the BSOD to provide more information as possible
  cause: see TIP.

  MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
  TIP - Options - Advanced filter allows you to see a period of time instead of the whole of the record-
  Set it for a bit before and after the time of the BSOD.
  http://www.NirSoft.NET/utils/my_event_viewer.html

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

  AppCrashView - free - a small utility for Windows Vista and Windows 7 which shows the
  Details of all application crashes occurred in your system. The information of the plant are extracted
  the .wer files created by the Windows Error Reporting (WER) of exploitation component
  system each time that an accident has occurred. AppCrashView also allows you to easily record the
  list of accidents to the text/html/csv/xml file.
  http://www.NirSoft.NET/utils/app_crash_view.html

  I hope this helps.

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

• Windows 7 BSOD - ntoskrnl.exe (nt + 0x7F1C0)

  I have this problem since April, 2012

  HP support suggested that I should reinstall windows 7. I did some time at the beginning of August, but the problem persists.
  Help, please! Otherwise, I'll keep change the OS with a Microsoft OS No.
  Here are the dumps:
  (Local) information system
  computer name: RADU-PC
  Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
  Windows dir: C:\Windows
  CPU: GenuineIntel Intel (r) Core i5 CPU M 520 @ 2.40 GHz Intel586, level: 6
  4 logical processors, active mask: 15
  RAM: 4145868800 total
  VM: 2147352576, free: 1943330816

  Crash Dump Analysis
  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

  Sat 29-Sep-12 12:56:36 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092912-34632-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003344E30, 0xFFFFF8800AEE8C70, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  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 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.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Sat 29-Sep-12 12:56:36 GMT crashed your computer
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: bcm42rly.sys (BCM42RLY + 0 x 1280)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003344E30, 0xFFFFF8800AEE8C70, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\drivers\bcm42rly.sys
  product: Broadcom iLine10 (TM) PCI network card
  company: Broadcom Corporation
  Description: Broadcom iLine10 (TM) PCI network adapter Proxy Protocol Driver
  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. It is suggested that you search for an update the following driver: bcm42rly.sys (Broadcom iLine10 (TM) PCI network adapter Proxy Protocol Driver, Broadcom Corporation).
  Google search: bcm42rly.sys Broadcom Corporation SYSTEM_SERVICE_EXCEPTION

  Sat 29-Sep-12 12:47:59 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092912-34772-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003347E30, 0xFFFFF8800BCDCC70, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  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 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.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Sat 29-Sep-12 12:39:07 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092912-35552-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000333CE30, 0xFFFFF88008D9CC70, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  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 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.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Fri 28-Sept-12 07:30:24 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092812-35630-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003389E30, 0xFFFFF8800C0C5C70, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  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 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.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Fri 28-Sept-12 07:20:56 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092812-58531-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003349E30, 0xFFFFF8800ACA9C70, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  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 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.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Play 27 Sept - 12 22:01:30 GMT your computer crashed
  crash dump file: C:\Windows\Minidump\092712-21606-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x1A (0xFFFFFA8000532F50, 41790, 0 x 0 x 0, 0xFFFF)
  Error: MEMORY_MANAGEMENT
  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 an error occurred serious memory management.
  This could be a case of corruption of memory. The corruption of memory more often happens because of software errors in the defective drivers buggy, not because of RAM modules.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Play 27 Sept - 12 09:26:28 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092712-30108-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x19 (0 x 22, 0 x 20000000000000, 0x0, 0x0)
  Error: BAD_POOL_HEADER
  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 pool header is corrupt.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This could be a case of corruption of memory. The corruption of memory more often happens because of software errors in the defective drivers buggy, not because of RAM modules.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  The sea 26-Sept-12 07:12:30 GMT your computer crashed
  crash dump file: C:\Windows\Minidump\092612-19734-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0x5A88)
  Verification of error code: 0 x 24 (0xFFFFF8800996BAE8, 0xFFFFF8800996B340, 0x1904FB, 0xFFFFF88001231A74)
  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.

  Mar 25 - Sep - 12 20:55:48 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092612-22354-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x7A (0xFFFFFFFFC0000005, 0xFFFFFA8004646060, 0x1, 0xFFFFF680000B1000)
  Error: KERNEL_DATA_INPAGE_ERROR
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: this bug check indicates that the data page of the kernel of the required paging file cannot be read into memory.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  The game 20-Sept-12 15:08:27 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092012-53929-01.dmp
  This was probably caused by the following module: win32k.sys (win32k + 0xC6A12)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000116A12, 0xFFFFF8800AC5B130, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\win32k.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: Multi-User Win32 Driver
  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.
  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.

  Wednesday, August 7, 12 10:29:53 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\080712-41917-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x71F00)
  Verification of error code: 0 x 50 (0x0, 0xFFFFF8000311445B, 0xFFFFF8A00B2DF000, 0 x 2)
  Error: PAGE_FAULT_IN_NONPAGED_AREA
  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 invalid system memory was referenced.
  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.

  Wednesday, August 7, 12 10:08:21 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\080712-53305-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x1A50F3)
  Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002DBB0F3, 0xFFFFF880031A18B8, 0xFFFFF880031A1110)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  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 system thread threw an exception who 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.

  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.

  If you are overclocking STOP

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

  Please follow these instructions to collect data against crashes and upload them here, to your Skydrive or a service such as Rapidshare file sharing.

  http://www.SysNative.com/forums/showthread.php/68-blue-screen-of-death-%28BSOD%29-posting-instructions-Windows-8-7-amp-Vista?p=303&viewfull=1#post303

  http://SysNative.com/0x8/BSOD_Windows7_Vista_v2.64_jcgriff2_.exe

  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 contents of this folder
  Please, upload to skydrive or a file sharing service and put a link to them in your next post.

  Go to start > search/run > cmd > msinfo32 and include it in the upload

  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.

  http://www.SysNative.com/forums/showthread.php/325-BSODs-but-no-dump-files

  http://www.osronline.com/article.cfm?article=545

  Please also go to start > run > msinfo32 and record the results.  Send it with the DMP files, thank you.

• Windows 7 BSOD Lenovo T410

  I'm getting intermittent BSOD on my Lenovo T410.

  It is the output of the text file of the blue screen.  As soon as I can I'll post the minidump on my skydrive. (Current wireless connection has blocked access to SkyDrive)
  Thanks for anyhelp.
  ==================================================

  Dump file: TB-42869 - 01.dmp 102413

  Crash time: 24/10/2013-07:53:08

  Bug Check String: IRQL_NOT_LESS_OR_EQUAL

  Bug check code: 0x1000000a

  Parameter 1: 0xf0e72de8

  Parameter 2: 0x00000002

  Parameter 3: 0x00000000

  Parameter 4: 0x83acdd40

  Caused by the driver: ntoskrnl.exe

  Caused by the address: ntoskrnl.exe + 7ad40

  File description: NT kernel & system

  Product name: Microsoft® Windows® Operating System

  Company: Microsoft Corporation

  File version: 6.1.7601.18247 (win7sp1_gdr.130828 - 1532)

  Processor: 32-bit

  Plant address: ntoskrnl.exe + 7ad40

  Stack address 1: ntoskrnl.exe + 7abce

  Stack address 2: ntoskrnl.exe + 7ab99

  Battery 3 address: ntoskrnl.exe + 82c26

  Computer name:

  Full path: C:\Windows\Minidump\102413-42869-01.dmp

  Number of processors: 4

  Main version: 15

  Minor Version: 7601

  Size of the dump file: 181 625

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

  Paul

  Please let us know how you solved your problems.

  When you are satisfied with your problem is solved, please mark the answer. It helps others see what answered your question.

  I had a question and that someone else posted the answer. How it mark as answer?

  If you posted the original question, you can mark the question as yourself have. Just click the mark as answer button.
  Source: http://answers.microsoft.com/en-us/page/faq#faqAskQuestion8

• Windows 7 BSOD and receiver code error BCCode: 9f

  Original title: Windows 7 BSOD
   
  Hey guys I just built my first system and it was a lot. I used the trial version of Windows 8 64-bit for about a week I had to wait for my windows 7 to arrive. Windows 8 everything went fine with no problems. Then I installed windows 7 and ever since then, every time I leave my system alone for an hour or two, I'll be back to see that it crashed because of this error message below. Can I use my computer all day, video, editing, etc, but when I close all and leave for an hour, I'll be back to see that I have broke down. I try to leave it overnight to install my steam on games but crashes after about an hour.
  Any help would be great.
  Error message:
  Signature of the problem:
  Problem event name: BlueScreen
  OS version: 6.1.7601.2.1.0.256.48
  Locale ID: 1033
  More information about the problem:
  BCCode: 9f
  BCP1: 0000000000000003
  BCP2: FFFFFA80070A4A10
  BCP3: FFFFF800047C43D8
  BCP4: FFFFFA80097AB010
  OS version: 6_1_7601
  Service Pack: 1_0
  Product: 256_1
  Files helping to describe the problem:
  C:\Windows\Minidump\122112-20077-01.dmp
  C:\Users\Ryan\AppData\Local\Temp\WER-58203-0.SysData.XML
  Read our privacy statement online:
  http://go.Microsoft.com/fwlink/?LinkId=104288&clcid=0x0409
  If the online privacy statement is not available, please read our offline privacy statement:
  C:\Windows\system32\en-US\erofflps.txt
  Data sheet:
  Intel i5 3570 k @3.4 ghz
  Cooler Master Hyper 212 Evo
  Z77 UD5H Gigabyte motherboard
  EVGA Gtx 670 FTW
  Corsair Vengeance 8 GB 1600
  Corsair HX 750w PSU
  Seagate Barracuda 7200 rpm 1 TB
  Cooler Master Storm Stryker
  Edit: I thought it might have something to do with memory, so I ran Memtest 86 + 4 hours and had no error: P

  Hello

  Thanks for posting your query in Microsoft Community!

  According to the description, you are receiving BSOD (Blue Screen of Death) and receive the error code BCCode: 9f.

  To help you to propose measures to solve the problem, I would appreciate if you could answer the following question:

  Did you do changes on the computer before the show?

  I suggest to follow the steps of the items listed below and check if it works.

  Error message when you try to resume a Windows 7 or Windows Server 2008 R2 to Hibernate computer-based: "Stop 0x0000009F"

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

   

  Stop error when you upgrade a computer that is running Windows 7 or Windows Server 2008 R2 standby or into hibernation, or when you restart the computer: "0x9F".

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

   

  stop "0x0000009F" error message when a computer enters and fate of putting into hibernation in Windows 7 or Windows Server 2008 R2

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

  Hope this information helps. For any other corresponding Windows help, do not hesitate to contact us and we will be happy to help you.

• Windows 8, BSOD bugcheck 3B, ATI

  My machine crashed and when I try to check for solutions to a problem, the service is unable to download files to windows error reporting. I put the minidump on my skydrive here http://sdrv.ms/1h3ntG5

  Of a Dumpcheck on the minidump file

  Bugcheck 3B {c0000005, fffff880076650b5, fffff8800f42f050, 0}

  Probably caused by: atikmpag.sys (atikmpag + 480b 5)

  The blue screen that has happened when you try to view a flash video in Internet Explore.

  Install the latest driver for ATI graphics card. You can download ATI form site.

  After installation, restart and monitor the system.

  Ded9

• Windows 7 blue screen (file uploaded to SkyDrive minidump)

  I am running Windows 7 Ultimate 32-bit, updated since Vista. I get a blue screen every 1-3 days with no special action takes place.  Minidump file is available at:

  http://CID-f669dc5583876d16.SkyDrive.live.com/self.aspx/Windows%207%20Blue%20Screen%20Issue/010610-25781-01.dmp

  Any help is appreciated!

  Ron

  Just a final note to all those who might find this thread. I have finally saved my entire system, reinstalled Windows 7 from scratch and re-installed everything being of course to only load Windows 7 approved drivers and programs.  It was a good exercise, but the blue of the system proposed once more with the same error. The next step was to download Microsoft Memory Diagnostic program and place it on a bootable CD. I ran the tests extended for several hours, and it turns out a number of memory errors. I bought a set of replacement of memory, test it too (no error after 10 full hours of testing). So I hope I've chased it away.

  IMPORTANT: Before you spend hours (days, months) looking for a software solution, be sure to carefully check your memory before you do!

• Windows 7 BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

  Hey, I really need help with this problem, today 13/10/2013, I got a BSOD at 04:14. For more details, I enclose the minidump here:

  https://SkyDrive.live.com/?v=FirstRunView#CID=ffeb8e1ecdbb1c20

  If you could help me I will be very proud. Cordially, Cristian.

  Thank you!

  The attached file of the DMP is the error checking SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) .

  This indicates that a system thread threw an exception who did not catch the error handler.

  Bugcheck 1000007E, {c0000005, 82e24734, 8ab1f648, 8ab1f220}

  ^^ The 1st parameter of error c0000005 checking indicating an access violation has occurred, we will see what caused:

  : kd > .exr 0xffffffff8ab1f648
  ExceptionAddress: 82e24734 (nt!) RtlEqualUnicodeString+ 0x0000002f)
  ExceptionCode: c0000005 (access violation)

  It was caused by RtlEqualUnicodeString which is the routine compares two Unicode strings to determine if they are equal. Most likely a related device driver.

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

  Remove and replace avast! with Microsoft Security Essentials for purposes of troubleshooting temporary:

  avast!-removal tool from http://www.avast.com/uninstall-utility

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

  In your list of drivers loaded, dtsoftbus01.sys figure who is the driver for Daemon Tools. Daemon Tools is a very popular cause of BSOD in 7/8 base systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

  Kind regards

  Patrick

• 8 windows multiple BSOD errors

  I had a HARD drive on my system to Windows 7. I wanted to install a SSD and move to Windows 8. I bought a Samsung EVO 250 GB Solid State Drive and have had any other problems with Windows 8. I can still update Windows without having a BSOD. Here is a list of the BSOD errors I received in 24 hours:

  PAGE_FAULT_IN_NONPAGED_AREA (Ntfs.sys) (fltmgr.sys)

  DRIVER_IRQL_NOT_LESS_OR_EQUAL (dxgmms1.sys) (nvlddmkm.sys)

  System_service_exception (no data) (nvlddmkm.sys)

  Each parenthesis is a different phenomenon and there are many others. I don't know if it's my real SSD which is a failure or if the controller is not compatible with Windows 8, or if any other piece of hardware is not. I tried updating, deleting, adding updates, firmware and drivers and nothing is.

  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.

  
  

  WE NEED AT LEAST TWO FILES DMP TO SPOT TRENDS AND TO CONFIRM THE DIAGNOSIS.

  
  

  If you're overclocking (pushing components beyond their design) return you to default at least until the crash is resolved. If you don't know what it is that you're probably not overclocking.

  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 (compress)

  * Please download to a service like Skydrive or "Rapidshare" to share files and put a link to them in your answer.

  Link to find out how to download below.

  http://www.WikiHow.com/use-SkyDrive

  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

  System specs are extremely useful then please include everything you know.

  
  

  Blue screen view and that crashed are often wrong and should only be used in case of emergency...
  
  
  You can learn more about BSOD here
  You will learn how to test your memory here 
  An effective question gets help more quick read how here

• Windows 7 BSOD page_fault_in_nonpaged_area with IRQL_LESS_THAN_OR_EQUAL meeting

  Hello

  I get the BSOD frequently for every 10-15 minutes with BSOD IRQL_LESS_THAN_OR_EQUAL and page_fault_in_nonpaged_area and other error messages like 7F, 9A etc. I downloaded the dmp in the C:\windows\minidump folder files to the link below. Can you please help me solve the problem?

  https://SkyDrive.live.com/?CID=0A1C9391BACB2CBB&ID=A1C9391BACB2CBB%21119

  I recently updated my system in Windows Vista Home Premium to Windows 7 Home Premium. My laptop is HP Pavilion dv2500t CTO Notebook PC. I searched the site of hp for the latest drivers for windows 7 and they have no drivers for windows 7 for my laptop model.

  Please let me know if you need more details on my side.

  Thanks in advance for your help.

  Kind regards

  Kumar

  Hello
  Click on the link below:

  Windows 7 Upgrade Guide for dv2000 models

  There are a lot of updated for Windows 7 drivers.

  Please install important drivers there are two for you right now:

  • Intel chipset
  • Intel Rapid Storage

  This approach will solve one of the BSOD problems.

  When you do this test run it please for the RAM and HARD drive.
  In this guide, you will find information how you can do this:
  How to test the RAM and HARD drive (HDD).

  PS.

  I don't recommend integrated BIOS test tools.

  It will be much more better if you do this with the 3rd party tools that are recommended by me in above guide.

• Windows Vista BSOD for years that I can't fix.

  Greetings,

  I have Windows Vista on my Gateway Gt5622. Every year or so I had to wipe the computer and re install Vista with drive manufacturer. The reason is that I get BSOD that I can't solve. It always seems to be something of a problem kernel or windows software. I have recently just re installed vista, everything seems to be ok. I spent a few days to install all updates and not a BSOD. He started happening after installing SP2. The only program I have is Norton 360 and 1 game called Tibia. I know that the problem is not one of those. I don't have any additional hardware installed either. Here's a copy of my BSOD file. If someone could help me please I would be very happy! Thank you for your time. Randy

  Bug Check String: MEMORY_MANAGEMENT

  Bug check code: 0x0000001a

  Parameter 1: 0 x 00041287

  Parameter 2: 0x00834c76

  Parameter 3: 0x00000000

  Parameter 4: 0x00000000

  Caused by the driver: ntkrnlpa.exe

  Caused by the address: ntkrnlpa.exe + 98292

  File description: NT kernel & system

  Product name: Microsoft® Windows® Operating System

  Company: Microsoft Corporation

  File version: 6.0.6002.18881 (vistasp2_gdr.130707 - 1535)

  Processor: 32-bit

  Plant address: ntkrnlpa.exe + 98292

  Stack address 1: ntkrnlpa.exe + 4dde4

  Stack address 2: ntkrnlpa.exe + b2fa8

  Battery 3 address: ntkrnlpa.exe + b2f7e

  Full path: C:\Windows\Minidump\Mini102114-01.dmp

  Number of processors: 2

  Main version: 15

  Minor Version: 6002

  Level the size of the file: 143 104

  Patrick,

  I installed the graphics card and so far so good. I'll put my soundcard in tonight. Ill keep you updated.

  Thank you

  Randy R.

• Windows 7 BSOD

  We have recently started getting BSOD on Dell XPS8700 with 16G of Ram, processor I7, Windows 7 Professional.

  The error is caused by ntkrnlmp.exe, process name: audiodg.exe and (sometimes) can be triggered by her disconnect and reconnect the speaker/headphone cable or line-in cable.

  Some of the information from the Minidump is listed below, and zipped Minidump and MSInfo files have been downloaded on this link OneDrive:

  https://onedrive.live.com/redir?RESID=685745AE9B3E889E! 106 & authkey =! AOCyTvAkAsOQbVc & ithint = % 2czip

  You can provide any help will be greatly appreciated.

  Thank you!

  Bugcheck 3B {c0000005, fffff800034c2a3e, fffff8800f35ec30, 0}

  Probably caused by: ntkrnlmp.exe (nt! KiSignalSynchronizationObject + 4th)

  System_service_exception (3B)
  An exception occurred during the execution of a system service routine.
  Arguments:
  Arg1: 00000000c 0000005, Exception that caused the error checking code
  Arg2: fffff800034c2a3e, the address of the instruction that caused the error checking
  Arg3: fffff8800f35ec30, address of the context record to the exception that caused the error checking
  Arg4: 0000000000000000, zero.

  DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

  BUGCHECK_STR: 0X3B

  Nom_processus: audiodg.exe

  CURRENT_IRQL: 2

  ANALYSIS_SESSION_HOST: LAPTOP_2

  ANALYSIS_SESSION_TIME: 12/05/2016 00:17:05.0764

  ANALYSIS_VERSION: 10.0.10586.567 amd64fre

  LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800034c2a3e

  STACK_TEXT:
  fffff880 '0f35f610 00000000' 00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiSignalSynchronizationObject + 0x4e

  Update the driver Realtek Audio version 6.0.1.7525:

  http://downloads.Dell.com/FOLDER03113490M/1/XPS-8700_Audio_Driver_MN0T2_WN32_6.0.1.7525_A00.exe

  This file automatically installs automatically after downloading. Reboot required.

  Update Intel AMT HECI driver to version 11.0.0.1153:

  http://downloads.Dell.com/FOLDER03130113M/1/XPS-8700_Chipset_Driver_VJ54R_WN32_11.0.0.1153_A00.exe

  Installation

  1. navigate to the location where you downloaded the file, and then double-click the new file.

  2. read the information about the version presented in the dialogue window.

  3. download and install all of the components required in the dialogue window before proceeding.

  4. click on the button to install.

  5. follow the remaining prompts to perform the update

  Update the Chipset Intel version 10.1.1.7:

  http://downloads.Dell.com/FOLDER03130099M/1/XPS-8700_Chipset_Driver_CR5PJ_WN32_10.1.1.7_A00.exe

  This file automatically installs automatically after downloading. Reboot required.

  The 7260 Intel Wireless Driver version 17.1.0 update:

  http://www.Dell.com/support/home/us/en/19/drivers/DriversDetails?driverId=VXCDN&FILEID=3493199299&osCode=W764&ProductCode=XPS-8700&LanguageCode=en&CategoryID=NI

  Intel rapid storage technology driver update to version 14.5.0.1081:

  http://downloads.Dell.com/FOLDER03127021M/1/XPS-8700_Serial-ATA_Driver_C2JM0_WN32_14.5.0.1081_A00.exe

  This file automatically installs automatically after downloading. Reboot required.

  Updated the Realtek network driver 8111E to version 10.1.505.2015:

  http://downloads.Dell.com/FOLDER03184762M/1/XPS-8700_Network_Driver_5Y97W_WN64_10.1.505.2015_A01.exe

  Update the Nvidia graphics driver to version 10.18.13.5324:

  http://downloads.Dell.com/FOLDER03102665M/1/Video_Driver_086XM_WN32_10.18.13.5324_A00.exe

• Stop Windows 7 BSOD 0x0000000A code

  Hello

  I started having BSOD in my two year, Windows 7 Home Premium edition desktop PC on 08/12/15 after an automatic update of Windows and then get their most frequently every day since.  The minidump lists always stop Code A to NTOSKRNL.exe + 73c40 as the offending code.  What I've tried so far:

  • BlueScreenView installed
  • Opened the case and clear any dust of fittings of air circulation where it could have been due to overheating
  • A ran Memtest86 for 10 assists without reported errors (8G of RAM)
  • A ran chkdsk with no error reported.
  • Tried to manually run Windows Update - get BSOD Stop Code 50
  • Tried running a full virus scan - get BSOD
  • Uninstalled SuperAntiSpyware and Avast, install MSE - produced complete sweep of the BSOD
  • Run the full scan MSE properly in Mode safe
  • Using Device Manager, try to update the drivers one by one in Safe Mode.  Among those that I tried, most respond that the existing driver is up-to-date.  The ATI/AMD video driver did however update.  However, as soon as I press the mouse in Normal mode, he returned BSOD.

  I'm not a gamer nor I am overclocking (whatever it is) anything.  I would like to believe that my BSOD is related to the software, but am now short of ideas on how to proceed.

  The only two actions absolutely will be 100% of the time product Code A BSOD Stop are: 1) try any virus (quick or full) of any of the three scanners scan I tried - get the BSOD in a minute; and (2) try a Windows Update - produced the BSOD once I select an update to download and install.  Otherwise, they seem to appear randomly in about 5 minutes after the start.

  I think my next steps are:

  1. Restore the PC to a restore before the 08/12/15 point (but then how I never go forward again?)
  2. Try the driver verifier (although the debate surrounding this step sounds scary)
  3. Repair Windows from the CD (although if it is a non-Windows, the origin of the problem driver, how can he help?)
  4. Re-install Windows on a hard drive clean (a lot of work to reload everything)
  5. Buying a new PC (groan)

  Any help would be greatly appreciated.

  The most recent minidump are at: https://www.dropbox.com/s/savjud82p70i6io/121715-16894-01.dmp?dl=0

  Hello

  We can successfully close this thread.  The source of my BSOD has proved to be the four old vestige McAfee drivers.    My Dell PC of 2012 has been preloaded with McAfee and I must not have successfully uninstalled three years ago.  For anyone else who may be looking for a BSOD from 0 to stop Code referencing NTOSKRNL.exe + 73c40, the key for me was to find a file to mcafee under c:\program files\common files and also several pilot named MFExxxx.sys in the folder c:\windows\system32\drivers.  When I ran check, he scored these MFE drivers as being loaded.  I don't know exactly how and why they were active in my PC.  Maybe a registry key to load.  Since McAfee is not listed as a product registered in my PC, they have not updated successfully since installation in 2012.  They were apparently benign drivers for the last 3 years until 08/12/15 Windows Update which turned them into little evil monsters.  To remove all the remains of McAfee, search for "Tool McAfee Consumer Product Removal" in your favorite browser.  Download and run the latest version of MCPR.exe to purge your system.  No BSOD more.

  Ken

• Windows 7 BSOD Dump

  I'm looking for help with my BSOD dump.  As far as I can tell, the research that the core of the system is having a problem.  Can someone tell me exactly what can happen?  Dump below.

  --------------------------------------------------------------------------------------
  Microsoft (R) Windows debug 6.12.0002.633 AMD64 Version
  Copyright (c) Microsoft Corporation. All rights reserved.

  Loading dump file [C:\Windows\Minidump\102615-19063-01.dmp]
  The mini kernel dump file: only registers and the trace of the stack are available

  Symbol search path is: SRV * C:\Windows\symbol_cache* http://msdl.microsoft.com/download/symbols
  Executable search path is:
  Windows 7 Kernel Version 7600 MP (2 processors) free x 64
  Product: WinNt, suite: TerminalServer SingleUserTS
  By: 7600.16385.amd64fre.win7_rtm.090713 - 1255
  Computer name:
  Kernel base = 0xfffff800 '0302 c 000 PsLoadedModuleList = 0xfffff800' 03269e50
  The debugging session: 18:56:39.560 Mon 26 Oct 2015 (UTC - 04:00)
  System Uptime: 0 days 0:00:12.183
  Loading the kernel symbols
  ...............................................................
  ....................................................
  Loading user symbols
  Loading unloaded module list
  .
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  Bugcheck 50, {fffff8a005070000, 0, fffff800030ec69e, 0}

  WARNING: Unable to verify timestamp for ntoskrnl.exe
  ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe

  Could not read the name of the problem driver
  Probably caused by: ntoskrnl.exe (nt_fffff80003000000 + 2a 49)

  Follow-up: MachineOwner
  ---------

  1: kd >! analyze - v
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  PAGE_FAULT_IN_NONPAGED_AREA (50)
  Invalid system memory was referenced.  This cannot be protected by try-except,
  It must be protected by a probe.  In general, the address is simple bad or it
  pointing to freed memory.
  Arguments:
  Arg1: fffff8a005070000, memory referenced.
  Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
  Arg3: fffff800030ec69e, if not zero, the address of the instruction that refers to bad memory
  address.
  Arg4: 0000000000000000, (reserved)

  Debugging information:
  ------------------

  Could not read the name of the problem driver

  READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032d40e0
  fffff8a005070000

  FAULTING_IP:
  NT! wcsrchr + 6
  fffff800'030ec69e 0fb701 movzx eax, word ptr [rcx]

  MM_INTERNAL_CODE: 0

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

  BUGCHECK_STR: 0 X 50

  Nom_processus: smss.exe

  CURRENT_IRQL: 0

  TRAP_FRAME: fffff88002e71570-(.trap 0xfffff88002e71570)
  NOTE: The frame trap does contain not all registers.
  Some registry values can be set to zero or incorrect.
  Rax = 000000000000000c rbx = 0000000000000000 rcx = fffff8a005070000
  RDX = 000000000000005c rsi = 0000000000000000 rdi = 0000000000000000
  RIP = fffff800030ec69e rsp = fffff88002e71708 rbp = fffff8000324b4a8
  R8 = 0000000000000000 r10 = 0000000000501902 fffff8a00506ffc0 = r9
  R11 = 0000000000000000 r12 = 0000000000000000 r13 = 0000000000000000
  R14 = 0000000000000000 r15 = 0000000000000000
  iopl = 0 nv up ei pl nz na po nc
  NT! wcsrchr + 0 x 6:
  fffff800'030ec69e 0fb701 movzx eax, word ptr [rcx] ds:1902:fffff8a0'05070000 =?
  Reset the default scope

  LAST_CONTROL_TRANSFER: from fffff8000311d1e4 to fffff8000309df00

  STACK_TEXT:
  "fffff880 '02e71408 fffff800' 0311d1e4: 00000000'00000050 fffff8a0 ' 05070000 00000000 00000000' fffff880 ' 02e71570: nt! KeBugCheckEx
  fffff880 '02e71410 fffff800' 0309bfee: 00000000'00000000 00000000'00000001 fffffa80 '08 a 17000 00000000' 00000160: nt! : FNODOBFM: 'chain' + 0 x 42907
  fffff880 '02e71570 fffff800' 030ec69e: fffff800 '03002-49 fffff880' 02e717b0 00000000'00000001 00000000'00000000: nt! KiPageFault + 0x16e
  fffff880 '02e71708 fffff800' a 03002, 49: fffff880'02e717b0 00000000'00000001 00000000'00000000 00000000'00000000: nt! wcsrchr + 0 x 6
  fffff880 '02e71710 fffff880' 02e717b0: 00000000'00000001 00000000'00000000 00000000'00000000 00000000'00000002: nt_fffff80003000000 + 0x2a49
  fffff880'02e71718 00000001' 00000000: 00000000'00000000 00000000'00000000 00000000'00000002 fffff800'0307e0d2: 0xfffff880'02e717b0
  fffff880 '02e71720 00000000' 00000000: 00000000'00000000 00000000'00000002 fffff800 '0307e0d2 00000000' a 0000030: 0 x 1

  STACK_COMMAND: kb

  FOLLOWUP_IP:
  nt_fffff80003000000 + 2 has 49
  fffff800'03002 has 49?              ???

  SYMBOL_STACK_INDEX: 4

  SYMBOL_NAME: nt_fffff80003000000 + 2 has 49

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: nt_fffff80003000000

  Nom_image: ntoskrnl.exe

  DEBUG_FLR_IMAGE_TIMESTAMP: 550e41b6

  FAILURE_BUCKET_ID: X64_0x50_nt_fffff80003000000 + 2 has 49

  BUCKET_ID: X64_0x50_nt_fffff80003000000 + 2 has 49

  Follow-up: MachineOwner
  ---------

  1: kd > lmvm nt_fffff80003000000
  start end module name
  fffff800 '03000000 fffff800' nt_fffff80003000000 03016000 T (no symbol)
  Loaded symbol image file: ntoskrnl.exe
  Image path: \SystemRoot\system32\ntoskrnl.exe
  Image name: ntoskrnl.exe
  Timestamp: Sun Mar 22 00:14:46 2015 (550E41B6)
  CheckSum: 00014804
  ImageSize: 00016000
  Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
  1: kd > .trap 0xfffff88002e71570
  NOTE: The frame trap does contain not all registers.
  Some registry values can be set to zero or incorrect.
  Rax = 000000000000000c rbx = 0000000000000000 rcx = fffff8a005070000
  RDX = 000000000000005c rsi = 0000000000000000 rdi = 0000000000000000
  RIP = fffff800030ec69e rsp = fffff88002e71708 rbp = fffff8000324b4a8
  R8 = 0000000000000000 r10 = 0000000000501902 fffff8a00506ffc0 = r9
  R11 = 0000000000000000 r12 = 0000000000000000 r13 = 0000000000000000
  R14 = 0000000000000000 r15 = 0000000000000000
  iopl = 0 nv up ei pl nz na po nc
  NT! wcsrchr + 0 x 6:
  fffff800'030ec69e 0fb701 movzx eax, word ptr [rcx] ds:1902:fffff8a0'05070000 =?

  Good work on win debugger

  First of all, you need to update to SP - 1

  Service pack 1 update.
  
  http://Windows.Microsoft.com/installwindows7sp1

  Learn how to install Windows 7 Service Pack 1 (SP1)

  http://Windows.Microsoft.com/en-us/Windows7/learn-how-to-install-Windows-7-Service-Pack-1-SP1
  
  Additional resources:
  http://Windows.Microsoft.com/en-us/Windows7/uninstall-SP1
  http://Windows.Microsoft.com/troubleshootwindows7sp1

  If you continue to plant

  These accidents were related to the corruption of memory (probably caused by a driver).

  Run these two tests to check your memory and find which driver is causing the problem.  Launch auditor.  You don't need to run memtest again unless the auditor is not the cause, or you want to.

  If you are overclocking anything reset by default before running these tests.

  In other words STOP! If you don't know what it means that you're probably not  

  
  

  
  

  1-Driver Verifier (for full instructions, see our wiki here)
  
  2-Memtest. (You can learn more about running memtest here)

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