none
UNEXPECTED_KERNAL_MODE_TRAP BSOD (ntoskrnl.exe) RRS feed

  • Question

  • So yeah, I was getting BSOD's with Windows 8 (Which only started in the last 2 months) so It thought it might just be a compatibility error but apparently not. I freshly installed windows 7, 2 days ago and it's still going for it. I can't even boot normally anymore it just instantly BSODS when I click any program. All of the Hardware is virtually brand new, the CPU, 2 sticks of RAM were both bought at the start of the year and the Mobo, GPU and the other 2 sticks of RAM + the HDD are all 3-4 months old

    DMP files (In Bluescreenviewer they all have one thing in common, ntoskrnl.exe

    http://ge.tt/8CkJXPq/v/5 = 8/28/2013 12:39AM
    http://ge.tt/8CkJXPq/v/6 = 8/28/2013 12:42AM
    http://ge.tt/8CkJXPq/v/3 = 8/29/2013 11:32PM
    http://ge.tt/8CkJXPq/v/2 = 8/29/2013 11:33PM
    http://ge.tt/8CkJXPq/v/1 = 8/29/2013 11:34PM
    http://ge.tt/8CkJXPq/v/0 = 8/29/2013 11:29PM
    http://ge.tt/8CkJXPq/v/4 = 8/30/2013 12:06AM
    http://ge.tt/5qKtUTq/v/0 = 8/30/2013 8:34AM
    http://ge.tt/5L9iVUq/v/3 = 8/30/2013 10:25AM
    http://ge.tt/5L9iVUq/v/2 = 8/30/2013 10:46AM
    http://ge.tt/5L9iVUq/v/1 = 8/30/2013 10:48AM
    http://ge.tt/5L9iVUq/v/0 = 8/30/2013 10:55AM

    Hardware:

    CPU: i5 3570k (Stock)
    GPU: Palit GTX 770
    Mobo: GA-Z77X-UD3H
    RAM: 16GB Corsair Vengeance (4x4gb Sticks)
    PSU: Corsair TX850M
    HDD: Seagate 2TB Barracuda

    Just some other backgroud info, The last lot of BSODS that I had that eventually made me give up with windows 8 corrupted my BIOS somehow and I only recently got that fixed. As of now everything is sitting outside of the Case because if I have to RMA something I don't want to have it take it all out again.

    I await your response

    AVAST was on there but then I unistalled the program because I've heard it causes BSDOS and like 10 minutes later it happened again

    The Whocrashed Log:

    Crash Dump Analysis
    --------------------------------------------------------------------------------
    
    Crash dump directory: C:\Windows\Minidump
    
    Crash dumps are enabled on your computer.
    
    On Fri 8/30/2013 12:54:22 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\083013-20217-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) 
    Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF800020085CD)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Fri 8/30/2013 12:47:48 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\083013-21184-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) 
    Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF80002C0B5CD)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Fri 8/30/2013 12:45:25 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\083013-24757-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) 
    Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF80002BB05CD)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Fri 8/30/2013 12:23:02 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\083013-22744-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) 
    Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF80002BA55CD)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Thu 8/29/2013 10:34:05 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\083013-36831-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8) 
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880091D7038, 0xFFFFF880091D6890, 0xFFFFF8800104B1C3)
    Error: NTFS_FILE_SYSTEM
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT File System Driver
    Bug check description: This indicates a problem occurred in the NTFS file system. 
    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 that cannot be identified at this time. 
    
    
    
    On Thu 8/29/2013 2:06:04 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\083013-20888-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8) 
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88007AFDD18, 0xFFFFF88007AFD570, 0xFFFFF880012F0BA4)
    Error: NTFS_FILE_SYSTEM
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT File System Driver
    Bug check description: This indicates a problem occurred in the NTFS file system. 
    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 that cannot be identified at this time. 
    
    
    
    On Thu 8/29/2013 2:06:04 PM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: aswsnx.sys (aswSnx+0x14940) 
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88007AFDD18, 0xFFFFF88007AFD570, 0xFFFFF880012F0BA4)
    Error: NTFS_FILE_SYSTEM
    Bug check description: This indicates a problem occurred in the NTFS file system. 
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsnx.sys . 
    Google query: aswsnx.sys NTFS_FILE_SYSTEM
    
    
    
    On Thu 8/29/2013 1:37:17 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082913-28111-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) 
    Bugcheck code: 0x50 (0xFFFFDA8023D56562, 0x0, 0xFFFFF80002ACFFC7, 0x7)
    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 check description: This indicates that invalid system memory has been referenced.
    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 that cannot be identified at this time. 
    
    
    
    On Thu 8/29/2013 1:33:38 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082913-28844-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) 
    Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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 that cannot be identified at this time. 
    
    
    
    On Thu 8/29/2013 1:32:18 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082913-38828-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) 
    Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF80002BAE5CD)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Thu 8/29/2013 1:30:52 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082913-40653-01.dmp
    This was probably caused by the following module: fltmgr.sys (fltmgr+0x1F40) 
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800106EF40, 0xFFFFF88006548A20, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\drivers\fltmgr.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Microsoft Filesystem Filter Manager
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
    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 that cannot be identified at this time. 
    
    
    
    On Tue 8/27/2013 2:40:18 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082813-53913-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) 
    Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF800029FB5CD)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Tue 8/27/2013 2:36:42 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082813-48235-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8) 
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88005D61C98, 0xFFFFF88005D614F0, 0xFFFFF8000288C506)
    Error: NTFS_FILE_SYSTEM
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT File System Driver
    Bug check description: This indicates a problem occurred in the NTFS file system. 
    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 that cannot be identified at this time. 
    
    
    
    
    --------------------------------------------------------------------------------
    Conclusion
    --------------------------------------------------------------------------------
    
    13 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: 
    
    aswsnx.sys 
    

    Friday, August 30, 2013 1:22 AM