DRIVER_CORRUPTED_EXPOOL

Similar Questions

• Windows 7: BAD_POOL_CALLER, then DRIVER_CORRUPTED_EXPOOL blue screens.

  Hi all

  I experienced a blue screen for months, using BlueScreenView, it's especially:

  BAD_POOL_HEADER

  BAD_POOL_CALLER

  DRIVER_CORRUPTED_EXPOOL

  DRIVER_IRQL_NOT_LESS_OR_EQUAL

  Crashes. It was during the past year. Recently, it has been more than the BAD_POOL_CALLER who ends up killing machine, and I'm getting tired of him. Does anyone have any suggestions as to what this might be? The most recent event is this:

  http://PUU.sh/bhEr8/5644b55d15.PNG

  So a BAD_POOL_CALLER began, then when Windows tried to reboot (twice), I got a DRIVER_CORRUPTED_EXPOOL. How can I find out exactly what the cause is here?

  This is C:/Windows/Minidump, btw.

  https://onedrive.live.com/redir?RESID=463B62EEFE2B6349%21142

  Thank you to all or part of this who can help!

  FT

  All these 2013 & 2104 are related to memory corruption cuased by two things.  The previous ones were e1c62x64.sys Gigabit adapter NDIS 6.x driver of Intel Corporation.  Yours is 2012.  I remove this driver and install the latest driver available.  I would also like to update your iAstor.sys as is often problematic in your have version (2010)

  The second question (which I think is the real reason your Symantec.  I remove it and use Microsoft security essentials in its place.

  Symantec is a common cause of BSOD.

  
  

  I remove and replace it with Microsoft Security Essentials at LEAST FOR TESTER
  http://us.Norton.com/support/kb/web_view.jsp?wv_type=public_web&docURL=20080710133834EN

  http://www.Microsoft.com/security_essentials/

  Use it to Norton 360 http://Symantec.pcperformancetools.com/Norton-360-how-to-uninstall.html 

  

• XPS 15 (9550) Windows BSOD 10 DRIVER_CORRUPTED_EXPOOL

  I have experience at least one daily BSOD on my new Dell XPS 15 (9550) running Windows 10.  DRIVER_CORRUPTED_EXPOOL.  Ntoskrnl.exe + 151d0

  You have updated to the latest version of the BIOS? Yes.

  Your drivers are up to date?  Yes.

  Are you running the driver version 1.1 for the SSD is Samsung?  Yes

  Do you use UEFI in AHCI mode?  Yes

  You have reloaded your operating system from scratch?  Yes.

  I'm curious to know after you have reinstalled Windows, how long to wait before installing programs or drivers, just to let the system run Windows only and see if you still receive the error?  I'm almost tempted to suggest working with the system in SafeMode overnight and check in the morning to see if there are blue screens.

  I could check the resource monitor and see if all programs stand using an abnormal amount of system resources, open Task Manager (press the windows with the x button, choose Task Manager) click on the performance tab and then click the resource monitor button. You can see at a glance which fits CPU, memory, disk and network resources and maybe get a hint about what is at the origin of the problem.

  I you will be shooting a friendship, with the erratic error request so I'm careful about suggesting replacements of parts, but if the problem persists, it may be something to consider.

  TB

• Problem with control of bug 0xC5: DRIVER_CORRUPTED_EXPOOL on the virtual machine (Windows Server 2012 R2) - TDI vShield Manager error on vnetflt.sys

  Hello guys, I'm having this problem:

  KB.VMware.com/selfservice/microsites/Search.do?Language=en_US & cmd = displayKC & externalId = 2081616

  The thing is that my ESXi hosts run 5.1 Patch Update 3 7 and this says KB updated to 5.1 Patch Update 2 6.

  No idea what to do?

  Thank you

  I just reinstalled the VMware tools without the vnetflt.sys driver and the problem resolved.

• Blue screen of death (Minidump) - several stop codes.

  Hello

  ==================================================
  Dump file: Mini101911 - 02.dmp
  Crash time: 2011-10-19 14:22:12
  Bug Check String: KERNEL_MODE_EXCEPTION_NOT_HANDLED
  Bug check code: 0x1000008e
  Parameter 1: 0xc0000005
  Parameter 2: 0xbf80124b
  Parameter 3: 0xba127a48
  Parameter 4: 0x00000000
  Caused by the driver: win32k.sys
  Caused by the address: win32k.sys + 124 b
  Description of the file: multi-user Win32 Driver
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 5.1.2600.6149 (xpsp_sp3_gdr.110906 - 1620)
  Processor: 32-bit
  Plant address: win32k.sys + 124 b
  Stack address 1: win32k.sys + 831d0
  Stack address 2: win32k.sys + b8fa7
  Battery 3 address: win32k.sys + 1142
  Computer name:
  Full path: C:\windows\Minidump\Mini101911-02.dmp
  Number of processors: 2
  Main version: 15
  Minor Version: 2600
  Size of the dump file: 94 208
  ==================================================

  ==================================================
  Dump file: Mini101911 - 01.dmp
  Crash time: 19/10/2011-12:01:17
  Bug Check String: DRIVER_CORRUPTED_EXPOOL
  Bug check code: 0x100000c5
  Parameter 1: 0 x 00000004
  Parameter 2: 0x00000002
  Parameter 3: 0x00000001
  Parameter 4: 0x8054bfd2
  Caused by the driver: sr.sys
  Caused by the address: sr.sys + 4bbf
  Description of the file: System Restore filesystem filter driver
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 5.1.2600.5512 (xpsp.080413 - 2108)
  Processor: 32-bit
  Plant address: ntoskrnl.exe + 74fd2
  Stack address 1: ntoskrnl.exe + 19eb1
  Stack address 2: ntoskrnl.exe + aca58
  Battery 3 address: ntoskrnl.exe + e44aa
  Computer name:
  Full path: C:\windows\Minidump\Mini101911-01.dmp
  Number of processors: 2
  Main version: 15
  Minor Version: 2600
  Size of the dump file: 94 208
  ==================================================

  ==================================================
  Dump file: Mini101811 - 02.dmp
  Crash time: 2011-10-18 12:45:15
  Bug Check String: DRIVER_CORRUPTED_EXPOOL
  Bug check code: 0x100000c5
  Parameter 1: 0x00076e14
  Parameter 2: 0x00000002
  Parameter 3: 0x00000001
  Parameter 4: 0x8054bfd2
  Caused by the driver: Ntfs.sys
  Caused by the address: Ntfs.sys + 575 b
  Description of the file: NT File System Driver
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 5.1.2600.5512 (xpsp.080413 - 2111)
  Processor: 32-bit
  Plant address: ntoskrnl.exe + 74fd2
  Stack address 1: ntoskrnl.exe + 19eb1
  Stack address 2: ntoskrnl.exe + aca58
  Battery 3 address: ntoskrnl.exe + e44aa
  Computer name:
  Full path: C:\windows\Minidump\Mini101811-02.dmp
  Number of processors: 2
  Main version: 15
  Minor Version: 2600
  Size of the dump file: 94 208
  ==================================================

  ==================================================
  Dump file: Mini101811 - 01.dmp
  Crash time: 2011-10-18 12:23:39
  Bug Check String: IRQL_NOT_LESS_OR_EQUAL
  Bug check code: 0x1000000a
  Parameter 1: 0x005c003a
  Parameter 2: 0x0000001c
  Parameter 3: 0x00000001
  Parameter 4: 0x80502cd6
  Caused by the driver: ntoskrnl.exe
  Caused by the address: ntoskrnl.exe + 2bcd6
  File description: NT kernel & system
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 5.1.2600.6055 (xpsp_sp3_gdr.101209 - 1647)
  Processor: 32-bit
  Plant address: ntoskrnl.exe + 2bcd6
  Stack address 1: ntoskrnl.exe + 2bf2f
  Stack address 2: ntoskrnl.exe + 230d9
  Battery 3 address: ntoskrnl.exe + 2316c
  Computer name:
  Full path: C:\windows\Minidump\Mini101811-01.dmp
  Number of processors: 2
  Main version: 15
  Minor Version: 2600
  Size of the dump file: 94 208
  ==================================================

  So, I'm wondering for corrupted files, I can just remove or repair? For example, I got a blue screen of death before, so I remove the source of the blue screen of death which is

  ==================================================
  Dump file: Mini070811 - 01.dmp
  Crash time: 08/07/2011-18:28:31
  Bug Check String: IRQL_NOT_LESS_OR_EQUAL
  Bug check code: 0x1000000a
  Parameter 1: 0 x 00000016
  Parameter 2: 0x0000001c
  Parameter 3: 0x00000000
  Parameter 4: 0x80502eb4
  Caused by the driver: adasprot32.sys
  Caused by the address: adasprot32.sys + 1440
  Description of the file:
  Product name:
  Company:
  Version of the file:
  Processor: 32-bit
  Plant address: ntoskrnl.exe + 2beb4
  Stack address 1: ntoskrnl.exe + 2329e
  Stack address 2: adasprot32.sys + b31
  Battery 3 address: ntoskrnl.exe + 1819f
  Computer name:
  Full path: C:\WINDOWS\Minidump\Mini070811-01.dmp
  Number of processors: 2
  Main version: 15
  Minor Version: 2600
  Size of the dump file: 94 208
  ==================================================

  This is an example for you to understand the process. The essential 'Address', what is more important than 'address crash' and ' address 1-3' of the battery. I delete the corrupt of this show. So I wonder is that files that are displayed as blue screen of death appear as new files or has been corrupted (not new, but the changes) so that files is important, it is not good to remove it but just fix it? In this case, it is program file, so that files can be removed, but for above I'll list five blue screen of death (at the top of this page and recently), is files computer, more important than the program files. So I can delete files, but it would affect the entire computer? Or fix it? Another thing that is feature computer sank black and can't restart for some time. Thus, the program can cause corrupted files or delete files that is corrupt to become new and separate, which means that it can be? Are there two types of files? SE do not become like nine files can you repair files, but changes or files that become like new but bad files, it can therefore be removed. Thus, since the site Web who say it is the right program or files, but it is good to scan files that can cause of spyware, malware, virus or a program? So, do you know what could be cause of the last blue screen of death to connect to black on computer screen. It's as if I hard harddirve, but this isn't like that. This is exactly the same process of result with old hard drive causing the computer screen black, but this case is different departure process. If you tell me to use the cd, to solve the problem, tell me what cd and if it is a restore cd that say recovery on the cd for xp or more. It is large and clear a word that mean the recovery? If this is the case, I don't have it. Well, don't have no possible, but in case I did not.

  Hello Khalif Foster,

  It may be a problem with the Table of master files on the hard drive that does not, however, another option is to use the tool in the mentionted Knowledge Base article.

  Using Driver Verifier to identify issues with Windows drivers for users advanced

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

  To verify exactly which driver may be the cause of this problem. (if you don't believe the issue is the hard drive).

  Hope this information helps.

• Blue screen of death-IRQ_... driver ntoskrnl.exe plus 2 other cause problem

  Blue screens reappear.

  I have scanned for viruses using Mcafee, Malwarebytes, superantispyware,

  I uninstalled the programs deleted files... do not know what is gong. Here's... more information please help!

  Computer information:

  Name of the operating system Microsoft Windows XP Home Edition
  Version 5.1.2600 Service Pack 3 Build 2600
  Manufacturer of operating system Microsoft Corporation
  System manufacturer Gateway
  System model D915GAG_
  System Type X 86-based PC
  Processor x 86 family 15 model 3 Stepping 4 GenuineIntel ~ 3200 Mhz
  BIOS Version/Date Intel Corp., EV91510A.15A.0067.2004.0722.1717, 22/07/2004
  SMBIOS Version 2.3
  Windows C:\WINDOWS directory
  System directory C:\WINDOWS\system32
  Boot Device \Device\HarddiskVolume1
  Hardware Abstraction Layer Version = "5.1.2600.5512 (xpsp.080413 - 2111).
  Total physical memory 512,00 MB
  Available physical memory 73,34 MB
  Total virtual memory 2.00 GB
  Available virtual memory 1.96 GB
  Page file space 1.22 GB
  Paging file C:\pagefile.sys

  I used the program BlueScreenView for minidump files:

  ==================================================
  Dump file: Mini081810 - 01.dmp
  Crash time: 08/18/2010-15:58:56
  Bug Check String: IRQL_NOT_LESS_OR_EQUAL
  Bug check code: 0x1000000a
  Parameter 1: 0x00000000
  Parameter 2: 0x00000002
  Parameter 3: 0x00000001
  Parameter 4: 0x80701a79
  Caused by the driver: hal.dll
  Caused by the address: hal.dll + 2 has 79
  Description of the file: Hardware Abstraction Layer DLL
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 5.1.2600.5512 (xpsp.080413 - 2111)
  Processor: 32-bit
  Computer name:
  Full path: C:\WINDOWS\Minidump\Mini081810-01.dmp
  Number of processors: 2
  Main version: 15
  Minor Version: 2600
  ==================================================

  ==================================================
  Dump file: Mini081710 - 01.dmp
  Crash time: 08/17/2010 11:10:06
  Bug Check String: IRQL_NOT_LESS_OR_EQUAL
  Bug check code: 0x1000000a
  Parameter 1: 0 x 00000004
  Parameter 2: 0x00000002
  Parameter 3: 0x00000000
  Parameter 4: 0x804e7f0d
  Caused by the driver: hal.dll
  Caused by the address: hal.dll + 2428
  Description of the file: Hardware Abstraction Layer DLL
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 5.1.2600.5512 (xpsp.080413 - 2111)
  Processor: 32-bit
  Computer name:
  Full path: C:\WINDOWS\Minidump\Mini081710-01.dmp
  Number of processors: 2
  Main version: 15
  Minor Version: 2600
  ==================================================

  ==================================================
  Dump file: Mini081610 - 01.dmp
  Crash time: 08/16/2010 12:54:11
  Bug Check String: DRIVER_CORRUPTED_EXPOOL
  Bug check code: 0x100000c5
  Parameter 1: 0x0a030001
  Parameter 2: 0x00000002
  Parameter 3: 0x00000000
  Parameter 4: 0x8055196d
  Caused by the driver: USBSTOR. SYS
  Caused by the address: USBSTOR. SYS + 1440
  File description: USB mass storage class driver
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 5.1.2600.5512 (xpsp.080413 - 2108)
  Processor: 32-bit
  Computer name:
  Full path: C:\WINDOWS\Minidump\Mini081610-01.dmp
  Number of processors: 2
  Main version: 15
  Minor Version: 2600
  ==================================================

  Hi Nass1:

  Can you be specific with the name of the tool mentioned in your statement below? Thank you

  "It will be a good idea to test the RAM by using the windows crash Analyzer tool you can download from Microsoft."

• blue screen with windows vista

  Hello! yesterday a blue screen appeared on my compaq 6830 s with windows vista. I used view bluescreen

  Here's what I read:

  Mini063015 - 01.dmp 30/06/2015 1.33.33 0x0000000b 0x000000c5 DRIVER_CORRUPTED_EXPOOL 0x00000002 0 x 00000001 0x822f5010 ecache.sys ecache.sys + 17c48 special memory device Cache Microsoft® Windows® operating system Microsoft Corporation 6.0.6002.18005 (lh_sp2rtm.090410 - 1830) 32-bit ntkrnlpa.exe + 4dfd9 ntkrnlpa.exe + ee010 ecache.sys + b142 ntkrnlpa.exe + a71fb C:\windows\Minidump\Mini063015-01.dmp 2 15 6002 133.792

  CLASSPNP. CLASSPNP SYS. SYS + fcbc5a48 0x83a27000 0x83a48000 0 x 00021000 0x49e01ee9 2009-11-04 6.39.05 class System Dll Microsoft® Windows® operating system SCSI 6.0.6002.18005 (lh_sp2rtm.090410 - 1830) Microsoft Corporation C:\windows\system32\drivers\CLASSPNP. SYS
  Ecache.sys ecache .sys + 17c48 0x8bba2000 0x8bbc9000 0 x 00027000 0x49e01f2c 2009-11-04 6.40.12 Microsoft® Windows® operating system special device Cache Memory 6.0.6002.18005 (lh_sp2rtm.090410 - 1830) Microsoft Corporation C:\windows\system32\drivers\ecache.sys
  iastor.sys iastor.sys + fcb9cb1c 0x83a50000 0x83b2a000 0x000da000 0x4bba0dee 04/05/2010 18.21.02 Intel Matrix Storage Manager driver Intel Matrix Storage Manager driver - ia32 8.9.8.1005 Intel Corporation C:\windows\system32\drivers\iastor.sys
  MUP.sys mup.sys + d023 0x8bb93000 0x8bba2000 0x0000f000 0x49e01914 driver Microsoft® Windows® operating system Multiple UNC Provider 2009-11-04 6.14.12 6.0.6002.18005 (lh_sp2rtm.090410 - 1830) Microsoft Corporation C:\windows\system32\drivers\mup.sys
  Ntkrnlpa.exe ntkrnlpa.exe + ee010 0 x 82207000 0x825c0000 0x003b9000 0x4b7d1e08 18/02/2010 13.01.28 Microsoft® Windows® NT Kernel operating system & 6.0.6002.18209 (vistasp2_gdr.100218 - 0019) Microsoft Corporation C:\windows\system32\ntkrnlpa.exe

  How can I solve the problem? Thank you

  Wow, you've been crashing for a long time.

  1: kd > .bugcheck
  Error checking code 000000C 5
  Arguments 0000000b 00000002 00000001 822f5010

  1: kd > knL
  # ChildEBP RetAddr
  805ec89c 00 822f5010 nt! KiTrap0E + 0x2e1
  01 805ec958 8bbad142 nt! ExAllocatePoolWithTag + 0x4ca
  02 805eca0c 822ae1fb ecache! EcCacheBootPopulateCompletion + 0x1d2
  03 805eca40 83a2cd5f nt! IopfCompleteRequest + 0x11d
  04 805eca48 83a2c3ee CLASSPNP! ClassCompleteRequest + 0x11
  05 805eca74 822ae1fb CLASSPNP! TransferPktComplete + 0x2b6
  06 805ecaac 83a94fc9 nt! IopfCompleteRequest + 0x11d
  WARNING: Information not available stack unwind. Sequence of images may be wrong.
  07 805ecb1c 83 has 55285 iastor + 0x44fc9
  08 805ecbbc 83a562f9 iastor + 0 x 5285
  09 805eccd8 83a9508f iastor + 0x62f9
  0a 805ecce8 822b16c2 iastor + 0x4508f
  0b 805ecd50 822af89d nt! KiRetireDpcList + 0 x 147
  0c 805ecd54 00000000 nt! KiIdleLoop + 0 x 49

  The storage technology Intel Raid driver corrupted pool system, which caused an attempt to access invalid memory at an IRQL that was too high. In our case:

  1: kd > .trap 805ec89c
  ErrCode = 00000002
  EAX = ebx 00000007 = 8230971c ecx = 8233f140 edx = 00000000 esi = 823096e0 edi = 880e29e0
  EIP = 822f5010 esp = 805ec910 ebp = 805ec958 iopl = 0 nv up ei pl nz ca po nc
  CS = 0008 ss = 0010 ds = 0023're = 0023 fs = 0030 gs = 0000 efl = 00210212
  NT! ExAllocatePoolWithTag + 0x4ca:
  822f5010 895804 mov dword ptr [eax + 4], ebx ds:0023:0000000 b is?

  About the unhandled, exception generated by the TSRI driver corrupting the pool when he allowed it, he would lie ebx to the value stored at the address of eax + 4. contents of EAX look pretty fake to me (00000007), is whence the crash.

  1: kd > lmvm iastor
  start end module name
  83a 50000 83b2a000 iastor T (no symbol)
  Loaded symbol image file: iastor.sys
  Image path: \SystemRoot\system32\drivers\iastor.sys
  Image name: iastor.sys
  Timestamp: Mon Apr 05 12:21:02 2010

  Very old driver.

  Try to update the driver of the TSRI first of your manufacturers website and if not lucky, follow my guide here to remove it. Even if you're running Vista, it should still work if all goes well - http://answers.microsoft.com/en-us/windows/wiki/windows_7-hardware/uninstalling-the-intelr-rapid-storage-technology/e3c4b6d6-56ba-4ac5-be50-89843c9d9b22

• Random & sometimes return BSOD is please help

  Hi all

  Recently I had recurring problems with my 4-5 + years, Compaq Presario CQ60-417DX running Windows Vista Home Premium 32-bit. I received several bsod, and the majority of them are DRIVER_CORRUPTED_EXPOOL bugs. I don't know what is the cause but I did tests of hard drive, memory, and several times startup repair. The tests come back fine Startup Repair has fixed the temproarily only problem and then come back the BSOD. Any suggestions?
  Kind regards
  Brenden

  Hello

  Welcome to the community Microsoft and thanks for posting the question.

  According the description, you get BSOD in Vista-based computer.

  1A what situation do you get BSOD? That you get when you work on a particular application/operation or it occurs randomly?

  2. don't you make recent changes that caused the problem?

  3. do you have external devices attached to the computer?

  4. What are the error numbers, see the BSOD screen?

  See the link below for trouble below to resolve blue screen issues:

  Method 1)

  How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart unexpectedly

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

  Note: The data available on bad sectors may be lost when chkdsk attempts to repair your hard drive.

  Method 2) run Microsoft Safety Scanner to check any Virus infection:

  Microsoft safety scanner

  http://www.Microsoft.com/security/scanner/en-us/default.aspx

  Note: If infections are detected during the scan, there is a risk of data loss because infected files will be deleted.

  Click the link below to provide newspapers at the time when the computer crashed:

  Open event viewer

  http://Windows.Microsoft.com/en-us/Windows-Vista/what-information-appears-in-event-logs-Event-Viewer

  Please follow these recommended steps, review the additional information provided and post back if you still have the problem. I will be happy to provide you with additional options.

