BSOD issue with ntoskrnl.exe

Similar Questions

• BSOD with ntoskrnl.exe (nt + 75 b 80)

  Hello

  Can someone help me with the question BSOD. This BSOD occur intermittently and usually the BSOD caused by ntoskrnl.exe (nt + 75 b 80).
  I have attached the minidump as well.
  Kindly help me to check it out.
  SkyDrive:
  https://SkyDrive.live.com/redir?RESID=2BB9014DF75DB8D6! 1454 & authkey =! AAoIhuMavrJPqbc&ithint=folder%2c.dmp

  Goh KS

  These were related to driver USB Camera 5U877.sys from Ricoh co., Ltd..  I would remove at least to test

  You have also a driver of 2005 that need to be updated or deleted called SSPORT.sys 2005-08-11 18:07:32 (related to the SSPORT.sys 32-bit Port claim Driver of Samsung Electronics.)

• Receive lots of BSOD due to ntoskrnl.exe, they stopped, but started again after a month

  I get lots of BSOD. I installed "WhoCrashed" and analyze the dump files. Here's what he said:

  Saturday, October 3, 14 17:29:30 GMT PM your computer crashed
  crash dump file: C:\Windows\Minidump\031014-15147-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75B80)
  Bugcheck code: 0x4E (0 x 0x2007E, 0 x 2, 0 20075, 99)
  Error: PFN_LIST_CORRUPT
  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 the page frame number (PFN) list is corrupted.
  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.

  I have this problem for a long time. I've updated the drivers, windows updates, no effect. But, for some reason, he did not seem since February. But Monday, I used MiniCygwin_GOptimize_v1.34.02 to compress files apk android. He uses a lot of CPU. And after that the BSOD began to reappear. I downloaded the Minidump file and Information System if someone wants to check.

  Let me know the reason for these BSOD and how can I solve this problem.

  Hello

  We have many bug different controls:

  PFN_LIST_CORRUPT (4th)

  This indicates that the page frame number (PFN) list is corrupted.

  This error is usually caused by a driver passing a list of descriptor of bad memory. For example, the pilot could call MmUnlockPages twice with the same list.

  MEMORY_MANAGEMENT (1A)

  This indicates that an error occurred serious memory management.

  Error checking 1A, {5003, fffff780c0000000, 6933, 64ba0002d266}

  -1 setting of the bug check is 5003 which lists free work is corrupt. It is probably a hardware error.

  We also have another 1st parameter:

  Error checking 1 a, {fffff6800005cf40, eab00001beb34867,403, fffff6fc00df59a0}

  - Parameter 1 of the bug check is 403 which indicates the page table and NFPs are out of sync. It is also probably a clerical error.

  ^^ Pointed out that both of the above can still be caused by a driver causing corruption, but it is generally unlikely.

  And another...

  Error checking 1A, {41284, 159a0e001, 104 d 57, fffff70001080000}

  -1 setting of the bug check is 41284 indicating a PTE or the fixed work list is corrupted.

  BAD_POOL_HEADER (19)

  This indicates that a pool header is corrupt.

  Error checking 19, {20, fffff8a00b91df40, fffff8a00b91e020, 50e040c}

  6: kd >! pool fffff8a00b91df40
  Pool page fffff8a00b91df40 region is unknown
  fffff8a00b91d000 size: 4 d 0 previous size: 0 Ntff (allocated)
  fffff8a00b91d4d0 size: 30 size: 4 d 0 PfFK (allocated)
  fffff8a00b91d500 size: 30 size: 30 PfFK (allocated)
  fffff8a00b91d530 size: 10 previous size: 30 (free) NtfE
  fffff8a00b91d540 size: 30 size: 10 Ntf0 (allocated)
  fffff8a00b91d570 size: size previous 10:30 (free) Nbmc
  fffff8a00b91d580 size: 40 previous size: 10 DxgK (allocated)
  fffff8a00b91d5c0 size: c0 size previous: AfdX (protected) process (allocated) 40: fffffa801098c7f0
  fffff8a00b91d680 size: 170 previous size: c0 MPsc (allocated)
  fffff8a00b91d7f0 size: size previous c0: 170 FIcs (allocated)
  fffff8a00b91d8b0 size: 40 size: c0 (allocated) NtFs
  fffff8a00b91d8f0 size: 30 size: 40 (allocated) PfFK
  fffff8a00b91d920 size: 30 size: 30 Ntf0 (allocated)
  fffff8a00b91d950 size: 150 size: 30 FMfn (allocated)
  fffff8a00b91daa0 size: size 160: 150 FMfn (allocated)
  fffff8a00b91dc00 size: 40 size: 160 (allocated) MmSm
  fffff8a00b91dc40 size: c0 size previous: 40 FIcs (allocated)
  fffff8a00b91dd00 size: 10 size: c0 sect (free)
  fffff8a00b91dd10 size: 170 previous size: 10 MPsc (allocated)
  fffff8a00b91de80 size: size previous c0: 170 (allocated) NtFs
  * fffff8a00b91df40 size: size previous e0: c0 (free) * FIcs
          PoolTag FIcs: Context of FileInfo FS-Filter binary stream: fileinfo.sys

  ^^ Block of pool who looked in the page pool belongs to the context of FileInfo FS-Filter flow. This is related to the file system.

  6: kd >! poolval fffff8a00b91df40
  Pool page fffff8a00b91df40 region is unknown

  Validation of the headers of pool the pool page: fffff8a00b91df40

  [Fffff8a00b91d000] page pool is __inVALID.

  System_service_exception (3B)

  This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  
  This error has been linked to the excessive use of expanded memory and resulting from user mode graphics drivers enjambment and passing data incorrect of the kernel code.

  2: kd > fffff960000a874f ln
  (fffff960'000 a 8720)   win32k! NextOwnedWindow + 0x2f |  (fffff960'000 a 8770) win32k! xxxRemoveDeleteMenuHelper

  ^^ The exception is produced in win32k! NextOwnedWindow.

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

  Overall, this looks like the faulty RAM. It's not like there is a foul-smelling waters driver causing memory corruption here, but it is possible. The reason I mention this is because I see it in the crash dumps after dumping the! v

  OVERLAPPED_MODULE: Address overlap 'WinUsb' and 'ssudbus.sys'.

  ^^ WinUsb.sys - pilot class USB Windows system, it is a part of Windows. ssudbus.sys-

  SAMSUNG USB Composite Device Driver. Probably a part of Samsung Kies. Uninstall everything that you can find this topic.

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

  Please run Memtest for NOT LESS than 8 ~ (several hours):

  Memtest86 +:

  Download Memtest86 + here:

  http://www.memtest.org/

  Which should I download?

  You can either download the ISO pre-built you want to burn to a CD and then boot from the CD, or you can download the automatic installer of the USB. What this will do is format your USB drive, make a boot device and then install the necessary files. Both do the same job, it's just you that you choose, or you have available (be it CD or USB).

  Note that some older generation motherboards do not support USB boot, your only option is CD (or floppy if you really wanted to).

  How Memtest works:

  Memtest86 writes a series of test patterns for most of the addresses of memory, reads the written data and compares it to find errors.

  The default pass is 9 different tests, varying in the modes of access and test data. A tenth test, bland, is selectable in the menu. He wrote all the memory with zeros, then sleeps 90 minutes before checking to see if the bits have changed (perhaps because of refresh problems). This is repeated with all those for a total time of 3 hours by pass.

  Many chipsets can report RAM speed and timings by SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclockee, Memtest86 can test that memory is free of error with these faster settings.

  Some hardware is able to report the status of the "PAT" (PAT: active or PAT: disabled). This is a reference to the Intel performance acceleration technology; There may be the BIOS settings that affect this aspect of memory synchronization.

  This information, if it is available for the program, can be displayed via a menu option.

  Other questions, they can most likely be answered by reading this excellent guide here:

  http://Forum.canardpc.com/threads/28864-FAQ-please-read-before-posting

  Kind regards

  Patrick

