Recently have been having random blue screen issues
Heres the crash dump analysis
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 1/21/2014 9:55:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-23368-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Tue 1/21/2014 9:55:28 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: wusb54gv4x64.sys (WUSB54Gv4x64+0x2D7CF)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\wusb54gv4x64.sys
product: Ralink 802.11 Wireless Adapters
company: Ralink Technology Inc.
description: Ralink 802.11 Wireless Adapter 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.
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: wusb54gv4x64.sys (Ralink 802.11 Wireless Adapter Driver, Ralink Technology Inc.).
Google query: Ralink Technology Inc. KMODE_EXCEPTION_NOT_HANDLED
On Tue 1/21/2014 9:30:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-18610-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Tue 1/21/2014 8:23:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-17893-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Tue 1/21/2014 4:22:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-15350-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Mon 1/20/2014 1:31:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012014-24679-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Mon 1/20/2014 12:30:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012014-24039-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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.
--------------------------------------------------------------------------------
heres the analysis by whocrashed
Anyone can give me suggestions of solving this problem? Any feedback would be extremely helpful thanks
Heres the crash dump analysis
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 1/21/2014 9:55:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-23368-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Tue 1/21/2014 9:55:28 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: wusb54gv4x64.sys (WUSB54Gv4x64+0x2D7CF)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\wusb54gv4x64.sys
product: Ralink 802.11 Wireless Adapters
company: Ralink Technology Inc.
description: Ralink 802.11 Wireless Adapter 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.
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: wusb54gv4x64.sys (Ralink 802.11 Wireless Adapter Driver, Ralink Technology Inc.).
Google query: Ralink Technology Inc. KMODE_EXCEPTION_NOT_HANDLED
On Tue 1/21/2014 9:30:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-18610-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Tue 1/21/2014 8:23:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-17893-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Tue 1/21/2014 4:22:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-15350-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Mon 1/20/2014 1:31:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012014-24679-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Mon 1/20/2014 12:30:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012014-24039-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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.
--------------------------------------------------------------------------------
heres the analysis by whocrashed
Anyone can give me suggestions of solving this problem? Any feedback would be extremely helpful thanks