BSOD with ntkrnlmp.exe

OK files are here

I guess it's the right way to put the problem. Ntkrnlmp.exe more often then the other. Occurs randomly during web browsing, games, writing a word document, and if I leave it on for a while just idling it does.

Data sheet:

-Asrock a785gm - the

-Athlon II X 4 645 3.1 Ghz Quad Core

-Kingston HyperX 1600 mhz 2x2gb DDR2 (clocked at 1600 mhz with 2.2V recommend Kingston manual. timing is 5-5-5-15)

-Evga GTX 580 1.5 GB

-Crucial 250 Bx200

-Some random 320 GB 7200 RPM HARD drive

Things I've tried:

-memtest with 8 parallel and sequential passes 0 errors

-updated the drivers from the website of the manufacturers, including Nvidia, with poses new problem

-looked at the time and the use of the cpu and gpu (with hwinfo and MSIAfterburner) and everything was normal just before it BSOD

The graphics card is out a pc without any problems. Just bought a best and decided to put in this machine that had a need. Any ideas on whats going on.

Well, I went and updated updated to windows 10 with a new installation and looks that did the trick. no more errors. computer works well. not collapsed yet. guess ill never know what was going on.

Tags: Windows

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

  • Please help me solve this BSOD ntoskrnl.exe, ntkrnlmp.exe

    Hello

    I have problems with my new computer since I bought it, it started giving problems. Now this BSOD. I am totally frustrated with it. Please help me get rid of this questions.
    Here is the link of the minidump file:
    https://SkyDrive.live.com/redir?RESID=1F218460C89B0917%21114
    I guess that the culprit is wireless driver. With the old version of the wireless driver, I got another BSOD, so I uninstalled and installed the most recent version. Still problem persists.
    With whoCrashed, I found this information:
    Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    Windows dir: C:\Windows
    CPU: GenuineIntel Intel (r) Core i7-3610QM CPU @ 2.30 GHz Intel586, level: 6
    8 logical processors, active mask: 255
    RAM: 8469991424 total
    VM: 2147352576, free: 1902690304

    Crash Dump Analysis
    Crash dump directory: C:\Windows\Minidump

    Dumps are enabled on your computer.

    Tuesday, December 23, 13 9:36:04 CEST your computer crashed
    crash dump file: C:\Windows\Minidump\122313-27736-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt + 0 x 72680)
    Bugcheck code: 0x9F (0x3, 0xFFFFFA8007539060, 0xFFFFF80000B9C3D8, 0xFFFFFA800FE606B0)
    Error: DRIVER_POWER_STATE_FAILURE
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    Description: NT Kernel System &
    Bug control description: this bug check indicates that the driver is in an inconsistent or invalid power state.
    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 23, 13 9:36:04 CEST your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
    Bugcheck code: 0x9F (0x3, 0xFFFFFA8007539060, 0xFFFFF80000B9C3D8, 0xFFFFFA800FE606B0)
    Error: DRIVER_POWER_STATE_FAILURE
    Bug control description: this bug check indicates that the driver is in an inconsistent or invalid power state.
    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.

    Please help me. Thanks in advance.

    Apvmz

    This phenomenon was related to the device driver wireless Extensible athrx.sys of Atheros Communications, Inc.  Yours is almost 2 years so not the most recent.

    I would like to re - install the latest driver available

  • Ntkrnlmp.exe 0x19 BSOD on Win7

    My PC put a 0 x 19 on Win7 BSOD this week. By WinDbg, I saw the detail below. But I'm not what the problem is. Can you help me on this? Thank you.
    BSOD file: https://1drv.ms/u/s! AtTcAFIw1IN-hAv5b4fW9ZMvxP46

    Some information in the dump file.
    -------------------------------------------------------------------------------
    Error checking 19, {20, fffffa80044d7470, fffffa80044d74f0, 4080002}
    Probably caused by: ntkrnlmp.exe (nt! ExFreePoolWithTag + 18aa)
    Follow-up: MachineOwner
    ---------

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

    BAD_POOL_HEADER (19)
    The pool is already damaged at the time of the current request.
    This may or may not be due to the appellant.
    The internal pool links must be traversed to find a possible cause of
    the problem and the pool then special applied to the suspect tags or driver
    Auditor for a suspect driver.
    Arguments:
    Arg1: 0000000000000020, a pool block header size is damaged.
    Arg2: fffffa80044d7470, the pool entry we were looking for on the page.
    Arg3: fffffa80044d74f0, the next entry to the pool.
    Arg4: 0000000004080002, (reserved)

    ...

    DUMP_TYPE: 1
    BUGCHECK_P1: 20
    BUGCHECK_P2: fffffa80044d7470
    BUGCHECK_P3: fffffa80044d74f0
    BUGCHECK_P4: 4080002
    BUGCHECK_STR: 0x19_20
    POOL_ADDRESS: non paged fffffa80044d7470
    ...

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    Nom_processus: System
    CURRENT_IRQL: 0
    ANALYSIS_SESSION_HOST: COMPUTER DESK-NU0LNMM
    ANALYSIS_SESSION_TIME: 30/07/2016 18:26:14.0813
    ANALYSIS_VERSION: 10.0.10586.567 amd64fre
    LAST_CONTROL_TRANSFER: from fffff800047bdcbe to fffff80004687380
    STACK_TEXT:
    "fffff880 '04fb6a48 fffff800' 047bdcbe: 00000000'00000019 00000000'00000020 fffffa80 ' 044 d 7470 fffffa80 ' 044d74f0: nt! KeBugCheckEx
    fffff880 '04fb6a50 fffff800' 04b12e23: fffff800 ' 0483b6e0 fffffa80 '08db9860 fffff800' 69646d4d fffffa80 ' 03fcd660: nt! ExFreePoolWithTag + 0x18aa
    "fffff880 '04fb6b00 fffff800' 048db736: ffffffff ' 8000028 c fffff800 ' 048db700 00000000'00000001 00000000'00000000: nt! PopFreeHiberContext + 0 x 93
    "" fffff880'04fb6b40 fffff800'04690355: fffff800 ' 04830200 fffff800 ' 04980001 fffff880 ' 01cde000 fffffa80 ' 03fcd660: nt! PopUnlockAfterSleepWorker + 0 x 36
    fffff880'04fb6b70 fffff800'04920476: 00000000 00000000' fffffa80 '03fcd660 00000000 00000080' fffffa80' 03fb0040: nt! ExpWorkerThread + 0 x 111
    fffff880'04fb6c00 fffff800'04678726: fffff880'04dd5180 fffffa80 '03fcd660 fffff880' 04ddffc0 00000000'0000000 c: nt! PspSystemThreadStartup + 0x5a
    fffff880'04fb6c40 00000000' 00000000: fffff880'04fb7000 fffff880 '04fb1000 fffff880' 04fb5b30 00000000' 00000000: nt! KiStartSystemThread + 0x16

    STACK_COMMAND: kb
    THREAD_SHA1_HASH_MOD_FUNC: 9cbd837fee095df4f6be091ff8822c987c3e5d8c
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e2f0adb349ed2c073eba40583cc96cd00185810e
    THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6
    FOLLOWUP_IP:
    NT! ExFreePoolWithTag + 18aa
    fffff800'047bdcbe cc int 3
    FAULT_INSTR_CODE: c23d83cc
    SYMBOL_STACK_INDEX: 1
    SYMBOL_NAME: nt! ExFreePoolWithTag + 18aa
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nt
    Nom_image: ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP: 56f579f0
    IMAGE_VERSION: 6.1.7601.23403
    FAILURE_BUCKET_ID: X64_0x19_20_nt! ExFreePoolWithTag + 18aa
    BUCKET_ID: X64_0x19_20_nt! ExFreePoolWithTag + 18aa
    PRIMARY_PROBLEM_CLASS: X64_0x19_20_nt! ExFreePoolWithTag + 18aa
    -------------------------------------------------------------------------------

    Really thanks.

    These accidents were related to the corruption of memory (probably caused by a driver).

    Run these two tests to check your memory and find which driver is causing the problem.  Launch auditor.  You don't need to run memtest again unless the auditor is not the cause, or you want to.

    If you are overclocking anything reset by default before running these tests.
    In other words STOP! If you don't know what it means that you're probably not  


    1-Driver Verifier (for full instructions, see our wiki here)
    2-Memtest. (You can learn more about running memtest here)
  • BSOD with Qosmio F60-033

    I updated my drivers in accordance with this url: http://www.mytoshiba.com.au/support/notebooks/qosmio/f60/pqf65a-033002/download?os=25 I ran windows update and it reports no new drivers. Yet these two got BSOD I did a debug of depressed windows done and have pasted below. I just brought this PC like 2 days ago isn't happy he's already planted. _ ;

    =========
    = DEBUG =
    =========

    Open the logfile "c:\debuglog.txt".
    6: kd > .sympath srv * c:\symbols* http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv * c:\symbols* http://msdl.microsoft.com/download/symbols
    Expanded the symbol search path is: srv * c:\symbols* http://msdl.microsoft.com/download/symbols
    WARNING: A space at the end of the trace element
    6: kd > .sympath srv * c:\symbols* http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv * c:\symbols* http://msdl.microsoft.com/download/symbols
    Expanded the symbol search path is: srv * c:\symbols* http://msdl.microsoft.com/download/symbols
    6: kd > .reload!; analyze - v; lmnt; r; kV. logclose; q
    Loading the kernel symbols
    .................................................. .............
    .................................................. ..............
    ................................................
    Loading user symbols
    Loading unloaded module list
    ...................
    ************************************************** *****************************
    * *
    * Bugcheck analysis *.
    * *
    ************************************************** *****************************

    BAD_POOL_CALLER (c2)
    The current thread is doing a bad pool request. In general, it is an IRQL bad or double freeing the same allocation, etc.
    Arguments:
    Arg1: 0000000000000007, attempt to free pool which was already freed
    Arg2: 0000000000001097, (reserved)
    Arg3: 0000000009060007, content of the memory of the pool block
    Arg4: fffffa800bffa4b0, address of the block of pool is released

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

    POOL_ADDRESS: fffffa800bffa4b0

    FREED_POOL_TAG: PKI

    BUGCHECK_STR: 0xc2_7_Icp

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    Nom_processus: svchost.exe

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff800035ad60e to fffff8000347a740

    STACK_TEXT:
    fffff880 '08-73958 fffff800' 035ad60e: 00000000'000000 c 2 00000000'00000007 00000000'00001097 00000000'09060007: nt! KeBugCheckEx
    fffff880 '08-73960 fffff800' 0373296b: fffff880 '0dce1000 fffff800 ' 03764748 fffffa80' 20706349 00000000' 6e496c41: nt! ExDeferredFreePool + 0x11eb
    "fffff880 '08a73a10 fffff800' 034310ca: fffffa80 ' 051 c 1000 00000021' 08d4ab30 fffff880 ' 0dce1000 00000000' 00000000: nt! IopFreeMiniCompletionPacket + 0 x 87
    "" fffff880 '08a73a40 fffff800' 03430f00: fffffa80 ' 051 c 1000 fffffa80 ' 08d4d090 fffffa80 ' 051 c 1000 fffffa80 ' 08d4d090: nt! AlpcpDeferredFreeCompletionPacketLookaside + 0x2a
    fffff880 '08a73a70 fffff800' 036cf2fe: fffff8a0'0c957c80 fffff880 '08a73ca0 fffffa80' 08d4d090 00000000' 00000000: nt! AlpcpFreeCompletionPacketLookaside + 0 x 38
    fffff880'08a73ac0 fffff800'03767764: 00000000 00000000' fffffa80 ' 00000001 00000000' 0051f0a0 fffff880' 00000002: nt! AlpcpInitializeCompletionList + 0x21e
    fffff880'08a73b40 fffff800'03479993: fffffa80 '08d4d090 fffffa80'04779060 00000000' 01386740 00000000'00000000: nt! NtAlpcSetInformation + 0x32f
    fffff880 '08a73c20 00000000' 778d05ba: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiSystemServiceCopyEnd + 0x13
    00000000' 0051f078 00000000'00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: 0x778d05ba

    STACK_COMMAND: kb

    FOLLOWUP_IP:
    CTA IopFreeMiniCompletionPacket + 87
    fffff800'0373296 b eba1 jmp nt! IopFreeMiniCompletionPacket + 0 x 26 (fffff800'0373290e)

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: nt! IopFreeMiniCompletionPacket + 87

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    Nom_image: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

    FAILURE_BUCKET_ID: X64_0xc2_7_Icp__nt! IopFreeMiniCompletionPacket + 87

    BUCKET_ID: X64_0xc2_7_Icp__nt! IopFreeMiniCompletionPacket + 87

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

    Rax = 0000000009060007 rbx = fffffa800bffa4a0 rcx = 00000000000000c 2
    RDX = IHR 0000000000000007 = 0000000000000003 rdi = fffffa80051c1088
    RIP = fffff8000347a740 rsp = fffff88008a73958 rbp = fffff88008a73ca0
    R8 = 0000000000001097 r9 = 0000000009060007 r10 = fffff880032f7be0
    R11 = fffffa800a011a30 r12 = fffff8800dce1000 r13 = fffffa800bffa4b0
    0000000000010000 = 0000000000200000 R14 = r15
    iopl = 0 nv in pe of na EI pl nz nc
    CS = 0010 ss = 0018 ds = 002 b're = 002 b fs = 0053 gs = 002 b efl = 00000202
    CTA KeBugCheckEx:
    fffff800 '0347 a 740 48894c 2408 mov qword ptr [rsp + 8], rcx ss:0018:fffff880' 08 a 73960 = 00000000000000 c 2
    Child-SP RetAddr: Args to child: call Site
    fffff880 '08-73958 fffff800' 035ad60e: 00000000'000000 c 2 00000000'00000007 00000000'00001097 00000000'09060007: nt! KeBugCheckEx
    fffff880 '08-73960 fffff800' 0373296b: fffff880 '0dce1000 fffff800 ' 03764748 fffffa80' 20706349 00000000' 6e496c41: nt! ExDeferredFreePool + 0x11eb
    "fffff880 '08a73a10 fffff800' 034310ca: fffffa80 ' 051 c 1000 00000021' 08d4ab30 fffff880 ' 0dce1000 00000000' 00000000: nt! IopFreeMiniCompletionPacket + 0 x 87
    "" fffff880 '08a73a40 fffff800' 03430f00: fffffa80 ' 051 c 1000 fffffa80 ' 08d4d090 fffffa80 ' 051 c 1000 fffffa80 ' 08d4d090: nt! AlpcpDeferredFreeCompletionPacketLookaside + 0x2a
    fffff880 '08a73a70 fffff800' 036cf2fe: fffff8a0'0c957c80 fffff880 '08a73ca0 fffffa80' 08d4d090 00000000' 00000000: nt! AlpcpFreeCompletionPacketLookaside + 0 x 38
    fffff880'08a73ac0 fffff800'03767764: 00000000 00000000' fffffa80 ' 00000001 00000000' 0051f0a0 fffff880' 00000002: nt! AlpcpInitializeCompletionList + 0x21e
    fffff880'08a73b40 fffff800'03479993: fffffa80 '08d4d090 fffffa80'04779060 00000000' 01386740 00000000'00000000: nt! NtAlpcSetInformation + 0x32f
    fffff880 '08a73c20 00000000' 778d05ba: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiSystemServiceCopyEnd + 0 x 13 (TrapFrame @ fffff880'08a73c20)
    00000000' 0051f078 00000000'00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: 0x778d05ba
    start end module name
    fffff800 '00bc4000 fffff800' 00bce000 kdcom kdcom.dll kills Jul 14 11:31:07 2009 (4A5BDFDB)
    fffff800 '0340-000 fffff800' 039e6000 nt ntkrnlmp.exe sat 19 June at 14:16:41 2010 (4C1C44A9)
    fffff800 '039e6000 fffff800' 03a2f000 hal hal.dll kills Jul 14 11:27:36 2009 (4A5BDF08)
    "fffff880 ' 00 c 00000 fffff880 ' 00c1a000 mountmgr mountmgr.sys kills Jul 14 09:19:54 2009 (4A5BC11A)
    fffff880 '00c1a000 fffff880' 00c6b000 rdbss rdbss.sys kills Jul 14 09:24:09 2009 (4A5BC219)
    fffff880 '00c8a000 fffff880' 00cce000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll kills Jul 14 11:29:10 2009 (4A5BDF66)
    fffff880 '00cce000 fffff880' 00ce2000 PSHED PSHED.dll kills Jul 14 11:32:23 2009 (4A5BE027)
    fffff880'00ce2000 fffff880'00 d 40000 CLFS CLFS. SYS kills Jul 14 09:19:57 2009 (4A5BC11D)
    "fffff880 ' 00 d 40000 fffff880 ' 00e00000 CI CI.dll kills Jul 14 11:32:13 2009 (4A5BE01D)
    fffff880 '00e00000 fffff880' 00e0a000 msisadrv msisadrv.sys kills Jul 14 09:19:26 2009 (4A5BC0FE)
    fffff880 '00e0a000 fffff880' 00e3d000 pci pci.sys kills Jul 14 09:19:51 2009 (4A5BC117)
    fffff880 '00e3d000 fffff880' 00e4a000 vdrvroot vdrvroot.sys kills Jul 14 10:01:31 2009 (4A5BCADB)
    fffff880 '00e4a000 fffff880' 00e5f000 partmgr partmgr.sys kills Jul 14 09:19:58 2009 (4A5BC11E)
    fffff880 '00e5f000 fffff880' 00e68000 compbatt compbatt.sys kills Jul 14 09:31:02 2009 (4A5BC3B6)
    fffff880 '00e68000 fffff880' 00e74000 BATTC BATTC. SYS Tue Jul 14 09:31:01 2009 (4A5BC3B5)
    fffff880 '00e74000 fffff880' 00e89000 volmgr volmgr.sys kills Jul 14 09:19:57 2009 (4A5BC11D)
    fffff880 '00e89000 fffff880' 00ee5000 volmgrx volmgrx.sys kills Jul 14 09:20:33 2009 (4A5BC141)
    fffff880 '00ee8000 fffff880' 00f8c000 Wdf01000 Wdf01000.sys kills Jul 14 09:22:07 2009 (4A5BC19F)
    fffff880 '00f8c000 fffff880' 00f9b000 WDFLDR WDFLDR. SYS kills Jul 14 09:19:54 2009 (4A5BC11A)
    fffff880 '00f9b000 fffff880' 00ff2000 ACPI ACPI.sys kills Jul 14 09:19:34 2009 (4A5BC106)
    fffff880 '00ff2000 fffff880' 00ffb000 WMILIB WMILIB. SYS kills Jul 14 09:19:51 2009 (4A5BC117)
    "fffff880 ' 01000000 fffff880 ' 0105e000 msrpc msrpc.sys kills Jul 14 09:21:32 2009 (4A5BC17C)
    fffff880'0105e000 fffff880'010 d 1000 CNG cng.sys kills Jul 14 09:49:40 2009 (4A5BC814)
    fffff880 '010ef000 fffff880' 012f7000 iaStor, iaStor.sys Sat Oct 03 05:58:50 2009 (4AC65B7A)
    fffff880'012f7000 fffff880'01300000 atapi atapi.sys kills Jul 14 09:19:47 2009 (4A5BC113)
    fffff880 ' 01300000 fffff880' a 0132, 000 ataport ataport. SYS kills Jul 14 09:19:52 2009 (4A5BC118)
    fffff880'0132 has 000 fffff880'01335000 msahci msahci.sys kills Jul 14 10:01:01 2009 (4A5BCABD)
    fffff880 ' 01335000 fffff880' 01345000 PCIIDEX PCIIDEX. SYS kills Jul 14 09:19:48 2009 (4A5BC114)
    fffff880 ' 01345000 fffff880' 01350000 amdxata amdxata.sys sea may 20 03:56:59 2009 (4A12F2EB)
    fffff880 '01350000 fffff880' c 0139 000 fltmgr fltmgr.sys kills Jul 14 09:19:59 2009 (4A5BC11F)
    "fffff880 ' c 0139 000 fffff880 ' 013b 0000 fileinfo fileinfo.sys Tue 14 Jul 09:34:25 2009 (4A5BC481)
    fffff880'013 b 0000 fffff880'013 000 volsnap volsnap.sys CF kills Jul 14 09:20:08 2009 (4A5BC128)
    fffff880 ' 01400000 fffff880' 01411000 blbdrive blbdrive.sys kills Jul 14 09:35:59 2009 (4A5BC4DF)
    fffff880 '01422000 fffff880' 015c Ntfs Ntfs.sys 5000 kills Jul 14 09:20:47 2009 (4A5BC14F)
    "fffff880 ' 015 c 5000 fffff880 ' ksecdd.sys 015df000 ksecdd kills Jul 14 09:20:54 2009 (4A5BC156)
    fffff880 '015df000 fffff880' 015f0000 pcw pcw.sys kills Jul 14 09:19:27 2009 (4A5BC0FF)
    fffff880 '015f0000 fffff880' 015fa000 Fs_Rec Fs_Rec.sys kills Jul 14 09:19:45 2009 (4A5BC111)
    fffff880 ' 01607000 fffff880' 016f9000 ndis ndis.sys kills Jul 14 09:21:40 2009 (4A5BC184)
    fffff880'016f9000 fffff880'01759000 NETIO NETIO. SYS kills Jul 14 09:21:46 2009 (4A5BC18A)
    fffff880 ' 01759000 fffff880' 01784000 ksecpkg ksecpkg.sys Fri Jan 11 17:03:32 2009 (4B21E0B4)
    fffff880 ' 01784000 fffff880' 017ce000 c:\windows\system32\drivers\fwpkclnt fwpkclnt.sys kills Jul 14 09:21:08 2009 (4A5BC164)
    fffff880 '017ce000 fffff880' 017d2e00 TVALZ TVALZ. SYS kills Jul 14 12:18:54 2009 (4A5BEB0E)
    "fffff880 ' 017 d 3000 fffff880 ' 017e2000 discache discache.sys kills Jul 14 09:37:18 2009 (4A5BC52E)
    fffff880'017e2000 fffff880'01800000 dfsc.sys dfsc kills Jul 14 09:23:44 2009 (4A5BC200)
    fffff880 ' 01803000 fffff880' 01a 00000 tcpip tcpip.sys Mon 14 Jun 13:39:04 2010 (4C15A458)
    fffff880 '01 a 00000 fffff880' 01 has 30000 CLASSPNP CLASSPNP. SYS kills Jul 14 09:19:58 2009 (4A5BC11E)
    fffff880 '01a3e000 fffff880' 01 has 64000 pacer pacer.sys kills Jul 14 10:09:41 2009 (4A5BCCC5)
    fffff880 '01 a 64000 fffff880' 01a7a000 vwififlt vwififlt.sys kills Jul 14 10:07:22 2009 (4A5BCC3A)
    fffff880 '01a7a000 fffff880' 01 has 89000 netbios netbios.sys kills Jul 14 10:09:26 2009 (4A5BCCB6)
    fffff880 '01 has 89000 fffff880' 01aa4000 wanarp wanarp.sys kills Jul 14 10:10:21 2009 (4A5BCCED)
    fffff880 '01aa4000 fffff880' 01ab8000 termdd termdd.sys kills Jul 14 10:16:36 2009 (4A5BCE64)
    fffff880 '01ab8000 fffff880' 01ac3000 mssmbios.sys mssmbios kills Jul 14 09:31:10 2009 (4A5BC3BE)
    fffff880 '01ac4000 fffff880' 01b3e000 tos_sps64 tos_sps64.sys sea June 24 at 15:31:09 2009 (4A41BA1D)
    fffff880 '01b3e000 fffff880' 01b3ff80 Thpevm Thpevm.SYS Fri Jun 29 18:15:37 2009 (A 4, 487829)
    fffff880 ' 01 b 40000 fffff880 ' 01b4c000 thpdrv thpdrv.sys Fri Jun 29 12:02:56 2009 (4A4820D0)
    fffff880 '01b4c000 fffff880' 01 b 54000 spldr spldr.sys Tue may 12 02:56:27 2009 (4A0858BB)
    fffff880 ' 01 b 54000 fffff880 ' 01b8e000 rdyboost rdyboost.sys Mar 14 Jul 09:34:34 2009 (4A5BC48A)
    fffff880 '01b8e000 fffff880' 01ba0000 mup mup.sys kills Jul 14 09:23:45 2009 (4A5BC201)
    fffff880 '01ba0000 fffff880' 01ba9000 hwpolicy hwpolicy.sys kills Jul 14 09:19:22 2009 (4A5BC0FA)
    fffff880 '01ba9000 fffff880' 01be3000 fvevol fvevol.sys my Sep 26 12:34:26 2009 (4ABD7DB2)
    fffff880 '01be3000 fffff880' 01bf9000 disk disk.sys kills Jul 14 09:19:57 2009 (4A5BC11D)
    fffff880 '02e00000 fffff880' 02e56000 USBPORT USBPORT. SYS kills Jul 14 10:06:31 2009 (4A5BCC07)
    fffff880 '02e70000 fffff880' 02e93000 aswSP aswSP.SYS Sat Oct 08 00:52:07 2010 (4 865197)
    fffff880 '02e93000 fffff880' 02eb9000 tunnel tunnel.sys kills Jul 14 10:09:37 2009 (4A5BCCC1)
    fffff880 '02eb9000 fffff880' 02ecf000 driver intelppm.sys kills Jul 14 09:19:25 2009 (4A5BC0FD)
    fffff880'02ecf000 fffff880'02 fc 3000 dxgkrnl dxgkrnl.sys Fri Oct 02 11:00:14 2009 (4AC5509E)
    fffff880 ' 02 fc 3000 fffff880' 02fe1000 i8042prt i8042prt.sys kills Jul 14 09:19:57 2009 (4A5BC11D)
    fffff880 '02fe1000 fffff880' 02ff0000 kbdclass kbdclass.sys kills Jul 14 09:19:50 2009 (4A5BC116)
    fffff880 '03e18000 fffff880' 03e6a000 SynTP SynTP.sys Thu Mar 11 13:02:01 2010 (4B984F19)
    fffff880 '03e6a000 fffff880' 03e6bf00 USBD USBD. SYS kills Jul 14 10:06:23 2009 (4A5BCBFF)
    fffff880 '03e6c000 fffff880' 03e7b000 mouclass mouclass.sys kills Jul 14 09:19:50 2009 (4A5BC116)
    fffff880 '03e7b000 fffff880' 03e85000 tdcmdpst tdcmdpst.sys Wed 30 Jul 18:39:35 2009 (4A715C47)
    fffff880 '03e85000 fffff880' 03e8c000 TVALZFL TVALZFL.sys Fri Jun 19 20:05:44 2009 (4A3B62F8)
    fffff880 '03e8c000 fffff880' 03e95000 tosrfec tosrfec.sys Mon 01 June at 16:58:53 2009 (4A237C2D)
    fffff880 '03e95000 fffff880' 03e99500 CmBatt CmBatt.sys kills Jul 14 09:31:03 2009 (4A5BC3B7)
    fffff880 '03e9a000 fffff880' 03eaa000 CompositeBus CompositeBus.sys kills Jul 14 10:00:33 2009 (4A5BCAA1)
    fffff880 '03eaa000 fffff880' 03ec0000 AgileVpn AgileVpn.sys kills Jul 14 10:10:24 2009 (4A5BCCF0)
    fffff880 '03ec0000 fffff880' 03ee4000 rasl2tp rasl2tp.sys kills Jul 14 10:10:11 2009 (4A5BCCE3)
    fffff880 '03ee4000 fffff880' 03ef0000 ndistapi ndistapi.sys kills Jul 14 10:10 2009 (4A5BCCD8)
    fffff880 '03ef0000 fffff880' 03f1f000 ndiswan ndiswan.sys kills Jul 14 10:10:11 2009 (4A5BCCE3)
    fffff880 '03f1f000 fffff880' 03f3a000 raspppoe raspppoe.sys kills Jul 14 10:10:17 2009 (4A5BCCE9)
    fffff880 '03f3a000 fffff880' 03f5b000 raspptp raspptp.sys kills Jul 14 10:10:18 2009 (4A5BCCEA)
    fffff880 '03f5b000 fffff880' 03f75000 rassstp rassstp.sys kills Jul 14 10:10:25 2009 (4A5BCCF1)
    fffff880 '03f75000 fffff880' 03f76480 swenum swenum.sys kills Jul 14 10:00:18 2009 (4A5BCA92)
    fffff880 '03f77000 fffff880' 03fba000 ks ks.sys kills Jul 14 10:00:31 2009 (4A5BCA9F)
    fffff880 '03fba000 fffff880' 03fcc000 circlass.sys circlass kills Jul 14 10:06:34 2009 (4A5BCC0A)
    fffff880 '03fcc000 fffff880' 03fde000 umbus umbus.sys kills Jul 14 10:06:56 2009 (4A5BCC20)
    fffff880 '03fde000 fffff880' 03ff6000 rspndr rspndr.sys kills Jul 14 10:08:50 2009 (4A5BCC92)
    fffff880 ' 04400000 fffff880' 04410000 aswTdi Device aswTdi.SYS Sat Oct 08 00:52:27 2010 (4C8651AB)
    fffff880 ' 04410000 fffff880' 0449 a 000 afd afd.sys kills Jul 14 09:21:40 2009 (4A5BC184)
    fffff880 '0449-000 fffff880' 044a 4000 aswRdr aswRdr.SYS Sat Oct 08 00:47:47 (4 865093) 2010
    fffff880 '044-4000 fffff880' 044e9000 netbt netbt.sys kills Jul 14 09:21:28 2009 (4A5BC178)
    fffff880 '044e9000 fffff880' 044f2000 wfplwf wfplwf.sys kills Jul 14 10:09:26 2009 (4A5BCCB6)
    fffff880 '044f2000 fffff880' 046fa000 dump_iaStor dump_iaStor.sys Sat Oct 03 05:58:50 2009 (4AC65B7A)
    fffff880 ' 04715000 fffff880' 0473f000 CD-ROM cdrom.sys kills Jul 14 09:19:54 2009 (4A5BC11A)
    fffff880'0473f000 fffff880'04748000 Null Null.SYS kills Jul 14 09:19:37 2009 (4A5BC109)
    fffff880 ' 04748000 fffff880' 0474f000 a Bleep c:\windows\system32\drivers\beep.sys kills Jul 14 10:00:13 2009 (4A5BCA8D)
    fffff880'0474f000 fffff880'0475 d 000 vga vga.sys kills Jul 14 09:38:47 2009 (4A5BC587)
    fffff880 ' 0475 d 000 fffff880' 04782000 VIDEOPRT VIDEOPRT. SYS kills Jul 14 09:38:51 2009 (4A5BC58B)
    fffff880 '04782000 fffff880' watchdog.sys 04792000 guard dog kills Jul 14 09:37:35 2009 (4A5BC53F)
    fffff880 ' 04792000 fffff880' b 0479, 000 system32\drivers\rdpcdd.sys RDPCDD kills Jul 14 10:16:34 2009 (4A5BCE62)
    fffff880 '0479b 000 fffff880' 047a 4000 rdpencdd rdpencdd.sys kills Jul 14 10:16:34 2009 (4A5BCE62)
    fffff880 '047-4000 fffff880' 047ad000 rdprefmp rdprefmp.sys kills Jul 14 10:16:35 2009 (4A5BCE63)
    fffff880 '047ad000 fffff880' 047b 8000 Msfs Msfs.SYS kills Jul 14 09:19:47 2009 (4A5BC113)
    fffff880'047 b 8000 fffff880'047 c 9000 Npfs Npfs.SYS kills Jul 14 09:19:48 2009 (4A5BC114)
    "fffff880 ' 047 c 9000 fffff880 ' 047e7000 tdx tdx.sys kills Jul 14 09:21:15 2009 (4A5BC16B)
    fffff880 '047e7000 fffff880' 047f4000 TDI TDI. SYS kills Jul 14 09:21:18 2009 (4A5BC16E)
    fffff880'047f4000 fffff880'04800000 nsiproxy nsiproxy.sys kills Jul 14 09:21:02 2009 (4A5BC15E)
    fffff880 ' 04800000 fffff880'd 0482 000 mrxsmb mrxsmb.sys Sat Feb 27 18:52:19 2010 (4B88CF33)
    "fffff880 ' 0482 d 000 fffff880 ' b 0487, 000 mrxsmb10 mrxsmb10.sys Sat Feb 27 18:52:28 2010 (4B88CF3C)
    fffff880 '0487b 000 fffff880' 0489e000 mrxsmb20 mrxsmb20.sys Sat Feb 27 18:52:26 2010 (4B88CF3A)
    fffff880 '048de000 fffff880' 049a 6000 HTTP HTTP.sys kills Jul 14 09:22:16 2009 (4A5BC1A8)
    fffff880'049 has 6000 fffff880'049 c 4000 bowser bowser.sys kills Jul 14 09:23:50 2009 (4A5BC206)
    "fffff880 ' 049 c 4000 fffff880 ' 049dc000 mpsdrv mpsdrv.sys kills Jul 14 10:08:25 2009 (4A5BCC79)
    fffff880 '04-00000 fffff880' 04a 19000 rimspe64 rimspe64.sys Thu Aug 02 09:54:49 2009 (4A4BF749)
    fffff880'04a1b000 fffff880'05544080 nvlddmkm nvlddmkm.sys Sat Jan 16 07:45:08 2010 (4B50D3D4)
    fffff880 ' 05545000 fffff880' 05546180 nvBridge nvBridge.kmd sat Jan 16 07:15:31 2010 (4B50CCE3)
    fffff880 ' 05547000 fffff880'd 0558-000 dxgmms1 dxgmms1.sys kills Jul 14 09:38:32 2009 (4A5BC578)
    "fffff880 ' 0558 d 000 fffff880 ' 055b 1000 HDAudBus HDAudBus.sys kills Jul 14 10:06:13 2009 (4A5BCBF5)
    fffff880'055 b 1000 fffff880'055 c 2000 HECIx64 HECIx64.sys Fri Sep 18 05:54:16 2009 (4AB293E8)
    fffff880 '055 c 2000 fffff880' 055d 3000 usbehci usbehci.sys Fri dec 04 18:26:02 2009 (4B18B98A)
    "fffff880 ' 055 d 3000 fffff880 ' 055ec000 risdpe64 risdpe64.sys Fri Nov 27 23:53:49 2009 (4B0FCBDD)
    fffff880 '055ec000 fffff880' 055f4080 HIDPARSE HIDPARSE. SYS kills Jul 14 10:06:17 2009 (4A5BCBF9)
    "fffff880 ' 05 c 00000 fffff880 ' 05c3a000 aswMonFlt-C:\windows\system32\drivers\aswmonflt.sys Sat Oct 08 00:47:32 (4 865084) 2010
    fffff880 '05c3a000 fffff880' 05c5b000 WudfPf WudfPf.sys kills Jul 14 10:05:37 2009 (4A5BCBD1)
    fffff880 '05c5b000 fffff880' 05cae000 nwifi nwifi.sys kills Jul 14 10:07:23 2009 (4A5BCC3B)
    fffff880 '05cae000 fffff880' 05cc1000 o ndisuio ndisuio.sys kills Jul 14 10:09:25 2009 (4A5BCCB5)
    fffff880'05 cd 8000 fffff880'05 d 32000 usbhub usbhub.sys Fri dec 04 18:26:39 2009 (4B18B9AF)
    fffff880 '05 d 32000 fffff880' 05 d 40000 kbdhid kbdhid.sys kills Jul 14 10:00:20 2009 (4A5BCA94)
    fffff880 '05 d 40000 fffff880' 05 d 55000 NDProxy NDProxy.SYS kills Jul 14 10:10:05 2009 (4A5BCCDD)
    "fffff880 ' 05 d 55000 fffff880 ' 05d6d000 nvhda64v nvhda64v.sys Sat Aug 22 06:23:50 2009 (4A8F0256)
    fffff880 '05d6d000 fffff880' 05daa000 Portcls.sys portcls cela kills Jul 14 10:06:27 2009 (4A5BCC03)
    fffff880 '05daa000 fffff880' 05dcc000 drmk.sys drmk kills Jul 14 11:01:25 2009 (4A5BD8E5)
    fffff880 '05dcc000 fffff880' 05dd1200 ksthunk ksthunk.sys kills Jul 14 10:00:19 2009 (4A5BCA93)
    fffff880 '05dd2000 fffff880' 05df5000 luafv luafv.sys kills Jul 14 09:26:13 2009 (4A5BC295)
    fffff880 ' 06805000 fffff880' 06a31d00 RTKVHD64 RTKVHD64.sys kills Mar 09 23:26:36 2010 (4B963E7C)
    fffff880 '06-32000 fffff880' 06a 43000 hidir hidir.sys kills Jul 14 10:06:23 2009 (4A5BCBFF)
    fffff880 '06-43000 fffff880' 06a 50000 me mouhid.sys kills Jul 14 10:00:20 2009 (4A5BCA94)
    fffff880 '06-50000 fffff880' 06a5c000 Dxapi Dxapi.sys kills Jul 14 09:38:28 2009 (4A5BC574)
    fffff880 '06a5c000 fffff880' 06b4c000 dvb7700all dvb7700all.sys Thu Jun 11 15:08:39 2009 (A 4, 309157)
    fffff880 '06b4c000 fffff880' 06b4fe80 BdaSup BdaSup.SYS kills Jul 14 10:06:40 2009 (4A5BCC10)
    fffff880 '06b 50000 fffff880' 06b5e000 monitor monitor.sys kills Jul 14 09:38:52 2009 (4A5BC58C)
    fffff880 '06b5e000 fffff880' 06b7b000 usbccgp usbccgp.sys kills Jul 14 10:06:45 2009 (4A5BCC15)
    fffff880 '06b 89000 fffff880' 06bb6100 usbvideo usbvideo.sys kills Jul 14 10:07 2009 (4A5BCC24)
    fffff880 '06bb7000 fffff880' 06bbde80 pgeffect pgeffect.sys Mon 22 June at 19:00:11 2009 (4A3F481B)
    fffff880 '06bbe000 fffff880' 06bcc000 crashdmp.sys crashdmp kills Jul 14 10:01:01 2009 (4A5BCABD)
    fffff880 '06bcc000 fffff880' 06bdf000 dump_dumpfve dump_dumpfve.sys kills Jul 14 09:21:51 2009 (4A5BC18F)
    fffff880 '06bdf000 fffff880' 06be8000 aswFsBlk aswFsBlk.SYS Sat Oct 08 00:47:09 2010 (4C86506D)
    fffff880 '06be8000 fffff880' 06bfd000 lltdio lltdio.sys kills Jul 14 10:08:50 2009 (4A5BCC92)
    fffff880 ' fffff880 0782 c 000' 078d 2000 peauth peauth.sys kills Jul 14 11:01:19 2009 (4A5BD8DF)
    "fffff880 ' 078 d 2000 fffff880 ' 078da000 regi regi.sys Fri Apr 17 01:19:10 2007 (462393EE)
    fffff880 '078da000 fffff880' 078e5000 secdrv secdrv. SYS kills Sep 13 23:18:38 2006 (4508052E)
    fffff880'078e5000 fffff880'07912000 srvnet Mar c:\windows\system32\drivers\srvnet.sys 22 June at 13:20:32 2010 (4C202C00)
    fffff880 ' 07912000 fffff880' 07924000 tcpipreg c:\windows\system32\drivers\tcpipreg.sys kills Jul 14 10:09:49 2009 (4A5BCCCD)
    fffff880 '07924000 fffff880' c 0798 000 srv2 srv2.sys Mar 22 June at 13:20:47 2010 (4C202C0F)
    fffff880 ' fffff880 0798 c 000' cd 079 000 truecrypt truecrypt.sys MON Sep 06 00:23:16 2010 (4C83A7D4)
    "fffff880 ' 07 c 00000 fffff880 ' 07c4b000 Rt64win7 Rt64win7.sys Fri Nov 06 01:15:41 2009 (4AF2DE0D)
    fffff880 '07c4b000 fffff880' 07C 62000 nuvotonir nuvotonir.sys MON Aug 31 21:43:16 2009 (4A9BB754)
    "fffff880 ' 07 c 65000 fffff880 ' 07cbb000 rixdpe64 rixdpe64.sys Sat Aug 04 20:27 2009 (4A4F2E74)
    fffff880 '07cbb000 fffff880' 07dc3000 rtl8192se rtl8192se.sys Fri Oct 02 15:33:48 2009 (4AC590BC)
    fffff880 '07dc3000 fffff880' 07dd0000 vwifibus vwifibus.sys kills Jul 14 10:07:21 2009 (4A5BCC39)
    fffff880 '07dd0000 fffff880' 07dde000 nuvotonhidcir nuvotonhidcir.sys MON Aug 31 23:34:12 2009 (4A9BD154)
    fffff880 '07dde000 fffff880' 07de6000 hidshim hidshim.sys MON Aug 31 23:34:14 2009 (4A9BD156)
    fffff880 '07de6000 fffff880' 07dff000 HIDCLASS HIDCLASS. SYS kills Jul 14 10:06:21 2009 (4A5BCBFD)
    fffff880 ' 08015000 fffff880' 080ab000 srv srv.sys Tue 22 June at 13:21:11 2010 (4C202C27)
    fffff880 '080ab000 fffff880' 080dc000 WUDFRd.sys WUDFRd kills Jul 14 10:06:06 2009 (4A5BCBEE)
    fffff880 '080dc000 fffff880' 080f0000 PROCMON20 PROCMON20. SYS Sun Mar 21 00:54:02 2010 (4BA4D37A)
    fffff880'080f9000 fffff880'08102000 cpuz133_x64 cpuz133_x64.sys Tue may 11 19:58:57 2010 (4BE92A61)
    fffff880'0813f000 fffff880'08146000 speedfan.sys speedfan Sun Sep 24 23:26:48 2006 (45168798)
    fffff880 '08146000 fffff880' 0817 000 fastfat fastfat c. SYS kills Jul 14 09:23:28 2009 (4A5BC1F0)
    fffff880'081bb000 fffff880'081 c 6000 PROCEXP141 PROCEXP141. SYS Thu Apr 15 19:24:06 2010 (4BC6DB36)
    "fffff880 ' 081 c 6000 fffff880 ' 081e1000 USBSTOR USBSTOR. SYS kills Jul 14 10:06:34 2009 (4A5BCC0A)
    fffff880 '081e1000 fffff880' 081ef000 hidusb hidusb.sys kills Jul 14 10:06:22 2009 (4A5BCBFE)
    "fffff960 ' 00070000 fffff960 ' 0037f000 win32k win32k.sys sat 19 June 14:31:59 2010 (4C1C483F)
    fffff960 ' 00550000 fffff960' a 0055, 000 TSDDD TSDDD.dll kills Jul 14 10:16:34 2009 (4A5BCE62)
    fffff960'006e0000 fffff960' c:\windows\system32\cdd.dll cdd 00707000 unavailable (00000000)

    Unloaded modules:
    fffff880 ' 08104000 fffff880' 08106000 MSPQM.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffff880'096e4000 fffff880'09755000 spsys.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffff880 ' 08102000 fffff880' 08104000 MSPQM.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffff880 '080f0000 fffff880' 080f9000 cpuz134_x64.
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffff880 '081f3000 fffff880' 081f5000 MSPQM.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffff880 '081f1000 fffff880' 081f3000 MSPCLOCK.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffff880 '081ef000 fffff880' 081f1000 MSPQM.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffff880 '081ad000 fffff880' 081bb000 hidusb.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    "fffff880 ' 0817 c 000 fffff880 ' 081ad000 WUDFRd.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffff880 '06b7b000 fffff880' 06b 89000 hidusb.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffff880 ' 08124000 fffff880' 0813f000 USBSTOR. SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffff880 ' 08122000 fffff880' 08124000 MSPCLOCK.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffff880 ' 08120000 fffff880' 08122000 MSPQM.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffff880'0811e000 fffff880'08120000 MSPCLOCK.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    "fffff880 ' 0811 c 000 fffff880 ' 0811e000 MSPQM.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffff880'080ab000 fffff880'0811 c 000 spsys.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffff880 '01 a 30000 fffff880' 01a3e000 crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffff880'044fa000 fffff880'04702000 dump_iaStor.
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffff880 ' 04702000 fffff880' 04715000 dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    C:\debuglog.txt closing open log file

    =========
    = DEBUG =
    =========

    Open the logfile "c:\debuglog.txt".
    16.6: kd:x 86 > .sympath srv * c:\symbols* http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv * c:\symbols* http://msdl.microsoft.com/download/symbols
    Expanded the symbol search path is: srv * c:\symbols* http://msdl.microsoft.com/download/symbols
    16.6: kd:x 86 > .reload!; analyze - v; lmnt; r; kV. logclose; q
    Loading the kernel symbols
    .................................................. .............
    .................................................. ..............
    .................................................. ........
    Loading user symbols
    PEB is paginated on (Peb.Ldr = 000007ff'fffd9018). Type ".hh dbgerr001" for more details
    Loading unloaded module list
    .......
    ************************************************** *****************************
    * *
    * Bugcheck analysis *.
    * *
    ************************************************** *****************************

    QUOTA_UNDERFLOW (21)
    This error occurs if a contingent improperly fresh core component and
    returns more quota than has been previously assigned to a particular block of quota.
    Arguments:
    Arg1: 0000000000000000, process (if any) who has been charged in the first place.
    Arg2: 0000000000000001, the type of quota in question (pool paged, non paged, etc..)
    Arg3: 0000000009000000, the amount of the initial return load.
    Arg4: 0000000008566294, charge remaining (not returned).

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

    PEB is paginated on (Peb.Ldr = 000007ff'fffd9018). Type ".hh dbgerr001" for more details
    PEB is paginated on (Peb.Ldr = 000007ff'fffd9018). Type ".hh dbgerr001" for more details

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0X21

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from 0000000000000000 to 0000000000000000

    STACK_TEXT:
    00000000 00000000 00000000 00000000 00000000 0 x 0

    STACK_COMMAND: kb

    SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Unknown_Module

    Nom_image: Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    BUCKET_ID: INVALID_KERNEL_CONTEXT

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

    EAX = 00000000 ebx = 00000000 ecx = 00000000 edx = 00000000 esi = 00000000 edi = 00000000
    EIP = 00000000 esp = 00000000 ebp = 00000000 iopl = 0 nv place di pl nz na po nc
    CS = 0000 ss = are ds = 0000 0000 = 0000 0000 0000 efl = 00000000 = fs = gs
    00000000? ???
    ChildEBP RetAddr Args to child
    WARNING: Frame IP not in any known module. Sequence of images may be wrong.
    00000000 00000000 00000000 00000000 00000000 0 x 0
    start end module name
    00b9f000 00ba9000 kdcom kdcom.dll kills Jul 14 11:31:07 2009 (4A5BDFDB)
    03400000 039dc000 nt ntkrnlmp.exe sat 19 June at 14:16:41 2010 (4C1C44A9)
    039dc000 03a 25000 hal hal.dll kills Jul 14 11:27:36 2009 (4A5BDF08)
    00C 00000 00cc0000 CI CI.dll Tue Jul 14 11:32:13 2009 (4A5BE01D)
    00cca000 00d0e000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll kills Jul 14 11:29:10 2009 (4A5BDF66)
    00d0e000 00D 22000 PSHED PSHED.dll Thu Aug 14 11:32:23 2009 (4A5BE027)
    00D 22000 00D 80000 CLFS CLFS. SYS kills Jul 14 09:19:57 2009 (4A5BC11D)
    00D 80000 00ddc000 volmgrx volmgrx.sys kills Jul 14 09:20:33 2009 (4A5BC141)
    00e00000 00e33000 pci pci.sys kills Jul 14 09:19:51 2009 (4A5BC117)
    00e33000 00e40000 vdrvroot vdrvroot.sys kills Jul 14 10:01:31 2009 (4A5BCADB)
    00e40000 00e55000 partmgr partmgr.sys kills Jul 14 09:19:58 2009 (4A5BC11E)
    00e55000 00e5e000 compbatt compbatt.sys kills Jul 14 09:31:02 2009 (4A5BC3B6)
    00e5e000 00e6a000 BATTC BATTC. SYS Tue Jul 14 09:31:01 2009 (4A5BC3B5)
    00e6a000 00e7f000 volmgr volmgr.sys kills Jul 14 09:19:57 2009 (4A5BC11D)
    00e7f000 00e99000 mountmgr mountmgr.sys kills Jul 14 09:19:54 2009 (4A5BC11A)
    00e99000 00eb3000 rassstp rassstp.sys kills Jul 14 10:10:25 2009 (4A5BCCF1)
    00ed9000 00f7d000 Wdf01000 Wdf01000.sys kills Jul 14 09:22:07 2009 (4A5BC19F)
    00f7d000 00f8c000 WDFLDR WDFLDR. SYS kills Jul 14 09:19:54 2009 (4A5BC11A)
    00f8c000 00fe3000 ACPI ACPI.sys kills Jul 14 09:19:34 2009 (4A5BC106)
    00fe3000 00fec000 WMILIB WMILIB. SYS kills Jul 14 09:19:51 2009 (4A5BC117)
    00fec000 00ff6000 msisadrv.sys msisadrv kills Jul 14 09:19:26 2009 (4A5BC0FE)
    01000000 0101b 000 raspppoe raspppoe.sys kills Jul 14 10:10:17 2009 (4A5BCCE9)
    0101b 000 0103c 000 raspptp raspptp.sys kills Jul 14 10:10:18 2009 (4A5BCCEA)
    0103f000 01247000 iaStor, iaStor.sys Sat Oct 03 05:58:50 2009 (4AC65B7A)
    01247000 01250000 atapi atapi.sys kills Jul 14 09:19:47 2009 (4A5BC113)
    0127a 000 01250000 ataport ataport. SYS kills Jul 14 09:19:52 2009 (4A5BC118)
    0127a 000 01285000 msahci msahci.sys kills Jul 14 10:01:01 2009 (4A5BCABD)
    01285000 01295000 PCIIDEX PCIIDEX. SYS kills Jul 14 09:19:48 2009 (4A5BC114)
    01295000 012a 0000 amdxata amdxata.sys sea may 20 03:56:59 2009 (4A12F2EB)
    012a 0000 012ec000 fltmgr fltmgr.sys kills Jul 14 09:19:59 2009 (4A5BC11F)
    FileInfo 01300000 012ec000 fileinfo.sys Tue 14 Jul 09:34:25 2009 (4A5BC481)
    01300000 0135e000 msrpc msrpc.sys kills Jul 14 09:21:32 2009 (4A5BC17C)
    0135e000 013d 1000 CNG cng.sys kills Jul 14 09:49:40 2009 (4A5BC814)
    013d 1000 01400000 ndiswan ndiswan.sys kills Jul 14 10:10:11 2009 (4A5BCCE3)
    01400000 0141a 000 ksecdd ksecdd.sys kills Jul 14 09:20:54 2009 (4A5BC156)
    0141a 000 0142 b 000 pcw.sys pcw kills Jul 14 09:19:27 2009 (4A5BC0FF)
    0142b 000 01435000 Fs_Rec Fs_Rec.sys kills Jul 14 09:19:45 2009 (4A5BC111)
    01435000 01450000 wanarp wanarp.sys kills Jul 14 10:10:21 2009 (4A5BCCED)
    0145c 000 015ff000 Ntfs Ntfs.sys kills Jul 14 09:20:47 2009 (4A5BC14F)
    01600000 01660000 NETIO NETIO. SYS kills Jul 14 09:21:46 2009 (4A5BC18A)
    b 01660000 0168, 000 ksecpkg ksecpkg.sys Fri Jan 11 17:03:32 2009 (4B21E0B4)
    0168b 000 016d 5000 c:\windows\system32\drivers\fwpkclnt fwpkclnt.sys kills Jul 14 09:21:08 2009 (4A5BC164)
    016D 5000 016eb000 vwififlt vwififlt.sys kills Jul 14 10:07:22 2009 (4A5BCC3A)
    016f3000 017e5000 ndis ndis.sys kills Jul 14 09:21:40 2009 (4A5BC184)
    017e5000 017f7a00 tosrfcom tosrfcom.sys kills Jul 28 20:18:20 2009 (4A6ED06C)
    01803000 01a 00000 tcpip tcpip.sys Mon 14 Jun 13:39:04 2010 (4C15A458)
    01a 00000 01a3a000 rdyboost rdyboost.sys Mar 14 Jul 09:34:34 2009 (4A5BC48A)
    01a3a000 01a4c000 mup mup.sys kills Jul 14 09:23:45 2009 (4A5BC201)
    01a4c000 01 has 55000 hwpolicy hwpolicy.sys kills Jul 14 09:19:22 2009 (4A5BC0FA)
    01a 55000 01a8f000 fvevol fvevol.sys my Sep 26 12:34:26 2009 (4ABD7DB2)
    01a8f000 01aa5000 disk disk.sys kills Jul 14 09:19:57 2009 (4A5BC11D)
    01aa5000 01ad5000 CLASSPNP CLASSPNP. SYS kills Jul 14 09:19:58 2009 (4A5BC11E)
    01ae1000 01b2d000 volsnap volsnap.sys kills Jul 14 09:20:08 2009 (4A5BC128)
    01b2d000 01b31e00 TVALZ TVALZ. SYS kills Jul 14 12:18:54 2009 (4A5BEB0E)
    01 b 32000 01bac000 tos_sps64 tos_sps64.sys sea June 24 at 15:31:09 2009 (4A41BA1D)
    01bac000 01badf80 Thpevm Thpevm.SYS MON 29 Jun 18:15:37 2009 (A 4, 487829)
    01bae000 01bba000 thpdrv thpdrv.sys Fri Jun 29 12:02:56 2009 (4A4820D0)
    01bba000 01bc2000 spldr spldr.sys Tue may 12 02:56:27 2009 (4A0858BB)
    01bc2000 01bc9000 speedfan speedfan.sys Sun Sep 24 23:26:48 2006 (45168798)
    01bd7000 01bfd000 pacer pacer.sys kills Jul 14 10:09:41 2009 (4A5BCCC5)
    02e00000 02e0e000 nuvotonhidcir nuvotonhidcir.sys MON Aug 31 23:34:12 2009 (4A9BD154)
    02e0e000 02e16000 hidshim hidshim.sys MON Aug 31 23:34:14 2009 (4A9BD156)
    02e16000 02e2f000 HIDCLASS HIDCLASS. SYS kills Jul 14 10:06:21 2009 (4A5BCBFD)
    02e2f000 02e37080 HIDPARSE HIDPARSE. SYS kills Jul 14 10:06:17 2009 (4A5BCBF9)
    02e38000 02e47000 kbdclass.sys kbdclass kills Jul 14 09:19:50 2009 (4A5BC116)
    02e47000 02e48f00 USBD USBD. SYS kills Jul 14 10:06:23 2009 (4A5BCBFF)
    02e4b000 02f78000 rtl8192se.sys rtl8192se kills Apr 27 03:23:06 2010 (4BD5CBFA)
    02f78000 02f85000 vwifibus vwifibus.sys kills Jul 14 10:07:21 2009 (4A5BCC39)
    02f85000 02fdc000 Rt64win7 Rt64win7.sys Fri Mar 05 00:42:52 2010 (4B8FB8DC)
    02fdc000 02ff3000 nuvotonir nuvotonir.sys MON Aug 31 21:43:16 2009 (4A9BB754)
    02ff3000 02ffd000 tdcmdpst tdcmdpst.sys Wed 30 Jul 18:39:35 2009 (4A715C47)
    02ffd000 02ffe480 swenum swenum.sys kills Jul 14 10:00:18 2009 (4A5BCA92)
    03e00000 03e8a000 afd afd.sys kills Jul 14 09:21:40 2009 (4A5BC184)
    03e8a000 03e94000 aswRdr aswRdr.SYS Sat Oct 08 00:47:47 (4 865093) 2010
    03e94000 03e9d000 wfplwf wfplwf.sys kills Jul 14 10:09:26 2009 (4A5BCCB6)
    03e9d000 03eac000 netbios netbios.sys kills Jul 14 10:09:26 2009 (4A5BCCB6)
    03eac000 040b 4000 dump_iaStor dump_iaStor.sys Sat Oct 03 05:58:50 2009 (4AC65B7A)
    040 c 9000 040f3000 CD-ROM cdrom.sys kills Jul 14 09:19:54 2009 (4A5BC11A)
    040f3000 fc 040 000 Null Null.SYS Tue Jul 14 09:19:37 2009 (4A5BC109)
    040 000 04103000 c:\windows\system32\drivers\beep.sys CF beep kill Jul 14 10:00:13 2009 (4A5BCA8D)
    04103000 04111000 vga vga.sys kills Jul 14 09:38:47 2009 (4A5BC587)
    04111000 04136000 VIDEOPRT VIDEOPRT. SYS kills Jul 14 09:38:51 2009 (4A5BC58B)
    04136000 04146000 watchdog.sys guard dog kills Jul 14 09:37:35 2009 (4A5BC53F)
    04146000 0414f000 RDPCDD system32\drivers\rdpcdd.sys Tue Jul 14 10:16:34 2009 (4A5BCE62)
    0414f000 04158000 rdpencdd rdpencdd.sys kills Jul 14 10:16:34 2009 (4A5BCE62)
    04158000 04161000 rdprefmp rdprefmp.sys kills Jul 14 10:16:35 2009 (4A5BCE63)
    04161000 0416c 000 Msfs Msfs.SYS Tue Jul 14 09:19:47 2009 (4A5BC113)
    0416c 000 0417d 000 Npfs Npfs.SYS Tue Jul 14 09:19:48 2009 (4A5BC114)
    0417d 000 0419b 000 tdx tdx.sys kills Jul 14 09:21:15 2009 (4A5BC16B)
    0419b 000 041 has 8000 TDI TDI. SYS kills Jul 14 09:21:18 2009 (4A5BC16E)
    041a 8000 041 b 8000 aswTdi Device aswTdi.SYS Sat Oct 08 00:52:27 2010 (4C8651AB)
    041b 8000 041fd000 netbt netbt.sys kills Jul 14 09:21:28 2009 (4A5BC178)
    04600000 04624000 rasl2tp rasl2tp.sys kills Jul 14 10:10:11 2009 (4A5BCCE3)
    04624000 04630000 ndistapi.sys ndistapi kills Jul 14 10:10 2009 (4A5BCCD8)
    04644000 04685000 truecrypt.sys of truecrypt MON Sep 06 00:23:16 2010 (4C83A7D4)
    04685000 04699000 termdd termdd.sys kills Jul 14 10:16:36 2009 (4A5BCE64)
    04699000 046ea000 rdbss rdbss.sys kills Jul 14 09:24:09 2009 (4A5BC219)
    046ea000 046f6000 nsiproxy nsiproxy.sys kills Jul 14 09:21:02 2009 (4A5BC15E)
    046f6000 mssmbios 04701000 mssmbios.sys kills Jul 14 09:31:10 2009 (4A5BC3BE)
    04701000 discache 04710000 discache.sys kills Jul 14 09:37:18 2009 (4A5BC52E)
    04710000 0472e000 dfsc dfsc.sys kills Jul 14 09:23:44 2009 (4A5BC200)
    0472e000 0473f000 blbdrive blbdrive.sys kills Jul 14 09:35:59 2009 (4A5BC4DF)
    0473f000 04762000 aswSP aswSP.SYS Sat Oct 08 00:52:07 2010 (4 865197)
    04762000 04788000 tunnel tunnel.sys kills Jul 14 10:09:37 2009 (4A5BCCC1)
    04788000 0479e000 intelppm intelppm.sys kills Jul 14 09:19:25 2009 (4A5BC0FD)
    0479e000 047f0000 SynTP SynTP.sys Thu Mar 11 13:02:01 2010 (4B984F19)
    04a 00000 04 has 16000 AgileVpn AgileVpn.sys kills Jul 14 10:10:24 2009 (4A5BCCF0)
    04a1b000 05544080 nvlddmkm nvlddmkm.sys Sat Jan 16 07:45:08 2010 (4B50D3D4)
    05545000 05546180 nvBridge nvBridge.kmd sat Jan 16 07:15:31 2010 (4B50CCE3)
    05547000 05560000 risdpe64 risdpe64.sys Fri Nov 27 23:53:49 2009 (4B0FCBDD)
    05560000 05579000 rimspe64 rimspe64.sys Thu Aug 02 09:54:49 2009 (4A4BF749)
    05579000 055cf000 rixdpe64 rixdpe64.sys Sat Aug 04 20:27 2009 (4A4F2E74)
    055cf000 055ed000 i8042prt i8042prt.sys kills Jul 14 09:19:57 2009 (4A5BC11D)
    055ed000 055fd000 CompositeBus CompositeBus.sys kills Jul 14 10:00:33 2009 (4A5BCAA1)
    05600000 05623000 luafv luafv.sys kills Jul 14 09:26:13 2009 (4A5BC295)
    05623000 0565d 000 aswMonFlt C:\windows\system32\drivers\aswmonflt.sys Sat Oct 08 00:47:32 (4 865084) 2010
    0565d 000 05666000 aswFsBlk aswFsBlk.SYS Sat Oct 08 00:47:09 2010 (4C86506D)
    05666000 05687000 WudfPf WudfPf.sys Tue Jul 14 10:05:37 2009 (4A5BCBD1)
    05689000 05779000 dvb7700all dvb7700all.sys Thu Jun 11 15:08:39 2009 (A 4, 309157)
    05779000 0577ce80 BdaSup BdaSup.SYS Tue Jul 14 10:06:40 2009 (4A5BCC10)
    d 0577 000 0579a 000 usbccgp usbccgp.sys kills Jul 14 10:06:45 2009 (4A5BCC15)
    0579a 000 057 b 5000 USBSTOR USBSTOR. SYS kills Jul 14 10:06:34 2009 (4A5BCC0A)
    057b 5000 057c 3000 hidusb hidusb.sys kills Jul 14 10:06:22 2009 (4A5BCBFE)
    057c 3000 057f0100 usbvideo usbvideo.sys kills Jul 14 10:07 2009 (4A5BCC24)
    057f1000 057f7e80 pgeffect pgeffect.sys Mon 22 June at 19:00:11 2009 (4A3F481B)
    0585 to 000 0589d 000 ks ks.sys kills Jul 14 10:00:31 2009 (4A5BCA9F)
    0589d 000 058af000 circlass circlass.sys kills Jul 14 10:06:34 2009 (4A5BCC0A)
    058af000 1000 058c umbus umbus.sys kills Jul 14 10:06:56 2009 (4A5BCC20)
    058c 1000 0591b 000 usbhub usbhub.sys Fri dec 04 18:26:39 2009 (4B18B9AF)
    0591b 000 05929000 kbdhid kbdhid.sys kills Jul 14 10:00:20 2009 (4A5BCA94)
    05929000 0593 has 000 tosporte tosporte.sys Mar 16 June 20:48:47 2009 (4A37788F)
    0593 to 000 0594f000 NDProxy NDProxy.SYS kills Jul 14 10:10:05 2009 (4A5BCCDD)
    0594f000 05967000 nvhda64v nvhda64v.sys Sat Aug 22 06:23:50 2009 (4A8F0256)
    05967000 059a 4000 portcls portcls.sys kills Jul 14 10:06:27 2009 (4A5BCC03)
    059a 4000 059c 6000 drmk drmk.sys kills Jul 14 11:01:25 2009 (4A5BD8E5)
    059c 6000 059cb200 ksthunk ksthunk.sys kills Jul 14 10:00:19 2009 (4A5BCA93)
    06800000 06853000 nwifi nwifi.sys kills Jul 14 10:07:23 2009 (4A5BCC3B)
    06853000 06866000 o ndisuio ndisuio.sys kills Jul 14 10:09:25 2009 (4A5BCCB5)
    06866000 0687e000 rspndr rspndr.sys kills Jul 14 10:08:50 2009 (4A5BCC92)
    0687e000 068b 4000 fastfat fastfat. SYS kills Jul 14 09:23:28 2009 (4A5BC1F0)
    068e0000 06b0cd00 RTKVHD64 RTKVHD64.sys kills Mar 09 23:26:36 2010 (4B963E7C)
    06b0d000 06b1e000 hidir.sys hidir kills Jul 14 10:06:23 2009 (4A5BCBFF)
    06b1e000 06b2b000 mouhid.sys me kills Jul 14 10:00:20 2009 (4A5BCA94)
    06b2b000 06b 37000 Dxapi Dxapi.sys Tue Jul 14 09:38:28 2009 (4A5BC574)
    06b 37000 06 b 45000 crashdmp crashdmp.sys kills Jul 14 10:01:01 2009 (4A5BCABD)
    06b 45000 06 b 53000 monitor monitor.sys kills Jul 14 09:38:52 2009 (4A5BC58C)
    06b 53000 06 b 66000 dump_dumpfve dump_dumpfve.sys kills Jul 14 09:21:51 2009 (4A5BC18F)
    06b 66000 06 b 73700 tosrfusb tosrfusb.sys Thu Apr 08 12:06:16 2010 (4BBD3A18)
    b 06, 74000 06ba6f80 tosrfbd tosrfbd.sys sea Apr 07 10:49:48 2010 (4BBBD6AC)
    06ba7000 06bbcb00 Tosrfhid Tosrfhid.sys sea 20 May 11:23:51 2009 (4A135BA7)
    06bbd000 06bd2000 lltdio lltdio.sys kills Jul 14 10:08:50 2009 (4A5BCC92)
    07400000 0744e000 mrxsmb10 mrxsmb10.sys Sat Feb 27 18:52:28 2010 (4B88CF3C)
    0744e000 07471000 mrxsmb20 mrxsmb20.sys Sat Feb 27 18:52:26 2010 (4B88CF3A)
    07471000 0747 has 000 cpuz133_x64 cpuz133_x64.sys Tue may 11 19:58:57 2010 (4BE92A61)
    0747a 000 07483000 cpuz134_x64 cpuz134_x64.sys Fri Jul 09 21:16:58 2010 (4C37052A)
    074b 7000 0757f000 HTTP HTTP.sys kills Jul 14 09:22:16 2009 (4A5BC1A8)
    0757f000 d 0759 000 bowser bowser.sys kills Jul 14 09:23:50 2009 (4A5BC206)
    0759d 000 075 b 5000 mpsdrv mpsdrv.sys kills Jul 14 10:08:25 2009 (4A5BCC79)
    075b 5000 075e2000 mrxsmb mrxsmb.sys Sat Feb 27 18:52:19 2010 (4B88CF33)
    07a4b000 07af1000 peauth peauth.sys kills Jul 14 11:01:19 2009 (4A5BD8DF)
    07af1000 07af9000 regi regi.sys Fri Apr 17 01:19:10 2007 (462393EE)
    07af9000 b 07/04000 secdrv secdrv. SYS kills Sep 13 23:18:38 2006 (4508052E)
    07b 04000 07 b 31000 c:\windows\system32\drivers\srvnet.sys srvnet Mar 22 June at 13:20:32 2010 (4C202C00)
    07b 31000 07 b 43000 tcpipreg c:\windows\system32\drivers\tcpipreg.sys kills Jul 14 10:09:49 2009 (4A5BCCCD)
    b 07, 43000 07bab000 srv2 srv2.sys Mar 22 June at 13:20:47 2010 (4C202C0F)
    08800000 08846000 dxgmms1 dxgmms1.sys kills Jul 14 09:38:32 2009 (4A5BC578)
    a 08846000 0886, 000 HDAudBus HDAudBus.sys kills Jul 14 10:06:13 2009 (4A5BCBF5)
    0886a 000 0887 b 000 HECIx64 HECIx64.sys Fri Sep 18 05:54:16 2009 (4AB293E8)
    0887b 000 c 0888 000 usbehci usbehci.sys Fri dec 04 18:26:02 2009 (4B18B98A)
    c 0888 000 088e2000 USBPORT USBPORT. SYS kills Jul 14 10:06:31 2009 (4A5BCC07)
    088e2000 088f1000 mouclass mouclass.sys kills Jul 14 09:19:50 2009 (4A5BC116)
    088f6000 089ea000 dxgkrnl dxgkrnl.sys Fri Oct 02 11:00:14 2009 (4AC5509E)
    089ea000 089f1000 TVALZFL TVALZFL.sys Fri Jun 19 20:05:44 2009 (4A3B62F8)
    089f1000 089fa000 tosrfec tosrfec.sys Mon 01 June at 16:58:53 2009 (4A237C2D)
    089fa000 089fe500 CmBatt CmBatt.sys Tue 14 Jul 09:31:03 2009 (4A5BC3B7)
    0ae71000 0ae7c000 ElbyCDIO C:\windows\system32\drivers\elbycdio.sys Fri Dec 18 09:25:16 2009 (4B2AAFCC)
    0ae7c000 0ae8b000 VClone VClone.sys Fri Aug 10 07:25:45 2009 (4A7F3ED9)
    0ae8b000 0aeba000 SCSIPORT SCSIPORT. SYS kills Jul 14 10:01:04 2009 (4A5BCAC0)
    0aeba000 0aed7000 cdfs.sys cdfs kills Jul 14 09:19:46 2009 (4A5BC112)
    0aedb000 0aedca80 MSPQM.sys MSPQM kills Jul 14 10:00:17 2009 (4A5BCA91)
    0aee7000 0af7d000 srv srv.sys Tue 22 June at 13:21:11 2010 (4C202C27)
    0af7d000 0afae000 WUDFRd WUDFRd.sys Tue Jul 14 10:06:06 2009 (4A5BCBEE)
    0afae000 0afb9000 PROCEXP141 PROCEXP141. SYS Thu Apr 15 19:24:06 2010 (4BC6DB36)
    000f0000 003ff000 win32k win32k.sys sat 19 June 14:31:59 2010 (4C1C483F)
    a 00540000 0054, 000 TSDDD TSDDD.dll kills Jul 14 10:16:34 2009 (4A5BCE62)
    00640000 00667000 cdd c:\windows\system32\cdd.dll Thu May 20 05:48:26 2010 (4BF4408A)

    Unloaded modules:
    0aed9000 0aedb000 MSPQM.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    0aed7000 0aed9000 MSPQM.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    0ae00000 0ae71000 spsys.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    05687000 05689000 MSPQM.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    01bc9000 01bd7000 crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    03eae000 040b 6000 dump_iaStor.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    040b 6000 9000 dump_dumpfve.sys 040 c
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    C:\debuglog.txt closing open log file

    Why you run Windows update to check if all the drivers are available Toshiba drivers? Use only the drivers of Toshiba. What drivers did you updated?

    Have you installed something that may be responsible for BSOD?
    Have you tried to roll back the OS before starting?

    Sorry for all these questions. I put t had time to check debugs and don t think that anyone here will take time to study this, but I don t think this BSOD are caused by Toshiba software.

  • Win 7 64 bit ntkrnlmp.exe PILOT OUT of STATE

    So I tried to solve this problem for 2 weeks with no luck.  Been randomly do the BSOD.  I went through windows update to update drivers, checked the hard drive with chkdsk, ran sfc/scannow and to verify the RAM memtest.  Search around in several forums and it seems to be driver related (but in each post, this is another).  In the end, I think I need someone to analyze my memory dump file to which driver is the cause of the crash.

    Enjoy, thank you.

    Using that crashed:

    Monday, February 8, 2016 22:19:02 this computer crashed
    crash dump file: C:\Windows\memory.dmp

    This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
    Bugcheck code: 0x9F (0x3, 0xFFFFFA800DAC4CD0, 0xFFFFF8000557F3D8, 0xFFFFFA8011732940)
    Error: DRIVER_POWER_STATE_FAILURE
    Bug control description: this bug check indicates that the driver is in an inconsistent or invalid power state.
    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.

    DMP file: https://www.dropbox.com/s/riyk3i9zsbzpazx/MEMORY.DMP?dl=0

    Hello Matthew,.

    Thanks for posting your query on the Microsoft Community.

    With the publication of the description, I understand that you are getting the BSOD with error: DRIVER_POWER_STATE_FAILURE on your Windows 7 machine. I will certainly help you get this fixed number.

    This issue/error when the material was suspended by Driver Verifier. I suggest you refer to the article below and check if that helps:

    Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE

    https://msdn.Microsoft.com/en-us/library/ff559329%28V=vs.85%29.aspx?f=255&MSPPError=-2147217396

    In order to diagnose the problem, I also suggest you to run the pilot test and to check after you have disabled.

    In addition, you can also run the following hotfix and check if this is useful:

    "stop error message 0x0000009F" in Windows 7 or in Windows Server 2008 R2 when the computer enters or leaves soft power off (S5) power state

    https://support.Microsoft.com/en-us/KB/2459268

    Hope this information is useful. Please come back to write to us if you need more help, we will be happy to help you.

  • Win 7 crash dump ntkrnlmp.exe

    My Sony Vaio hangs on 2 to 5 times a day. This is the dump file. I made a memory check and its all good. Any help would be appreciated

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

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

    Loading dump file [C:\Windows\Minidump\071910-28204-01.dmp]
    The mini kernel dump file: only registers and the trace of the stack are available

    Symbol search path is: SRV * your local folder for symbols * http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (4 procs) free x 64
    Product: WinNt, suite: TerminalServer personal TerminalServer
    By: 7600.16539.amd64fre.win7_gdr.100226 - 1909
    Computer name:
    Kernel base = 0xfffff800 '03402000 PsLoadedModuleList = 0xfffff800' 0363fe50
    The debugging session: 10:35:48.104 Mon 19 Jul 2010 (UTC + 12:00)
    System Uptime: 0 days 2:49:29.292
    Loading the kernel symbols
    ...............................................................
    ................................................................
    ....................................
    Loading user symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    * Bugcheck analysis *.
    *                                                                             *
    *******************************************************************************

    Use! analyze - v to obtain detailed debugging information.

    Bugcheck 7F, {8, 80050031, 6f8, fffff8000343ae58}

    Probably caused by: ntkrnlmp.exe (nt! KiDoubleFaultAbort + b2)

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

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

    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means an interruption occurred in kernel mode, and it's a trick of nature
    that the kernel is not allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first digit of the
    bugcheck params is the number of the trap (8 = double fault, etc.)
    Consult an Intel x 86 family manual to learn more about what these
    traps are. Here's a * part * of these codes:
    If kv shows a taskGate
    Use .tss on the part before the sign colon, then kv.
    Otherwise, if kv shows a trapframe
    use .trap on that value
    On the other
    . Trap on the appropriate frame will show where the trap was taken
    (on x 86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    Ko poster then the battery has been corrected.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050031
    Arg3: 00000000000006f8
    Arg4: fffff8000343ae58

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

    BUGCHECK_STR: 0x7f_8

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    Nom_processus: System

    CURRENT_IRQL: 2

    LAST_CONTROL_TRANSFER: from fffff80003471b69 to fffff80003472600

    STACK_TEXT:
    fffff880 '009eece8 fffff800' 03471b 69: 00000000' 0000007f 00000000'00000008 00000000'80050031 00000000' 000006f8: nt! KeBugCheckEx
    fffff880'009eecf0 fffff800'03470032: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiBugCheckDispatch + 0 x 69
    fffff880 '009eee30 fffff800' 0343ae58: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiDoubleFaultAbort + 0xb2
    fffff880 '02d15ce0 00000000' 00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! SeAccessCheckFromState + 0 x 58

    STACK_COMMAND: kb

    FOLLOWUP_IP:
    NT! KiDoubleFaultAbort + b2
    fffff800'03470032 90 nop

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: nt! KiDoubleFaultAbort + b2

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    Nom_image: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

    FAILURE_BUCKET_ID: X64_0x7f_8_nt! KiDoubleFaultAbort + b2

    BUCKET_ID: X64_0x7f_8_nt! KiDoubleFaultAbort + b2

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

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

    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means an interruption occurred in kernel mode, and it's a trick of nature
    that the kernel is not allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first digit of the
    bugcheck params is the number of the trap (8 = double fault, etc.)
    Consult an Intel x 86 family manual to learn more about what these
    traps are. Here's a * part * of these codes:
    If kv shows a taskGate
    Use .tss on the part before the sign colon, then kv.
    Otherwise, if kv shows a trapframe
    use .trap on that value
    On the other
    . Trap on the appropriate frame will show where the trap was taken
    (on x 86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    Ko poster then the battery has been corrected.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050031
    Arg3: 00000000000006f8
    Arg4: fffff8000343ae58

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

    BUGCHECK_STR: 0x7f_8

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    Nom_processus: System

    CURRENT_IRQL: 2

    LAST_CONTROL_TRANSFER: from fffff80003471b69 to fffff80003472600

    STACK_TEXT:
    fffff880 '009eece8 fffff800' 03471b 69: 00000000' 0000007f 00000000'00000008 00000000'80050031 00000000' 000006f8: nt! KeBugCheckEx
    fffff880'009eecf0 fffff800'03470032: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiBugCheckDispatch + 0 x 69
    fffff880 '009eee30 fffff800' 0343ae58: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiDoubleFaultAbort + 0xb2
    fffff880 '02d15ce0 00000000' 00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! SeAccessCheckFromState + 0 x 58

    STACK_COMMAND: kb

    FOLLOWUP_IP:
    NT! KiDoubleFaultAbort + b2
    fffff800'03470032 90 nop

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: nt! KiDoubleFaultAbort + b2

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    Nom_image: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

    FAILURE_BUCKET_ID: X64_0x7f_8_nt! KiDoubleFaultAbort + b2

    BUCKET_ID: X64_0x7f_8_nt! KiDoubleFaultAbort + b2

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

    1: kd > lmvm nt
    start end module name
    fffff800 ' 03402000 fffff800' 039de000 nt (PDB symbols) your local folder for symbols\ntkrnlmp.pdb\7E9A3CAB626845DE8E10816E3080A3B72\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Mapped memory image file: your local folder for symbols\ntoskrnl.exe\4B88CFEB5dc000\ntoskrnl.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp: Sat Feb 27 20:55:23 2010 (4B88CFEB)
    CheckSum: 00545094
    ImageSize: 005DC000
    File version: 6.1.7600.16539
    Product version: 6.1.7600.16539
    Flags of the file: 0 (mask 3F)
    Folder OS: 40004 NT Win32
    File type: App 1.0
    File date: 00000000.00000000
    Translations: 0409.04b0
    CompanyName: Microsoft Corporation
    ProductName: Microsoft® Windows® Operating System
    InternalName: ntkrnlmp.exe
    OriginalFilename: ntkrnlmp.exe
    ProductVersion: 6.1.7600.16539
    FileVersion: 6.1.7600.16539 (win7_gdr.100226 - 1909)
    FileDescription: NT kernel & system
    LegalCopyright: © Microsoft Corporation. All rights reserved.

    UNEXPECTED_KERNEL_MODE_TRAP (BugCheck 7F) stop error is probably related to ZoneAlarm as in the following thread:

    http://social.answers.Microsoft.com/forums/en-us/w7repair/thread/e94de527-183F-4227-9749-072ba0e7769f

    You can try to disable NetBIOS over TCP/IP or uninstall ZoneAlarm and see if the BSOD solve.

    As an alternative to turning off NetBIOS over TCP/IP or uninstall ZoneAlarm, you could try the following fix:

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

    There is a link at the top of the article to request the hotfix.

  • BSOD of ntoskrnl.exe and other issues

    It is a new construction, new CPU/motherboard, etc, have a new video card. Three hard drives are in my system (1 SSD and HDD 2). I don't really know where to start to look at what may be the issue. I thought it was the video card, so I replaced it, but I still get similar questions.

    The BSOD is sporadic and the question doesn't seem to be the same thing every time, but ntoskrnl.exe has developed a couple of times. What are the possible problems that I might have?
    Here's what WhoCrashed said on the more recent accidents:
    Friday, February 8, 2013 4:59:24 AM GMT crashed your computer
    crash dump file: C:\Windows\Minidump\020713-8751-01.dmp
    This was probably caused by the following module: atikmdag.sys (atikmdag + 0x33F79)
    Bugcheck code: 0xA (0xFFFFF88042F698C0, 0xFFFFF80002AD574F, 0x2, 0 x 1)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\atikmdag.sys
    product: ATI Radeon Family
    company: Advanced Micro Devices, Inc..
    Description: ATI Radeon driver in Kernel Mode
    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.
    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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
    Google search: Advanced Micro Devices, Inc. IRQL_NOT_LESS_OR_EQUAL

    Friday, February 8, 2013 4:59:24 AM GMT crashed your computer
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
    Bugcheck code: 0xA (0xFFFFF88042F698C0, 0xFFFFF80002AD574F, 0x2, 0 x 1)
    Error: IRQL_NOT_LESS_OR_EQUAL
    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, February 7, 2013 21:41:43 this computer crashed
    crash dump file: C:\Windows\Minidump\020713-8564-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt + 0x7EFC0)
    Verification of error code: 0 x 50 (0 x 8, 0xFFFFFFFFFFFFFFFF, 0xFFFFFFFFFFFFFFFF, 0x0)
    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, February 5, 2013 11:53:09 PM GMT crashed your computer
    crash dump file: C:\Windows\Minidump\020513-9063-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt + 0x7EFC0)


    Verification of error code: 0 x 50 (0 x 8, 0xFFFFF80006BC3FF6, 0xFFFFF80006BC3FF6, 0 x 2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    Description: NT Kernel System &
    Bug control description: This indicates that invalid system memory was referenced.
    This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

    Wednesday, January 30, 2013 3:26:32 AM GMT crashed your computer
    crash dump file: C:\Windows\Minidump\012913-9110-01.dmp
    This was probably caused by the following module: dxgkrnl.sys (dxgkrnl + 0 x 2333)
    Bugcheck code: 0xD1 (0xD, 0x301A460, 0x6FD35E33, 0x1)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\dxgkrnl.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    Description: DirectX Graphics Kernel
    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 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, January 28, 2013 10:35:18 PM GMT crashed your computer
    crash dump file: C:\Windows\Minidump\012813-8314-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt + 0x7EFC0)
    Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80002AE3305, 0xFFFFF8800DEEA090, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    Description: NT Kernel System &
    Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
    This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

    Saturday, January 26, 2013 4:26:54 AM GMT crashed your computer
    crash dump file: C:\Windows\Minidump\012513-9500-01.dmp
    This was probably caused by the following module: hal.dll (hal + 0 x 5472)
    Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
    Error: "KMODE_EXCEPTION_NOT_HANDLED"
    file path: C:\Windows\system32\hal.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    Description: Hardware Abstraction Layer DLL
    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 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.

    Friday, January 25, 2013 05:35:47 GMT crashed your computer
    crash dump file: C:\Windows\Minidump\012413-11622-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt + 0x705C0)
    Bugcheck code: 0x3B (0xFFFFF80002A91846, 0xFFFFF8800CCB9600, 0xC0000096, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    Description: NT Kernel System &
    Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
    This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

    Wednesday, January 23, 2013 05:06:04 GMT crashed your computer
    crash dump file: C:\Windows\Minidump\012213-9328-01.dmp
    This was probably caused by the following module: pci.sys (pci + 0x25F1)
    Bugcheck code: 0xA (0 x 4722, 0xFFFFF80002ACEF85, 0 x 2, 0 x 1)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\pci.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    Description: NT Plug-and - Play PCI enumerator
    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 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.

    Dan you have 5 different causes there. May be an indication of Malware.
    To eliminate this possible cause, please download the free version of Malwarebytes.

    Update immediately.
    Do a full scan of the system
    Let us know the results at the end.

    http://www.Malwarebytes.org/products
  • Ntkrnlmp.exe does not load on Compaq Presario SR1303WM

    Hello, all, someone please advise. I have a Compaq Presario, ~ 40 GB Hd, 256 MB of ram, Windows XP Home SP2. The user tells me it has fried, couple of blocking issues and freezes here and there, so I take it home to try reinstalling the operating system to factory.

    I save all the data for a value of savings and try a system restore just to see what is happening, so I chose to come back to a point in March. After the restore, I get a message "could not start bcause the file next is missing or corrupt: Windows\System32\Config\System" and information on the repair with the original installation CD. So next I go to the recovery console to start the relocation and get the message "Cannot load ntkrnlmp.exe" with an error code 7.

    I look online and see on resetting the Bios default and shooting of ACPI on the computer, can someone please advise on the place to go on this particular machine? I have also reinstalled the memory and upgraded to 512, still the same messages.

    I ordered the hp system recovery disks but the machine will not even read the first disk. It CAN read a Windows 98 boot disk, I can access the a: prompt and switch for fair c: and d:, readers will not read this disc. I tried another disc of restoration for a Compaq machine, but it was the wrong - he read and gave me a message "the system restore disks do not support this Compq PC model."

    All advice is appreciated. Thank you.

    Well, it sounds as if the recovery partition is no longer usable. Try to start at the C: prompt and format the drive. Type format C:, and then press ENTER. Allow to format and then try the disks.

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

    Message edited by dmhoo29 on 07/15/2009 02:12

  • 2012 R2 server hangs randomly - Dump shows "probably caused by: ntkrnlmp.exe.

    Try to find what has caused the problem. Please check below for debugging details:

    HP (ProLiant DL380p Gen8) with Windows Server 2012 R2

    *******************************************************************************
    *                                                                             *
    * Bugcheck analysis *.
    *                                                                             *
    *******************************************************************************

    Use! analyze - v to obtain detailed debugging information.

    Error checking 133, {1, 1e00, 0, 0}

    Probably caused by: ntkrnlmp.exe (nt! FNODOBFM: 'chain' + adbe)

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

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

    DPC_WATCHDOG_VIOLATION (133)
    The CPD watchdog detected an extended operation to an IRQL of DISPATCH_LEVEL level
    or higher.
    Arguments:
    Arg1: 0000000000000001, the system has cumulatively spent a long period of time to
    DISPATCH_LEVEL or above. The offending component may generally be
    identified with a stack trace.
    Arg2: 0000000000001e00, the monitoring period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000

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

    SYSTEM_SKU: 665552-B21

    BIOS_DATE: 02/08/2014

    BUGCHECK_P1: 1

    BUGCHECK_P2: 1e00

    BUGCHECK_P3: 0

    BUGCHECK_P4: 0

    DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

    CPU_COUNT: 10

    CPU_MHZ: a21

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 3rd

    CPU_STEPPING: 4

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT_SERVER

    BUGCHECK_STR: 0 X 133

    Nom_processus: EndpointServic

    CURRENT_IRQL: d

    ANALYSIS_VERSION: 10.0.10240.9 amd64fre

    LAST_CONTROL_TRANSFER: from fffff8019a1e0f7e to fffff8019a1c5ca0

    STACK_TEXT:
    ffffd001 '9dd31c88 fffff801' 9a1e0f7e: 00000000'00000133 00000000'00000001 00000000' 00001e00 00000000' 00000000: nt! KeBugCheckEx
    ffffd001 '9dd31c90 fffff801' 9a0b1871: ffffd001 '9efc0c80 00000000' 15bf41c1 ffffe001' d6c621a0 00000001' 00000000: nt! : FNODOBFM: 'string' + 0xadbe
    ffffd001 '9dd31d20 fffff801' 9a00d7b5: 00000000 00000001' fffff801 '9a3d0000 00000000 00000001' ffffe001' ec99e580: nt! KeClockInterruptNotify + 0 x 91
    ffffd001 '9dd31f40 fffff801' 9a14c143: ffff9ee3'c1e337dd fffff801 '9a 174057 00000000 00000001' ffffe001' ec99e580: hal! HalpTimerClockIpiRoutine + 0x15
    ffffd001 '9dd31f70 fffff801' 9a1c712a: ffffe001'd6a03e00 fffff801 '9a3d0000 ffffe001' e41be080 00000000 00000001': nt! KiCallInterruptServiceRoutine + 0xa3
    ffffd001 '9dd31fb0 fffff801' 9a1c750f: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiInterruptSubDispatchNoLockNoEtw + 0xea
    ffffd001 'a25946b0 00000000' 00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiInterruptDispatchLBControl + 0x11f

    STACK_COMMAND: kb

    FOLLOWUP_IP:
    NT! : FNODOBFM: 'chain' + adbe
    fffff801'9a1e0f7e cc int 3

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt! : FNODOBFM: 'chain' + adbe

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    Nom_image: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 550f41a6

    IMAGE_VERSION: 6.3.9600.17736

    BUCKET_ID_FUNC_OFFSET: adbe

    FAILURE_BUCKET_ID: 0x133_ISR_nt! _ ?? _::FNODOBFM:_string_

    BUCKET_ID: 0x133_ISR_nt! _ ?? _::FNODOBFM:_string_

    PRIMARY_PROBLEM_CLASS: 0x133_ISR_nt! _ ?? _::FNODOBFM:_string_

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x133_isr_nt! _ ?? _::fnodobfm:_string_

    FAILURE_ID_HASH: {89366ad1-5557-ac2b-d015-8f6ec2fdbf31}

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

    This issue is beyond the scope of this site (for consumers) and to be sure, you get the best (and fastest) reply, we have to ask either on Technet (for IT Pro) or MSDN (for developers)
    *
    We need the log files themselves (called a DMP files) because they contain the only record of the sequence of events that led to the accident, what drivers have been loaded, and what has been loaded.
    Please follow our instructions to find and download the files, we need to help you fix your computer. They can be found at here
    If you have any questions regarding the procedure, please ask
  • I come from components to build a new computer. Try to use the Windows XP Pro computer old version but after BIOS and XP installation I get the error "file not found \i386\ntkrnlmp.exe. The error code is 7. "What should I do?

    New components is a new computer.
    Inserted the XP Pro CD in the drive but get the error "file not found \i386\ntkrnlmp.exe. The error code is 7. »
    Rebooted comp 5 times with the same problem after BIOS.

    Hi Milkshake83,

    Thanks for posting. Proceed as follows for this error.

    Method 1: Restore the default settings of the BIOS WARNING: this procedure may involve changing the semiconductor (CMOS) settings of the computer's complementary metal oxide and by changing the BIOS of the computer. Incorrect changes to the BIOS of your computer can result in serious problems. Change the CMOS settings of the computer at your own risk.

    To resolve this issue, restore the BIOS of the computer to its default settings. For more information about the correct settings of the BIOS of the computer and how to check and change these settings, see the computer documentation or contact the manufacturer of the computer.

    In addition, to confirm that the computer's BIOS is current, contact the computer manufacturer to inquire about the last update of the BIOS available for the computer.

    Method 2: Remove the faulty RAM to resolve this issue, remove the memory modules installed in the computer.

    NOTE: you must leave enough RAM for the computer to start and run Windows.

    For more information on the amount of RAM that is required to run Windows, click on the number below to view the article in the Microsoft Knowledge Base:

    304297 configuration (http://support.microsoft.com/kb/304297/) System requirements for Microsoft Windows 2000 operating systems

    If the error message described in the "Symptoms" section of this article appears again after removing the memory module, remove a different memory module. This procedure may ask you to restart your computer several times to identify the specific memory module that is not working properly.

    For more information about how to add and remove RAM to the computer, contact the manufacturer of your computer or see the documentation that came with your computer.

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

    I hope this helps!
    Shawn - Support Engineer - MCP, MCDST
    Microsoft Answers Support Engineer
    Visit our Microsoft answers feedback Forum and let us know what you think

  • BSOD due ntkrnlpa.exe + 98339

    Hello, im of the bsod and find nothing anywhere to fix it.

    makes 2 standard tests with verifier.exe and read the dumps with BlueScreenView, which tells me that the bsod is caused by the ntkrnlpa.exe + 98339.
    any help is appreciated!

    Hello

    Ntkrnlpa.exe is a component of Windows which means than anything else he has led astray.

    Pick up the pieces after a computer crash
    http://Windows.Microsoft.com/en-us/Windows-Vista/picking-up-the-pieces-after-a-computer-crash

    Check this thread for more information using BlueScreenView, MyEventViewer and other methods
    to troubleshoot the BlueScreens - top 3 responses (+ 1 other).

    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

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

    Also this, so you can see the probable bluescreens.

    Windows Vista restarts automatically if your computer encounters an error that requires him to plant.
    (also Windows 7)
    http://www.winvistatips.com/disable-automatic-restart-T84.html

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

    Check out these utilities to see if information may be collected:

    It is an excellent tool for displaying the blue screen error information

    -Free - BlueScreenView scans all your minidump files created during 'blue screen of death '.
    hangs and displays information about all accidents of a table.
    http://www.NirSoft.NET/utils/blue_screen_view.html

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

    MyEventViewer can be verified at the time of the blue screen (BSOD) for a second or less
    the time of the BSOD for more information on the possible cause - see TIP.

    MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
    TIP - Options - Advanced filter allows you to see a period of time instead of the whole of the record-
    Set it for a bit before and after the time of the BSOD.
    http://www.NirSoft.NET/utils/my_event_viewer.html

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

    AppCrashView - free - a small utility for Windows Vista and Windows 7 which shows details
    application of all accidents occurred in your system. The information breaks down is extracted from
    the wer files created by the Windows Error Reporting (WER) of the operating system component
    whenever an accident occurred. AppCrashView also allows you to easily record the list of accidents
    text/html/csv/xml file.
    http://www.NirSoft.NET/utils/app_crash_view.html

    I hope this helps.

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

  • Windows Vista SP2, random BSOD with error checking code 0 x 19

    Hi all

    I have seemingly random crashes on my old laptop 3 years recently - BSOD with error checking code 0 x 0000019 (0x00000020, 0xe92f4780, 0xe92f48d0, 0x0a2a0440), and BlueScreenView says that accidents are caused by ntkrnlpa.exe and Ntfs.sys. I have absolutely no idea why it happened--unusual does update, none of the material changes & software installations. The system hangs especially after maybe one or two days after starting with some sleep & wake ups inbetween and the only accidents while there are prominent running shows - namely, all the accidents that happened while I was running Firefox. Seconds before the BSoD (shell & all) system simply freezes and does not respond to ctrl + alt + delete, but is still running (as indicated by the fact that once, I forced a power off and after that restart the event log indicates the previous stop at was not planned), then watch the usual BSoD screen.

    After doing some googling, I began to suspect that this should be a memory or a hard drive problem, or maybe an overheating causing the two since he not there no significant change of software on my computer recently again issues just appeared without reason. So I cleaned my laptop fan and the heatsink and ensured that the hot air can leave the chassis without being blocked, did some checking of memory with memory auditing Windows - no problems in 5 innings and ran chkdsk on my system partition with all available options - perfectly normal, but the chkdsk has acted quite strangely that check all took about 30 seconds and no normal as the ID information of partition, size etc. that should be there never appeared; is this a normal behavior? or something is wrong with my chkdsk?

    I'm still (lol) impatiently waiting for the next crash, not sure whether the problem is still there or not. Meanwhile could you please help me understand what is the problem with my system?

    It seems that the disc is the most likely cause. If it is intermittent, it may be difficult to diagnose.

    The manufacturer of the laptop provides any diagnosis?  Several manufacturers have a key at startup to access the diagnostics.

    CHKDSK should last several minutes. There is information about the different ways to run chkdsk here:

    http://www.Vistax64.com/tutorials/67612-check-disk-Chkdsk.html

    You can try this disc test program:

    http://www.Seagate.com/www/en-us/support/downloads/SeaTools/

    If the version of WIndows does not find anything. Try to use the version BACK from a CD.

  • Intermittent BSOD with 0X000000D1

    Hello

    I have a Lenovo X 250 meeting BSOD with 0X000000D1 driver_irql_not_less_or_equal.

    Igdkmd64.sys addresses FFFFF880051AE27B, FFFFF880050EF000, Datestamp 546C13B9...

    Anyone encounter this before?

    Your support "COMPUTING" is wrong on several levels.  First of all, you have a driver of November 2014 and there are at least 3 more recent.  Secondly even though he was the most recent driver that does not mean it is not corrupt.

    Still related to the video driver

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

    Loading dump file [C:\Users\zigza\Desktop\minidump\102115-14679-01.dmp]
    The mini kernel dump file: only registers and the trace of the stack are available

    Symbol of validation of the path summary *.
    Location of response time (ms)
    Deferred SRV * E:\symbols* http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV * E:\symbols* http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) free x 64
    Product: WinNt, suite: TerminalServer SingleUserTS
    By: 7601.23223.amd64fre.win7sp1_ldr.150928 - 0600
    Computer name:
    Kernel base = 0xfffff800 '03a 67000 PsLoadedModuleList = 0xfffff800' 03ca 9730
    The debugging session: Wed 21 Oct 2015 06:57:27.681 (UTC - 04:00)
    System Uptime: 0 days 9:58:54.618
    Loading the kernel symbols
    ...............................................................
    ................................................................
    ..........................................................
    Loading user symbols
    Loading unloaded module list
    ...........
    *******************************************************************************
    *                                                                             *
    * Bugcheck analysis *.
    *                                                                             *
    *******************************************************************************

    Use! analyze - v to obtain detailed debugging information.

    Bugcheck 3B {c0000005, fffff8800513927b, fffff8802080dc20, 0}

    Probably caused by: igdkmd64.sys (igdkmd64 + bf27b)

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

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

    System_service_exception (3B)
    An exception occurred during the execution of a system service routine.
    Arguments:
    Arg1: 00000000c 0000005, Exception that caused the error checking code
    Arg2: fffff8800513927b, the address of the instruction that caused the error checking
    Arg3: fffff8802080dc20, address of the context record to the exception that caused the error checking
    Arg4: 0000000000000000, zero.

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

    SYSTEM_SKU: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X 250

    SYSTEM_VERSION: ThinkPad X 250

    BIOS_DATE: 06/04/2015

    BASEBOARD_PRODUCT: 20CLCTO1WW

    BASEBOARD_VERSION: 0B 98417 WIN

    BUGCHECK_P1: c0000005

    BUGCHECK_P2: fffff8800513927b

    BUGCHECK_P3: fffff8802080dc20

    BUGCHECK_P4: 0

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

    FAULTING_IP:
    Igdkmd64 + bf27b
    fffff880'0513927 b 488b1b mov rbx, qword ptr [rbx]

    CONTEXT: fffff8802080dc20-(.cxr 0xfffff8802080dc20)
    Rax = 0000000006ea28f0 rbx = ffff0000004c004c rcx = 00000001062f8000
    RDX = fffffa8006ea28d0 rsi = 0000000000000060 rdi = 0000000105b 00000
    RIP = fffff8800513927b rsp = fffff8802080e600 rbp = fffffa8006ea28d0
    R8 = 0000000105b 00000 r9 = 00000000007f8000 r10 = fffff80003c56820
    R11 = fffffa800e09c6d0 r12 = fffffa800a557000 r13 = 0000000000000002
    R14 = 00000000007f8000 r15 = fffffa800a557000
    iopl = 0 nv up ei ng nz na po nc
    CS = 0010 ss = 0018 ds = 002 b're = 002 b fs = 0053 gs = 002 b efl = 00010286
    Igdkmd64 + 0xbf27b:
    fffff880 ' 0513927b 488b1b mov rbx, qword ptr [rbx] b ds:002: ffff0000 ' 004c004c =?
    Reset the default scope

    CPU_COUNT: 4

    CPU_MHZ: 892

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 3D

    CPU_STEPPING: 4

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    BUGCHECK_STR: 0X3B

    NOM_PROCESSUS: EXCEL. EXE

    CURRENT_IRQL: 2

    ANALYSIS_VERSION: 10.0.10563.566 amd64fre

    LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8800513927b

    STACK_TEXT:
    fffff880 '2080e600 00000000' 00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: igdkmd64 + 0xbf27b

    FOLLOWUP_IP:
    Igdkmd64 + bf27b
    fffff880'0513927 b 488b1b mov rbx, qword ptr [rbx]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: igdkmd64 + bf27b

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: igdkmd64

    Nom_image: igdkmd64.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 546c13b9

    STACK_COMMAND: .cxr 0xfffff8802080dc20; Ko

    FAILURE_BUCKET_ID: X64_0x3B_igdkmd64 + bf27b

    BUCKET_ID: X64_0x3B_igdkmd64 + bf27b

    PRIMARY_PROBLEM_CLASS: X64_0x3B_igdkmd64 + bf27b

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:x64_0x3b_igdkmd64 + bf27b

    FAILURE_ID_HASH: {a103711e-7d13-3c9e-b714-f34fb1cf841a}

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

    0: kd > lmvm igdkmd64
    Browse the full list of module
    start end module name
    fffff880'0507 has 000 fffff880'05521000 T igdkmd64 (no symbol)
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Browse all global symbols data functions
    Timestamp: Kills Nov 18 22:51:21 2014 (546C13B9)
    CheckSum: 0049668E
    ImageSize: 004A 7000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

  • BSOD with WIN7_DRIVER_FAULT and 0x1E

    Original title: what is causing the BSOD.

    I'm trying to understand why my computer keeps a BSOD.  Here's the minidump.

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    BUGCHECK_STR: 0X1E

    Nom_processus: System

    CURRENT_IRQL: 0

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

    DPC_STACK_BASE: FFFFF8800344DFB0

    EXCEPTION_RECORD: fffff88003446928-(.exr 0xfffff88003446928)
    ExceptionAddress: fffff800032d5374 (nt! PoIdle + 0 x 0000000000000194)
    ExceptionCode: c0000005 (access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter [0]: 0000000000000000
    Parameter [1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff

    TRAP_FRAME: fffff880034469d0-(.trap 0xfffff880034469d0)
    NOTE: The frame trap does contain not all registers.
    Some registry values can be set to zero or incorrect.
    Rax = 0000000000004092 rbx = 0000000000000000 rcx = 0000000000000000
    RDX = fffdfa80108527c8 rsi = 0000000000000000 rdi = 0000000000000000
    RIP = fffff800032d5374 rsp = fffff88003446b60 rbp = 0000000000000000
    R8 = 000000000000212e r9 = 00000004def18e30 r10 = 000000000000cefe
    R11 = 00000000002f5f00 r12 = 0000000000000000 r13 = 0000000000000000
    R14 = 0000000000000000 r15 = 0000000000000000
    iopl = 0 nv di pl nc nz ac PE
    NT! PoIdle + 0 x 194:
    fffff800'd cmp rax, qword ptr [rdx] ds:fffdfa80' 108527 032 5374 483 b 02 c 8 =?
    Reset the default scope

    LAST_CONTROL_TRANSFER: from fffff800032c45be to fffff800032ccb90

    STACK_TEXT:
    "fffff880 '03445-08 fffff800' 032c45be: fffffa80 '1027d1a0 fffff880' 01a4c0ff fffff880 ' 03446180 fffff800 ' 032f7a90: nt! KeBugCheck
    fffff880 '03445-10 fffff800' 032f775d: fffff800 '034db0c8 fffff800' 03419a 80 fffff800 ' 03257000 fffff880' 03446928: nt! KiKernelCalloutExceptionHandler + 0xe
    "fffff880 '03445-40 fffff800' 032f6535: fffff800 ' 0341 c 038 fffff880 ' 03445ab8 fffff880 ' 03446928 fffff800' 03257000: nt! RtlpExecuteHandlerForException + 0xd
    "fffff880'03445 has 70 fffff800'033074 c 1: fffff880 ' 03446928 fffff880' 03446180 fffff880 ' 00000000 fffffa80 ' 118c8b50: nt! RtlDispatchException + 0 x 415
    "" fffff880 ' 03446150 fffff800' 032cc242: fffff880 ' 03446928 fffdfa80 ' a 10852 70 fffff880 ' 034469 d 0 fffff880 ' 009 b 3180: nt! KiDispatchException + 0 x 135
    fffff880 '034467f0 fffff800' 032cab4a: ffffc973 00000000'00000069 00000000'00000000 ' 00001f80'00000200 c62da47d: nt! KiExceptionDispatch + 0xc2
    "fffff880 '034469 d 0 fffff800' 032 5374 d: 00000000 ' 00328 c 23 fffdfa80" 10852 has 70 00000000'00000000 00000000'00000000: nt! KiGeneralProtectionFault + 0x10a
    fffff880 '03446b 60 fffff800' 032c489c: fffff880'009 b 3180 fffff880 ' 00000001 00000000 00000001' fffff800' 00000000: nt! PoIdle + 0 x 194
    fffff880'03446 c 40 00000000 00000000': fffff880 ' 03447000 fffff880' 03441000 fffff880'03446 c 00 00000000 00000000': nt! KiIdleLoop + 0x2c

    STACK_COMMAND: kb

    FOLLOWUP_IP:
    NT! KiKernelCalloutExceptionHandler + e
    fffff800'032c45be 90 nop

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt! KiKernelCalloutExceptionHandler + e

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    Nom_image: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 531590fb

    IMAGE_VERSION: 6.1.7601.18409

    FAILURE_BUCKET_ID: X64_0x1E_nt! KiKernelCalloutExceptionHandler + e

    BUCKET_ID: X64_0x1E_nt! KiKernelCalloutExceptionHandler + e

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:x64_0x1e_nt! kikernelcalloutexceptionhandler + e

    FAILURE_ID_HASH: {31b31670-23d4-78dd-b3a6-d5566ed846e6}

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

    These accidents were related to the corruption of memory (probably caused by a driver).

    Please run these tests to check your memory and find which driver is causing the problem.


    If you're overclocking (pushing components beyond their design) return you to default at least until the crash is resolved. If you don't know what it is that you're probably not overclocking.

    Since then, it is more likely to be a pilot run everything first.
    1-Driver Verifier (for full instructions, see our wiki here)

    If the auditor does not have the issue we move to it.

    2-Memtest. (You can learn more about running memtest here)


    If you cannot start after you have enabled the auditor reboot in safe mode
    In Vista & victory (F8)

    Co-written by JMH3143

    .

Maybe you are looking for

  • How to move photos flickr in iPhoto?

    Apple TV is more integrated Flickr albums in its screen saver options. In recent years, I have created a Flickr album, mainly using Instagram. I agree on taking these pictures live from the IG, on Flickr. Now, I have all the photos stored online on F

  • custom conditions

    I have a power step measure 4.2 TS using LV adapter.  If the test fails, the next step is a popup indicating the possible cause operator (check power supply 1 lights).  No problem that establishment of preconditions.  Now how do you get the sequence

  • I'm looking for the update driver free from microsoft which was released a year ago and I don't have to pay to buy or use

    It is free to download from the website of microsoft on a year or two ago that would update all drivers and you don't have to buy this product. Can someone help me, please?

  • Downgrade from windows 10-7 and no internet access

    Hey,. I've recently demoted Windows 10 come back to my original windows 7 because of some of my programs work does not correctly. But now my Ethernet and wireless is not connecting. I tried to turn all my firewall off the coast and the protectors of

  • DVD writer cannot detect a cd/dvd

    Hello... As the title says windows cannot detect any cd/dvd but it appears in startup and if I want I can change my os on that drive, but cannot show cd/DVD in my computer... what to do 1 change of register2. I tried automatic microsoft dvd troublesh