• 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

• Windows 8 BSOD caused by ntoskrnl.exe

  Hello.

  I get a lot of the dreaded BSOD lately.
  From the beginning I thought that it's nvidia drivers. Update of those fixed everything except a BSOD I get.
  Now I get the same BSOD, and it is caused by ntoskrnl.exe and playback memory problems.
  I've been all around you are looking for assistance and use of memtest86 without result.
  The Msinfo32 and .dmp files are located here: DMP.zip 
  Anyone have any idea what may be causing this?
  I couldn't find the RAM that I use in the compatibility table for the motherboard. So that's what I think may cause the problem.
  Any help is greatly appreciated.
  Kind regards
  Arve

  Hi Arve,

  All attached files of the DMP are the bug check IRQL_NOT_LESS_OR_EQUAL (a) .

  This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.

  This bug check is issued if the memory paged (or invalid) is accessible when the IRQL is too high. The error that usually generates this bug check occurs after the installation of the faulty device driver or service system, BIOS.

  If we look at the call stack:
  
  STACK_TEXT:
  "fffff880 '0335caf0 fffff880' 06a4d817: fffff880 00000000' fffffa80 ' 00000008 fffffa80 ' 12fdbe10 00000005' 00001f80: nt! KeSetEvent + 0x2ad
  fffff880 '0335cb60 00000000 fffff880': fffffa80'00000008 fffffa80 '12fdbe10 00000005' 00001f80 fffffa80' 1458a6a0: MBfilt64+ 0 x 1817
  fffff880'0335cb68 fffffa80'00000008: fffffa80 '12fdbe10 00000005' 00001f80 fffffa80 '1458a6a0 fffff800' 9bc62d4c: 00000000' 0xfffff880
  fffff880 '0335cb70 fffffa80' 12fdbe10: 00000005' 00001f80 fffffa80'1458a6a0 fffff800 '9bc62d4c fffffa80' 1458a6a0: 0xfffffa80'00000008
  fffff880 '0335cb78 00000005' 00001f80: fffffa80 ' 1458a6a0 fffff800 '9bc62d4c fffffa80' 1458a6a0 fffffa80 ' 1458a6a0: 0xfffffa80'12fdbe10
  fffff880 '0335cb80 fffffa80' 1458a6a0: fffff800 ' 9bc62d4c fffffa80 '1458a6a0 fffffa80' 1458a6a0 fffffa80 ' 12fdbe10: 0 x 5 ' 00001f80
  fffff880 '0335cb88 fffff800' 9bc62d4c: fffffa80 ' 1458a6a0 fffffa80 '1458a6a0 fffffa80' 12fdbe10 fffff880 ' 02fc9f00: 0xfffffa80'1458a6a0
  fffff880 '0335cb90 00000000' 00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! ViPendingCompleteAfterWait + 0xc4

  Cannot load the image MBfilt64.sys, 0n2 error Win32
  WARNING: Unable to verify timestamp for MBfilt64.sys
  ERROR: Module load completed but symbols can be loaded for MBfilt64.sys
  Probably caused by: MBfilt64.sys (MBfilt64 + 1817)

  ^^
  Driver Realtek HiDefinition Audio (referred to as Creative Audio Driver file).

  If we run a lmvm on your:

  4: kd > lmvm MBfilt64
  start end module name
  fffff880 '06a4c000 fffff880' 06a5a000 MBfilt64 T (no symbol)
  Loaded symbol image file: MBfilt64.sys
  Image path: MBfilt64.sys
  Image name: MBfilt64.sys
  Timestamp: Thu Aug 30 23:40:32 2009 (4A7267B0)

  ^^, Yours is dated 2009 ~ The most recent is AFAIK as early as September 2013, via - Realtek site

  http://www.Realtek.com.tw/downloads/downloadsCheck.aspx?langid=1&PNid=24&PFID=24&level=4&Conn=3&DownTypeID=3&GETDOWN=false

  To update this driver as soon as POSSIBLE.

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

  In addition, to provide peace of mind regarding your request of RAM. If you receive a card mother and they have a list of the RAM compatible in the manual, etc., this is called a QVL (qualified suppliers list). It is simply a list of RAM which has been tested internally and is PROVING to be quite compatible 100%. If the RAM is not on the list, it is not by all means, implies that the RAM will be inconsistent and cause problems. Actually today is very rare. Your RAM doesn't seem to be the issue at all in these accidents.

  Kind regards

  Patrick

