BSOD while browsing with Chrome - Crash address ntoskrnl.exe + 5 has 440

Hello, everyone. My laptop Dell Inspiron 1425, and the operating system is Windows 8 64-bit.

These two days I get a blue screen while browsing with Chrome. So far, it's happened three times. Minidump files, we can see that the drivers that caused them are different, but their address of accident are the same: ntoskrnl.exe + 5 has 440. And each one happened when I was browsing with Chrome, I think they are relevant. Here's my Minidump files:
https://SkyDrive.live.com/redir?RESID=77106B4AC1BE0CA8! 10830

Thank you for your help :)

Hello

We have two bugs attached landfills here:

DPC_WATCHDOG_VIOLATION (133)

Bug DPC_WATCHDOG_VIOLATION control has a value of 0 x 00000133. This bug check indicates that the watchdog DPC executed, either because it has detected a call single lengthy proceedings deferred (DPC), the system spent an extended time at a level (IRQL) IRQ to DISPATCH_LEVEL or above. The value of parameter 1 indicates whether one single DPC exceeded a timeout, or if the system is cumulatively spent a long period of time IRQL DISPATCH_LEVEL or higher.

I notice you have installed Norton. I will recommend to temporary troubleshooting purposes remove you Norton and replace it with built-in Windows Defender from Windows 8.

Norton removal tool - ftp://ftp.symantec.com/public/english_us_canada/removal_tools/Norton_Removal_Tool.exe

If the removal and replacement of Norton do not help, the second error checking is:

VIDEO_TDR_FAILURE (116)

The basic definition of a bugcheck 0 x 116 is:

There may be a bug in the video driver or video material.

So I would now explain what means VIDEO_TDR_ERROR. Firstly, TDR is an acronym for Timeout detection and recovery. Detection time and recovery was introduced in Vista and carried over to Windows 7. Rather than exactly what detection time and recovery did exactly, I'll just quote the MSDN article!

Timeout detection:

Planner of the GPU, which is part of the DirectX Graphics kernel subsystem (Dxgkrnl.sys), detects that the GPU takes more than the amount of time to perform a particular task. The GPU scheduler then attempts to anticipate on this particular task. Preempt is a timeout 'wait', which is the actual time of TDR. This step is the detection of delay of the process phase. The period of default timeout in Windows Vista and later versions is 2 seconds. If the GPU cannot complete or anticipate the current task period TDR, the diagnostic operating system that the GPU is frozen.
To avoid detection of timeout to occur, hardware vendors should ensure that graphics operations (i.e. buffer DMA completion) will not take more than 2 seconds in scenarios such as productivity and the game to the end user.

Preparation for recovery:

The operating system GPU Scheduler calls the function DxgkDdiResetFromTimeout of the miniport driver of the display to inform the driver that the operating system detected a timeout. The pilot must then resets and reset the GPU. In addition, the driver must stop access to memory and go not material. The operating system and the driver collect material and other State information that might be useful for post-mortem diagnosis.

Recovery of funds:

The operating system resets the State appropriate graphics stack. The video memory manager, which is also part of Dxgkrnl.sys, serving all allocations of video memory. The miniport display driver resets the State of the GPU hardware. The graphics stack takes the final steps and restores the receptive office. As mentioned previously, some older DirectX applications could make only in black at the end of this recovery, which requires the user to restart these applications. Well-written 9Ex, DirectX and DirectX 10 and subsequent applications which manage peripheral technology delete continue to function correctly. An application must release and then recreate the Direct3D device and all the objects in the device. For more information on how get the DirectX applications, see the Windows SDK.

Article here.

That being said, if the detection time and recovery fails to retrieve the display driver, it will then pull the bugcheck 0 x 116. There are many different things that can cause a 0 x 116, which I'll explain below:

The following hardware problems may cause a TDR event:

1 unstable overclock (CPU, GPU, etc.). Return any overclocks to stock settings.

2 bad sector in memory, resulting in corrupted data is communicated between the GPU and system (memory video, otherwise known as VRAM or physical memory, also called RAM).

GPU tests: Furmark

RAM test: Memtest86 +.

3 corrupt hard drive or install Windows / OS install resulting in corruption in the registry or the page file.