• Recurring blue screen error BCCode: c5 BCP1: 00000000 BCP2: 00000002 BCP3: 00000000 BCP4: 828EE4A2 OS

  Hi all and I want to thank you in advance
  I get this non-stop error and my computer stops and restarts all the hours
  and that's the exact blue screen. I checked against viruses and malware and my laptop is clean, so I don't know what else to do
  Thanks in advance :)

  Signature of the problem:
  Problem event name: BlueScreen
  The system version: 6.0.6002.2.2.0.768.3
  Locale ID: 4105

  More information about the problem:
  BCCode: c5
  BCP1: 00000000
  BCP2: 00000002
  BCP3: 00000000
  BCP4: 828EC4A2
  OS version: 6_0_6002
  Service Pack: 2_0
  Product: 768_1

  Files helping to describe the problem:
  C:\Windows\Minidump\Mini011012-01.dmp
  C:\Users\Shima\AppData\Local\Temp\WER-62915-0.SysData.XML
  C:\Users\Shima\AppData\Local\Temp\WERD0A6.tmp.version.txt

  Hello

  See this thread for more information on using BlueScreenView, MyEventViewer and other methods of
  Troubleshoot BlueScreens - answers top 3 (+ 1 more).

  http://answers.Microsoft.com/en-us/Windows/Forum/windows_vista-system/blue-screen-plug-and-play-detected-an-error-most/3deab2fa-4000-4136-8c78-a3d22b1db009

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

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

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

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

  BCCode: C5 0x000000C5

  This error is most often a driver, thinks the video and other BIOS. Antivirus/antispyware/security
  programs are also suspected.

  BCCode: C5 0x000000C5

  Bug Check 0xC5: DRIVER_CORRUPTED_EXPOOL

  Value of 0x000000C5 DRIVER_CORRUPTED_EXPOOL bug control a. This indicates that the system attempted to access invalid memory at IRQL level too high.

  Important information if you have received a STOP Code

  If you have received a blue screen error, or stop code, the computer stopped abruptly to protect against data loss. A hardware device, its driver or software might have caused this error. If your copy of Windows is shipped with your computer, contact your computer manufacturer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact information for Microsoft or the manufacturer of your computer connect with Support.

  If you have experience with computers and try to recover from this error, follow the steps in the Microsoft article solution STOP (blue screen) errors in Windows.

  The following actions could prevent a mistake like this does not happen:

  1. Download and install updates for your computer from Windows Update device drivers.
  2. Scan your computer for computer viruses.
  3. Check your hard drive for errors.

  DRIVER_CORRUPTED_EXPOOL parameters

  The following settings are displayed on the blue screen.

  Parameter	Description
  1	Memory referenced
  2	IRQL at time of reference
  3	0: Read 1: To write
  4	Memory address

  Cause

  The kernel attempted to access pageable memory (or may be completely invalid memory) when the IRQL was too high. The ultimate cause of this problem is almost certainly a driver that has damaged the system pool.

  In most cases, this bug results if checking a driver corrupts a small amount (less than PAGE_SIZE). Allowances cause more bug check 0xD0 (DRIVER_CORRUPTED_MMPOOL).

  Resolution

  If you have recently installed new software, check if it is properly installed. Check the updated drivers on the manufacturer's website.

  To debug this error, use special pool of driver verifier. Failure to reveal the driver that caused the error, use the global flags utility to enable the special pool by pool tag.

  BCCode: C5 0x000000C5<-- read="" this="">
  * 1198.html http://www.faultwire.com/solutions-fatal_error/A-Device-Driver-has-pool-0x000000c5-

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

  Driver Verifier can help find some BSOD problems:

  Using Driver Verifier to identify issues with Windows drivers for users advanced
  http://support.Microsoft.com/kb/244617

  How to solve the problems of driver in Windows Vista or 7.
  http://www.WinVistaClub.com/T79.html

  Using Driver Verifier
  http://msdn.Microsoft.com/en-us/library/ff554113 (v = VS. 85) .aspx

  How to use Windows drivers check Manager to solve problems and identify the Driver questions
  http://www.YouTube.com/watch?v=_VwIDD9xngM

  Driver Verifier
  http://www.techsupportforum.com/2110308-POST3.html

  Using Driver Verifier
  http://www.faultwire.com/solutions/using_driver_verifier.php

  How to use Windows drivers check Manager to solve problems and identify the Driver questions
  http://www.YouTube.com/watch?v=_VwIDD9xngM

  You can disable the driver verifier
  http://support.Microsoft.com/kb/244617

  Start - type in the box search-> auditor/Reset hit enter to disable

  BlueScreenView lets you know if there is a driver specified in the error message. Also check with
  MyEventViewer at the blue screen.

  If DriverVerifier creates a minidump upload it and post the link here so we can analyze.

  I hope this helps.

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

