BSOD ntoskrnl.exe, ntkrnlmp.exe

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 7 Home Premium 64 bit OEM
       #1

    BSOD ntoskrnl.exe, ntkrnlmp.exe


    Since Yesterday i get alot of crashes.

    My system:

    CPU: Sandybridge i5 2500K
    Ramsj:Corsair Vengeance 8GB DDR3-1333(2x 4GB)
    Mobo: MSI Z68A-GD65 (G3) (MS-7681)
    grapics card: HD Radeon 5850
    SSD: Crucial CT128M4SSD2 (Windows is on this drive installed)
    HHD: Western digital 1TB (Just my external Hard disk)
    Windows: Windows 7 Home Premium 64 bit OEM

    I had alot of crashes the first time i builded this pc and Windows was installed on the HDD, but then i bought the SSD and installed windows there.
    I tought beceause of the reading windows runs slow on the HDD so i tried to solve the problem bu replacing the HHD for a SSD.
    Well it runs Faster but after 3 weeks im getting the same BSoD and now i dont know what it is.

    The pc is now 3 months old.

    My windows is up to date also my drivers

    I am using the program WhoCrashed and getting these results:


    On Wed 4-4-2012 10:34:06 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\040412-10670-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
    Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x1, 0xFFFFF800032B5932)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Wed 4-4-2012 10:34:06 GMT 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: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x1, 0xFFFFF800032B5932)
    Error: IRQL_NOT_LESS_OR_EQUAL
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Tue 3-4-2012 23:37:10 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\040412-9734-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
    Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x1, 0xFFFFF800032CC932)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Tue 3-4-2012 15:39:14 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\040412-10545-01.dmp
    This was probably caused by the following module: fltmgr.sys (fltmgr+0x42EC)
    Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x1, 0xFFFFF800032AD932)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\fltmgr.sys
    product: Besturingssysteem Microsoft® Windows®
    company: Microsoft Corporation
    description: Microsoft Bestandssysteemfilterbeheer
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


    On Tue 3-4-2012 12:40:20 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\040312-9656-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
    Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x1, 0xFFFFF80003311932)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Thu 29-3-2012 19:53:52 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\032912-9656-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
    Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x1, 0xFFFFF800032B5932)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Sat 24-3-2012 17:26:12 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\032412-9906-01.dmp
    This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x8172)
    Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x1, 0xFFFFF800032FC932)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\dxgmms1.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics MMS
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


    On Sat 24-3-2012 15:58:48 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\032412-9984-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
    Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x1, 0xFFFFF800032C7932)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Wed 21-3-2012 11:32:39 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\032112-10608-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
    Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x1, 0xFFFFF80003309932)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Wed 14-3-2012 15:16:18 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\031412-9906-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
    Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x1, 0xFFFFF80002EFF932)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Thu 8-3-2012 23:09:42 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\030912-9500-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x1, 0xFFFFF80002F0A3A2)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    I have also followed your threat how to post a threat for BSoD and see the attatchemt files.

    I hope you guys can help me out, and my pc is in dutch, so i dont know if it is a problem.

    Already thankyou for helping me.

    Gr,

    Terence
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    I am a big fan of Nir Sofer's work, BUT blueScreenView more often than not, doesn't point out the correct causes. Similarly Who crashed is even worse.

    I prefer to use WinDbg (the Windows Debugging Tools) to read the memory dumps. It is the Gold standard for those of us that do this and often will give us the answer by itself. (we don't need the full jcgriff2 report each time).



    These were related to your McAfee

    McAfee is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST!

    http://download.mcafee.com/products/...tches/MCPR.exe

    Microsoft Security Essentials - Free Antivirus for Windows
      My Computer


  3. Posts : 7
    Windows 7 Home Premium 64 bit OEM
    Thread Starter
       #3

    oke yeah i tried to use the windbg system but was to complicated for me, unless you have a threat for dummies :P
    i can try to make a windbg file for you, ill try to remove MCafee and will use windows Defender as my main scanner and come back in a week
      My Computer


  4. Posts : 7
    Windows 7 Home Premium 64 bit OEM
    Thread Starter
       #4

    well its now a week later, and my crashes reduced alot, but now since i play WoW i get them again the last 2 days i crash in mid game.

    i have tried what you suggested with the WinDBG and tried analyzing 1 crash

    he gives this:


    Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {ffffffffffffffff, 2, 1, fffff800032bb812}

    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
    Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: ffffffffffffffff, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff800032bb812, address which referenced memory

    Debugging Details:
    ------------------

    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034bc100
    GetUlongFromAddress: unable to read from fffff800034bc1c0
    ffffffffffffffff

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!KxWaitForLockOwnerShip+12
    fffff800`032bb812 48890a mov qword ptr [rdx],rcx

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: svchost.exe

    TRAP_FRAME: fffff880090463a0 -- (.trap 0xfffff880090463a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff880090465e0
    rdx=ffffffffffffffff rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800032bb812 rsp=fffff88009046530 rbp=fffff880090465c0
    r8=0000000000000000 r9=0000000000000000 r10=fffffa8006bfe190
    r11=fffff800034bfac0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na pe nc
    nt!KxWaitForLockOwnerShip+0x12:
    fffff800`032bb812 48890a mov qword ptr [rdx],rcx ds:ffffffff`ffffffff=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff8000328a229 to fffff8000328ac80

    STACK_TEXT:
    fffff880`09046258 fffff800`0328a229 : 00000000`0000000a ffffffff`ffffffff 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`09046260 fffff800`03288ea0 : fffff800`03826460 fffff880`09046450 00000000`00000e38 fffffa80`0121c020 : nt!KiBugCheckDispatch+0x69
    fffff880`090463a0 fffff800`032bb812 : 00000000`00000000 fffff800`0329a12f 00000000`00000010 00000000`00000206 : nt!KiPageFault+0x260
    fffff880`09046530 fffff800`0329a5ad : fffffa80`0121c020 00000000`00000000 fffff880`090465c0 fffffa80`06d0c460 : nt!KxWaitForLockOwnerShip+0x12
    fffff880`09046560 fffff800`032bcdc7 : 00000000`00000000 fffff680`000715d0 00000000`00000000 00000001`00000001 : nt!MiInsertPageInFreeOrZeroedList+0x55d
    fffff880`09046670 fffff800`032bc017 : 00000000`00000000 fffff680`00071ff8 fffffa80`0ab3bb30 00000000`000000a9 : nt!MiDeletePteRun+0x4ed
    fffff880`09046820 fffff800`032774bf : fffffa80`00000000 00000000`0e832fff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
    fffff880`090469e0 fffff800`03289f13 : ffffffff`ffffffff 00000000`010ae200 00000000`010ae1c8 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
    fffff880`09046ae0 00000000`76e514fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`010ae138 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e514fa


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KxWaitForLockOwnerShip+12
    fffff800`032bb812 48890a mov qword ptr [rdx],rcx

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: nt!KxWaitForLockOwnerShip+12

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4f558b55

    FAILURE_BUCKET_ID: X64_0xA_nt!KxWaitForLockOwnerShip+12

    BUCKET_ID: X64_0xA_nt!KxWaitForLockOwnerShip+12

    Followup: MachineOwner
    ---------


    i really cant read what is wrong or what i should chance or update, i also made a new 2 new .zip files for your reading,

    if you say that the winDGB lets you see what the problem is i can maybe analyze the other crashes to.

    could you tell me what is wrong?
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #5

    Security Software (this is just to check it is installed and working properly; nothing needs to be done with this information at this time):
    Code:
    mbamgui.exe	c:\program files (x86)\malwarebytes' anti-malware\mbamgui.exe	3424	8	200	1380	16-4-2012 17:51	Niet beschikbaar	Niet beschikbaar	Niet beschikbaar
    mbamservice.exe	c:\program files (x86)\malwarebytes' anti-malware\mbamservice.exe	5668	8	80	80	16-4-2012 17:53	Niet beschikbaar	Niet beschikbaar	Niet beschikbaar
    msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	856	8	200	1380	16-4-2012 17:51	3.0.8402.0	12,48 kB (12.784 bytes)	27-4-2011 17:21
    nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	2628	8	200	1380	16-4-2012 17:51	3.0.8402.0	281,52 kB (288.272 bytes)	27-4-2011 17:21
    msseces.exe	c:\program files\microsoft security client\msseces.exe	2508	8	200	1380	16-4-2012 17:51	2.1.1116.0	1,37 MB (1.436.736 bytes)	15-6-2011 14:35
    system idle process	Niet beschikbaar	0	0	Niet beschikbaar	Niet beschikbaar	Niet beschikbaar	Niet beschikbaar	Niet beschikbaar	Niet beschikbaar

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [D:\Kingston\BSODDmpFiles\Terence091\Windows_NT6_BSOD_jcgriff2\041612-9937-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
    Machine Name:
    Kernel base = 0xfffff800`0320e000 PsLoadedModuleList = 0xfffff800`03452650
    Debug session time: Mon Apr 16 09:50:36.764 2012 (UTC - 6:00)
    System Uptime: 0 days 2:16:41.966
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {ffffffffffffffff, 2, 1, fffff800032bb812}
    
    Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: ffffffffffffffff, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff800032bb812, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034bc100
     ffffffffffffffff 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KxWaitForLockOwnerShip+12
    fffff800`032bb812 48890a          mov     qword ptr [rdx],rcx
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  svchost.exe
    
    TRAP_FRAME:  fffff880090463a0 -- (.trap 0xfffff880090463a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff880090465e0
    rdx=ffffffffffffffff rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800032bb812 rsp=fffff88009046530 rbp=fffff880090465c0
     r8=0000000000000000  r9=0000000000000000 r10=fffffa8006bfe190
    r11=fffff800034bfac0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    nt!KxWaitForLockOwnerShip+0x12:
    fffff800`032bb812 48890a          mov     qword ptr [rdx],rcx ds:0202:ffffffff`ffffffff=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8000328a229 to fffff8000328ac80
    
    STACK_TEXT:  
    fffff880`09046258 fffff800`0328a229 : 00000000`0000000a ffffffff`ffffffff 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`09046260 fffff800`03288ea0 : fffff800`03826460 fffff880`09046450 00000000`00000e38 fffffa80`0121c020 : nt!KiBugCheckDispatch+0x69
    fffff880`090463a0 fffff800`032bb812 : 00000000`00000000 fffff800`0329a12f 00000000`00000010 00000000`00000206 : nt!KiPageFault+0x260
    fffff880`09046530 fffff800`0329a5ad : fffffa80`0121c020 00000000`00000000 fffff880`090465c0 fffffa80`06d0c460 : nt!KxWaitForLockOwnerShip+0x12
    fffff880`09046560 fffff800`032bcdc7 : 00000000`00000000 fffff680`000715d0 00000000`00000000 00000001`00000001 : nt!MiInsertPageInFreeOrZeroedList+0x55d
    fffff880`09046670 fffff800`032bc017 : 00000000`00000000 fffff680`00071ff8 fffffa80`0ab3bb30 00000000`000000a9 : nt!MiDeletePteRun+0x4ed
    fffff880`09046820 fffff800`032774bf : fffffa80`00000000 00000000`0e832fff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
    fffff880`090469e0 fffff800`03289f13 : ffffffff`ffffffff 00000000`010ae200 00000000`010ae1c8 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
    fffff880`09046ae0 00000000`76e514fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`010ae138 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e514fa
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KxWaitForLockOwnerShip+12
    fffff800`032bb812 48890a          mov     qword ptr [rdx],rcx
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!KxWaitForLockOwnerShip+12
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!KxWaitForLockOwnerShip+12
    
    BUCKET_ID:  X64_0xA_nt!KxWaitForLockOwnerShip+12
    
    Followup: MachineOwner
    ---------
    These crashes appear to point to hardware problems since they are blaming system files. Could also be system file corruption, a bad BIOS version, or drivers. Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL

    Start by checking your Windows files.
    • If you are overclocking any hardware, please stop.

    • Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
      My Computer


  6. Posts : 7
    Windows 7 Home Premium 64 bit OEM
    Thread Starter
       #6

    i did the first scan and it says that there is nothing found (in dutch)



    but after the crashes i saw that windows had to be updated so i installed the latest versions



    so yesterday i played WoW without any problems and crashes (after the updates), i don't over-clock any hardware because i still feel that the system is unstable imo. (the crashes)
      My Computer


  7. Posts : 7
    Windows 7 Home Premium 64 bit OEM
    Thread Starter
       #7

    3 important updates
      My Computer


  8. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #8

    Alright, let us know if you need further troubleshooting. Hopefully the updates resolved the issue. :)
      My Computer


  9. Posts : 7
    Windows 7 Home Premium 64 bit OEM
    Thread Starter
       #9

    but do you guys have any guide how to use the Windbg software?
    was it good that i posted what the WinDBG software scanned or did i do something wrong?
      My Computer


  10. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #10

    It's better to provide the full .dmp files for us to analyze as you did until you are able to understand the intricacies of the WinDbg reports. BSOD Analysis - Getting Started can help with analysis.

    User-friendly: Analyzing your first BSoD! may also be useful.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 10:05.
Find Us