• Crash blue screen by Page fault with ntoskrnl.exe

  My laptop has been crashing every time than in quite awhile for these last months. It shows the blue screen "physical basis '' dumping and then crashes to black. Subsequently, the computer restarts and just told me that an error has occurred that crashed it.

  I downloaded BlueScreenView to check what was causing the error and found that the pilot "ntoskrnl.exe" broke due to "PAGE_FAULT_IN_NONPAGED_AREA"

  I tried to look for possible solutions, such as windows update and my computer of compensation so the hard drive wasn't full. None of these worked; I have had no updates available and 120 GB of free HDD GB 970.

  Here is a link to my OneDrive with my dump files:

  Please help, I don't want my computer crashing on me more.

  Edit: I have uninstalled and reinstalled the drivers. I'll wait and see if it keeps crashing. Updates in the month or two a report.

  Associated with the AtihdLH3.sys high definition Audio function Driver of ATI Technologies, Inc.

  Remove the driver current completely and install the latest driver available.  For instructions on how to do read everything to update the drivers of my partner JMH3143 http://answers.microsoft.com/en-us/windows/wiki/windows_other-hardware/updating-a-driver/a5e6345e-af9b-4099-bef0-8d22254aa1c1?tm=1436753520149 here

  The blue screen is wrong at least as often it is correct.