• Several system crashes due to blue screen errors

  In the last 8 days, I had 10 breakdowns of the system. They are due also System 32 drivers, such as ntfs.sys, ntkrnlpa.exe, hsx_dp.sys, ksecdd.sys, ecache.sys.

  The most recent is down today because of ksecdd.sys. The error code that was produced was 0xA (10110, 0xFFFFFFFF82B11926, 2, 0 x 0 x 0 x 0). The name of the error is error: IRQL_NOT_LESS_OR_EQUAL. Also the computer crashed today, because of the same error, ksecdd.sys (ksecdd! SecMakeSPN + 0x12CE).
  12 it crashed due too: ecache.sys. The error code product was 0xD1 (0x1E, 0 x 2, 0 x 0, 0xFFFFFFFF88971971). The title of the error is error: DRIVER_IRQL_NOT_LESS_OR_EQUAL. Also 12, the computer crashed had too much hsx_dp.sys (HSX_DP + 0x365AC). The error code that was produced was 0x1000007E (0xFFFFFFFF8D0405AC, 0xFFFFFFFF8935B4DC, 0xFFFFFFFF80000004, 0xFFFFFFFF8935B1D8). The title of the error is error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M. Still 12, it crashed right again also, ntkrnlpa.exe (nt + 0x4DFD9). The error code that was produced was 0xA (0 x 0 0 x 2, 0 x 0, 0xFFFFFFFF824594DF). The title of the error isIRQL_NOT_LESS_OR_EQUAL. The computer has crashed again on the 11th due too, ntkrnlpa.exe (nt + 0 x 98379). The error code that was produced was, 0 x 50 (0x0, 0xFFFFFFFF8209F2C0, 0xFFFFFFFFC900000F, 0 x 2). The title of the error is PAGE_FAULT_IN_NONPAGED_AREA. The computer has crashed again on the 9th due too, ntkrnlpa.exe (nt + 0x4DFD9). The error code that was produced was 0xA (0 x 0, 4 2, 0 x 0, 0xFFFFFFFF820CCBF7). The title of the error is: IRQL_NOT_LESS_OR_EQUAL. The computer has crashed once more 9, time too ksecdd.sys (ksecdd + 0x3C3A7). The error code that has been produced is 0xA (0 x 0, 8 x 2, 0 x 0, 0xFFFFFFFF820CBCBB). The title of the error is IRQL_NOT_LESS_OR_EQUAL. The computer has crashed once more on the 8th due too, ntfs.sys (Ntfs + 0xB850). The error code that has been produced is 0xA (0 x 0, 4 2, 0 x 0, 0xFFFFFFFF820E2BF7). The title of the error is: IRQL_NOT_LESS_OR_EQUAL. Yet once the computer crashed on 6th due too, ksecdd.sys (ksecdd + 0x3C3A7). The error code that has been produced is, 0xC5 (0x1, 0x2, 0 x 1810108, 0xFFFFFFFF8213D82A). The title of error is DRIVER_CORRUPTED_EXPOOL. The computer is a compaq Presario SR5510F. I'm running Windows Vista Home premium 32-bit. The computer has 2gbs of ram and a processor AMD Athlon X 25000 bicoeur.

  Hello

  Step 1: Disconnect all the external devices connected to the computer and start the computer in Mode safe.

  Step 2: If you are able to start the computer normally, run step 3A suggested in my previous post.

