Windows 10: BSOD - Crashing way too frequently in the past few weeks...

As your temperatures are quite low and stable you can run for a lot longer if you wish. It is strange that you have not had any BSOD considering they happened every few minutes before.

 

Funny you should mention the BSOD. After I closed everything, the BSOD showed up again. *cry

I got the recent DUMP file reviewed and it's the same old:

FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE
BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE
PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_PROCESSOR_MAE
FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_mae

Could this be related to the i7-6700k that can't display in the native 3840x2160 resolution? Should I install the GTX-980 card in my computer and validate that it's not the dedicated GPU issue, rather CPU only?

 

I'm not sure that fitting the new graphics card will help, I think it is a CPU core fault that gets corrected most of the time according to your event logs but not always - hence the BSOD.

Can you check that all the voltages are running stable for the CPU? I assume you are not overclocking in any way? Make sure that any turbo boost settings are off for the purposes of testing.

 

Hi PiCASSiMO,

Welcome to the 10forums *Smile

Please boot in the BIOS and let us know what the 3.3v, 5v and 12v values are.

I have analyzed the dumps, unfortunately they are of no use because the reported error by the CPU is unknown.
Attempting to dump the stack reveals also nothing.
Code: =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe00051b40138 Section @ ffffe00051b40280 Offset : 600 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Unknown (Proc 2 Bank 0) Status : 0xf200004000010005[/quote] Interesting to see, the system up time is almost always a max of 10 minutes, this means that either a service at boot is causing the crashes or we're dealing with a faulty hardware.
The services at boot need a few minutes after Windows has loaded for initializing, but the services are in the POST of the boot process.
We can try a simple diagnostic test to find out whether we're dealing with hardware or a service *Smile
Code: System Uptime: 0 days 0:06:34.723 System Uptime: 0 days 0:02:15.750 System Uptime: 0 days 0:02:20.525 System Uptime: 0 days 0:02:29.817 System Uptime: 0 days 0:04:48.045 System Uptime: 0 days 0:02:00.016 System Uptime: 0 days 0:01:36.670 System Uptime: 0 days 0:02:10.295 System Uptime: 0 days 0:10:55.950[/quote] Please remove / disable items from the startup in taskmanager
These programs could interfere with the boot process giving you trouble and increase the boot time.






Diagnostics Test

Clean boot
Please try the following:

• Open taskmanager
  • Go to the tab startup
  • disable everything
• Search msconfig and open it
  • Go to the tab services
  • Check 'hide microsoft services'
  • Uncheck all other services
  • Click apply and click ok
• Reboot if asked

See if the problem persist, if the problem does not persist enable in the startup tab in taskmanager 1 item and in the services tab in msconfig also 1 service, reboot and see if the problem persist. Keep doing this until you find the culprit or there is nothing left.
If the problem still persist, try booting in safe mode and see if the problem still persist.

Please note, the GPU is NOT loaded in safe mode, if the CPU itself is not faulty the GPU part could be.

 

As you wrote this, I had installed the GTX 980. And you were correct, the BSOD came one shortly after installation. Unfortunately for me, I've got a 980 that I'm doing an RMA with. One of the fans is unbalanced and causing contact with the plastic frame, resulting in very annoying and loud noise.

 

Attached is the screen that you are probably requesting... in addition, I've taken several more in the attached ZIP file.

+ 3.3v = 3.383 V
+5v = 5.100 V
+ 12V = 12.240 V

Thank you.

 

Please follow the clean boot instructions as detailed by @axe0

It is not necessarily the CPU that is faulty, the CPU detects and reports the faults but they could and most likely are caused by something else.

 

Please try the following:

• Open taskmanager
  • Go to the tab startup
  • disable everything
• Search msconfig and open it
  • Go to the tab services
  • Check 'hide microsoft services'
  • Uncheck all other services
  • Click apply and click ok
• Reboot if asked

See if the problem persist, if the problem does not persist enable in the startup tab in taskmanager 1 item and in the services tab in msconfig also 1 service, reboot and see if the problem persist. Keep doing this until you find the culprit or there is nothing left.
If the problem still persist, try booting in safe mode and see if the problem still persist.

Please note, the GPU is NOT loaded in safe mode, if the CPU itself is not faulty the GPU part could be. First, just like PhilC43, I want to give you Axe0 thanks for your your help.

Second:

• I've initially started with the Taskmanager, and have disabled everything. Rebooted. Then within a short time frame got the BSOD.
• I've then gone to MSConfig and then removed all but the Microsoft sources. Rebooted. Then again, the BSOD showed it's ugly head.
• I continued with running the computer in Safemode (Option 5 with network), which actually never gave me wireless network connection, so I opened up a few programs that could open in the Safemode state and then managed to run a MKV file for about 1.5 hours (without sound). It turned out that nothing happened in Safemode.
• I rebooted back into standard mode, and before I got a chance to enter my password the BSOD came crashing in. This happened at 6:17pm my local time, so I've gathered this dump and a few others in the past day since I've uploaded my original ZIP file. I've also gathered new EvenLogs, where I believe the last dump file (070916-4984-01.dmp) started just after Event[9891]. I'm hoping that you guys could review this updated information and let me know where I should go next (outside of trying to get the CPU RMA'd with Intel).

 

When you restart system in SMWN on the login screen you will find wifi icon on the right bottom of the screen. Try to connect from there. You will still see a red x though the wifi is connected.

 

Download whocrashed software and analyze the issue. It gives you the exact error message. I feel it might be an issue with video drivers.

 

@pranay1988, WhoCrashed is a useless program, it cannot analyze the dumps like a human being can.

Please read the post, wifi connection in safe mode is very limited, there is not much possible.
@PiCASSiMO:





STOP 0x124 Troubleshooting

Read carefully before proceeding.

*Arrow Chkdsk Log in Event Viewer - Read in Windows 10 - Windows 10 Forums



Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the error scan,
• the health,
• the benchmark incl. following
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

FOUR

GPU TEST


Run FurMark - GPU Stress Test - Windows 10 Forums



Note Run Furmark for around 30 minutes.


Warning Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.
Make a photo of the result and post it.

In Furmark you can find a tool called 'GPU-Z' (if you want to install GPU-Z is up to you), when GPU-Z is open click on the 'Sensors' tab, on this tab you can monitor

• the frequency of the GPU,
• the GPU memory clock,
• the temperature,
• the power,
• the load on the GPU,
• Etc.

I would like you to make a screenshot of GPU-Z after you have either cancelled Furmark for any reason or Furmark is finished, post this screenshot in your next reply with the result of Furmark.

 

I've decided to give this a chance and here's the conclusion (attached is the complete output). So what is this "intelppm.sys" file that could possibly be the culprit?

For a while now, I was thinking of reformatting my SSD and installing from scratch with Windows 10 and their latest USB ISO. I've used an old October 2015 USB ISO, and from the beginning, it's been buggy (and recently the BSOD) compared to the other Windows 10 computers around my house.

Conclusion
49 crash dumps have been found and analyzed. Only 10 are included in this report. 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:

intelppm.sys (Processor Device Driver, Microsoft Corporation)

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.

 

It is a driver issue. May i know the manufacturer name of your computer

 

It's a custom build.

System Spec Computer typeC/Desktop
OS: Windows 10 Pro
CPU: i7-6700k
Motherboard: GIGABYTE GA-Z170X-UD5
Memory: G.SKILL Ripjaws V Series 16GB
Graphics Card(s): Intel HD Graphics 530

 

Chipset and video drivers needs to be updated. If the issue persists create a new user account with admin rights n check.