Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Clevo P151EM1 frequent BSOD

17 Dec 2015   #1
ausmisc

Windows 7 Ultimate x64
 
 
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.


Quote:
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.






My System SpecsSystem Spec
.
17 Dec 2015   #2
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

Code:
Event[7951]:
  Log Name: System
  Source: BTHUSB
  Date: 2015-12-17T19:12:52.635
  Event ID: 17
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Laptop-PC
  Description: 
The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.
Reinstall the Bluetooth adapter driver with the latest driver version, or turn it OFF.

Code:
ffff800`00b9a838  00000004`00044018
fffff800`00b9a840  fffff800`00b9aa00
fffff800`00b9a848  fffff880`0575c40cUnable to load image igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
 igdkmd64+0xe540c
fffff800`00b9a850  fffff880`0575c40c igdkmd64+0xe540c
fffff800`00b9a858  00000004`00000000
fffff800`00b9a860  fffff800`00000000
fffff800`00b9a868  fffff800`00b9a8c8
.
tart             end                 module name
fffff880`05677000 fffff880`05b8cfa0   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Thu Oct 18 05:42:29 2012 (507F031D)
    CheckSum:         0051C6DC
    ImageSize:        00515FA0
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Update the outdated Intel graphics driver here:
https://downloadcenter.intel.com/

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050033, 406f8, fffff8800444ef4e}

*** WARNING: Unable to verify timestamp for rtwlane.sys
*** ERROR: Module load completed but symbols could not be loaded for rtwlane.sys
Probably caused by : rtwlane.sys ( rtwlane+35f4e )

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

start             end                 module name
fffff880`04419000 fffff880`04538000   rtwlane  T (no symbols)           
    Loaded symbol image file: rtwlane.sys
    Image path: rtwlane.sys
    Image name: rtwlane.sys
    Timestamp:        Thu Dec 01 13:11:24 2011 (4ED6E954)
    CheckSum:         00116FAE
    ImageSize:        0011F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Update the Realtek NIC driver here:
Realtek

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffffffffff89, 1, fffff80002ad1cb9, 0}


Could not read faulting driver name
Probably caused by : hardware ( nt!PoIdle+4ea )

Followup: MachineOwner
---------
Run a minimum of 8 consecutive passes, preferably overnight, or until errors occur using MemTest86+.

Reference:
RAM - Test with Memtest86+
My System SpecsSystem Spec
17 Dec 2015   #3
ausmisc

Windows 7 Ultimate x64
 
 

Hi Golden, I appreciate the reply and I'll work on trying this out today!

Edit: I went through and updated the mentioned drivers plus some other ones that were picked up by the driver update program I used. Here's an updated dm log if it's needed. I'll run memtest86 over night.

Edit2: Had another BSOD after I'd updated everything.

Quote:
On Fri 18/12/2015 6:07:46 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121815-14742-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0xDA (0x504, 0xFFFFF6FC40074988, 0x13, 0xE931)
Error: SYSTEM_PTE_MISUSE
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 page table entry (PTE) routine has been used in an improper way.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
My System SpecsSystem Spec
.

18 Dec 2015   #4
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

Code:
Start Menu\Programs\Smart Driver Updater	Public:Start Menu\Programs\Smart Driver Updater	Public
Start Menu\Programs\Smart Driver Updater\Check other products	Public:Start Menu\Programs\Smart Driver Updater\Check other products	Public
Uninstall the above applications (don't use these sorts of applications to update drivers, they often cause trouble). Reboot, then follow these instructions:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Driver Verifier - Enable and Disable

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
System Restore Point - Create

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
Safe Mode
My System SpecsSystem Spec
18 Dec 2015   #5
ausmisc

Windows 7 Ultimate x64
 
 

Ah bugger, I just installed Smart Driver Updater earlier today to try make sure I had all the ones you mentioned. I've uninstalled it, enabled driver verifier as per the guide and rebooted.
My System SpecsSystem Spec
18 Dec 2015   #6
ausmisc

Windows 7 Ultimate x64
 
 

Ran through 8 passes of memtest with not a single error, also used the laptop for about 5 hours yesterday with driver verifier enabled and didn't crash.
My System SpecsSystem Spec
18 Dec 2015   #7
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

OK. Turn Driver Verifier OFF, reboot and use as normal. Lets see if it crashes.
My System SpecsSystem Spec
19 Dec 2015   #8
ausmisc

Windows 7 Ultimate x64
 
 

BSOD again today while playing a game. It seems strange that the error is different nearly every time..

Quote:
On Sat 19/12/2015 7:02:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121915-7597-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x18864)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88001267864, 0xFFFFF8800352B4F8, 0xFFFFF8800352AD50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 that a system thread 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.
My System SpecsSystem Spec
19 Dec 2015   #9
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

Additional information is required.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

My System SpecsSystem Spec
19 Dec 2015   #10
ausmisc

Windows 7 Ultimate x64
 
 

Been reading other posts, don't know if it's of any help but I ran a CHKDSK with no issues, also did a full scan with HD Tune, and sfc.exe/scannow but nothing showed any problems.
My System SpecsSystem Spec
Reply

 Clevo P151EM1 frequent BSOD




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD - GTX 660M - nvlddmkm.sys - Windows 7 - Clevo Laptop -
Hi, Im going to post as much information as possible, but currently I can play games for about 5 minutes before the I get a Blue screen. I will post the make and model details below, as well as the BSOD info/files whichever is best. If anyone can help or point me in the right...
BSOD Help and Support
BSOD randomly on P370 Clevo laptop when loading random programs
The first problem with this issue is that it is erratic, it tends to happen alot, or only once or twice each day. I basically load up the laptop, load for example Chrome GMAIL and bang BSOD, load it up again, load up Spotify and BANG BSOD. Load it up again and load Chrome and nothing its fine,...
BSOD Help and Support
Frequent BSOD playing SimCity / Frequent applications crashing
Hello, This has all started since installing EA's Origin in order to play SimCity and Battlefield 3, the later crashes with a BSOD Stop 0x0000001 within about 1 minute of starting, SimCity will give me up to an hour before BSOD'ing. It's 50:50 whether it's a BSOD or a 'SimCity has stopped...
BSOD Help and Support
Clevo P170EM random BSOD ntoskrnl.exe
I am having alot of trouble figuring this one out and would GREATLY appreciate any help. I'm about to the point of ripping my hair out! The last reply I've had from the manufacturer is that they'd look into my problem and get back to me. I have had this computer for two months and don't want...
BSOD Help and Support
Sager NP5170 / Clevo W170HN BSOD Potentially from Updates?
Hello everyone, As the title says I have a Sager NP5170 and its been running perfectly; however, every time a particular update occurs it bugs my computer and crashes. Though I cannot for sure say it is in fact an update causing this I can voucher it as evidence of an update. I have owned the...
BSOD Help and Support
slowdown d900c clevo seven rtm 64
Good evening everybody. too happy tonight because i've solved a long time trouble with SLOWDOWN. i'll try to explain but be patient for my horrible english speaking. since i've bought my notebook i've had trouble with OS, first with Vista (ultimate 64) and after with Seven (some alphas,...
Performance & Maintenance


Our Sites

Site Links

About Us

Find 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 03:38.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App