Windows 10: Iam having different kind of bsod's and cannot figure out the cause

Hello everybody,

I have quite some issues with my PC. I bought it with Windows 10 OS pre-installed. I installed my typical programs and drivers. Very soon my PC started crashing and I got my first bsod's. The scenario's in which the bsod occured were different each time: after restarting my pc, after booting my pc, when opening steam, while installing new drivers, while attempting to rune prime95, while making a scan with malwarebytes.

The bsod's I got (those which I took a picture of): BAD_POOL_HEADER, MEMORY_MANAGEMENT, CRITICAL_PROCESS_DIED, DRIVER_IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NONPAGED_AREA, KERNEL_SECURITY_CHECK_FAILURE.

Sometimes when Iam gaming I get "*.exe hast stopped working". Those errors popup 0,5-2mins afters starting the 3D application. Same thing happened with my google chrome browser twice. But after restarting my pc those issues usually went away and I was able to browse the internet or play video games for 2 hours or more.

I started to uninstall wrong drivers and install the correct ones from the page of the manufactorer.

I checked my RAM with MemTest86 7.4. The first time with only 4 passes and after I informed myself I redid the test with 8 passes. Both times without any errors.

I watched the temperature of my hardware components with HWiNFO. I did not do any gpu testing, but I managed gaming sessions for 3-5 hours in high-ultra settings with 4k resolution.

I used driver verifier too and found a corrupt usb-driver which I uninstalled. Afterwards I ran the verifier again for 3 hours without any problems.

I also used cmd for sfc scannow, chkdsk (without other parameters) and ScanHealth without and errors.

The day before yesterday I was fed up and installed my OS again with the windows media creation tool. I let windows do its update thingy and installed the MSI chipset driver.

After that I used Display Driver Uninstaller to remove the default, windows-installed, gpu driver. As I was running the nvidia driver of the gpu card manufactorer and the application was in the progress of collection system informations, my system crashed yet again with another bsod.

Now Iam officially out of ideas what to do. The newest dump is included in the attachment of my post.

I would appreciate any help on what else to try.

Thank you!

Best regards,



:)

 

Windows 10 BSOD After update - KMODE EXCEPTION NOT HANDLED

After an automatic update the BSOD arises after a couple of minutes in normal boot. I cannot tell what file is causing the crash and I have sensitive info so cannot reset system.

The DMP files I have but cannot figure out how to upload them (onefile doesnt work in safe mode)

Please help!

I tried rolling back the updates and that caused a total crash, and had to restore.

 

Blue screen error

Upload a folder on OneDrive with the DMP files, as I previously mentioned. We need it to figure out the cause of the BSOD.

 

Hi DerSenpai,

Welcome to 10Forums *Smile

Unfortunately, the dump doesn't contain much information.
I do have a few suggestions though.
- Check Samsung for SSD firmware updates
- Run chkdsk on all partitions with the /r parameter, if asked to force unmounting press Y.

Please run CPU-Z | Softwares | CPUID, open it and make screenshots of the following tabs

• CPU
• Mainboard
• Memory
• SPD*
• Graphics

*SPD shows the details of each stick, you can show the details by choosing different slots in the left upper corner.
Please make screenshots of each stick.

Please post each screenshot in your next reply/replies.

 

Hi axe0,

thank you for your fast reply *Smile. Before installing windows 10 again I saved most of my minidumps. I don't know if they contain useful information, but i attached them anyway.

I will run chkdsk before going to bed. The RAM doesn't get recognized fully by my motherboard, but I thought it is better to avoid any tweaking. But here are those CPU-Z screens:





















I will also look into firmware updates for my ssd.

 

Is it a specific slot where your motherboard doesn't recognize the RAM module?

 

Are you overclocking your CPU or using an XMPP on your RAM?

DDR4 running at 1066MHz is not standard. Neither is a 1700x running at 2Ghz. Something is under-volting your system.

 

1066 needs to be multiplied, CPU-Z shows my system running at 1200MHz but I know from the BIOS it runs at 2133/2400.

 

Hello,

maybe that was bad wording on my part. While saying "doesn't get fully recognized" i meant the mhz and latency may be a bit of, as in my RAM just runs at 2132mhz and not 2400.

Iam also not undervolting my CPU. As far as I understand it is set to auto, so it will automatically clocks down if it isn't needed and applies the right amount of voltage on its own:






I did chkdsk /x /f /r and it reported no errors in the event log (for some reasons the log is in german and not english, so you have to trust me on this).

I also did hdtune for my SSD:












Iam running the error scan right now for the hdd but it takes some time. Will post the results later.

Yesterday I got an bsod while trying to install my realtek audio driver. For some reason the minidump was empty, but I saved the memory.dmp file ,7-ziped it and put it into my onedrive:

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Today I also got another bsod, which I will attach on my post.

I will also test my gpu and cpu in the next couple of day and post the results here.

Is there anything useful in those new dump-files?

 

