Windows 10: BSOD: ntoskrnl.exe and more

Hello,

A small update: The BSOD's have gotten better recently, but there are still a few each week (roughly 3-5) which is very annoying. I filled in manually my system specs, as you wished *Smile Now, I think we need to recheck everything, software, hardware, installed programs etc. Can you give me a list of steps / checks which I should apply? Where shall we start?

 

Depends mainly on what types the crashes are, there are several memory related crashes, some are also pretty specific to components.

If you can provide another log, or at least dumps we can find out where to start *Smile

 

I attached a few logs. Is the language correct? Let me know if not, I am not sure because I have an English windows but the German Keyboard layout. I remember having installed drivers from drivertalent a while ago, we surely need to check whether I have wrong drivers installed / whether correct drivers are lacking. What I noticed is also, that the two most recent bluescreens happened exact at the same time (21:55h) but four days apart. Thanks for your help so far *Smile

 

The language is not correct.

All the crashes, except for 1, are 0x1A which are all memory related crashes.
Run driver verifier again, but this time after 48h disable it and some time later enable it again.

Check your scheduled tasks to see if anything is active in that period.





Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

Here is the updated log, I hope the language is correct. If not, inform me. If yes, tell me if you could gather any particular information. I will run driver verifier tomorrow. I have an extern hard disk and I was thinking about copying my important documents there and then installing everything completely from scratch, how should I approach then? I might need>

A new windows or download the newest win 10 usb compatible boot media

A way to remove all currently installed drivers and start again by installing my drivers from the graphic & mainboard card cd dvd.

What do you think about it? I will keep you updated about the driver verifier.

 

Make sure the drivers of your Corsair devices are up to date.
Code: +++ WER6 +++: Fault bucket 116106565613, type 5 Event Name: BEX Response: Nicht verfügbar Cab Id: 0 Problem signature: P1: CorsairHID.exe P2: 1.15.36.0 P3: 56b216d6 P4: MSVCR120.dll P5: 12.0.21005.1 P6: 524f7ce6 P7: 000a7666 P8: c0000409 P9: 00000007 P10:[/quote]

 

Interesting! It says: P1: corsairHID

When I start up the computer and log in, two error messages pop up, one of them being HID related. I will update the drivers.

Edit> I attached two pictures

 

What is interesting about that? It is just a problem report.

