Windows 8 BSOD due to CORE 41

Similar Questions

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

• Cannot update Windows Vista kb971468 due to the error message 800B0100__

  Cannot update Windows Vista kb971468 due to the error 800b0100 of message

  Error code when you try to use Windows Update or Microsoft Update to install updates: "0x800B0001":
  http://support.Microsoft.com/kb/958045

  Vista SP1 or SP2 installed?

  What application or antivirus security suite is installed and your current subscription?  What anti-spyware (other than Defender) applications?  What third-party firewall (if applicable)?

  A (another) Norton or McAfee application has already been installed on the computer (for example, a free trial version which is preinstalled when you bought it)?

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

• can I install windows xp sp3 CPU intel core 2 duo? Please quick reply

  can I install windows xp sp3 CPU intel core 2 duo? Please quick reply

  Yes, you can.

• When I run mbsa 2.2 I get = firewall tests Windows may be due to an error. (0x8004100e)? What should I do to remove this message?

  When I run mbsa 2.2 I get = firewall tests Windows may be due to an error. (0x8004100e)? What should I do to remove this message? a few hours back this problem wasn't there, but now I'm stuck! Help?

  Hello

  Your question of Windows is more complex than what is generally answered in the Microsoft Answers forums. It is better suited for the public on the TechNet site. Please post your question in the below link: http://social.technet.microsoft.com/Forums/en-US/MBSA/threads

• I can not write the new message of Windows Live Essentials due to the demand of Silverlight.configuration.exe freeze my computer. How to replace this command?

  Silverlight.config.exe. appears again msg then causes a gel

  I can not write the new message of Windows Live Essentials due to the demand of Silverlight.configuration.exe freeze my computer.  How to replace this command?

  Hi JaphetMorales.

  (1) did you change on your computer before this problem?

  (2) what operating system is installed on your computer?

  What version of the operating system Windows am I running?

  http://Windows.Microsoft.com/en-us/Windows7/help/which-version-of-the-Windows-operating-system-am-i-running

  You can uninstall and reinstall Silverlight and then check.

  http://www.Microsoft.com/getSilverlight/get-started/install/uninstall-win.aspx

  See also:

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

• 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 cannot print due to a problem with the installation of the current printer.

  Thread title: Epson TX235W will not print

  When I click on 'print', I get the print control. the box that tells the printer how many copies, etc.  When I toast 'print' it get a little box that says Windows cannot print due to a problem with the installation of the current printer.  Try one of the following:

  Check the printer by printing a Windows test page

  Ensure that the printer is online and on

  Reinstall the printer driver

  I did everything above and I get the same result.

  Help!

  Hello

  Did you of recent changes made to your computer that caused the problem?

  This problem is limited to a particular application?

  How is the printer connected?

  Method 1) restart the print spooler service and delete the print queue

  Start the print spooler service in the Services console

  1. Click Start and run, type services.msc, and then click OK.
  2. Right click on the print spooler service, and then click on stop.
  3. Right click on the print spooler service and then click Start.

  Start the spooler service for printing at the command prompt

  1. Click Start, run, type cmd, and then click OK.
  2. Type the following commands at the command prompt:

     net stop spooler
     net start spooler
     Output

  Note: Press ENTER after each command line.

  Cancel printing

  http://Windows.Microsoft.com/en-us/Windows-Vista/cancel-printing

  Method 2) remove and add the printer and then check.

  Add or remove a printer (Applicable for Windows 7)

  http://Windows.Microsoft.com/en-us/Windows-Vista/add-or-remove-a-printer

  It will be useful.

• Windows 7 cannot print - "Windows cannot print due to a problem with the installation of the current printer"

  Window 7, Lexmark 1300 series. Cannot print. When you try to print from Notepad, the error message is "the system cannot find the file specified." What impression of the word is "Windows cannot print due to a problem with the installation of the current printer" have uninstalled and reinstalled all printers in many times. Removed the Lexmark 1300 in the registry and reinstalled. No change. Ran sfc/scannnow several times. Microsoft Fixit print detected no problems. Help, please.

  Hi Baccy138,

  See the methods mentioned below and check:
  Diagnose and automatically fix the Windows USB problems
  http://support.Microsoft.com/mats/Windows_USB_diagnostics/
   
  Try to download and update the drivers manually from this site:
  http://support.Lexmark.com/index?segment=support&UserLocale=en_US&locale=en&ProductCode=LEXMARK_Z1300&page=product&FromPage=null#1
  1. click on the above link and click the menu drop down and select Windows.
  2. Select the version of operating system like Windows 7 and check the bit as a result.
  3. Download complete drivers and install it.
   
  Hope this information helps.