Chkdsk should always report no errors, that means it has finished and repaired anything that needed repair.
If chkdsk reports errors, it means something is severely wrong or chkdsk couldn't save the log.

Please upload the chkdks log *Arrow Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums

 

Okay I put the event log into google translator:

File system on C: is checked.
The type of the file system is NTFS.


A disk check is planned.
The disk check is now running.




Phase 1: The basic file system structure is investigated ...
225024 records processed.
File verification finished.
6342 large records processed.
0 invalid records processed.


Phase 2: The file name association is investigated ...
292974 Processing index entries.
Index check finished.
0 non-indexed files.
0 non-indexed files restored.

Phase 3: Security Descriptions Are Investigated
542 unused index entries from index $ SII of file 0x9 are cleared.
542 unused index entries from index $ SDH of file 0x9 are cleaned up.
542 unused security descriptions are cleaned up.
Verification of the safety descriptions ended.
33976 Files processed.
CHKDSK reviews USN journal ...
41683808 USN bytes processed.
The review of the USN Journal has been completed.


Phase 4: Searching for faulty clusters in user file data ...
225008 Files were processed.
Date data check finished.

Phase 5: Searching for faulty, free clusters ...
23562010 processing free clusters.
Verification of free space is finished.

File system was checked, no problems detected.
No further action required.

134217727 KB Disk space on the disk total
39517796 KB in 148311 files
114060 KB in 33977 indexes
0 KB in bad sectors
337827 KB used by the system
65536 KB from the log file
94248044 KB available on the disk

4096 bytes in each allocation unit
33554431 Allocation units on the data carrier as a whole
23562011 Allocation units available on the data carrier

Internal information:
00 6f 03 00 f4 c7 02 00 1a dc 05 00 00 00 00 00 .o ..............
90 00 00 00 b9 15 00 00 00 00 00 00 00 00 00 00 ................

The check of the data carrier has been completed.
Please wait until the computer has restarted.

 

Don't forget the other partitions *Smile

 

Okay I let chkdsk run for my other partitions:

Chkdsk was executed in read/write mode. Checking file system on D:The type of the file system is NTFS.Volume label is Volume.Stage 1: Examining basic file system structure ... 8448 file records processed. File verification completed. 0 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 9344 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ...Cleaning up 3 unused index entries from index $SII of file 0x9.Cleaning up 3 unused index entries from index $SDH of file 0x9.Cleaning up 3 unused security descriptors.Security descriptor verification completed. 448 data files processed. Stage 4: Looking for bad clusters in user file data ... 8432 files processed. File data verification completed.Stage 5: Looking for bad, free clusters ... 72856579 free clusters processed. Free space verification is complete.Windows has scanned the file system and found no problems.No further action is required. 353588223 KB total disk space. 62075312 KB in 4735 files. 1404 KB in 450 indexes. 0 KB in bad sectors. 85187 KB in use by the system. 65536 KB occupied by the log file. 291426320 KB available on disk. 4096 bytes in each allocation unit. 88397055 total allocation units on disk. 72856580 allocation units available on disk.

Chkdsk was executed in read/write mode. Checking file system on E:The type of the file system is NTFS.Volume label is Volume.Stage 1: Examining basic file system structure ... 3584 file records processed. File verification completed. 0 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 4510 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ...Cleaning up 11 unused index entries from index $SII of file 0x9.Cleaning up 11 unused index entries from index $SDH of file 0x9.Cleaning up 11 unused security descriptors.Security descriptor verification completed. 463 data files processed. Stage 4: Looking for bad clusters in user file data ... 3568 files processed. File data verification completed.Stage 5: Looking for bad, free clusters ... 484088466 free clusters processed. Free space verification is complete.Windows has scanned the file system and found no problems.No further action is required.1953382399 KB total disk space. 16898616 KB in 2963 files. 764 KB in 465 indexes. 0 KB in bad sectors. 129151 KB in use by the system. 65536 KB occupied by the log file.1936353868 KB available on disk. 4096 bytes in each allocation unit. 488345599 total allocation units on disk. 484088467 allocation units available on disk.

Also here are the HDTune results for me HDD:












I also updated my gpu driver, as the manufactorer released a new version. Today I got 2 more bsods and maybe there is anything interesting in my event logs. Because of that I let the log collector do its work again and uploaded the results.

I Installed the Samsung Magician Software and it says the ssd firmware is up to date.

Is there anything interesting in my 2 previous and those 2 new dump-logs?

 

Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

 

Hello,

I may have finally figured out the problem:

I didn't put much attention to my RAM settings when I noticed my motherboard didn't recognize my ram as 2400mhz but only as 2133mhz.

But that wasn't the only thing it adjusted wrong. The motherboard also set the 16-16-16-16 timings of my RAM to 15-15-15-15 all while keeping the standard voltage at 1.2 V.

On saturday I set the correct timings manually and since then I haven't gotten any BSOD or CTD. I will continue to test the PC over the course of the week and I will mark this thread solved on the next weekend if no new problems have occured.

Thank you axe0 for your time and that you tried to help me!