• Blue screen BSOD caused by mrxsmb.sys or ntoskml.exe or l1c62x64.sys?

  Hello

  I frequently have some BSOD and after analysis with Whocrashed, there were 15 BSOD. See belong

  But I can't find where the problem:

  Mrxsmb.sys: I noticed that there are a lot of this file on my computer in C:\Windows\system32\drivers (27/04/2011 04:40 - 154Ko) as well as in several starting directory by C:\windows\winsxs\amd64_microsoft* different date & time, but the same size. There is also a variant of like mrxsmb10.sys and mrxsmb20.sys file.

  I read that this may be due to a malware. What do you think about this?

  l1c2x64.sys: I've already checked the driver and the driver is already uptodate on the website of the manufacturer of the computer.

  Ntoskrnl.exe: this is a file of the kernel and I prefer not to change anything...

  My laptop is a Lenovo G500s Win7 pro 64-bit

  Thank you for your help

  Monday, February 16, 2015 11:48:49 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\021615-22729-01.dmp
  This was probably caused by the following module: mrxsmb.sys (mrxsmb + 0x42C9)
  Bugcheck code: 0xC2 (0 x 0x109B, 0 x 20016, 7, 0xFFFFFA800C973170)
  Error: BAD_POOL_CALLER
  file path: C:\Windows\system32\drivers\mrxsmb.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: Windows NT SMB Minirdr
  Bug control description: This indicates that the current thread is doing a bad pool request.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Monday, February 16, 2015 11:48:49 GMT crashed your computer
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: l1c62x64.sys (L1C62x64 + 0x84A6)
  Bugcheck code: 0xC2 (0 x 0x109B, 0 x 20016, 7, 0xFFFFFA800C973170)
  Error: BAD_POOL_CALLER
  file path: C:\Windows\system32\drivers\l1c62x64.sys
  product: series Qualcomm Atheros Ar81xx PCI-E Gigabit Ethernet Controller
  company: Qualcomm Atheros Co., Ltd..
  Description: Qualcomm Atheros Ar81xx series PCI-E Gigabit Ethernet Controller
  Bug control description: This indicates that the current thread is doing a bad pool request.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: l1c62x64.sys (series of Qualcomm Atheros Ar81xx PCI - E Gigabit Ethernet Controller, Qualcomm Atheros Co., Ltd.).
  Google search: Qualcomm Atheros Co., Ltd. BAD_POOL_CALLER

  Saturday, February 14, 2015 15:34:19 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\021415-18876-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x74EC0)
  Bug check code: 0xC5 (0 x 2, 0 x 0, 0xFFFFF6800008E332, 0xFFFFF800037BDB15)
  Error: DRIVER_CORRUPTED_EXPOOL
  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 system attempted to access invalid memory at IRQL level too high.
  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.

  Friday, February 13, 2015 12:09:20 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\021315-19359-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x74EC0)
  Bugcheck code: 0xC2 (0 x 0x109B, 0 x 4030005, 7, 0xFFFFFA800DF82A30)
  Error: BAD_POOL_CALLER
  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 current thread is doing a bad pool request.
  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.

  Tuesday, January 20, 2015 12:00:23 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\012015-21418-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x76E80)
  Bugcheck code: 0xC2 (0 x 0x109B, 0 x 4030008, 7, 0xFFFFFA800CDBF260)
  Error: BAD_POOL_CALLER
  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 current thread is doing a bad pool request.
  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.

  Sunday, January 18, 2015 15:55:30 GMT your computer crashed
  crash dump file: C:\Windows\Minidump\011815-24304-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x76E80)
  Bugcheck code: 0x19 (0 x 22, 0 x 80000, 0x0, 0x0)
  Error: BAD_POOL_HEADER
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a pool header is corrupt.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This could be a case of corruption of memory. The corruption of memory more often happens because of software errors in the defective drivers buggy, not because of RAM modules.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Saturday, January 17, 2015 15:19:45 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\011715-32463-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x76E80)
  Bug check code: 0xC5 (0 x 2, 0 x 0, 0x5FFF2, 0xFFFFF8000380C9BF)
  Error: DRIVER_CORRUPTED_EXPOOL
  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 system attempted to access invalid memory at IRQL level too high.
  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.

  Monday, June 1, 2015 11:56:22 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\010615-31902-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Verification of error code: 0 x 50 (0 x 1, 0xFFFFF800037F82F2, 0xFFFFF8E0033429BC, 0 x 5)
  Error: PAGE_FAULT_IN_NONPAGED_AREA
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that invalid system memory was referenced.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Tuesday, December 16, 2014 12:01:14 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\121614-26956-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0xC2 (0 x 0x109B, 0 x 4030008, 7, 0xFFFFFA800D29FE20)
  Error: BAD_POOL_CALLER
  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 current thread is doing a bad pool request.
  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.

  Tuesday, December 16, 2014 11:49:21 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\121614-30716-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0xC2 (0 x 0x109B, 0 x 4030008, 7, 0xFFFFFA800D1BE090)
  Error: BAD_POOL_CALLER
  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 current thread is doing a bad pool request.
  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.

  Lammens

  I told you, that crashed was incorrect.  9 of them have been associated with your TplinkUDSMBus.sys 3 years and more

  (Print server relationship is a function built into your router. It allows you to share your printer with computers connected to the router of KCODES COMPANY) the driver information may or may not be correct but your must be removed or if you absolutely need it updated to a version

  