• Help! your windows license is due to expire the

  All of a sudden, I get this message, what should I do? do I need to buy the new key? I don't have any money just to buy windows, I want to know why this message shown even use my key to any other computer, it shows "your windows license is due to expire on 22/09/2013 '"

  really need help with that I WANT to BUY NEW LICENSE! :(

  Thanks for the 1st reply, I reinstalled my windows using online installation which took about 4 hours with my stupid slow connection and everything is fine. no more expires :D

• Updated my Windows 7 to Windows 10 and then installed AR version for windows 10.  Due to a problem unconnected with returned to Windows 7 and uninstalled AR for Windows 10.  When I try to reinstall AR for Windows 7, I get the following message. "The featu

  
  Updated my Windows 7 to Windows 10 and then installed AR for Windows 10.  Due to a problem, I deleted Windows 10 and returned to Windows 7 and uninstalled AR for Windows 10.  Have tried to reinstall AR for Windows 7 and get the following message.  "The feature you are trying to use is on a network unavailable resource.  Error 1714.  The older version of Acrobat Reader DC may not be withdrawn".  Help!

  Hi michaelw72331164,

  Try this: error 1714. Acrobat, Reader

  If it does not work. Cleaning tool to uninstall all traces of player and then install offline using.

  Download Adobe Reader and Acrobat cleaning tool - Adobe Labs

  Adobe - Adobe Acrobat Reader DC Distribution

  Thank you

  Abhishek

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

• Windows 7 BSOD ntoskrnl.exe question

  Hello.  I'm having the same problem as the next person - http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/ntoskrnlexe-1040b-e58d2-6d5be/ea3a3e93-69bd-47c7-9f31-ddb723120912.  I ran Driver Verifier and then encountered the problem of not being able to access my laptop normally.  I disabled the driver verifier now.

  I redid my laptop about 3 times in the hope of solving my BSOD problem, but it is ongoing.

  Any help is appreciated.

  David Martinez

  THE

  They are related to your video driver.  I would like to begin by updating to the latest driver that yours is ~ 1 year.

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

  Loading dump file [C:\Users\Ken\Desktop\052814-20592-01.dmp]
  The mini kernel dump file: only registers and the trace of the stack are available

  Symbol of validation of the path summary *.
  Location of response time (ms)
  Deferred SRV * H:\symbols* http://msdl.microsoft.com/download/symbols
  Symbol search path is: SRV * H:\symbols* http://msdl.microsoft.com/download/symbols
  Executable search path is:
  Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) free x 64
  Product: WinNt, suite: TerminalServer SingleUserTS
  By: 7601.18409.amd64fre.win7sp1_gdr.140303 - 2144
  Computer name:
  Kernel base = 0xfffff800'02e63000 PsLoadedModuleList = 0xfffff800'030 was 6890
  The debugging session: 14:44:02.483 Wed 28 may 2014 (UTC - 04:00)
  System Uptime: 0 days 0:02:46.482
  Loading the kernel symbols
  ...............................................................
  ................................................................
  ..................................................
  Loading user symbols
  Loading unloaded module list
  ....
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  BugCheck C4, {c0, fffffa800a546340, f6, fffff8800f2b9879}

  WARNING: Unable to verify timestamp for nvlddmkm.sys
  ERROR: Module load completed but symbols can be loaded for nvlddmkm.sys
  Probably caused by: nvlddmkm.sys (nvlddmkm + 9a 879)

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

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

  DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
  A device driver attempting to corrupt the system has taken.  It comes
  because the driver was specified in the registry as being suspect (by the)
  Administrator) and the kernel has allowed substantial control of this driver.
  If the pilot attempts to corrupt the system, looking for bugs, 0xC4, 0xC1, and 0xA
  Be one of the most commonly seen crashes.
  Arguments:
  Arg1: 00000000000000f6, handle user SEO as the core.
  Arg2: 00000000000000c 0, the value of Handle referenced.
  Arg3: fffffa800a546340, address of the current process.
  Arg4: fffff8800f2b9879, address inside the pilot making the incorrect reference.

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

  BUGCHECK_STR: 0xc4_f6

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

  Nom_processus: rundll32.exe

  CURRENT_IRQL: 0

  ANALYSIS_VERSION: 6.3.9600.17029 (debuggers (dbg). 140219-1702) amd64fre

  LAST_CONTROL_TRANSFER: from fffff800033654ec to fffff80002ed8bc0

  STACK_TEXT:
  "" fffff880 ' 0 c 315308 fffff800 ' 033654ec: 00000000 ' 000000 c 4 00000000' 000000f6 00000000'000000 c 0 fffffa80 ' a 0, 546340: nt! KeBugCheckEx
  "" fffff880 ' 0 c 315310 fffff800 ' 0337abf4: 00000000 ' 000000 c 0 fffffa80 ' 0a 546340 00000000'00000004 fffff880'0 c 317000: nt! VerifierBugCheckIfAppropriate + 0x3c
  fffff880 ' 0 c 315350 fffff800' 03132890: fffff8a0 '000016-0 fffff880' 0c3155a0 fffff880 '0 c 315700 fffff880' 0c 315930: nt! VfCheckUserHandle + 0x1b4
  "fffff880 ' 0 c 315430 fffff800 ' 031a95b5: 00000000 '00000000 fffff880' 00000001 fffffa80 '06067f30 fffff8a0' 05c08a00: nt! : NNGAKEGL: 'string' + 0x2027e
  "fffff880 ' 0 c 315500 fffff800 ' 02ed7e53: fffffa80 '0aa1e060 fffff880' 0c3158b8 00000000'00000002 00000000'00000000: nt! NtQueryValueKey + 0 x 115
  "" fffff880 ' 0 c 315690 fffff800 ' 02ed4410: fffff800 ' 03369 d 96 fffff880 ' 0f2b9879 fffff880 '0 c 315930 fffff880' 0c 315928: nt! KiSystemServiceCopyEnd + 0x13
  fffff880 '0 c 315898 fffff800' 03369d 96: fffff880 ' 0f2b9879 fffff880 '0 c 315930 fffff880' 0c 315928 fffff800 ' 02ed4410: nt! KiServiceLinkage
  "fffff880 '0c3158a0 fffff880' 0f2b9879: fffff880 ' 0c3168ca fffff880 ' 0 c 315970 fffff880 ' 0c3168b8 fffffa80 ' 0591ff18: nt! VfZwQueryValueKey + 0 x 76
  fffff880 '0c3158f0 fffff880' 0c3168ca: fffff880' 0591ff18 fffff880 '0c3168b8 fffffa80' 0 c 315970 00000000 00000000': nvlddmkm + 0x9a879
  fffff880'0c3158f8 fffff880'0 c 315970: fffff880 '0c3168b8 fffffa80' 0591ff18 00000000 00000000' fffff880 0'c 315920: 0xfffff880'0c3168ca
  "fffff880 ' 0 c 315900 fffff880 ' 0c3168b8: fffffa80'0591ff18 00000000 00000000' fffff880 ' 0 c 315920 fffff980' 00000000: 0xfffff880'0 c 315970
  "fffff880 ' 0 c 315908 fffffa80 ' 0591ff18: 00000000 '00000000 '0c 315920 fffff980'00000000 00000000 fffff880' 000000 c 0: 0xfffff880'0c3168b8
  fffff880'0 c 315910 00000000 00000000': fffff880 '0 c 315920 fffff980' c 0 00000000 00000000'000000 ' 00280026 fffffa80: 0xfffffa80'0591ff18

  STACK_COMMAND: kb

  FOLLOWUP_IP:
  nvlddmkm + 9 has 879
  fffff880'0f2b9879 3d340000c0 cmp eax, 0C0000034h

  SYMBOL_STACK_INDEX: 8

  SYMBOL_NAME: nvlddmkm + 9 has 879

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: nvlddmkm

  Nom_image: nvlddmkm.sys

  DEBUG_FLR_IMAGE_TIMESTAMP: 5280da75

  FAILURE_BUCKET_ID: X64_0xc4_f6_nvlddmkm + 9 has 879

  BUCKET_ID: X64_0xc4_f6_nvlddmkm + 9 has 879

  ANALYSIS_SOURCE: KM

  FAILURE_ID_HASH_STRING: km:x64_0xc4_f6_nvlddmkm + 9 has 879

  FAILURE_ID_HASH: {0c031110-986a-b405-c565-3ead8c9b6e45}

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