Various reapeating BSOD

[Sibona]

Hello,


My computer crashes regularly with different BSOD messages. I formatted the disk to reinstalled Windows from scratch several times, updated all the drivers provided with the laptop, but the issue remains. I tested the RAM logically and physically (running with each module individually), but the issue remains.

Your help would be very appreciated at this point. Attached are a number of minidumps to look into.


Here are the specs.
Clevo P151SM-A
OS Windows 8.1 64-bit
CPU Intel i7-4710MQ
RAM 32Go
Nvidia GeForce GTX 870M


Please help me out or let me know if you need additional info.


Regards,
Michel

 

[lifetec]

Many dumpfiles with memory corruption
Memory Test.
Please start withdiagnosing the system RAM first. You can use the free tool "Memtest86+"to stress test the RAM.

How to run "Memtest" - RAM - Test withMemtest86+ - Windows 7 Help Forums

Make sure you are using the latest version 5.01 - Memtest86+ - Advanced Memory Diagnostic Tool

You can stop the test even if a single error is found during the test.Otherwise continue the test for 7-10 passes and post a screenshot with nextreply. 7 passes is the recommended bare minimum but more passes will givebetter result.

In your Windows error Reporting many windows update faillures.
Try this.
Windows updatefaillure Fix it
Fix it for me
Use our Windows Update Automated Troubleshooter
Thistroubleshooter will detect and solve Windows update issues automatically.
Run now
source: https://support.microsoft.com/nl-nl/gp/windows-update-issues/en-us

 

[Sibona]

Thank you lifetec. I have already run Memtest several times and even for a whole night (12 hours) without error. As I have 2 memory modules, I even removed one for a week, and then switched with the other one for a week. The computer keeps crashes in both situations and I don't believe it could be a memory problem (except if both memory modules have a physical problem not detected by Memtest, which is very unlikely).

Regarding the Windows Update Automated Troubleshooter, I gave it a try and I will let you know if it crashes again in the coming hours/days

 

[Sibona]

Unfortunately, my computer keeps crashing and it seems the above solution doesn't solve the problem.
Attached is the updated configuration and latest minidump.
Your help is greatly appreciated at this point.
Thank you,
Michel

 

[lifetec]

The latest dumpfile is again.

  *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffd000219109a8, 0, fffff803bf031a7b, 1}

Could not read faulting driver name
Probably caused by : memory_corruption
Followup: memory_corruption
---------

The procesname was LogiOptionsMgr.
Please update the setpoint software for your logitech keyboard Illuminated Keyboard K740 - Logitech Support


Please run driver verifier to hopefully find a problematic driver.
You can enable "DriverVerifier" according to instructions from the below link.
http://www.tenforums.com/tutorials/5470-driver-verifier-enable-disable-windows-10-a.html
"Verifier" is a Microsoft's own tool to stress test third partydrivers and find the buggy one. If it detects a violation, a blue screen willbe created immediately and the dump will give us the name of offending driverstraight forward. After enabling "Verifier" , system will be a bitslow and laggy during to the background verification process. After you got twoor more blue screens, please upload the new crash dumps and we will knowwhether the issue is caused by third party drivers or low level hardware (averifier enabled dump which blames Windows system files is a clear confirmationof hardware problem).
"Verifier" should be only used to monitor third party drivers.Selecting Microsoft system drivers is totally unnecessary and doing so may make the system nonbootable. First read instructions from the below link and set "Windows"to write "Small Memory dumps".
SetMiniDump
Then enable "verifier" and select all.

 

[Sibona]

Thank you lifetec. I installed the latest setpoint software for the logitech keyboard, and enabled Verifier for the following drivers (all non Microsoft system drivers):
iastora.sys
fpwinio.sys
svthansp.sys
nvlddmkm.sys
igdkmd64.sys
teedriverx64.sys
rtsbastor.sys
rt630x64.sys
ndis.sys
netwbw02.sys
syntp.sys
smb_driver_intel.sys
airplanemodehid.sys
iwdbus.sys
dump_diskdump.sys
dump_iastora.sys
dump_dumpfve.sys
atmfd.dll
dot4.sys
dot4prt.sys
leqdusb.sys
lhideqd.sys
lhidfilt.sys
lmoufilt.sys

Will now let it run and crash a few times before posting the new status...

 

[Sibona]

After enabling Verifier, my computer crashed 3 times. The first time, no minindump was recorded (0% recording progress on blue screen). The 2 next times were the same: My computer was in sleep mode, I wake it up, get a black screen (no interactivity), power off with hard button, power on, get a blue screen from Verifier saying it records minidump,

But after these 3 crashes, I don't have any new minidump in %SystemRoot%\Minidump as it is set in Windows setting. I should have a small memory dump as before, but I get nothing since Verifier was enabled.

Attached is the new configuration status.

Any idea would be appreciated...

 

[lifetec]

Sorry no new dumpfiles in the new zip.

 

[Sibona]

Well, this is the problem: My computer crashes, it says it records the minidump, but it doesn't. This occurs since I enabled Verifier. Should I stop Verifier then?

 

[lifetec]

Yes stop it.
Check all the settings and try it again.

 

[Sibona]

Thank you. I have disable Verifier now. Will wait for the next crash and enable it again after that.
I will let you know how it goes...

 

[lifetec]

You have to let driver Verifier run on your system for about 24h and if it finds the abusing driver it will let the stystem crash and hopefully will make a dumpfile.
Then stop Driver Verifier and upload a new zip with verifier dumpfile included.

 