• I need assistance with ntoskrnl.exe + 7efc0, any help is appreciated

  I keep getting the BSOD errors and when I look at the mistakes I see:

  Ntoskrnl.exe + 7efc0

  and

  Tcpip.sys + d56b2

  and

  fwpkclnt.sys + 8172

  and

  mfewfpk.sys + 2ff80

  Please help me as I have done everything I can

  Clundeen

  In my previous post, I asked for the DMP REAL files. While I appreciated the synopsis I can review the DMP data in detail.

  BTW, your McAfee & Norton (never a good idea to run 2 malicious software apps) may be the problem itself

• BSOD caused by ntoskrnl.exe - bug DRIVER_POWER_STATE_FAILURE

  Hi all

  I'd appreciate help with my laptop problems I don't know neither the cause nor the solution...

  For several months, my laptop refuses to close directly. I explain: when I want to stop it, any reboot my laptop and I have to stop him again so he can actually stopped. In addition, at each attempt to stop / restart, I have this incredible Blue Screen of Death for 15 to 20 minutes, then my laptop actually restarts. Once it has restarted, it works normally for 3 minutes and then freezes for a duratation ranging from 5 min to 40 min...

  In addition, since the beginning of these problems, my laptop detects no USB devices (mouse, external driver...)...

  Please help me, this situation is driving me crazy...

  My laptop is an Asus ux32v and runs on 64-bit processor - i5 3317U and Windows 8 (if it helps).

  Here is the link to my minidump files:

  https://www.dropbox.com/sh/ix3bf3v7aog2xz5/AAAcgX3yNBDWVAj5JXs9JNzSa?DL=0

  I tried to open these files with software like BlueScreenView but couldn't do much about it. What I realized is that it was caused by ntoskrnl.exe.

  Thank you in advance for your help!

  MS

  It is possible because you do not remove it completely.  He was always loaded into the current DMP file

  You do not update to win 8.1.  I'll wait until you do.

• BSOD - NETIO.sys, NTOSKRNL.exe - DRIVER_IRQL_NOT_LESS_OR_EQUAL STOP: 0x000000d1

  Hello
  I am experiencing BSOD. Bed "DRIVER_IRQL_NOT_LESS_OR_EQUAL" Stop error: 0x000000d1.
  Drivers show NETIO.sys and NTOSKRN.exe.
  I'm running Lenovo T540p Windows Version 6.1.7601 with the latest updates.
  Here is the link to the dump file.
  https://SkyDrive.live.com/?CID=0E6019D47C4472B6&ID=E6019D47C4472B6%21163
  A hotfix is available? Dump file, can you tell which driver is causing BSOD?
  Thanks in advance!

  Hello

  In addition to checking the filter driver Web FortiClient also check for update with your network
  drivers because there is often an interaction involved.

  Check with Lenovo support, their drivers and documentation online and ask in their forums
  on known problems. Update the network drivers.

  Support from Lenovo and downloads
  http://www-307.IBM.com/PC/support/site.WSS/homeLenovo.do

  Lenovo forums
  http://forums.Lenovo.com/

  I hope this helps.

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

• Major issues with plugincontainer.exe gel firefox 34 CPU high usage

  Plugincontainer.exe is ruining my experience with firefox by endlessly to freeze due to the high utilization of the processor. Please provide a work around or another solution. Thank you.

  Thanks for posting back. Looks like it's pages using the plugin container are the important source of the processor.

  It is possible to disable hardware acceleration of Flash to see if there are improvements:

  • Flash Plugin - maintain and troubleshoot

  Please tell us if it helped!

