Windows 7 BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Similar Questions

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

• BSoD (System_thread_exception_not_handled) error on acer Z5771

  I hope someone can help me with BSoD (System_thread_exception_not_handled) error screen when I try to install Win 8 on an acer Z5771

  Unfortunately the files had no information on the BSOD.

  However, the error may be an incompatible video driver.

  There is a suggestion in the following link can help:

  http://social.technet.Microsoft.com/forums/en/w8itproinstall/thread/520411d1-b7fb-4C9F-BB6D-7964cfb7aea6#f4bc4923-8a8b-4403-86ae-b517f15b185d

  What has been proposed is to install the latest NVIDIA of NVIDIA display driver before upgrade:

  http://www.nvidia.com/object/WIN8-Win7-WinVista-64bit-310.90-WHQL-driver.html

  There is also mention of the Acer Upgrade Wizard tool, you could have a look if you don't have it already:

  http://us.Acer.com/AC/en/us/content/upgrade-Assistant-tool

• Windows 8: BSoD random-ing

  No idea why, my cell phone 6 months old was blue screen-ing on a random basis.

  System Specs:

  Manufacturer: ASUS
  Model: K55A-HI5014L
  Processor: Intel iCore i5 - 3210M @ 2.50 GHz
  Graphics card: Intel HD 4000 (on-board) graphics card
  RAM: 8 GB 4 GB enhanced
  OS: Windows 8

  RAM chips both (two 4 GB sticks) have been tested on an identical system. Same manufacturer/model/specs. No problems in the same terms. This has happened in the past before adding the second stick of 4 GB, both of which were exchanged for other sticks, tested, replaced the two primary sticks and continued on.

  All the drivers are up to date according to the manufacturer.
  Intel HD Graphics 4000 (64 MB by default) has been updated with generic drivers of Intel.com.
  ^ Has been increased from 64 MB of RAM of 512 MB dedicated with the BIOS in stock

  BIOS is updated according to the manufacturer.

  Laptop is at the top of a computer laptop cooling pad - connected via external power supply - on a constant basis. Once where that is not the key is when I'm away from my office, at a friend's House, or travel.

  Devices in use is a Logitech wireless mouse (mini-dongle is not removed unless they be stored in the bag, in which is stored inside the mouse's), Samsung Galaxy S II SGH-T989 and OEM micro USB cable and wired controller Microsoft Xbox 360 brand. Headphones I use fed current by a free USB port on laptop and has 3.5 mm headphone/mic separate jacks. Tested with USB power and external spare slot. No difference when BSoD that happens.

  CPU fan only turns on and begins to "work hard" by playing the games graphics-large. Web browsing, chat on Skype, watch videos (Youtube/Twitch.tv/whatever), the cool rest - same system using do not block cooling - for an extended period of time (5 hours on and off battery voltage)

  Power management is set to Power4Gear High Performance while it is plugged into an external source and energy savings of P4G while on battery.

  Not really sure what more to say, my laptop suddenly BSOD on not the case. He had moments when I watch videos youtube or casual browsing for hours with Firefox and all of a sudden - BSoD. Several other times I was in the middle of a game (Dead Space 3, Prototype 2, Team Fortress 2, to name a select few) and a Skype call with a friend when all of a sudden - Yes.
  ↑ Firefox is up to date, and to my knowledge - Flash is also updated. I don't use Internet Explorer, and Chrome.

  Temperature wise the bottom of the computer is frozen with the cooling pad and the CPU fan is not in overload.

  I even leave my computer in the middle of the night to update Windows as needed with the periodic BSoD - just came out of no where. (Wake up to the beautiful sound of BRRRRRRRRRRRRRRRRR is not exactly a wake-up call that I want to hear before it restarts at 03:45 in the morning). The spirit - I keep my laptop in the middle of the night - sitting at the top of the computer laptop cooling pad - without worrying in case someone needs to put a hand on me through Skype, I can hear the tone in my sleep.

  Around the 5th of this month (August), I tried to reformat (not with update of Win8) with ASUS recovery partition, but unfortunately the problem persists, as it happened 8 times during the month. I have 8 available minidumps if requested.

  I tried using a copy of Windows 7 Ultimate edition on the same computer through multiple startup in the past and had no problem with BSoD for a full month until I switched to Windows 8.

  To my knowledge, Windows 8 is updated to auto-updates, and most of the optional updates is installed without Bing and Bing Desktop toolbar. Alongside this, Malwarebytes reports nothing wrong to a complete and fast analysis.

  Probably a little too necessary info, but can get the details worked. Got this laptop in February as a laptop replacement for my previous. Works well. Only stickler is Windows 8 blue screening out not the case.

  Not really what else. Would really like to have a response out to reinstall Windows 7, which now seems to be the only other choice.

  Edit:

  I forgot to mention: recent BSOD were SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, as well as one selection of others that I don't remember off the top of my head.

  As well as the recent BSoD I have captured, has been a fairly long list of errors in programs (Bing, weather, Photos, Zune Music/Zune video/Xbox Live games, etc.) - programs I don't USE even - with a Kernel-Power (41) (63).

  https://PBS.twimg.com/Media/BS4ARIaCAAAUDG_.PNG

  Hello

  The question you posted would be better suited in the TechNet Forums. I would recommend posting your query in the link below.

  http://social.technet.Microsoft.com/forums/en/category/w8itpro

• Satellite A660-1CJ - 8.1 Windows crashes - BSOD bridge.sys

  Hello

  I have a Satelite A660-1CJ, running Windows 8.1 and he already broke 5 times with a BSOD:
  DRIVER_IRQL_NOT_LESS_OR_EQUAL (bridge.sys)

  What can I do?

  Hello

  It seems that the bridge.sys is causing the BSOD.
  Bridge.sys is a Windows system component.

  Toshiba says that the Windows 8.1 is not supported on Satellite A660 series.
  What does that mean?
  This means that Windows 8.1 drivers are not released by Toshiba.

  I assume that you have installed drivers in your own hand and probably one of the drivers causing the BSOD.

• Portege M200 - problem installing Windows Xp - BSOD

  I recently got 2 computers Portege M200 laptops, but previous users had wiped the hard drive.
  So now im trying to install windows Xp via cd-rom drives externel accompanying.
  But when its load to the top of the windows Xp cd it gives me a BSOD somewhere near the end of loading the CD (it always stops on 'Setup starts windows').

  Now, I thought that this could be a hard drive problem, so I have a drive hard "nine", but this still does not work (this problem exists on two laptops).

  Now im wondering if theres some sort of special installation process or something of the sort for the M200?

  I hope someone can help me with my problem.
  Thank you... DG

  Hi mate,

  What version of Windows XP you are trying to install? Windows XP Professional or Tablet edition? You have the available recovery? If Yes, then you should use it :)

  If not, you should check if there could be maybe something with the Tablet thing. It s just a hint, so I'm sorry that I Don t have a real good solution...

  Good luck