HARD drive Diagnostics: http://www.carrona.org/hddiag.html

To reset your swap file, follow these steps:

(a) go to start... Run... and type "sysdm.cpl" (without the quotes) and press ENTER.

-Then click on the Advanced tab.
- then the Performance Settings button.
- then on the tab advanced following.
-and then click the virtual memory button.

(b) in this window, note the current settings of your swap file (so you can restore them later).

-Then click on the option button "No paging file", and
- Press the Set"" button. Don't forget, if you have several hard drives, make sure that the paging file is set to 0 on all of them.
-Click OK to exit the dialog boxes.

(c) restarted (this will remove the file from your system)

((d) then go back following the directions in step one) and re-enter the settings that you noted in step

(b) follow the steps along the (and including) the reset.

(e) once you have restarted this second time, go back and make sure the settings are as they are supposed to be.

Run the System File Checker:

SFC. EXE/SCANNOW

Click on start and type "cmd.exe" (without the quotes)

At the top of the search box, right-click on the cmd.exe and select "Run as Administrator"

In the black window that opens, type "SFC. EXE/scannow"(without the quotes) and press ENTER.

Let the program run and after return what he says when it's done.

-Overheating of the CPU or GPU and or other elements can cause 0 x 116 bugs. Monitor your temperature and ensure that the system is sufficiently cooled.

-GPU failure. Whether the heat, power (PSU) issue, lack of VRAM, etc..

The following software issues can cause a TDR event:

-Incompatible drivers of any kind (two GPU, sound, etc)

-Messy registry / corrupted

-DirectX bad files (uninstall and reinstall DirectX)

-bad system files (System File Checker - has been run on it)

-Bad driver (some drivers will cause an event due to internal bugs, but they are not nearly as common as many think because of all the previous things, causing the same symptom) - (remove all 3rd party programs and make sure that are not load drivers. Then install only what you need 3rd party stuff and make sure it is the latest version).

Kind regards

Patrick

Tags: Windows