• BSOD caused by ntoskrnl.exe (and maybe hal.exe?)

  Hi all

  I don't have much experience in debugging BSOD minidumps so I turn for help. Attached all my files dump in time past. All caused my computer to turn off instantly, of course, sometimes it turns even off exactly when windows loads. From the little I know, I think maybe it's a hardware failure (0 x 124), but I'm not sure. Any help would be greatly appreciated.

  Here is the download link: MiniDump

  Thank you very much for any help!

  Hello

  References to Vista also apply to Windows 7.

  This is my generic how updates of appropriate driver:

  This utility, it is easy see which versions are loaded: run DriverView - set the VIEW to hide
  Microsoft drivers - update those without drain in their names. (Also update BIOS and)
  drivers chipset on the site of the constructor/the system motherboard.)

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

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

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

  Now in the system manufacturer (Dell, HP, Toshiba as examples) site (in a restaurant), peripheral
  Site of the manufacturer (Realtek, Intel, Nvidia, ATI, for example) and get their latest versions. (Look for
  BIOS, Chipset and software updates on the site of the manufacturer of the system here.)

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

  Always check in the Device Manager - drivers tab to be sure the version you actually install
  presents itself. This is because some restore drivers before the most recent is installed (sound card drivers
  in particular that) so to install a driver - reboot - check that it is installed and repeat as
  necessary.

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

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

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

  If you update the drivers manually, then it's a good idea to disable the facilities of driver under Windows
  Updates, this leaves ONE of Windows updates, but it will not install the drivers who will be generally
  be older and cause problems. If updates offers a new driver and then HIDE it (right click on it)
  and then go look for new ones manually if you wish.

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

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

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

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

  For the Windows Memory Diagnostic tool.

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

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

  I hope this helps.

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

• 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
  http://captaindbg.com/bug-check-0x124-whea_uncorrectable_error-how-to-troubleshoot/

• Ntoskrnl.exe BSOD at random

  I get a BSOD caused by ntoskrnl.exe or ntfs.sys, with a lot of different bugs 0x0f and 0x0A 0x01E. I used WhoCrashed to help me find what it was, but in no avai.

  Here at random, take a few minutes to a few hours.
  Here are the logs of WhoCrashed

  Thursday, November 10, 2011 2:48:45 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110911-26130-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0x213D8)
  Verification of error code: 0 x 24 (0xFFFFF88009D8C348, 0xFFFFF88009D8BBB0, 0x1904FB, 0xFFFFF80002EE2EEA)
  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.

  Thursday, November 10, 2011 2:48:45 AM GMT crashed your computer
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0x213D8)
  Verification of error code: 0 x 24 (0xFFFFF88009D8C348, 0xFFFFF88009D8BBB0, 0x1904FB, 0xFFFFF80002EE2EEA)
  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.

  Thursday, November 10, 2011 2:18:09 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110911-19515-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0x212A3)
  Verification of error code: 0 x 24 (0xFFFFF88008DD4708, 0xFFFFF88008DD3F70, 0 x 190477, 0xFFFFF80002EA5C84)
  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.

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

  Wednesday, November 9, 2011 11:39:15 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110911-20638-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x705C0)
  Bugcheck code: 0xA (0xFFFFF880029ED988, 0xFFFFF80002D205F1, 0x2, 0x0)
  Error: IRQL_NOT_LESS_OR_EQUAL
  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 Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.
  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.

  Thursday, October 27, 2011 7:49:38 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110911-25162-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x705C0)
  Bugcheck code: 0xD1 (0xFFFFF8808327B1DA, 0xFFFFF880042A41EA, 0x2, 0 x 1)
  Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a kernel-mode driver attempted to access pageable memory with a high IRQL.
  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.

  Thursday, October 27, 2011 3:11:46 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\102611-21106-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0 x 70600)
  Bugcheck code: 0x3B (0xC0000005, 0x1, 0x0, 0xFFFFF88009B94300)
  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.

  Let me know if I need to download the DPM

  Hello

  Doubt that its windows for millions would have the same questions.

  If you think that your Windows installation disc is damaged, try these as a test.

  This will give you a method to make and install from another disk as a test.

  Windows 7 Enterprise - 90 day trial
  http://TechNet.Microsoft.com/en-us/evalcenter/cc442495.aspx

  They will help make you the ERD that are bootable.

  If you need to repair disks - these help repair Windows not re-install.
  Often an ERD will help you when the recovery disk does not work.

  Download Windows 7 system recovery discs - charge now $9.75 for ISO
  images to make the discs.
  http://NeoSmart.net/blog/2009/Windows-7-system-repair-discs/

  How to create a Windows 7 - free system repair disc
  http://www.SevenForums.com/tutorials/2083-system-repair-disc-create.html

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

  These make it bootable Linux disks with many public services:

  Hiren Boot CD
  http://www.hirensbootcd.org/

  Rescue Kit Trinity
  http://trinityhome.org/home/index.php?wpid=1&front_id=12

  System Rescue CD
  http://www.SysRescCd.org/Main_Page

  Knoppix
  http://www.Knoppix.NET/

  Scan a Windows PC for viruses from a Ubuntu Live CD
  http://www.howtogeek.com/HOWTO/14434/scan-a-Windows-PC-for-viruses-from-a-Ubuntu-Live-CD/

  Use Ubuntu Live CD to backup files from your Windows computer dead
  http://www.howtogeek.com/HOWTO/Windows-Vista/use-Ubuntu-Live-CD-to-backup-files-from-your-dead-Windows-computer

  I hope this helps.

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

