BSOD codes 0x19 and 0x7E Help Please. Dump Files Included.

[iiXeno]

BSOD codes 0x19 (BAD POOL) and 0x7E Help Please. Dump Files Included.

Just wiped my friend's computer yesterday because he said he was having problems with crashing in games and not connecting. Was working good from yesterday to a little bit today, until I started to open up a new game I installed on it and it crashed with 0x19. I then searched and looked and eventually got to some answer saying to enable "verifier.exe" in cmd.

So I did that and restarted and then upon logging in I got 0x7E and restarted again and same thing happened upon logging in. So now I'm in safe mode and need some help. I have included the text documents for the dump files. Also, Firefox crashes OFTEN.

Thank you!

EDIT: Okay so verifier.exe actually causes the 7E code upon startup, I disabled it in safe mode and so we're back in the clear for that one, but 0x19 is still a problem.

Also if verifier wont work and it causes 7E, that's still a problem, does that narrow down solutions or say anything about the computer?

 

[ICIT2LOL]

Hello and welcome iiXeno now first up we need the specs of that machine if you can get this machine to work for just a while see this
Now before we can help we do need to know what is in your machine so please do this System Info - See Your System Specs
or either enter the specs of your system in your forum profile the specs will appear when we click on that little box bottom left of the post screen it is for me the preferable option as it is easy. As you may appreciate it is very hard when you don’t know what one is working with for example a diesel or petrol engine.
*(pretyped to save time)

& these

Dump Files - Configure Windows to Create on BSOD
&
Blue Screen of Death (BSOD) Posting Instructions
as the texts you have sent do not tell us much at all.

 

[iiXeno]

Updated specs and attached proper dump files.

 

[ICIT2LOL]

Updated specs and attached proper dump files.

Ok got the specs but no dump files. Now that is a nice rig you have there and have there been any hardware changes as well as doing a clean install?

Now another thing you would best off doing is updating the drivers for the machine from the manufacturers
Support For Z97 GAMING 5 | MSI Global | Motherboard - The world leader in motherboard design 64

Personally I would do them all as most are not that large a download or install. Now if you cannot download on that machine you may like to try what I do and that is download any drivers onto a dedicated stick and install them from that onto the machine. That way it avoids any issues with downloading and the stick will always come in handy for another day
Now once the machine is up and running it just remains to get those dump files because both of those error codes you quoted are usually driver issues though the dumps may actually show up other problems in addition to those codes.

After you have got that fixed then it would be a good idea to do these too
SFC /SCANNOW Command - System File Checker
Disk Check < if necessary include the /f switch and if this does not make any improvement then just run this switch instead /r in the command line as per Option2
Run these in safe mode and the sfc often best run for two to three runs – you can leave out the /r switch in ckdsk if you feel it not necessary

 

[iiXeno]

They should be in there, I clicked on the file and it opened up and I seen the DMP files.

I also JUST added one more in there because I got another blue screen with a different code which happened after I did a long check disk session. The computer started up and about 5 minutes into doing whatever I got hit with a 0x24 code for the first time. So that's in there too.

After finishing that last period in the middle of writing this, I just got hit with ANOTHER BSOD with a 0x1 code APC Index Mismatch I believe it said.

Also, no hardware changes. I don't get how it could be drivers though, all I did was add the necessary drivers from the motherboard disc after the clean wipe.

I just tried installing 4 of them and I got errors on all of them. I'm in safe mode, does that matter?

 

[ICIT2LOL]

Ok I mentioned updating the drivers only because the original dumps were referring to drivers and get them from the manufacturers because more often than not the software disk that comes with boards / machines contain drivers that are more likely than not out of date when you buy those products. Myself I never rely on those disks unless I am really stuck.

Now as for installing the drivers via safe mode I have never had to resort to that but I have sen that the basic ones like chipset etc can be installed. The other drivers such as the GPU etc might be a different kettle of fish and best installed when the system is up and running in a "normal" fashion. I would if it were me download those drivers to a stick then it is an easy install but he choice is yours. I know this is getting tedious but it seems to me that getting all these different error codes that the machine is well out of kilter.

The dump files can you please re send them because the error codes are not the only info in the dumps that are important for getting clues on what the problem/s are.

Now you mentioned you wiped the drive before you reinstalled just how did you do that as I prefer to use clean in DISKPART or the wipe in Partition Wizard and not just rely on a format.

 

[iiXeno]

Could it be faulty motherboard possibly? When I said wipe, I mean I just reinstalled windows. What about BIOS drivers? I just wiped this PC on Wednesday and it's out of kilter already lol. He has had these problems since it was first built a couple years ago, he finally sent it to me, and I didn't think it was going to be this defective.

I want to mention also that in the device manager that I have one caution sign and it's for PCI Simple Communication Controller. What driver would I download for that?

I'm thinking about wiping it again, but this time I'll have the latest drivers from the website ready on USB instead of installing from the disc.

EDIT: After re-installing today I got another '19' code. I installed all the latest drivers except any BIOS ones, never do anyway. Thinking about swapping motherboards =/

 

[ICIT2LOL]

Ok my friend now when I say wipe I mean to clean the drive thoroughly not just a format. That means whatever method you use ie a DISKPART clean or the wipe function in Partition Wizard it means the clean or wipe actually writes zeros to the entire disk and you the format it and then install onto it.
See this for the DISKPART Disk - Clean and Clean All with Diskpart Command

and this for the Partition Wizard Best Free Partition Manager for Windows | MiniTool Partition Free < see my pic for that - keeping in mind the interface may be a little different now because that a pic of the older version but the principle is the same.

Now I use the DISKPART mainly because it is reasonably quick but very thorough so just be sure to save any data before you use it or the wipe.

