New
#1
Clevo P151EM1 frequent BSOD
Hi, laptop is crashing fairly often, can happen just while web browsing, or playing a game etc. Can't seem to attribute it to heat or any particular operation. I've run memtest86 overnight with no errors found. Just wondering if anyone has any more ideas on how to go about diagnosing the issue. Have attached my "WhoCrashed' results which mention the lan card driver, but only in 1 instance. I have also tried a fresh install of Win7 but I'm still getting the same issue. It's a Clevo/Horizon P151EM1.
Edit: I believe at the moment I might have driver verifier running because I was attempting to track down the root cause.
Welcome to WhoCrashed (HOME EDITION) v 5.51
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
Home Edition Notice
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
System Information (local)
Computer name: LAPTOP-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: P151EMx, CLEVO
CPU: GenuineIntel Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17064312832 bytes total
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 17/12/2015 8:12:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121715-15568-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0xD1 (0x0, 0xB, 0x1, 0xFFFFFA800E09B004)
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 Sun 6/12/2015 6:55:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120615-10467-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF89, 0x1, 0xFFFFF80002AD1CB9, 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 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 Sun 29/11/2015 7:11:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112915-12121-01.dmp
This was probably caused by the following module: rtwlane.sys (rtwlane+0x35F4E)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF8800444EF4E)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\rtwlane.sys
product: Realtek PCIEWireless LAN PCI-E NIC
company: Realtek Semiconductor Corporation
description: Realtek PCIE NDIS Driverr
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: rtwlane.sys (Realtek PCIE NDIS Driverr, Realtek Semiconductor Corporation ).
Google query: Realtek Semiconductor Corporation UNEXPECTED_KERNEL_MODE_TRAP
On Sat 21/11/2015 5:58:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112115-11746-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF89, 0x1, 0xFFFFF80002A81CB9, 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 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 Fri 20/11/2015 10:33:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112015-33555-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x741D0)
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 2/11/2015 12:26:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110115-14913-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFA9, 0x1, 0xFFFFF80002A87CB9, 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 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 Sun 18/10/2015 11:37:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101815-18610-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x167128)
Bugcheck code: 0xFC (0xFFFFF88001768128, 0x8000000003D65963, 0xFFFFF88003BE1500, 0x0)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
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 Sun 18/10/2015 11:37:03 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x167128)
Bugcheck code: 0xFC (0xFFFFF88001768128, 0x8000000003D65963, 0xFFFFF88003BE1500, 0x0)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
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 Sun 18/10/2015 8:10:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101815-16536-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFF4C, 0x2, 0x0, 0xFFFFF80002A5C650)
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.
Conclusion
9 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:
rtwlane.sys (Realtek PCIE NDIS Driverr, Realtek Semiconductor Corporation )
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Quote