Similar Questions

  • Windows BSOD KERNEL_DATA_INPAGE_ERROR 8; Ntoskrnl.exe + 7 has 040

    Hello world

    I had reinstall Windows 8 last month cause too many errors with the Windows 8 and I had still BOSD arrives with a new installation of Windows 8.

    The last that I have no will is this one:

    KERNEL_DATA_INPAGE_ERROR

    Ntoskrnl.exe + 7 has 040

    We arrive in surfing on the web and burning with IMGBURN. Many Disconnections occur when you use the dvd burner.

    The other at the moment that I solved is "atikmpag.sys" I read on the net that I need to update the file from a download of catalyst frensh.

    Here all DUMP files and the news of the computer:

    All files: https://skydrive.live.com/redir?resid=10F449F32E80D9B2! 390

    Thank you!

    8ternity

    They were related to the following

    KERNEL_DATA_INPAGE_ERROR (7A)
    The requested page of kernel data could not be read in.  Is usually caused by
    a bad block in the disk controller or paging file error.

    My gut feeling is that it is one of these drivers or your moy.  I would like to update the drivers and replace AVG with the built-in Defender

    000 fcl 26/09/2008 09:11:22
    ksaud.sys 2010-07-14 06:12:54
    ntk_PowerDVD_64.sys 03/08/2010 05:04:12
    PxHlpa64.sys 2011-10-17 10:29:34
    amdsbs.sys 21/02/2012 14:15:43

    AVG can be a cause of BSOD.

    http://www.Avg.com/us-en/utilities

    How to find drivers:
    -Google search for the name of the driver
    -compare Google results with what is installed on your system to determine on what device/program, it belongs to
    -Visit the web site of the manufacturer of the hardware or program to get the latest drivers (do not use Windows Update or Device Manager Update Driver function).
    s ' there is difficult to locate them, post back with questions, and someone will try and help you find the right program

    The most common drivers are listed on this page: driver reference

    http://www.carrona.org/dvrref.php

    http://SysNative.com/drivers/

    -Driver manufacturer links are on this page: http://www.carrona.org

  • High CPU usage while browsing with flash content more

    I know that this can cause a several times but still problem persists even after the rest of most of the stages (analysis of malware, disabling content flash etc.). MY model is certainly an old one 910 series motherboard intel with onboard graphics card intel 128 MB running windows xp professional service pack 3. I have recent changes to the system, but that it faces from the 1 of the past month, I started. Flash games used to work properly without lag and without using a lot of CPU, but for a 1 month, he started late as * and CPU spikes almost at 100%, while the jumps game and even during web browsing with flash content and decreases rapidly after you load the page completely. I tried to disable hardware acceleration but still problem. Hope that I find the solution earlier. Thanks in advance.

    Hi Vijay,

    1. Exactly how you try to play the games? Games online or offline?
    2. If you are referring to online games so what web browser are you using to play the games?

    If you use internet Explorer, then, refer to the following.

    When you browse a Web page in Microsoft Internet Explorer, the CPU usage meter in Task Manager may indicate 100% CPU usage. Because of this behavior, other programs may slow down or crash. For example, if you read a video DVD, an audio DVD or audio CD while you scroll through a Web page, you may strain video or audio.

    This problem may occur on some computers if the option of scroll smooth use is enabled in Internet Options.

    Note By default, the use smooth scrolling option is enabled in Internet Explorer.

    To work around this problem, disable the option of scroll smooth use in Internet Explorer. To do this, follow these steps:

    (a) click the Start button and then click Control Panel.

    (b) in the Control Panel, make sure you are in Classic view, with all the control panel display icons. If this is not the case, click switch to Classic view in the left pane of the control panel.

    (c) click Internet Options to open the Internet Options dialog box. Click the Advanced tab and scroll down to the settings: navigation on topic. Select or clear the Use smooth scrolling check box.

    (d) click OKand then click the close button.

    http://Windows.Microsoft.com/en-in/Windows-XP/help/turn-off-smooth-scrolling

    Please post back with the State of the question.

  • BSOD - DRIVER_IRQL_NOT_LESS_OR_EQUAL with nvlddmkm.sys and ntoskrnl.exe

    Hey there,

    My computer has started planting since yesterday. I played a game for a while and it might or might not be related; Eitherway, it suddenly froze the system unexpectedly and I had to reset my pc. After that system started correctly. I ran the game again to see what's going on, and unfortunately, it crashed the system again; has had to reset hard once more. After that, I got a BSOD with DRIVER_IRQL_NOT_LESS_OR_EQUAL score to nvlddmkm.sys. I tried to reboot once more to see if it disappears and the system charged up to the floating logo of W7, but I only got a black screen afterwards, no login screen either. I wasn't able to boot the system normally more, forcing me to use safe mode. After checking terrils, I decided to uninstall completely nvidia drivers and that helped - loaded correctly and installed system software of windows default driver.

    Right now I'm in a situation where Windows seems to work stable unless I have try re-installing the drivers nvidia; In doing so, does not load results in a system and the BSOD screen again after W7 logo, no matter how many times I restart.

    My basic features are:

    Gigabyte P35-DS3R

    Intel Core 2 Quad Q6600 (2.40 ghz, oc'ed to stable 3.20 ghz)
    8 GB DDR2 RAM
    Gigabyte Geforce GTX460 1 GB of RAM

    Samsung 840 EVO 120 GB

    ST1000DM003-1SB10C 1 TB

    Silentium VERO L1 600W

    W7 Pro SP1 with all latest updates

    Here are the dumps (contains the dump of the first and the last being).

    So far what I've done - tried unplugging all devices (including my Sound Blaster Tactic 3D Sigma headset), uninstalled Avast antivirus, tried reinstalling drivers nvidia in two different ways (of unsuccessfully); clean the GPU/CPU/power supply. I'm slowly running out of ideas. To add, I never really had problems with my PC - it works all the time for 8-9 years with no issues whatsoever and I moved from c2d e6750 and GTS250 a year (or more) there are what I currently; never had any problems with these components, either. I always intend to Exchange my gpu for further testing, but since I do not have an integrated GPU and video signal passes through GTX460, I don't really know if there is a damaged graphics card (perhaps wrong, however).

    If anyone knows what is the origin of the problem and what can be done to avoid a full system reinstall, I would be really grateful for any help.

    Update:

    I swapped the GTX460 with my old GTS250 for test. Apparently, it seems that the GTX460 was damaged and all misleading BSOD was actually caused by defective behavior. Fix to 750ti in a while.

    Edit [21/05/2016]:

    I swapped to 750ti and all is well again. This case can be considered resolved.

  • Windows registry is linked to the .dll files? HELP several BSoD and browse... crashed during post! for the love of God

    Must be quick, title says it all
    Windows registry is responsible for the .dll files?
    SFC shows SEVERAL DLLs not missing, no installation CD.
    Not good recovery CD.
    I have the copy of the registry before changes but online before browser support multiple and many BSOD.
    Will post now as browser crashed early in post and the 5 th time in half an hour.

    Thanks for the reply Elizabeth23, but I finally found the part of the SFC.

    SFC showed 167 system missing files - if you continue to press Cancel > continue every time SFC tells you to put in your Windows installation CD eveeentually happen to you at the end of his race - and I ran 3 times and each time got 167.
    Now I had some of the 'missing' located in System32 .dll files, but some were also in i386 and the drivercache but I had not located a bit; but I knew that something is not right I had found some system 'missing' files and after that a few hunting came across a site that said to check the registry key
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\
    CurrentVersion\Setup

    and under SourcePath my entry is a file that does not exist 'Temp' so I changed the entry to C:\WINDOWS rebooted and ran SFC/scannow and it scanned without stopping.
    Weird as the registry key was in a file that is no Temp because I ran many SFC
    times in the last 2 months and it always scanned all the files in the operating system without a hitch...

    My computer is still BSoDing out, had two after SFC took place without a hitch.

  • I constantly problems while browsing with Google yahoo simply grab my research and won't let me come back to google. I have tried everything I can think

    This happening on my macbook pro and my I mack. Also on my PC but only on firefox.

    Hi TheJohnParr, to your Thunderbird (e-mail client) problem, I you suggest have another question for this, and we could concentrate on your Firefox search engine problem in this thread.

    You can view, disable and usually remove extensions on page modules. Either:

    • Command + shift + a
    • Tools menu > Modules

    In the left column, click Extensions. Then, when in doubt, turn off.

    Typically, a link will appear above at least an extension disabled to restart Firefox. You can complete your work on the tab and click one of the links in the last step.

    Any improvement?

    Moreover, the address bar works a bit different in the search boxes (homepage search box or the search box toolbar). If you enter a single word without spaces in the address bar (for example, hobbit or mozilla.org) then Firefox should first check with your provider if there is a known server name. Sometimes, these queries are diverted by your service provider to show you search results. By comparing your search in the address bar and the search box, you can see if it comes to the question.

  • While working with Office Home Student 2007 & microsoft it has locked and now I can not in it. He asked the product key that I entered re - nothing doesn't.

    How to unlock the program?

    Hello

    Check with the Office of the Experts here: (re - ask your question in these groups)

    Office newsgroups
    http://www.Microsoft.com/Office/Community/en-us/FlyoutOverview.mspx

    Discussions in the Office Setup program
    http://www.Microsoft.com/Office/Community/en-us/default.mspx?DG=Microsoft.public.Office.Setup&lang=en&CR=us
    Or

    Welcome to Microsoft Discussion groups
    http://www.Microsoft.com/communities/newsgroups/list/en-us/default.aspx?GUID=1A61081E-1F66-5F7F-B5BA-04767E55A63B

    Microsoft.public.office.setup discussions
    http://www.Microsoft.com/communities/newsgroups/list/en-us/default.aspx?DG=Microsoft.public.Office.Setup&cat=en_us_642d5640-c1ba-43C3-A224-b3ec1473346c&lang=en&CR=us

    I hope this helps.
    Rob - bicycle - Mark Twain said it is good.

  • 0x0000009f DRIVER_POWER_STATE_FAILURE ntoskrnl.exe blue screen error / ntoskrnl.exe + 5 has 220

    Need help... My ASUS N43SL got BSOD every time I try to Hibernate. (Windows Pro 8, update Windows 7 via Windows site)

    Stop and restart Mode did not.
    It comes to my minidump link... https://SkyDrive.live.com/redir?RESID=F266C2A31EC1D90D! 344

    The minidump file showed a DRIVER_POWER_STATE_FAILURE (9f) referencing the ndiswan.sys.

    Other users report similar errors and Connectify and Kaspersky installed for example here , the problem seems to be Connectify or Connectify clashing with Kaspersky.

    Try to uninstall Connectify and, if him persists error uninstall Kaspersky and use alternative security such as firewall and antivirus integrated Windows 8 (Windows Defender) software.

    Also, the driver verifier seems to be activated which should not be enabled under normal circumstances also to 'turn off' the driver verifier:

    Start > type verifier.exe and press 'Enter' on the keyboard > clear the existing settings > finish > click 'Yes' to the message to delete the settings and exit the program

  • DRIVER_POWER_STATE_FAILURE - 0x0000009f - ntoskrnl.exe

    I am facing to the BSOD a couple times a day. Each time the blue screen appears the laptop shows "DRIVER_POWER_STATE_FAILURE" then restarts again, once rebooted everything looks normal as usual.
    The system is Windows 8, X 64. The properties of the dmp is illustrated below:
    Chain: DRIVER_POWER_STATE_FAILURE checking bug
    The bug check code: 0x0000009f
    Parameter 1: 00000000'00000003
    Parameter 2: fffffa80'04df9880
    Parameter 3: fffff803'fc5d2b40
    Parameter 4: fffffa80'05ad4290
    Plant address: ntoskrnl.exe + 5 has 440
    And my minidump link is
    https://SkyDrive.live.com/redir?RESID=F8ACA593B484724A! 1437 & authkey =! AI3q_oKn6TnvVOQ

    Hello

    The attached file of the DMP is to bug checking DRIVER_POWER_STATE_FAILURE (9f) .

    This bug check indicates that the driver is in an inconsistent or invalid power state.

    If we run one! IRP on the 4th parameter of the bug check (IRP address blocked), we get the following:

    > [16, 2] e1 0 fffffa8006d36040 fffff803fd551830-fffffa800a43e690 00000000 success error cancel pending
    \Driver\nvlddmkm nt! PopRequestCompletion

    nvlddmkm nvlddmkm.sys = which is the video driver nVidia.

    Make sure you have the latest video card drivers. If you are already on the latest graphics card drivers, uninstall and install a version or a few versions behind the last to make sure this isn't a last number one driver. If you have already experienced with the driver of the card later and earlier versions, please try the driver beta for your card.

    Kind regards

    Patrick

  • BSOD ntoskrnl.exe + 72 0x0000009f DRIVER_POWER_STATE_FAILURE has 40

    I almost brand new HP ProBOOK 450 G2 with Windows 7 Enterprise, just noticed today the first Memory Dump, thought then to ask... like the laptop is under warranty... laptop computer is on battery power and the battery is dead so saw the light flashing 'orange' and he got the memory dump and he came down, the battery was finished It happened... but its still not the right way to go then... I have through the app "BlueScreenView" about something, but he could not say exactly... searched thing many error BSOD here in the office, but none had the same error, sharing so if someone is kind enough to help.

    Dump file 050415-21028 - 01.dmp
    Time of the accident 04/05/2015-11:01:32
    Bug Check String DRIVER_POWER_STATE_FAILURE
    Bug check code 0x0000009f
    Parameter 1 00000000'00000003
    Parameter 2 fffffa80'07f37a10
    Parameter 3 fffff800'048943 d 8
    Parameter 4 fffffa80'08da0010
    Caused by the driver Ntoskrnl.exe
    Caused by the address ntoskrnl.exe + 72 has 40

    DMP file: http://1drv.ms/1K9FKRC

    Thanks in advance

    ONE

    This phenomenon was related to rtlane.sys NDIS Driver of Realtek Semiconductor Corporation.  I remove the current driver and install the latest driver available.

  • blue screen of death 0 x 00000050 ntoskrnl.exe

    Evry time I play company of Heroes 2, I got a blue screen of death

    PAGE_FAULT_IN_NONPAGED_AREA 0 x 00000050 fffff880 '09b 80004 00000000 00000001' fffff880' 0516a 384 00000000 00000000' ntoskrnl.exe ntoskrnl.exe + 5 has 440 x 64 ntoskrnl.exe + 5 a 440
    I downloaded the minidump and here his him shorten the link :)

    http://sdrv.Ms/15koHJI

    Please help me

    DK

    This a DMP are inconclusive (we usually have 2 or more), but you should try these things first

    Older drivers who need update
    emupia2k.sys 09/04/2007 09:08:10
    ctsfm2k.sys 09/04/2007 09:08:11
    ctoss2k.sys 09/04/2007 09:08:14
    ha10kx2k.sys 09/04/2007 09:08:15
    hap16v2k.sys 09/04/2007 09:08:17
    ctaud2k.sys is 09/04/2007 09:08:29
    ctprxy2k.sys 09/04/2007 09:08:30
    COMMONFX. DLL 2007-04-09 09:08:38
    CTAUDFX. DLL 2007-04-09 09:08:39
    CTSBLFX. DLL 2007-04-09 09:08:42
    HECIx64.sys 2010-10-19 19:33:43
    C:\windows\system32\drivers\elbycdio.sys 2010-12-16 18:58:13
    VClone.sys 15/01/2011 12:21:04
    anvsnddrv.sys 2011-11-14 04:17:35
    e1i63x64.sys 29/02/2012 23:25:14

    How to find drivers:


    Search
    Google for the name of the driver
    Compare the Google results with what is installed on your system to determine on what device/program, it belongs to
    Visit the web site of the manufacturer of the hardware or program to get the latest drivers (do not use Windows Update or Device Manager Update Driver function).
    If there are difficulties to locate them, post back with questions and someone will try and help you find the right program

    The most common drivers can be found on these pages:
    http://www.carrona.org/dvrref.php
    http://SysNative.com/drivers/

    Driver manufacturer links are on this page: http://www.carrona.org


    ALSO I would like to use the built in Defender & remove Kaspersky

  • BSOD, BCCode f9, caused by ntoskrnl.exe, could you please help me with this?

    I get the BSOD with f9 code and I do not understand what is? Could you please advice what may cause this? I'm not sure,
    It happen when I stop or restart (15 minutes with him saying to stop) followed by BSOD (pilot State power failure).
    Once I'm back I can see that Windows has recovered from unexpected shutdown down. Using BlueScreenView tells me that ntoskrnl.exe is the cause.
    I was wondering if it has something to do with the USB Ports, because it won't work as a plug-and-Play (need to reboot USB is plugged).

    I reinstall all the USB drivers.

    My system:
    ASUS Z170A
    nVIDIA GTX 980ti

    850 M2 OF EVO 250 GB SSD

    Intel Core i7 - 4700 k
    32 GB of RAM (4 sticks 8 GB)
    Windows 7 64 bit

    All up to date.

    ==================================================
    Name of the file: ntoskrnl.exe
    Address of stack: ntoskrnl.exe + e23f0
    Address: Fffff800'0325e000
    Address: Fffff800'03844000
    Size: 0x005e6000
    Time stamp: 0x5708972e
    Time string: 09/04/2016 13:46:22
    Product name: Microsoft® Windows® Operating System
    File description: NT kernel & system
    File version: 6.1.7601.23418 (win7sp1_ldr.160408 - 2045)
    Company: Microsoft Corporation
    Full path: C:\Windows\system32\ntoskrnl.exe
    ==================================================
    ==================================================
    Dump file: 081316-13447 - 01.dmp
    Crash time: 13/08/2016-12:46:05
    Bug Check String: DRIVER_POWER_STATE_FAILURE
    Bug check code: 0x0000009f
    Parameter 1: 00000000'00000003
    Parameter 2: fffffa80'1a0f1060
    Parameter 3: fffff800'052373 d 8
    Parameter 4: fffffa80'1f739c60
    Caused by the driver: ntoskrnl.exe
    Caused by the address: ntoskrnl.exe + 6f400
    File description: NT kernel & system
    Product name: Microsoft® Windows® Operating System
    Company: Microsoft Corporation
    File version: 6.1.7601.23418 (win7sp1_ldr.160408 - 2045)
    CPU: x 64
    Plant address: ntoskrnl.exe + 6f400
    Stack address 1:
    The stack address 2:
    Address 3 the battery:
    Computer name:
    Full path: C:\Windows\Minidump\081316-13447-01.dmp
    Number of processors: 8
    Main version: 15
    Minor Version: 7601
    Size of the dump file: 1 250 528
    Dump of file time: 13/08/2016-12:47
    ==================================================

    Hello

    There is a possibility that there is a problem with a driver on your PC. Here are a few things to try:
    • If you know which driver is causing the problem, update.
    • Make sure your hardware drivers are updated.

    Please keep us updated.

    Kind regards.

  • BSoD, which is related to ntoskrnl.exe error

    Hello. I've known a few occasional BSODS, all associated with ntoskrnl.exe. Two of them were 0 x 124, while the most recent is a 0 x 101. I already ran Ccleaner in case it was a registry problem, but I doubt it. I also did a BIOS update for a couple of months. My specs are:

    Windows 7 x 64

    CPU: AMD FX-6300

    GPU: AMD Radeon HD 7750

    Motherboard: Asus M5A78L-M LX3

    Bluescreenview ran, so I'll post the reports here. Thanks for your help.

    ==================================================
    Dump file: 111614-47096 - 01.dmp
    Crash time: 15/11/2014 19:37:06
    Bug Check String:
    Bug check code: 0 x 00000101
    Parameter 1: 00000000'00000021
    Parameter 2: 00000000'00000000
    Parameter 3: fffff880'02f65180
    Parameter 4: 00000000'00000002
    Caused by the driver: ntoskrnl.exe
    Caused by the address: ntoskrnl.exe + 75bc0
    File description: NT kernel & system
    Product name: Microsoft® Windows® Operating System
    Company: Microsoft Corporation
    File version: 6.1.7601.18526 (win7sp1_gdr.140706 - 1506)
    CPU: x 64
    Plant address: ntoskrnl.exe + 75bc0
    Stack address 1:
    The stack address 2:
    Address 3 the battery:
    Computer name:
    Full path: C:\Windows\Minidump\111614-47096-01.dmp
    Number of processors: 6
    Main version: 15
    Minor Version: 7601
    Size of the dump file: 275 608
    Dump of file time: 16/11/2014-09:36:27
    ==================================================

    ==================================================
    Dump file: 111314-38657 - 01.dmp
    Crash time: 13/11/2014-18:35:27
    Bug Check String:
    Bug check code: 0 x 00000124
    Parameter 1: 00000000'00000000
    Parameter 2: fffffa80'07fa3038
    Parameter 3: 00000000'00000000
    Parameter 4: 00000000'00000000
    Caused by the driver: ntoskrnl.exe
    Caused by the address: ntoskrnl.exe + 4adb5c
    File description: NT kernel & system
    Product name: Microsoft® Windows® Operating System
    Company: Microsoft Corporation
    File version: 6.1.7601.18526 (win7sp1_gdr.140706 - 1506)
    CPU: x 64
    Plant address: ntoskrnl.exe + 4adb5c
    Stack address 1:
    The stack address 2:
    Address 3 the battery:
    Computer name:
    Full path: C:\Windows\Minidump\111314-38657-01.dmp
    Number of processors: 6
    Main version: 15
    Minor Version: 7601
    Size of the dump file: 262 144
    Dump of file time: 13/11/2014-18:35:49
    ==================================================

    ==================================================
    Dump file: 110514-33540 - 01.dmp
    Crash time: 11/05/2014-19:49:30
    Bug Check String:
    Bug check code: 0 x 00000124
    Parameter 1: 00000000'00000000
    Parameter 2: fffffa80'07f7e6c8
    Parameter 3: 00000000'00000000
    Parameter 4: 00000000'00000000
    Caused by the driver: ntoskrnl.exe
    Caused by the address: ntoskrnl.exe + 4adb5c
    File description: NT kernel & system
    Product name: Microsoft® Windows® Operating System
    Company: Microsoft Corporation
    File version: 6.1.7601.18526 (win7sp1_gdr.140706 - 1506)
    CPU: x 64
    Plant address: ntoskrnl.exe + 4adb5c
    Stack address 1:
    The stack address 2:
    Address 3 the battery:
    Computer name:
    Full path: C:\Windows\Minidump\110514-33540-01.dmp
    Number of processors: 6
    Main version: 15
    Minor Version: 7601
    Size of the dump file: 262 144
    Dump of file time: 11/05/2014-19:49:52
    ==================================================

    GT

    Both have been BCC124 two materials

    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
  • Whenever I connect to my HDTV using vga, I get a BSOD, even tried with different pc tv/cable

    Hello

    Thank you for taking the time to read this! Yesterday that I tried to connect to an HDTV using VGA instead of someone else, worked well. Buy a vga cable today and connected to my 1080 p full hd Phillips and got a BSOD almost instantly. I tried some things and managed to do the work! Played skyrim for a little and left the laptop in sleep mode. Came, open upward and the screen stayed black, nothing I could do to get a Visual.
    Now, whenever I connect the cable I get a BSOD, it works with any other laptop, excludes the cable and television.
    I have updated all drivers in the list, checked my drive for errors using the good chkdsk, smart status on the disk is good, all withdrew. I know for a fact that my laptop works fine with extra monitors, we use all the time on my internship and as stated, it worked yesterday on another TV.
    Features of the laptop:

    ASUS n73jn

    processor Intel i5 460 m
    NVIDIA geforce 335 m
    Windows 7 64 bit
    4 GB ddr3 RAM
    the HDMI port is dysfunctional, just a few flickering screens filled with black lines, that's why I try vga. My guess is the hdmi port is DOA, but did not have a hd tv up to 2 years after purchase.

    News of the capture of blue screen:
    ==================================================
    Dump file: 093012-44382 - 01.dmp
    Crash time: 30/09/2012-18:57:22
    Bug Check String: SYSTEM_SERVICE_EXCEPTION
    Bug check code: 0x0000003b
    Parameter 1: 00000000' c0000005
    Parameter 2: fffff880'074259 cd
    Parameter 3: fffff880'029f90a0
    Parameter 4: 00000000'00000000
    Caused by the driver: igdkmd64.sys
    Caused by the address: igdkmd64.sys + 1e29cd
    Description of the file:
    Product name:
    Company:
    Version of the file:
    CPU: x 64
    Plant address: ntoskrnl.exe + 7f1c0
    Stack address 1:
    The stack address 2:
    Address 3 the battery:
    Computer name:
    Full path: C:\Windows\Minidump\093012-44382-01.dmp
    Number of processors: 4
    Main version: 15
    Minor Version: 7601
    The dump file size: 262,144
    ==================================================
    Thanks for your time!

    Greetings,

    Joachim

    Sorry, I was a little confused with the HDMI and VGA - continues to be the same advice.

    Looks like you have isolated to a hardware problem.  With the Intel graphics card is not posted, I have to wonder if the hardware problem is with the graphics card Intel

    FWIW - we have seen a number of overheating problems with the graphics from nVidia on your model.  Make sure the laptop is on a hard surface - and I would also use a filling of cooling (if possible) to ensure that the system is not overheating.

    Install a new copy of Intel video drivers is probably the most important thing to do now - and ensure that this card appears in Device Manager (and check in the nVidia PhysX tab to see if it appears here - even though I'm not familiar with this program).

    Try the video stress tests here: http://www.carrona.org/addldiag.html
    They can show that there is a hardware problem - but a lot of this will involve what video card works at the time of the test (even once, I don't have a lot of experience to make systems to change video card).

    Good luck!

  • Problem with explore crashing.

    Separated from this thread.

    I have problem with explore crashing. This web page has not a place to post my question.

    Details of the accident are:

    The failing application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4
    The failed module name: ole32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c92c
    Exception code: 0xc0000005
    Offset: 0x00000000001729ac
    ID of the process failed: 0xcb0
    Start time of application vulnerabilities: 0x01cfd840a81222d8
    The failing application path: C:\Windows\Explorer.EXE
    The failed module path: C:\Windows\system32\ole32.dll
    Report ID: 7ae39c84-444c-11e4-b245-00030d000001

    Try this link:

    http://support.Microsoft.com/kb/2541119/en-us

Maybe you are looking for