Clevo P151EM1 frequent BSOD

[ausmisc]

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.

[FONT=Segoe UI, Arial] Welcome to WhoCrashed (HOME EDITION) v 5.51 [/FONT]
[FONT=Segoe UI, Arial]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.
[/FONT]
[FONT=Segoe UI, Arial]To obtain technical support visit www.resplendence.com/support

[/FONT][FONT=Segoe UI, Arial]Click here to check if you have the latest version or if an update is available.

[/FONT][FONT=Segoe UI, Arial]Just click the Analyze button for a comprehensible report ...


[/FONT][FONT=Segoe UI, Arial] Home Edition Notice [/FONT]
[FONT=Segoe UI, Arial]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.
[/FONT]
[FONT=Segoe UI, Arial] System Information (local) [/FONT]
[FONT=Segoe UI, Arial]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


[/FONT]
[FONT=Segoe UI, Arial] Crash Dump Analysis [/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x74200)
Bugcheck code: 0xD1 (0x0, 0xB, 0x1, 0xFFFFFA800E09B004)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x74200)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF89, 0x1, 0xFFFFF80002AD1CB9, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]rtwlane.sys[/FONT] (rtwlane+0x35F4E)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF8800444EF4E)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP[/FONT]
file path: C:\Windows\system32\drivers\rtwlane.sys
product: [FONT=Segoe UI, Arial]Realtek PCIEWireless LAN PCI-E NIC [/FONT]
company: [FONT=Segoe UI, Arial]Realtek Semiconductor Corporation [/FONT]
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: [FONT=Segoe UI, Arial]Realtek Semiconductor Corporation UNEXPECTED_KERNEL_MODE_TRAP[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x74200)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF89, 0x1, 0xFFFFF80002A81CB9, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x741D0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x74200)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFA9, 0x1, 0xFFFFF80002A87CB9, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]tcpip.sys[/FONT] (tcpip+0x167128)
Bugcheck code: 0xFC (0xFFFFF88001768128, 0x8000000003D65963, 0xFFFFF88003BE1500, 0x0)
Error: [FONT=Segoe UI, Arial]ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY[/FONT]
file path: C:\Windows\system32\drivers\tcpip.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]tcpip.sys[/FONT] (tcpip+0x167128)
Bugcheck code: 0xFC (0xFFFFF88001768128, 0x8000000003D65963, 0xFFFFF88003BE1500, 0x0)
Error: [FONT=Segoe UI, Arial]ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY[/FONT]
file path: C:\Windows\system32\drivers\tcpip.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75BC0)
Bugcheck code: 0xA (0xFFF4C, 0x2, 0x0, 0xFFFFF80002A5C650)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]

[FONT=Segoe UI, Arial] Conclusion [/FONT]
[FONT=Segoe UI, Arial]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:

[FONT=Segoe UI, Arial]rtwlane.sys (Realtek PCIE NDIS Driverr, Realtek Semiconductor Corporation )[/FONT]

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.



[/FONT]

 

[Golden]

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[B][COLOR="red"] local Bluetooth adapter has failed in an undetermined manner[/COLOR][/B] and will not be used. The driver has been unloaded.

Reinstall the Bluetooth adapter driver with the latest driver version, or turn it OFF.

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 [B][COLOR="red"]Oct 18[/COLOR][/B] 05:42:29 [B][COLOR="Red"]2012[/COLOR][/B] (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/

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

*** WARNING: Unable to verify timestamp for [B][COLOR="Red"]rtwlane.sys[/COLOR][/B]
*** 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 [B][COLOR="red"]Dec 01[/COLOR][/B] 13:11:24 [COLOR="red"][B]2011[/B][/COLOR] (4ED6E954)
    CheckSum:         00116FAE
    ImageSize:        0011F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update the Realtek NIC driver here:
Realtek

*******************************************************************************
*                                                                             *
*                        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 : [B][COLOR="red"]hardware[/COLOR][/B] ( nt!PoIdle+4ea )

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

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

Reference:
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[ausmisc]

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.

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x74200)
Bugcheck code: 0xDA (0x504, 0xFFFFF6FC40074988, 0x13, 0xE931)
Error: [FONT=Segoe UI, Arial]SYSTEM_PTE_MISUSE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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. [/FONT]

 

[Golden]

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.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

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:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

 

[ausmisc]

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.

 

[ausmisc]

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.

 

[Golden]

OK. Turn Driver Verifier OFF, reboot and use as normal. Lets see if it crashes.

 

