Windows 10: BSOD at random times, mostly when playing. Various error codes

So, new computer, was using Windows 7 and getting BSODs constantly. So I decided to make a clean install with Windows 10 and thought the issue was resolved, clearly not the case.

I will be uploading the last mini dump, but let me already tell you that more than one error code happened (more than one BSOD).

I used the forum's guide to collect the mini dump information. The dump archives I got from the Windows folder are huge, I guess we are not going to use that, am I right?

I am suspecting it to be some Hard Disk issue or RAM memory, but I am not an expert. Actually, I am really frustrated and lost here.

One of the messages I could capture was "Kmode_Exception_Not_Handled".

Attachment 27981

Thanks, hope to hear from you guys,
Rogério.

:)

 

Multiple random errors of different kinds when using any Browser in Windows 10

I get these errors at random times at the bsod when using any of my 3 browsers(mostly) using windows 10.

I have what I think are all my drivers up to date.

Bad Pool Header

Memory Management

Kernel security check failure

IRQL not less or equal

Page fault in nonpaged area

PFN list corrupt

any suggestions?

 

Windows 10 BSOD (driver irql, clock watchdog)

I have a relatively new system running W10. When I first got it around 6 months ago it would BSOD and I thought nothing of it as the hardware was brand new and so was the OS, and as such expected a few teething issues.

However, the issues still continue. My PC BSODs at various times, specifically : while playing games (Rust and Diablo, but also a few others), and also more occasionally at boot. (Causing the system to reboot again).

While playing games it BSODs frequently, often hourly or even more frequently than that.

These BSODs are mostly: driver irql_less_or_not_equal, or clock watchdog timeout.

All my drivers are up to date, and so is my windows installation.

I've tried running stress tests and memory diagnostics, and it doesn't seem to be a hardware fault.

What do I do?

 

Hello rogeriop, welcome to the forums. I need you to do a few things for me. Please look at the bottom left of your last post and click on 'My System Specs', there is a link there that says edit system specs. Please fill out your system specs as completely as possible, including the Manufacturer and Model of each component. Please be sure to include your PSU and CPU cooler.

You talk about many BSODs and only have 2 from today. If you ran the BSOD Posting instructions, please upload the entire folder it creates. Those dump file did not tell me a whole lot. I hope several together may tekk me more. These are the results.

Code: Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff8002ff5d119, ffffd00020fe6bb0, 0} Probably caused by : hardware ( win32kfull!xxxRealSleepThread+355 ) Followup: MachineOwner[/quote] Code: APC_INDEX_MISMATCH (1) This is a kernel internal error. The most common reason to see this bugcheck is when a filesystem or a driver has a mismatched number of calls to disable and re-enable APCs. The key data item is the Thread->CombinedApcDisable field. This consists of two separate 16-bit fields, the SpecialApcDisable and the KernelApcDisable. A negative value of either indicates that a driver has disabled special or normal APCs (respectively) without re-enabling them; a positive value indicates that a driver has enabled special or normal APCs (respectively) too many times. Arguments: Arg1: 00007ffd73ea372a, Address of system call function or worker routine Arg2: 0000000000000000, Thread->ApcStateIndex Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable Arg4: ffffd00026199ec0, Call type (0 - system call, 1 - worker routine)[/quote] Please tell me the process you used to upgrade the system and did you upgrade to the new 10240 release?

Please, right click the start flag in the bottom left and select Command prompt administrator. Provide administrator permissions and in the window that opens copy/paste this into the window sfc /scannow and press enter. It will only take a few minutes to run. We want it to say no integrity violations were found. If it says files were found that could not be repaired. close the window, reboot and run it again. You may have to run it 3 times before it can fix the files, if it can.

Also, please tell me how many hard drives you have and how much free space is on the system drive. if you have more dump files, please run the posting instructions again and upload the entire zip folder it creates.

 

Ok, I will do these tasks, but I can only do that on the weekend, so please, be patient!

Thanks!

 

Take your time. I'm in no hurry. Whenever you have time, just let me know the results.

 

Let me explain that though I had many BSODs, I only gathered the last one's dump file (from last week), so I will be posting more of them as they happen (The Dump files get overwritten as a BSOD happens, right?).

OK!

Step 1 (System Spec) - System Spec updated to the maximum of information that I could gather!

Step 2 (Windows Installation) - I did a clean installation, formating my partition that contained Windows 7 and installing Windows 10 through the Media Creation Tool x64.

Step 3 (sfc /scannow) - I will be performing these as I end the post and I will edit the info here.

Step 4 (Hard Drive) - I have just one Hard Drive, which contains 1 TB of space. The partition in which Windows 10 is installed has 80GB of space, which 56,7GB are free space.

Hope to hear from you!

Edit1 - So I ran Scannow and I got errors, the system said that they made a Log, it follows: Attachment 29362

Edit2 - Ok, second Scannow found no errors, now I will be waiting!

 

Looks good. I'll look at the files tomorrow.

 

Please run the BSOD Posting instructions again for me. BSOD - Posting Instructions

Things are new in Windows 10, so we are all still learning. Kernel memory dumps will usually overwrite the last one. Small memory dumps won't. Please make sure you are configured for Small Memory dumps. This will tell you how. We prefer small memory dumps, for several reasons. https://www.tenforums.com/tutorials/5...dows-10-a.html . Please post the entire zip file.

It is good that you successfully completed the sfc scan. Maybe the errors it fixed will solve your problem. Also, how much free space is on your hard drive? Also, please run Seatools. This is a Windows 7 tutorial but I am sure it will work the same on Windows 10. Please use the DOS version if you can. You get much more accurate results that way. Please run the short and the long test. http://www.sevenforums.com/tutorials...use.html#Part2

I know you mentioned booting into Safe Mode. How did the computer run in Safe Mode? Did you have any BSOSs?

 

About the Hard Drive: The partition in which Windows 10 is installed has 80GB of space, which 56,7GB are free space.

I am trying to aplly the configuration to not overwrite the small dump files, but the check box is unreacheable, I will follow the instructions again and post the results here, I will be editing it here soon. I will also run the SealTools.

I didn't mention booting into Safe Mode though.

Edit 1 - Right, do I need to burn a CD to use SeaTools or is there a way to put it on a USB?

 

I'm not sure, but Rufus will usually do most things.

 

BTW, just so you know. If you edit a post, I won't know about it. But, if you make a new post, I will be notified.

 

Ok, so, I am really not being able to run SeaTools, Rufus tells me that the ISO I have is not compatible and Win32DiskImager looks like it creates a corrupted USB. Any other tip for me? I will try a little bit more

About the BSOD dumps, here it is again:

Attachment 29510

As I see, this batch contains 2 small dumps.

I am trying to configure it to NOT overwrite the future dumps.

 

Here it is on the dump configurations:

Attachment 29516

I can't unmark that, any idea?

 

Ok, I managed to disable the overwrite option!

I will use the computer a bit to see if I get a BSOD!

Hope to hear from you.