Windows 10: BSOD Errors after installing Windows 10: IRQ Not Equal and others

Since upgrading to Windows 10 from Windows 7, I have experienced BSOD (or in Windows 10's case, sad face) errors with increasing frequency, to the point that I am considering reverting back to Windows 7.

What happens? (one of the following):

• Computer screen/everything freezes and emits a hum/buzzing noise; or
• Blue sad face screen appears identifying unspecified error, indicating that the computer will reboot (but nothing happens); or
• Blue sad face screen appears identifying IRQ-Not_Equal error, indicating that the computer will reboot (but nothing happens); or
• Blue sad face screen appears identifying (something like) Execute-Non-Execute error, indicating that the computer will reboot (but nothing happens).

I am then forced to turn the power bar off and then back on in order to restart the computer.

In my own (initial) attempts to address this, I did check for a memory problem (answer: no) and I updated my graphics driver. The problem has persisted - and has possibly become more frequent.

As directed, I downloaded and ran the diagnostic program. The resulting file is attached.

Any help fixing this would be MUCH appreciated. I would prefer not to revert to Windows 7 OR buy a new computer (although it might be time to do do...)

:)

 

Getting random BSOD after Windows update

Some of the bsods were "critical structure corruption" " page file in non paged area" "irq not less or equal" "service exeption" there are loads but I cant remember them

• 
  

 

BSOD Help

Hi Deepkia,

Thanks for your response.

I built the pc but here are some details:

MB: Gigabyte GA-78LMT

CPU: AMD FX 6350

8GB ram

AMD R9 200 Series

Sandisk extreme pro 250gb ssd

WD 500GB HDD

I am receiving several different BSOD errors:

During installation

0x8007025D

During normal use ( I was able to successfully install windows 10 after several tries, but still get BSOD during use)

Kernel security check failure

0xA irq not less or equal

system thread exception error

I am able to boot in normal mode but eventually will get once of the errors above during use. I tried uninstalling all unnecessary hardware: extra hdd, video card, optical drive.

As suggested I followed the Troubleshoot blue screen errors article instructions but have had no success. Win 10 is successfully updating but the BSODs continue.

 

Unfortunately there are no crash dump files in the attachment. There is also very little information in your system specs. Please fill these in as much as you can - see here for a tutorial.

Check that you are setup to save the crash dump files and please redo the log file collector when you get another BSOD.

 

Can you please indicate what kind of dump files are required? Right now, my computer would appear to be set up to create the kernel ones, so I don't know why it would not have done so. (Each time it hangs, however, it fails to reboot/restart on its own, so perhaps that is why).

 

I would go for the automatic memory dump which is the default setting for W10.

 

Attached is the file generated following the most recent crash.
I suspected either Play TV and/or Raptr of creating a problem. As I don't need either, I have uninstalled both.

 

Once again the crash dump failed. There are no records of any BSOD in the dxdiag.txt either.

Code: Event[8534]: Log Name: System Source: volmgr Date: 2016-08-25T17:12:55.600 Event ID: 46 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: User-PC Description: Crash dump initialization failed![/quote] Sometimes this can happen if your paging file is too small. It needs to be large enough to capture the memory data for the crash. Might be worth checking this in Advanced System Settings.

Attachment 98198

 

Mine is set at 1856 MB. I presume that is ok. I have tried again.

 

Still no crash dump files *Sad

Do you have your settings as shown below?

Attachment 98263

 

Where might I find that?

 

Type Advanced in the search box and select Advanced System Settings and in the Start-up and Recovery section click on Settings

Attachment 98269

 

The only thing that was different was that the restart button was checked - I have now unchecked it.

Yet another crash - yet another file.... (This time the blue screen said that it was a KMODE something-or-other error and the computer rebooted itself without me having to turn the power off and then on again.)

One thought: could it be Stream? It has a habit of updating - perhaps that is the cause?

 

Sorry for the delay in responding, it has been a holiday weekend in the UK. *Smile

There is a crash dump file this time and it has revealed a few things that I was not aware of from your system specs.