[Sibona]

Here is some new information:

After disabling Verifier, my computer crashed on 30/01 and a new minidump was generated.

I then reactivated Verifier according to the instructions, and restarted the machine. Surprisingly, my computer did not crash for a long time. But today, a new crash occured while I was away of my machine. When I rebooted, Windows installed some updates and I could not restart the machine because Verifier crashed when it was restarting. I had to use the recovery options to type the command line "verifier /bootmode resetonbootfail". Now my machine is back up, but without Verifier.

Attached is the new configuration, logs and minidumps. Could you please have a look and let me know what should be the next step?

Thank you for your help,
Michel

 

[lifetec]

The last dumpfile blames

 *******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C9, {300, fffff8001fdebf5c, ffffe00145fc3b80, 49db9b60}
*** WARNING: Unable to verify timestamp for FPWinIo.sys
*** ERROR: Module load completed but symbols could not be loaded for FPWinIo.sys
Probably caused by : FPWinIo.sys ( FPWinIo+4f5c )

This is the driver for your Egis fingerprint device.
Please upload the driver to the latest version fom your supportpage CLEVO Driver Download+

Also check if there are other newer drivers for your laptop from this page.

Because your laptop run a long time without a crash, do not use Driver verifier after updating the fingerprint driver.
And let see what is happening.

 

[Sibona]

Thank you lifetec. The version of the Egis fingerprint driver available on Clevo / Internet is the same as the version I already use. It seems it is the latest. I resinstalled it anyway.

I restarted the machine and I will let you know how it goes in the coming days...

 

[Sibona]

Here is some update since I disabled Verifier : 2 new BSODs on 14/02 and 16/02
What should I do now?
Thank you for your help,
Michel

 

[lifetec]

According to your dumpfile you are only using 3 memory modules of 8 gb is this the ment way, because in your first post you said you have a system with 32 gb of RAM.

This could mean that one of your memory modules is broken amd that this the cause of your BSOD.

  [Memory Device (Type 17) - Length 34 - Handle 0019h]
  Physical Memory Array Handle  0018h
  Memory Error Info Handle      [Not Provided]
  Total Width                   0 bits
  Data Width                    0 bits
  Size                          [Not Populated]
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                ChannelA-DIMM0
  Bank Locator                  BANK 0
  Memory Type                   02h - Unknown
  Type Detail                   0000h -
  Speed                         0MHz
  Manufacturer                  [Empty]
  Serial Number                        
  Asset Tag Number                        
  Part Number                   [Empty]
[Memory Device (Type 17) - Length 34 - Handle 001ah]
  Physical Memory Array Handle  0018h
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          8192MB
  Form Factor                   0dh - SODIMM
  Device Set                    [None]
  Device Locator                ChannelA-DIMM1
  Bank Locator                  BANK 1
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1600MHz
  Manufacturer                  Transcend
  Serial Number                         
  Asset Tag Number                        
  Part Number                   JM1600KSH-8G      
[Memory Device Mapped Address (Type 20) - Length 35 - Handle 001bh]
  Starting Address              00800000h
  Ending Address                00ffffffh
  Memory Device Handle          001ah
  Mem Array Mapped Adr Handle   0020h
  Partition Row Position        [Unknown]
  Interleave Position           [Unknown]
  Interleave Data Depth         [Unknown]
[Memory Device (Type 17) - Length 34 - Handle 001ch]
  Physical Memory Array Handle  0018h
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          8192MB
  Form Factor                   0dh - SODIMM
  Device Set                    [None]
  Device Locator                ChannelB-DIMM0
  Bank Locator                  BANK 2
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1600MHz
  Manufacturer                  Transcend
  Serial Number                         
  Asset Tag Number                        
  Part Number                   JM1600KSH-8G      
[Memory Device Mapped Address (Type 20) - Length 35 - Handle 001dh]
  Starting Address              00000000h
  Ending Address                007fffffh
  Memory Device Handle          001ch
  Mem Array Mapped Adr Handle   0020h
  Partition Row Position        [Unknown]
  Interleave Position           [Unknown]
  Interleave Data Depth         [Unknown]
[Memory Device (Type 17) - Length 34 - Handle 001eh]
  Physical Memory Array Handle  0018h
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          8192MB
  Form Factor                   0dh - SODIMM
  Device Set                    [None]
  Device Locator                ChannelB-DIMM1
  Bank Locator                  BANK 3
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1600MHz
  Manufacturer                  Transcend
  Serial Number                         
  Asset Tag Number                        
  Part Number                   JM1600KSH-8G

 

[Sibona]

Initially, I had 32 Gb RAM in my computer, split into 2 memory modules of 16 GB each. Since the logical memory test with Memtest was all fine, I wanted to test memory physically. Thus, I first removed one of the two 16 GB modules for a few days, and then switched with the other 16 GB module. The crashed occured the same way with both modules.

The configuration I have at this time is only one 16 Gb module. I can put the other 16 GB module back in if necessary. I just wonder why you see 3 x 8 Gb as it should be 2 x 8 Gb for a single 16 Gb module.

What do you think?

 

[Sibona]

Hi,

This problem is not fixed and my computer keeps crashing every few days... I know this is a tough one as the reason for the crash is not clear.

I would really appreciate the help from the experienced ones. Attached is the latest configuration data along with the minidumps.

Please let me know what I can do and thank you for your help...

Michel