Just so you know this will need the use of a second machine because the wipe or DISKPART function cannot carry out the clean on a running OS for obvious reasons. I use a dock to USB or a SATA to USB adaptor and you can of course connection it internally to a working machine - the choice is yours personally I prefer using the dock (much less fiddling around).

Now the mother board well I suspect not likely but possible and I think more likely the drive if there were an external issue.

Another cause may be the installation media of course just remind me of where it came from please because if need be the install can be done using an official Microsoft ISO as long as you have a genuine activation code for the copy you are installing if so I can link that site. It just means downloading the ISO and burning it to a bootable disk.

The BIOS I would not touch just yet because making changes to it can have rather disastrous consequences ie bricking the board!!

 

[iiXeno]

Well I got ancy yesterday, and I just said f*** the bs, I just got him a 1tb SSD and so I will be using that brand spanking new with no problems.

I noticed when I install the OS on his SSD and then I make his HDD the default drive in the registry settings, there is still some issues, some things still just insist on installing in the C drive, or if I install them on the D drive, but for some reason they dont work it will say something like "D: blah blah blah specified path does not exist" and then the shortcut will lose its picture and when I go to the properties it will say startup in c drive but the target is in d drive, simple fix I know, but its just little things like that. Also, the web browsers keep crashing on this computer.

So I'm just going to put it all on one SSD and that should narrow it down or hopefully fix issues with the 19 code.

 

[ICIT2LOL]

That's good mate I would have done exactly the same because there is probably something quite wrong with the original drive and I think that once you have the system up and running on the SSD then the ?spinner I am assuming it is - can be cleaned and used as extra storage either internally or as an external - maybe good for imaging even - a good backup method for the system if you want of course.

So I would be interested in how the new install boots and you need to make the SSD the default boot in the BIOS or yes making the old drive the default will cause issues because it will look for the Windows boot instructions on it and may not necessarily go on to look for the boot on the other listed drives.

I would wait until that other drive is cleaned as I mentioned above and in the boot setup just make it last but you should not have to do that anyway. My desktops are all setup for the OS drive to boot first then the optical then whatever is in the listings next.
What you may see in the boot order is "Windows Boot Manager" it needs to be set as the first boot device. In any case it doesn't need to be installed or added to the machine until it has settled down. Plus I would also put off transferring anything from the old drive until the system is like I mentioned settled down.

Now the updates bless their little cotton socks will take a very long time and this may be of use to you.
Four steps to reduce the pain of Windows 7 installations using cumulative updates - Tech Pro Research

 

[iiXeno]

Well it's not the hard drives. =/

Firefox still crashing a bunch, installing software sometimes gives me errors and corrupt messages windows updates failing to install half the time, same old news. Just waiting on ol' code 19 to really confirm that nothing has changed.

I'm still hanging onto my motherboard theory based on the inconsistencies of the software crashes and installations.

 

[ICIT2LOL]

Ok well the bugcheck is still telling me that it could be a disk problem but there are other possibilities such as memory issues, problems with any AV you have installed, or even file corruption even though you have just installed the OS again.
I am also assuming that the new drive is the only drive connected up as of now?

[COLOR="Red"]BugCheck 24[/COLOR]

So I think we had better start with these please before we move onto testing the RAM because that takes a long time to do. Plus what AV is there on that drive if any at all?
SFC /SCANNOW Command - System File Checker
Disk Check < if necessary include the /f switch and if this does not make any improvement then just run this switch instead /r in the command line as per Option2
Run these in safe mode and the sfc often best run for two to three runs – you can leave out the /r switch in ckdsk if you feel it not necessary

 

[iiXeno]

Yeah I left the other drives disconnected and only the SSD one up and running. I did windows memory diagnostic a few days ago, it was all good, I don't know if that does a good enough job. I even swapped them to the other slots they were not using and they still work. There was no AV installed after OS installation today, but the problems still persisted.

 

[ICIT2LOL]

Ok my friend now I am not a great fan of the Windows memory test feature it does not cut the mustard with me and a lot of the others. The only memtest we recommend is linked in this

Now to make absolutely we are on the same page the memtest linked here is the only*one we recommend and it MUST be run for at least 8 passes or you may as well not bother. It is rather lengthy and best left for a downtime for that machine - overnight is good. Having said that you can stop the test if errors show up while you are around and then it is a matter of tracking down the bad stick of RAM.* RAM - Test with Memtest86+
(This is pretyped to save time)

Just another reminder to that is 8 passes no less it is tedious but if it finds errors with the RAM then it will be a plus because that is quite easy to remedy. Plus it sometimes can be a bad slot but that is quite uncommon but possible.

The AV after the memtest has completed then I suggets you install something MSE is good and there are more here Free Windows Desktop Software Security List - Realtime Protection | Gizmo's Freeware just a tip avoid AVG, Baidu, McAfee, Comodo (only because ti is a terrible nagger) and Ad Aware.
My personal choice would be Bitdefender, MSE, Avast, Avira, Sophos, and Panda in about that order.

 

[iiXeno]

It's not the motherboard, swapped it out, and still problems. I think I figured it out, I may be speaking too early, but I think it's a bad RAM stick. I checked each, first time got a blue screen and firefox crashes, corrupt file messages, but the 2nd stick has been running good with no problems for the 2 hours currently it has been running, only one windows update failed, the rest were successful.

If this doesn't work, the CPU is my last resort. Thanks for trying to help, you were the only one!!

 

[ICIT2LOL]

Ok my friend now just go ahead with the memtest I linked - it does take quite a while to run but if you are righ and there is a bad stick then the errors should come up fairly quickly and in that case you can stop the test. It then remains to test each stick separately to find the culprit stick and replacing it.

Please let us know how it goes.
John