Firstly your BIOS is very old and it is possible that there may not be an update as I doubt that Gateway support this model or are even in existence anymore.
Code: BIOS_VERSION: P01-A0 BIOS_DATE: 03/19/2010[/quote] Your memory is made up of two matched pairs 2x4GB along with 2x2GB, these pairs need to be in the matching slot colours or there will be problems since they are of different types. Please refer to your motherboard manual to make sure they are correctly paired.
Code: [Memory Device (Type 17) - Length 28 - Handle 0011h] Physical Memory Array Handle 000fh Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 4096MB Form Factor 09h - DIMM Device Set [None] Device Locator DIMM0 Bank Locator BANK0 Memory Type 18h - Specification Reserved Type Detail 0080h - Synchronous Speed 1333MHz Manufacturer 80CE Serial Number Asset Tag Number Part Number M378B5273BH1-CH9 [Memory Device Mapped Address (Type 20) - Length 19 - Handle 0012h] Starting Address 00600000h Ending Address 009fffffh Memory Device Handle 0011h Mem Array Mapped Adr Handle 0010h Partition Row Position 01 Interleave Position [None] Interleave Data Depth 01 [Memory Device (Type 17) - Length 28 - Handle 0013h] Physical Memory Array Handle 000fh Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 4096MB Form Factor 09h - DIMM Device Set [None] Device Locator DIMM1 Bank Locator BANK1 Memory Type 18h - Specification Reserved Type Detail 0080h - Synchronous Speed 1333MHz Manufacturer 80CE Serial Number Asset Tag Number Part Number M378B5273BH1-CH9 [Memory Device Mapped Address (Type 20) - Length 19 - Handle 0014h] Starting Address 00000000h Ending Address 003fffffh Memory Device Handle 0013h Mem Array Mapped Adr Handle 0010h Partition Row Position 01 Interleave Position [None] Interleave Data Depth 01 [Memory Device (Type 17) - Length 28 - Handle 0015h] Physical Memory Array Handle 000fh Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 2048MB Form Factor 09h - DIMM Device Set [None] Device Locator DIMM2 Bank Locator BANK2 Memory Type 18h - Specification Reserved Type Detail 0080h - Synchronous Speed 1333MHz Manufacturer 80CE Serial Number Asset Tag Number Part Number M378B5673FH0-CH9 [Memory Device Mapped Address (Type 20) - Length 19 - Handle 0016h] Starting Address 00a00000h Ending Address 00bfffffh Memory Device Handle 0015h Mem Array Mapped Adr Handle 0010h Partition Row Position 01 Interleave Position [None] Interleave Data Depth 01 [Memory Device (Type 17) - Length 28 - Handle 0017h] Physical Memory Array Handle 000fh Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 2048MB Form Factor 09h - DIMM Device Set [None] Device Locator DIMM3 Bank Locator BANK3 Memory Type 18h - Specification Reserved Type Detail 0080h - Synchronous Speed 1333MHz Manufacturer 80CE Serial Number Asset Tag Number Part Number M378B5673FH0-CH9[/quote] The crash was probably caused by a partition manager driver:
Code: BugCheck 1E, {ffffffffc000001d, fffff8004afa74af, ffffe001f8fed080, 0} Probably caused by : partmgr.sys ( partmgr!PartitionIo+1c6 )[/quote] I'm not sure if this is a "one-off" or if all your crashes have been caused by this - we would need to see a few more crash dump files to be sure. This is a windows system file so all you can do is run the SFC command to check all your system files are correct.

Let me know how you get on.

 

Thank you very much for your reply and your efforts. No apologies are necessary, as to my knowledge I'm not paying you for this *Smile

I thought that I might be out of the woods, as I had no BSODs over the weekend; but then I got home from work today and experienced another. I am attaching the file to see if we get a consistent problem showing up.

• If it is a BIOS problem it could be God telling me to get a new computer.
• If it is the memory configuration that might be pointing to same solution, as I am reluctant/averse to opening up my box myself to look. (I suppose that I could take it to The GeekSquad or a similar outfit to take a look if you think that there would be a point in doing so.)
• I will try the SFC command when I have time.

Thanks again for all of your help.