• Start the upgrade to Windows 7 BSOD

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

  Journal displays all tests OK except:

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

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

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

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

  Any thoughts?

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

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

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

• I've corrected the 10 Feb Windows update BSOD issue. What to do next?

  Like many others my infographic died with a BSOD after the windows update Feb10th. Returning the suggested KB977165 had no effect, but fortunately after returning all the updates, my computer is back to life.
  I have now a computer with windows update disabled with an update waiting that I suspect is causing the BSOD again if I turn on updates.
  The various forums etc I found will tell you how to recover your computer on but none that I have found tell me if I can go back to windows update or how carefully remove any update caused the BSOD.
  I haven't tried the "no support for Windows Update problems" for an answer and gave with an automated response telling me to try here.
  Can someone please point me to a 'next steps' to recover completely from this?

  I've heard reports of infected, media files cj. The two movies and songs that have been downloaded through Limewire.  If I hear anything else about it, I will be sure to post it here. All the protection we use still depends on who is using the keyboard or mouse click.

  Suggest that you scan the system with Malwarebytes anti-malware , too.  Download the free version, install and allow update when installed.
  Then click on the button scan and use the default quick scan setting. Once the scan is complete click on the button to display the results.
  If sure all detected object is checked and then click on the button select Remove.
  If nothing is detected, I would start the system into safe mode and do a Full scan, too. It will take time to finish but worth it.

  One way that you would be able to be almost certain to 100% that you have detected and deleted all the bad creatures is to shoot on the hard drive, install it as a slave on another system and then scan the HD active.
  Or you can create a BartsPE or Linux boot cd and the scanner without having to shoot HD.

  Anyway is not elegant, to say the least, and not give the same level of confidence you would have with (ugh) formatting and reinstalling.
  MowGreen Services consumer safety update

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

• Vista - MSE updates OK if via Windows updates > BSOD?

  Hi yesterday my Vista very reliable (32 bit Home Premium SP2 on a Toshiba Satellite Pro L300d 4 GB of RAM) Blue installation proposed - this never happened before in 2 years of use!

  I use MSE for about a week or two, & find it fine - in fact my first full scan has detected a Trojan horse that the previous program never seen or reported.
  The BSOD pending symptoms that start (just before logon is displayed), the ORB does not appear either or if this is the case there is no sound. Then the connection at the time where MSE starts to load a lock-up followed the BSOD (which is just a big bar at the bottom of the screen).
  I can retrieve using the last point of restoration (which was the installation of a definition of ESM by Windows Update). This morning, I applied a definition through MSE & everything was OK. This definition appeared in WU previously but I had not updated via WU. I applied it through MSE & everything was OK.
  Anyone has any ideas as to why this is happening?
  TIA

  Hi-brush,

  Thank you for following up on that.

  I'm glad that you were able to get up and running.

  Let us know if you have any other questions on this or other issues.

  Best regards

  Matthew_Ha

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

• How to fix a Windows 7 BSoD?

  In recent weeks, I was struck with the BSoD. Somehow, after going into Safe Mode, I was able to revive the box (though I doubt that really fixed anything.).

  When I try to use Windows repair software, it is said that I have no problem.

  When I use Windows recovery software, it says it's 'something', but nothing changes.

  When I try to use restore points, he tells me that they are corrupt and cannot be used.

  Here's my last BSoD:

  

  I went looking for a crashdump... There is none with the date of the day!

  Where should I go from here?

  Thank you very much...

  Paul

  Hello

  Well, it could be a hardware error and those who can only be fixed with software. Sometimes
  Re-installation of Windows is the solution to save time, or will tell you more material.

  Use the method of start-up mode minimum to see if you can get the system starts.

  How to troubleshoot a problem by performing a clean boot in Windows
  Vista or Windows 7
  http://support.Microsoft.com/kb/929135

  Do not forget the other methods in original convenience stores that I posted.

  Rob - SpiritX

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