[ausmisc]

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

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs+0x18864)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88001267864, 0xFFFFF8800352B4F8, 0xFFFFF8800352AD50)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

 

[Golden]

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.

 

[ausmisc]

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.

 

[Golden]

Please try Driver Verifier again, but this time leave it enabled for 24hrs - do not shut down overnight. Just leave it running.

 

[ausmisc]

Still going on the 24 hours, but did notice a trend. With verifier running - it crashed 3 times in an hour while trying to watch youtube/streams or game..but whilst being unused it ran for 9 hours overnight so far without a single BSOD. I'll upload the log later.

 

[ausmisc]

So even with driver verifier running, it only seems to want to BSOD when I'm watching videos or playing games etc. It went about 18 hours in total just sitting on the desktop or being used to browse webpages, but the 3 or 4 times it did crash was when I was playing heroes of the storm/diablo or fired up prime95.

 

[Golden]

Mmmmm....that suggest to me its the video card/s, although the .dmp files don't point to that.

Can you see whether you can turn off the Intel HD 4000 card in the BIOS/uEFI and just use the NVidia card?

 

[essenbe]

Hello, ausmisc. I am assuming from the dump files you have an Nvidia graphics card. If that is true, please follow the suggestions below. However, for right now, just do the first part until we can see how it reacts. Don't disable it in Device Manager just yet.

First set the integrated graphics as preferred .....

1. Open Nvidia control panel.
2. Click on "Manage 3D settings".
3. Click on the button below "Preferred Graphics Processor"
4. Change it to "Integrated graphics"from the drop down menu.
   
   
   This image has been resized. Click this bar to view the full image. The original image is sized 772x284.
   
   This image has been resized. Click this bar to view the full image. The original image is sized 772x284.
   
5. Apply it.

Now restart the computer.

Now, disable nvidia graphics card in the device manager.

1. Click on the start button.
2. Type Device Manager in the search bar.
3. Click on the resulting link. The Device Manager window will open.
4. The third one should be "Display Adapter". Expand it by clicking on the "►" in front of it. Your nvidia card name will be shown.
5. Right click on it. Choose "Disable" in the context menu.
6. A dialog will appear with some scary words. Dont be afraid. Click on "Yes" .
7. Restart the computer.

Hopefully the nvidia display is out of use now, and so there will not be any further chance of graphics switching.

Let us know how the computer is running after doing it.

 

[Golden]

Thanks Steve

 

[essenbe]

No problem. I hope it works for him.

 

[ausmisc]

Thanks guys, running it now with the nvidia card disabled, gaming to try make it crash.

Edit: Unfortunately it crashed within about 15mins =/ Don't think there is any option in the BIOS to disable the onboard intel VGA to try disabling it.

 

[essenbe]

Ausmisc, I'll try to help you until Golden returns. This is what your dump says

BugCheck 50, {fffff8a009fca420, 0, fffff88003f34120, 0}
Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98 )
Followup:     MachineOwner

fffff880`06c857f8  fffff880`049cf184Unable to load image igdkmd64.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for igdkmd64.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
 igdkmd64+0x1c7184

That is your Integrated Intel Graphics. This is your current driver

start             end                 module name
fffff880`04808000 fffff880`04bbe000   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: igdkmd64.sys
    Image name: igdkmd64.sys
    Browse all global symbols  functions  data
    Timestamp:       [COLOR=Red] Mon May 25 05:13:13 2015[/COLOR] (5562F5B9)
    CheckSum:         003A6BB5
    ImageSize:        003B6000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

That is not that old of a Driver. Where did you download it from? You are normally better off downloading graphics drivers from the manufacturer's web site. Most Laptop Manufacturers alter their drivers to fit how theit products are set up.

Also, if you don't have one, please download and install a CPU Temp Monitoring program. Watch your CPU temps at all times. I need to know what they are, especially at the time of the crash.

 

[ausmisc]

Sorry I'm not 100% clear on which VGA you are referencing in the third quote. If it's the Intel driver then it came from the Intel update utility that I got just the other day as Golden mentioned my Intel VGA driver was pretty outdated. It's kind of strange though because it says I'm running 10.18.10.4226 and that the latest one is 15.33.36.64.4226 and gives me the option to download and install it.. I do that but then it still says the same thing (and my device manager still lists the 10.18.10.4226 driver).

Ive been using HWmonitor to check temperatures.. my CPUs seem to max out around 95c under Prime95 blend test, graphics card about 80c.