Clevo P151EM1 frequent BSOD

[ausmisc]

Again 4 minutes later, and a few minutes after that

 

[essenbe]

here are the results

Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, 138c84, 0, 133884}
[COLOR=red]Probably caused by : memory_corruption[/COLOR] ( nt!MiBadShareCount+4c )
Followup:     MachineOwner
 
[COLOR=red]PFN_LIST_CORRUPT[/COLOR] (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000138c84, page frame number
Arg3: 0000000000000000, current page state
Arg4: 0000000000133884, 0
Debugging Details:

Use !analyze -v to get detailed debugging information.
BugCheck D1, {108, b, 8, 108}
[COLOR=red]Probably caused by : dxgkrnl.sys[/COLOR] ( dxgkrnl!DpiFdoDpcForIsr+2e )
Followup:     MachineOwner

Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80002c93160, 1, 10}
[COLOR=red]Probably caused by : hardware[/COLOR] ( nt!KeAcquireInStackQueuedSpinLock+30 )
Followup:     MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002c93160, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000010, Parameter 1 of the exception

Please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Also, please make sure all of your Windows Updates are current and make sure your Flash and Flash plugin for Firefox are both up to date. The next time you run a You Tube Video, please disable hardware acceleration and see if that works. Go through Steam or wherever your games are installed and verify the game files.

 

[ausmisc]

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

I was running an older version of firefox but I've updated to the newest. Flash is the latest. Ran windows update and installed all important and optional files except for the Intel 4000 (still running the old driver for this). Verified all game installations via Battlenet said they were okay. Disabled hardware acceleration.

 

[ausmisc]

Was just watching twitch.tv again.

 

[essenbe]

Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c000001d, fffff80002fbf298, fffff88009222970, 0}
Probably caused by : memory_corruption
[COLOR=red]Followup:     memory_corruption[/COLOR]

Please Run Memtest86+​

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask

 

[ausmisc]

Hey mate I've ran memtest twice overnight through 8 passes but I'll give it another go tonight.

 

[essenbe]

We can wait if you want to. Instead run Seatools for DOS http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part3

 

[ausmisc]

Hi it passed the Seagate DOS test fine for both drives, I ran the long tests to make sure. Do you think reformatting and making sure I just use the latest drivers from the manufacturers site might be an option? Or is it pointing towards a hardware issue?

Will start it on memtest again overnight.

 

[essenbe]

Some of the dump files keep saying Hardware. But, that could also be a bad driver causing that.

 

[ausmisc]

Yeah seems like a doozy to track down. Still running memtest at the moment, 12 hours in and it has done 4 passes with 0 errors. I didn't pretty any buttons at the start so it's okay that it's only testing on core 0 with SMP disabled? I'm guessing it's because we only care about the memory being tested.

 

[ausmisc]

20 hours and 8 passes with 0 errors!

 

[essenbe]

That's great. What I want to try next, there is some risk involved. It is theoretically possible you may have to do a clean install. But, we take every precaution for that not to happen. It has never happened on a case I have worked on. Just to be safe I would back up everything and do an image. Also, be certain to create a restore point before you start.

   Warning

Be sure to create a System Restore point before proceeding further http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

Driver Verifier - Enable and Disable

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

   Information

What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.

What you will notice:

It will tend to make the computer rather slow and sluggish because the drivers are being stressed.

   Warning

Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

This was done on Windows 10 but it is the same on Windows 7.

 

[ausmisc]

I ran driver verifier earlier but only tried it for 5 hours or so I think, didn't crash just sitting on the desktop. I'll load it up tonight and let it run overnight.

 

[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.

Oops it was longer than 5 hours, went 18 hours with DV running, no crashes as long as it was just sitting on the desktop. I'll leave it again overnight with DV running.

 

[essenbe]

Use it tomorrow too. Do what you normally do, except for games or videos for a good while. Then play a game or watch a video after you've given it a good workout.

 

[ausmisc]

It went over 24 hours fine with driver verifier running, didn't use the laptop just left it running. I've been gaming again but haven't actually had another BSOD since the 23/12/15 which is the longest I've ever seen it go (usually it would be a couple every hour). I haven't tried watching any twitch.tv yet though.

I'm still running with the NVidia card disabled.

 

[essenbe]

Try the gaming again and some Twitch TV and see how it does then disable Verifier. Then we'll punt.