• BAD_POOL_HEADER

  Hello

  I lived a random BSOD and wanted support for the dump file:

  ==================================================
  Dump file: 010115-20295 - 01.dmp
  Crash time: 2015/01/01 13:25:34
  Bug Check String: BAD_POOL_HEADER
  Bug check Code: 0 x 00000019
  Parameter 1: 00000000'00000020
  Parameter 2: fffffa80'0b5280a0
  Parameter 3: fffffa80'0b5280c0
  Parameter 4: 00000000' 0402000 a
  Caused by the driver: dxgmms1.sys
  Caused by the address: dxgmms1.sys + 1f9f0
  Description of the file: DirectX Graphics MMS
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 6.1.7601.18126 (win7sp1_gdr.130409 - 1534)
  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\010115-20295-01.dmp
  Number of processors: 8
  Main version: 15
  Minor Version: 7601
  Size of the dump file: 281 408
  Time to dump file: 2015/01/01 13:26:38
  ==================================================

  Could someone please help? I really need to know why my PC suffered a BSOD.

  I also experience freezing randomly, it's a dump of a month ago:

  ==================================================
  Dump file: 112814-23868 - 01.dmp
  Crash time: 2014/11/28 17:08:22
  Bug Check String: DRIVER_CORRUPTED_EXPOOL
  Bug check code: 0x000000c5
  Parameter 1: 00000000'00040108
  Parameter 2: 00000000'00000002
  Parameter 3: 00000000'00000000
  Parameter 4: fffff800'035ffa9b
  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.18409 (win7sp1_gdr.140303 - 2144)
  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\112814-23868-01.dmp
  Number of processors: 8
  Main version: 15
  Minor Version: 7601
  Size of the dump file: 281 408
  Time to dump file: 2014/11/28 17:09:51
  ==================================================

  Please let me know if there is sufficient information.

  Kind regards

  Claude

  GD

  You can try instead of NOD32 ESET smart security.  It's more built NOD32 in the world-class firewall.

  Good luck

