Brand new build of new PC. Receiving several BSOD's and I can't install any of the " Update for Windows 8 for x64-based systems " updates without having it fail and givin the reverting back to previous settings screen.
Quick overview: Been workin on this problem since I finished the install of all hardware about 4 days ago. Here is the Whocrashed analysis. Please help and let me know if there is anything else you need.
This PC is intended for high graphics gaming and even streaming in 1080p so i need it to run efficiently. This is only my 2nd build ever so i'm still a novice, I have installed windows 8 in ACHI .
System Information (local)
--------------------------------------------------------------------------------
computer name: MICHEAL
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 17135415296 total
VM: 2147352576, free: 1913389056
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 4/20/2013 11:02:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042013-5444-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0x50 (0xFFFFF803E1A93F18, 0x0, 0xFFFFF803E08CB882, 0x2)
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 Sat 4/20/2013 10:51:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042013-5101-01.dmp
This was probably caused by the following module: ndu.sys (0xFFFFF88008BC8DE6)
Bugcheck code: 0xD1 (0x25, 0x2, 0x0, 0xFFFFF88008BC8DE6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndu.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows Network Data Usage Monitoring Driver
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 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 Sat 4/20/2013 10:28:21 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042013-4992-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803358C2FB2, 0xFFFFF8800F616D40, 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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 4/20/2013 12:30:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041913-7472-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0xA (0xFFFFF87FE9B63584, 0xD, 0x0, 0xFFFFF801742BD336)
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 that cannot be identified at this time.
On Sat 4/20/2013 12:19:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041913-6598-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x15700)
Bugcheck code: 0x50 (0xFFFFF884009D15F0, 0x1, 0xFFFFF80024520169, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
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 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 Fri 4/19/2013 11:07:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041913-5226-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8024D8A43A7, 0xFFFFF880091668A0, 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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 4/19/2013 10:55:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041913-5709-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x40CF8)
Bugcheck code: 0x24 (0xB50019060B, 0xFFFFF8801188F858, 0xFFFFF8801188F090, 0xFFFFF802A88CFF72)
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 Fri 4/19/2013 9:17:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041913-4929-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802D64F8C43, 0xFFFFF8800D81EFD0, 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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 4/19/2013 9:14:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041913-5116-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8024A523173, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Fri 4/19/2013 5:38:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041913-5116-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0xA (0x68, 0x2, 0x0, 0xFFFFF8008C4EB4B6)
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 that cannot be identified at this time.
On Fri 4/19/2013 5:37:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041813-6193-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960001716C0)
Bugcheck code: 0x50 (0xFFFFF80200000022, 0x0, 0xFFFFF960001716C0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 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 Fri 4/19/2013 5:34:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041813-7987-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x40CF8)
Bugcheck code: 0x24 (0xB50019060B, 0xFFFFF8800CEA6B58, 0xFFFFF8800CEA6390, 0xFFFFF802992D62E2)
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 Fri 4/19/2013 3:12:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041813-6864-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801F3E479E5, 0x0, 0x100091)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Fri 4/19/2013 3:12:47 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngGradientFill+0x9A53)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801F3E479E5, 0x0, 0x100091)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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.
Quick overview: Been workin on this problem since I finished the install of all hardware about 4 days ago. Here is the Whocrashed analysis. Please help and let me know if there is anything else you need.
This PC is intended for high graphics gaming and even streaming in 1080p so i need it to run efficiently. This is only my 2nd build ever so i'm still a novice, I have installed windows 8 in ACHI .
System Information (local)
--------------------------------------------------------------------------------
computer name: MICHEAL
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 17135415296 total
VM: 2147352576, free: 1913389056
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 4/20/2013 11:02:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042013-5444-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0x50 (0xFFFFF803E1A93F18, 0x0, 0xFFFFF803E08CB882, 0x2)
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 Sat 4/20/2013 10:51:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042013-5101-01.dmp
This was probably caused by the following module: ndu.sys (0xFFFFF88008BC8DE6)
Bugcheck code: 0xD1 (0x25, 0x2, 0x0, 0xFFFFF88008BC8DE6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndu.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows Network Data Usage Monitoring Driver
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 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 Sat 4/20/2013 10:28:21 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042013-4992-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803358C2FB2, 0xFFFFF8800F616D40, 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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 4/20/2013 12:30:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041913-7472-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0xA (0xFFFFF87FE9B63584, 0xD, 0x0, 0xFFFFF801742BD336)
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 that cannot be identified at this time.
On Sat 4/20/2013 12:19:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041913-6598-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x15700)
Bugcheck code: 0x50 (0xFFFFF884009D15F0, 0x1, 0xFFFFF80024520169, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
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 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 Fri 4/19/2013 11:07:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041913-5226-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8024D8A43A7, 0xFFFFF880091668A0, 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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 4/19/2013 10:55:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041913-5709-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x40CF8)
Bugcheck code: 0x24 (0xB50019060B, 0xFFFFF8801188F858, 0xFFFFF8801188F090, 0xFFFFF802A88CFF72)
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 Fri 4/19/2013 9:17:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041913-4929-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802D64F8C43, 0xFFFFF8800D81EFD0, 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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 4/19/2013 9:14:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041913-5116-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8024A523173, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Fri 4/19/2013 5:38:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041913-5116-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0xA (0x68, 0x2, 0x0, 0xFFFFF8008C4EB4B6)
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 that cannot be identified at this time.
On Fri 4/19/2013 5:37:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041813-6193-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960001716C0)
Bugcheck code: 0x50 (0xFFFFF80200000022, 0x0, 0xFFFFF960001716C0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 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 Fri 4/19/2013 5:34:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041813-7987-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x40CF8)
Bugcheck code: 0x24 (0xB50019060B, 0xFFFFF8800CEA6B58, 0xFFFFF8800CEA6390, 0xFFFFF802992D62E2)
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 Fri 4/19/2013 3:12:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041813-6864-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801F3E479E5, 0x0, 0x100091)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Fri 4/19/2013 3:12:47 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngGradientFill+0x9A53)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801F3E479E5, 0x0, 0x100091)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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.
Facebook
Twitter
Instagram