• Serscan.sys ntoskrnl.exe BSOD

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

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

  Process of own fffffa800b83b380 Image: RapportService

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

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

  Driver Verifier - stalking a bad driver to behave.

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

• Ntoskrnl.exe SYSTEM_SERVICE_EXCEPTION

  Hello

  I get BSOD at random times, and the use of blue screen I determined the problem with ntoskrnl.exe file. Although I had similar problems with dxgkrnl.sys. The problem is very annoying and can happen completely randomly.

  A problem has been detected and Windows has been shut down to avoid damage
  on your computer.

  The problem seems to be caused by the following file: ntoskrnl.exe

  SYSTEM_SERVICE_EXCEPTION

  If this is the first time you've seen this stop error screen,
  Restart your computer. If this screen appears again, follow
  the following steps:

  Check to make sure any new hardware or software is installed correctly.
  If this is a new installation, ask your hardware manufacturer or software
  the Windows updates, you might need.

  If problems continue, disable or remove any newly installed hardware
  or software. Disable the BIOS memory options such as implementing caching or shading.
  If you need to use safe mode to remove or disable components, restart
  your computer, press F8 to select Advanced Startup Options and then
  select Safe Mode.

  Technical information:

  STOP: 0X0000003B (0X00000000C0000005, 0XFFFFF80002507F4F, 0XFFFFFA600E2D30C0,
  0 x 0000000000000000)

  Ntoskrnl.exe - address 0xfffff800022a3450 base at 0xfffff80002249000 DateStamp
  0x4a7801eb

  Thanks for your help

  Luke

  Hello

  1. turn your Page file - change anything to the value if you plan to leave it like that (make a little
  (- reboot - largest) then go back and revert to the DEFAULT value.

  How to change the virtual memory paging file in Vista
  http://www.Vistax64.com/tutorials/132201-virtual-memory-paging-file-change.html

  2 do these to erase corruption and missing/damaged file system repair or replacement.

  Start - type in the search box - find command top - RIGHT CLICK – RUN AS ADMIN

  sfc/scannow

  How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program
  generates in Windows Vista cbs.log
  http://support.Microsoft.com/kb/928228

  Then, run checkdisk - schedule it to run at next boot, then apply OK your way out, then restart.

  How to run the check disk at startup in Vista
  http://www.Vistax64.com/tutorials/67612-check-disk-Chkdsk.html

  3. update your video/display drivers manually using these methods.

  It's my generic how updates of appropriate driver: (you must manually update the video/display drivers)

  This utility, it is easy see which versions are loaded:

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

  For drivers, visit manufacturer of emergency system and of the manufacturer of the device that are the most common.
  Control Panel - Device Manager - Display Adapter - note the brand and complete model of your
  video card - double - tab of the driver - write version information. Now click on UPdate Driver (this
  cannot do anything as MS is far behind the certification of drivers) - then do a right click - Uninstall - REBOOT
  This will refresh the driver stack.

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

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

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

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

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

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

  How to install a device driver in Vista Device Manager
  http://www.Vistax64.com/tutorials/193584-Device-Manager-install-driver.html

  If you update the drivers manually, then it's a good idea to disable the facilities of driver in the Windows updates,
  This leaves ONE of Windows updates, but it will not install the drivers who are generally older and cause
  questions. If updates offers a new driver and then hide it (right click on it) and then go look for new ones
  manually if you wish.

  How to disable automatic driver Installation in Windows Vista - drivers
  http://www.AddictiveTips.com/Windows-Tips/how-to-disable-automatic-driver-installation-in-Windows-Vista/
  http://TechNet.Microsoft.com/en-us/library/cc730606 (WS.10) .aspx

  Hope these helps.

  Rob - bicycle - Mark Twain said it is good.