This are all the problem reports.
Code: Windows Error Reporting: +++ WER0 +++: Fault bucket 116106565613, type 5 Event Name: BEX Response: Not available Cab Id: 0 Problem signature: P1: CorsairHID.exe P2: 1.15.36.0 P3: 56b216d6 P4: MSVCR120.dll P5: 12.0.21005.1 P6: 524f7ce6 P7: 000a7666 P8: c0000409 P9: 00000007 P10: +++ WER1 +++: Fault bucket MEMORY_CORRUPTION_ONE_BIT, type 0 Event Name: BlueScreen Response: http://wer.microsoft.com/responses/...ate=1&ID=54ef4369-ec40-4b16-8861-ca2725fef32a Cab Id: 54ef4369-ec40-4b16-8861-ca2725fef32a Problem signature: P1: 1a P2: 41792 P3: fffff680000395b8 P4: 800000 P5: 0 P6: 10_0_10586 P7: 0_0 P8: 768_1 P9: P10: +++ WER2 +++: Fault bucket 116106565613, type 5 Event Name: BEX Response: Nicht verfügbar Cab Id: 116074350811 Problem signature: P1: CorsairHID.exe P2: 1.15.36.0 P3: 56b216d6 P4: MSVCR120.dll P5: 12.0.21005.1 P6: 524f7ce6 P7: 000a7666 P8: c0000409 P9: 00000007 P10: +++ WER3 +++: Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1a P2: 41792 P3: fffff680000395b8 P4: 800000 P5: 0 P6: 10_0_10586 P7: 0_0 P8: 768_1 P9: P10: +++ WER4 +++: Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1a P2: 41792 P3: fffff680000395b8 P4: 800000 P5: 0 P6: 10_0_10586 P7: 0_0 P8: 768_1 P9: P10: +++ WER5 +++: Fault bucket 116106565613, type 5 Event Name: BEX Response: Nicht verfügbar Cab Id: 0 Problem signature: P1: CorsairHID.exe P2: 1.15.36.0 P3: 56b216d6 P4: MSVCR120.dll P5: 12.0.21005.1 P6: 524f7ce6 P7: 000a7666 P8: c0000409 P9: 00000007 P10: +++ WER6 +++: Fault bucket 116106565613, type 5 Event Name: BEX Response: Nicht verfügbar Cab Id: 0 Problem signature: P1: CorsairHID.exe P2: 1.15.36.0 P3: 56b216d6 P4: MSVCR120.dll P5: 12.0.21005.1 P6: 524f7ce6 P7: 000a7666 P8: c0000409 P9: 00000007 P10: +++ WER7 +++: Fault bucket 125026835750, type 5 Event Name: MpTelemetry Response: Not available Cab Id: 0 Problem signature: P1: 2152759308 P2: unspecified P3: ScanFile P4: 4.9.10586.0 P5: Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24) P6: unspecified P7: unspecified P8: P9: P10: +++ WER8 +++: Fault bucket , type 0 Event Name: MpTelemetry Response: Not available Cab Id: 0 Problem signature: P1: 2152759308 P2: unspecified P3: ScanFile P4: 4.9.10586.0 P5: Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24) P6: unspecified P7: unspecified P8: P9: P10: +++ WER9 +++: Fault bucket MEMORY_CORRUPTION_ONE_BIT, type 0 Event Name: BlueScreen Response: http://wer.microsoft.com/responses/...ate=1&ID=358bb649-d018-4ef0-8c44-2942850fef87 Cab Id: 358bb649-d018-4ef0-8c44-2942850fef87 Problem signature: P1: 1a P2: 41792 P3: fffff6bffc43b4e8 P4: 400000 P5: 0 P6: 10_0_10586 P7: 0_0 P8: 768_1 P9: P10:[/quote]

 

Interesting because it shows the root of the problem. I have RAM from Corsair and the Keyboard from corsair. I had two more bsods within 30minutes, here are the logs. I had two different error messages, please check if both have the same program as a cause, if possible. Is corsair still the culprit? If yes, I will now only use one ram module and pin it into another slot, and then vice versa with the other. I will now start with driver verifier.

 

It isn't the RAM the reports are talking about, they never do.

Both are memory related crashes, not only because it says 'memory_corruption'
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff8015fe9d1fa, ffffd0005deb06f0, 0} Probably caused by : memory_corruption Followup: memory_corruption MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT STACK_COMMAND: .cxr 0xffffd0005deb06f0 ; kb FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_ONE_BIT ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41792, fffff6bffaf4a638, 20000, 0} Probably caused by : memory_corruption ( ONE_BIT ) Followup: MachineOwner MODULE_NAME: hardware IMAGE_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 IMAGE_VERSION: FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_ONE_BIT[/quote]

 

Alright, thank you. Verifier is now running. I checked all non-microsoft drivers in the option menu, as demanded in the tutorial. I ran into to corsair drivers, but Im not sure where they are from or to which part of my pc they belong. What I mean by this is that I dont know what drivers to update, I only have a keyboard and the ram from corsair but to neither of them are special drivers available. There is only a keyboard utility setup thing available but no specified driver, do you know what I mean?

Downloads


I redownloaded the corsair utility engine just now, maybe it automatically updates drivers I dont know. Will keep you updated about driver verifier and then what happens when I swap the ram modules and test them individually. Thank you so much for your help I really hope we get this solved.

 

RAM doesn't have drivers, it is a place to temporary store data in to access later, but that is done by the system and doesn't require anything from the RAM except that it shouldn't corrupt things by being faulty.

The software contains drivers to control the keyboard, although I have no idea what for the software is.

 

I left verifier on for 48 hours, no crash, turned it off and a few hours later it crashed. Shall I turn it on again? I now took off the first ram module. I have currently one module running and this is placed in a different slot than usual.

 

Its running again. Here is a list of all non-microsoft drivers, it might provide a bit of insight.

 

No drivers beneath Microsoft drivers?