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

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. :)

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

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

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 )

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 :)

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.

And another one

Neither of the last two zip files have had any new crash dump files to analyse.

As an experiment I wonder if you could remove the 2x 2GB memory sticks and just try with the 2x 4GB sticks for a while and see if it makes any difference. Mixing memory of different types has been known to cause problems.

philc43, sorry to barge in, but I would like to suggest the OP that he enables small memory dump instead of automatic.
BSOD Minidump - Configure to Create in Windows 10 - Windows 10 Forums
Let's see if the dumps will be dumps in the logs then :)

softwaremaniac said:

philc43, sorry to barge in, but I would like to suggest the OP that he enables small memory dump instead of automatic.
BSOD Minidump - Configure to Create in Windows 10 - Windows 10 Forums
Let's see if the dumps will be dumps in the logs then :)

I have made that change. We will see if it improves things when/if there is another BSOD. (Naturally I hope that there won't be).

Increasingly I think that I may just have to bite the bullet and get a new computer. After all, I think that I have had this one for YEARS (maybe five or more?)

It's fixable, but yeah, you have a point. Your PC is at least 6 years old, because mine is five years old and it has i7 2700K inside.
But let's not get ahead of ourselves.
Try enabling driver verifier and using the PC, but make sure you create a system restore point and disable the Driver Verifier after it has crashed and post a new zip file.
Driver Verifier - Enable and Disable in Windows 10 - Windows 10 Forums

I ran the SFC command: no errors.

Here's (yet another) file. This time the process was a lot shorter - perhaps because of the change in the dump file?