• Ive had problems of BSOD with this as my Dump Win 7 x 64

  Looks like it might be the system. is there a fix or should I reinstall?

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

  Loading dump file [C:\Users\Crux\Desktop\MEMORY. DMP]
  The core dump file summary: the single kernel address space is available

  Symbol search path is: D:\Symbols
  Executable search path is:
  Windows 7 Kernel Version 7600 MP (12 procs) free x 64
  Product: WinNt, suite: TerminalServer SingleUserTS
  By: 7600.16385.amd64fre.win7_rtm.090713 - 1255
  Computer name:
  Kernel base = 0xfffff800 '03068000 PsLoadedModuleList = 0xfffff800' 032a5e50
  The debugging session: 16:15:23.014 Sam August 11, 2012 (UTC - 05:00)
  System Uptime: 0 days 0:00:12.370
  Loading the kernel symbols
  ...............................................................
  ..............................
  Loading user symbols

  Loading unloaded module list
  .
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  The 7th, {ffffffffc0000005, fffff88006e9a75d, fffff88006538c68, fffff880065384c0}

  Probably caused by: NETIO. SYS (NETIO! NmrClientAttachProvider + 65)

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

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

  (7th) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
  It is a very common bugcheck.  Usually the PIN address of exception
  the driver/function that caused the problem.  Always note this address
  and the date of the picture link / driver that contains this address.
  Arguments:
  Arg1: ffffffffc0000005, unhandled exception code
  Arg2: fffff88006e9a75d, the address that the exception occurred at
  Arg3: fffff88006538c68, address of Exception report
  Arg4: fffff880065384c0, address of the context record

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

  EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - the instruction at 0 x % lx 08 referenced memory at 0 x % 08 lx. The memory could not be %s.

  FAULTING_IP:
  AFD! WskTdiInit + dd
  fffff880'06e9a75d 48c7442020c8000000 mov qword ptr [rax + 20 h], 0C8h

  EXCEPTION_RECORD: fffff88006538c68-(.exr 0xfffff88006538c68)
  ExceptionAddress: fffff88006e9a75d (afd! WskTdiInit + 0x00000000000000dd)
  ExceptionCode: c0000005 (access violation)
  ExceptionFlags: 00000000
  NumberParameters: 2
  Parameter [0]: 0000000000000001
  Parameter [1]: 0000000000000020
  Try to write at the address 0000000000000020

  CONTEXT: fffff880065384c0-(.cxr 0xfffff880065384c0)
  Rax = 0000000000000000 rbx = 0000000000000000 rcx = fffff88006e7d580
  RDX = 0000000000000000 rsi = 0000000000000000 rdi = fffff88007b2b320
  RIP = fffff88006e9a75d rsp = fffff88006538ea0 rbp = fffff88007b2b348
  R8 = 0000000000000000 r9 = 0000000000000000 r10 = fffff80003267888
  R11 = 0000000000000000 r12 = fffffa800c5fa98e r13 = ffffffff800001dc
  R14 = fffffa800c5c6560 r15 = 000000000000001c
  iopl = 0 nv up ei pl zr po nc
  CS = 0010 ss = 0018 ds = 002 b're = 002 b fs = 0053 gs = 002 b efl = 00010246
  AFD! WskTdiInit + 0xdd:
  fffff880'06e9a75d 48c7442020c8000000 mov qword ptr [rax + 20 h], 0C8h, ds:002 b: 00000000'00000020 =?
  Reset the default scope

  Nom_processus: System

  CURRENT_IRQL: 0

  Error_code: (NTSTATUS) 0xc0000005 - the instruction at 0 x % lx 08 referenced memory at 0 x % 08 lx. The memory could not be %s.

  EXCEPTION_PARAMETER1: 0000000000000001

  EXCEPTION_PARAMETER2: 0000000000000020

  WRITE_ADDRESS: 0000000000000020

  FOLLOWUP_IP:
  NETIO! NmrClientAttachProvider + 65
  fffff880'04427ea5 85 c 0 test eax, eax

  BUGCHECK_STR: 0X7E

  DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

  LOCK_ADDRESS: fffff800032dc400-(! fffff800032dc400 of locks)

  Resource @ nt! PiEngineLock (0xfffff800032dc400) the exclusive property
  Argument Count = 1
  NumberOfExclusiveWaiters = 1
  Discussions: fffffa8006a2f680-01<*>
  Threads waiting on exclusive access:
  fffffa8006a2e040

  1 total locks, 1 locks currently held

  PNP_TRIAGE:
  Lock the address: 0xfffff800032dc400
  Thread Count: 1
  Feed address: 0xfffffa8006a2f680
  Queue: 0 x 318

  LAST_CONTROL_TRANSFER: from fffff80003448824 to fffff800030d9f00

  STACK_TEXT:
  fffff880 '06538ea0 fffff880' 06e72950: fffffa80 ' 0c5fd6f0 fffffa80 '0c5fd6f0 fffff880' 07b2b348 fffff880 ' 07b2b348: afd! WskTdiInit + 0xdd
  "fffff880 '06538ef0 fffff880' 06e72b7c: fffffa80 ' fffff880 00000262 '07b2b348 fffffa80' 0c5fd6f0 fffffa80 ' 0c4d2ee0: afd! AfdWskInit + 0 x 30
  fffff880 '06538f30 fffff880' 04427ea5: fffff880 ' 07b2b348 fffffa80 '0c4d2ee0 fffffa80' 0c5fa940 fffffa80 ' 0c4d2ee0: afd! AfdWskNotifyAttachClient + 0x12c
  fffff880 '06538f80 fffff880' 07b 27173: fffffa80 '0c5fa98c 00000000 00000001' fffffa80' 0c5fcd70 00000000' 000007ff: NETIO! NmrClientAttachProvider + 0 x 65
  fffff880'06538fd0 fffff880'04430833: fffffa80' 771d7db4 fffffa80 '43820eee 0c5fcd70' c 336420 00000001'00000018 0: rasl2tp! WskNotifyAttachProvider + 0 x 73
  fffff880 ' 06539010 fffff880' 04431cbd: fffffa80 '0 c 336420 fffffa80' 07406820 fffff880' 06539120 00000000 00000000': NETIO! NmrpProposeAttachment + 0 x 53
  fffff880 ' 06539060 fffff880' 04432dde: fffffa80'0c5fcd70 00000000' fffff880'06539120 00000000 00000000 00000000': NETIO! NmrpAttachArray + 0x3d
  fffff880 '06539090 fffff880' 044340d 2: fffff880'07b2b300 00000000'00000000 00000000'00000001 00000000'00000000: NETIO! NmrpRegisterModule + 0x6e
  fffff880 '065390f0 fffff880' 07b4004c: fffffa80' 00000000 00000010 '0 c 547820 fffffa80' 0c 00000000'00000018 634000: NETIO! NmrRegisterClient + 0 x 52
  "fffff880 ' 06539120 fffff880' 07 b 45050: 00000000'746 c 6600 fffff880 ' 06539210 fffff880 ' 065391 b 0 fffff800'03267880: rasl2tp! WskStartClientModule + 0x3c
  fffff880 '06539150 fffff800' c 034 1477: fffffa80 '0 c 547820 fffffa80' 0c 547820 00000000 00000000' fffffa80'0 c 634000: rasl2tp! DriverEntry + 0x40
  fffff880 ' 06539240 fffff800' 03554780: fffff880 00000000'00000001 00000000'00000000 ' 065397e8 ffffffff 8000014 c: nt! IopLoadDriver + 0xa07
  fffff880 ' 06539510 fffff800' 03392cdc: fffff880'06539820 00000000 '00000000 00000000' c0000023 00000000' 00000000: nt! PipCallDriverAddDeviceQueryRoutine + 0 x 390
  "fffff880 ' 06539610 fffff800' 03392fea: 00000000'00000000 00000000'00000000 fffff880 ' 06539820 fffff880 ' 065397e8: nt! RtlpCallQueryRegistryRoutine + 0xf4
  fffff880 ' 06539690 fffff800' 034c472c: fffffa80 '06a7b010 00000000'00000000 00000000' c0000034 fffff880' 065397e8: nt! RtlQueryRegistryValues + 0x17e
  fffff880 ' 06539760 fffff800' 034c5ec2: fffffa80 '06a7a6b0 fffffa80' 06a7b010 00000000 00000001' fffff8a0'0000004 c: nt! PipCallDriverAddDevice + 0x45c
  fffff880 ' 06539910 fffff800' 034c635c: fffff800 '032d9d80 00000000'00000000 00000000'00000001 fffff800 0334671' c: nt! PipProcessDevNodeTree + 0x2b2
  "fffff880 '06539b 80 fffff800' 031da322: 00000001 0327d5f8 ' 00000003 fffff800 ' 00000000'00000001 00000000'00000000: nt! PiProcessStartSystemDevices + 0x7c
  fffff880 '06539bd0 fffff800' 030e7161: fffff800'031da020 fffff880 '04169e01 fffffa80' 06a2f600 00000000' 00000000: nt! PnpDeviceActionWorker + 0 x 302
  fffff880 ' 06539 c 70 fffff800 '0337 d 166:95259525' fb2ffb2f fffffa80 '06a2f680 00000000 00000080' fffffa80' 06a15b30: nt! ExpWorkerThread + 0 x 111
  "fffff880 ' 06539 d 00 fffff800 ' 030b 8486: fffff880 ' 0633f180 fffffa80 '06a2f680 fffff880' 0634a1c0 b83fb83f ' 6a116a11: nt! PspSystemThreadStartup + 0x5a
  fffff880'06539 d 40 00000000 00000000': fffff880'0653 has 000 fffff880 '06534000 fffff880' 06537780 00000000 00000000': nt! KiStartSystemThread + 0x16

  SYMBOL_STACK_INDEX: 3

  SYMBOL_NAME: NETIO! NmrClientAttachProvider + 65

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: NETIO

  NOM_IMAGE: NETIO. SYS

  DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc18a

  STACK_COMMAND: .cxr 0xfffff880065384c0; Ko

  FAILURE_BUCKET_ID: X64_0x7E_NETIO! NmrClientAttachProvider + 65

  BUCKET_ID: X64_0x7E_NETIO! NmrClientAttachProvider + 65

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

  Hi, I took a glance at the attached image file.

  It is a C5: DRIVER_CORRUPTED_EXPOOL error checking, which means that a device driver has a bug that has attempted to access a memory either non-existent memory or it is not allowed access.

  The driver failed in the dump is kbdclass.sys is a general Windows driver, which is probably not the real cause of the accident-, but something other driven in kbdclass.sys Fault, probably another 3rd driver we need to activate Driver Verifier catch.

  First, if Service Pack 1 is not installed - know how to install this here.

  Driver Verifier:

  
  

  What is the driver verifier?

  Driver Verifier is included in Windows 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP and Windows Server 2003 to promote stability and reliability; You can use this tool to troubleshoot driver problems. Components in kernel mode Windows can cause the corruption of system or failures in the system due to a poorly written driver, as a previous version of a driver Windows Driver Model (WDM).

  Essentially, if there is a 3rd driver left supposedly involved, activation of the driver verifier will help flush out the rogue driver by marking and origin of your system to BSOD.

  Before you enable Driver Verifier, it is recommended to create a System Restore Point:

  Vista - START | type rstrui - create a restore point

  Windows 7 - START | type create | Select "create a Restore Point.

  How to enable the driver verifier:

  Start > type "auditor" without quotes > select the following options.

  1. Select - create a custom settings (for code developers).

  2. Select - "select individual settings from a list."

  3. check the following boxes-

  -Special pool

  -Pool management

  -Force IRQL control

  -Detection of blockages

  -Security controls (Windows 7)

  -Concurrentcy (Windows 8) stress test

  -DDI compliance review (Windows 8)

  -Cheques

  4. Select - "select the driver names from a list.

  5. click on the tab 'supplier '. This will cause the sorting of all drivers by the provider.

  6. EACH box that is NOT provided by Microsoft / Microsoft Corporation.

  7. click on finish.

  8 restart.

  Important information about driver verifier:

  -If the Driver Verifier finds a violation, the system will search BSOD.

  -After activation of the auditor of drivers and restart the system, according to the guilty, will it be

  example, that the pilot is started, you may not be able to return to normal Windows

  Because Driver Verifier it will report and as shown above, which will cause / force a BSOD.

  If this happens, do [b] not [/ b] panic, follow these steps:

  -Start in Safe Mode by pressing repeatedly F8 key during boot to the top.

  -Once in Mode safe - start > type "System Restore" without the quotes.

  -Select the previously created restore point.

  If you have not set up a restore point, don't worry, you can always turn off Driver Verifier for

  in normal windows:

  -Start > Search > type "cmd" without the quotes.

  -To disable the Driver Verifier feature, type cmd ' auditor/Reset"without the quotes.

  -Reboot and start Windows normally.

  How long can I keep the compatible driver verifier for?

  It varies, many experts and analysts have different recommendations. Personally, I recommend

  keep it turned on for at least 36 to 48 hours. If you do not BSOD right there, turn off Driver Verifier.

  My BSOD system would be, where can find the dumps?

  They are in C:\Windows\Minidump

  For any other question can most likely be answered by this article:

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

  Kind regards

  Patrick