BSOD increased until stuck on endless loop...

[glenjj]

Hi guys.

I own a bought custom built desktop (had it for quite a few months now), and in recent weeks its slowly started to get more frequent BSOD's, though it's never been the most stable pc anyway..

Here's a rough date timeline with each BSOD BCCode:
25/2 - 1a
1/3 - a
2/3 - 1a
2/3 - 7a
7/3 - a
12/3 - a
12/3 - 24
15/3 - 1a
16/3 - 1a
17/3 - 1a (attached, along with recent "c9" crash text)

I looked for solutions a lot of times but they vary so much.. I did a disk check twice, all came out clean apparently, and today I followed a tutorial to use the "verifier" to check all drivers.
But that's where things got worse, once my pc restarted, and I log in, it crashes almost immediately every single time within 10-20 seconds... and always with a BCCode that I never seen before (c9)
I am currently stuck on safe mode to even write this, doesn't crash on safe mode, but normal it always crashes...
So I'm stuck with a crippled pc and dont know why its stuck in this crash loop :/

I attached a couple recent crash text files, couple photos of the looping blue screen, and the diagnostic zip file.

 

[peebee]

The C9 errors are Verifier doing its work. It's catching bad drivers and bug checking the system. You'll need to turn that off for the BSOD loop to go away. To turn it off, just open Verifier and select "Delete existing settings" from the menu.

Verifier is crashing because a dispatched IRP is not being serviced correctly.

Your other errors are all caused by page faults or trying to free pool that doesn't exist or doesn't have a correct page table entry. These types of transactions are heavily related to memory, so I would suggest running Memtest86+ overnight. You can google and find the download for it pretty easily.

Let us know what happens after you run MemTest.

 

[glenjj]

If its verifier doing its job should I just leave it to continue? does it ever end?
I know you said Verifier is crashing because a dispatched IRP is not being serviced correctly., though I dunno what that means sorry.

But OK I'll turn it off and see how that goes, then I'll run memtest, I have run it in the past and it seemingly passed ok, but that was months ago.

Cheers for the info

 

[peebee]

Verifier is really only used for debugging if you think a problem exists (or to verify drivers you're running play nicely with the kernel). The truth is, sometimes it catches problems with drivers that aren't necessarily fatal. In the case where it's crashing your system it's doing so because an IRP isn't being fulfilled in a timely manner, which is the responsibility of the driver. Driver updates may fix these problems, but I don't believe this is the source of your "normal" crashes. Yours are more centered around freeing address space and irrecoverable page faults.

Hope that helps and I'm interested in what MemTest finds.

 

[glenjj]

Verifier is really only used for debugging if you think a problem exists (or to verify drivers you're running play nicely with the kernel). The truth is, sometimes it catches problems with drivers that aren't necessarily fatal. In the case where it's crashing your system it's doing so because an IRP isn't being fulfilled in a timely manner, which is the responsibility of the driver. Driver updates may fix these problems, but I don't believe this is the source of your "normal" crashes. Yours are more centered around freeing address space and irrecoverable page faults.

Hope that helps and I'm interested in what MemTest finds.

Ah righto then, cheers for the extra details.
And success! the c9 problem stopped, I'll put memtest on tonight and let it run, though I have a feeling it'll just crash while I'm asleep.

 

[glenjj]

Okay, I ran memtest86 overnight, it went for just under 13hrs straight.

I don't know how to interpret the results though (apart from it saying there's a buttload of errors apparently lol)

so here's a screen shot just before I closed it

 

[peebee]

Okay, I ran memtest86 overnight, it went for just under 13hrs straight.

I don't know how to interpret the results though (apart from it saying there's a buttload of errors apparently lol)

so here's a screen shot just before I closed it

I think there's your answer. Time to replace that memory.

 

[glenjj]

So my RAM's buggered? coz all that info from the scan is beyond me lol

 

[peebee]

As long as you're running the RAM within specs it's safe to say it is screwed. If you're overclocking then that's another story, but I'm assuming you're running stock during our troubleshooting.

I know you said the memory was Corsair, and it sucks you're having problems with it, because I've had nothing but really solid products from them. Since everything you have is new you might be able to get a full refund and apply the funds toward another manufacturer.

I was also curious why you were going with 32GB of memory. No justification needed IMO, but I just found it somewhat odd you were running a single Core i7 3770k with 32GB.

Are you into media encoding, sound engineering, etc? Or just an enthusiast?

 

[glenjj]

As long as you're running the RAM within specs it's safe to say it is screwed. If you're overclocking then that's another story, but I'm assuming you're running stock during our troubleshooting.

I know you said the memory was Corsair, and it sucks you're having problems with it, because I've had nothing but really solid products from them. Since everything you have is new you might be able to get a full refund and apply the funds toward another manufacturer.

I was also curious why you were going with 32GB of memory. No justification needed IMO, but I just found it somewhat odd you were running a single Core i7 3770k with 32GB.

Are you into media encoding, sound engineering, etc? Or just an enthusiast?

I haven't overclocked anything no, but, I do not have 32gb? :/ I have 16gb, and I do not believe it is corsair, I think it's a generic brand I'm not sure, all the item description says is (16GB DDR3 1600MHz)
And the the CPU reads: "Intel Core i7 3770 Quad Core CPU, 3.4 GHz, 8MB Cache, Socket LGA1155, 22nm"

So I don't know if there were some facts mixed up? :/

I am a heavy photoshop user for graphic design, and a moderate gamer playing mostly new titles like BF4 etc

 

[peebee]

Ahhhhhhh, my bad, yep complete mixup in my brain.

I was almost bummed out that Corsair sent you bad memory, but since it's generic, I'm relieved! 16GB of RAM fits that CPU nicely. You've got plenty of cores with lots of memory they can churn through. It should threat you very well as long as you get GOOD memory. I would send that generic stuff back and try to get a full refund. Take the funds and get a 8GBx2 DDR3 "kit" by Corsair or Crucial. The "kits" are paired modules that are tested together which should give you a more reliable system.

 

[glenjj]

Ahhhhhhh, my bad, yep complete mixup in my brain.

I was almost bummed out that Corsair sent you bad memory, but since it's generic, I'm relieved! 16GB of RAM fits that CPU nicely. You've got plenty of cores with lots of memory they can churn through. It should threat you very well as long as you get GOOD memory. I would send that generic stuff back and try to get a full refund. Take the funds and get a 8GBx2 DDR3 "kit" by Corsair or Crucial. The "kits" are paired modules that are tested together which should give you a more reliable system.

heh well yeah I only hear good things about corsair too, but this seller was reputable, and did replace the PSU for free when it had issues, so I'll just pass this info onto them and I think they should replace the RAM, it states lifetime warranty, whatever the brand is lol

And yeah I'll see if I can just get the money back and buy my own good memory, if not I'll buy the good stuff anyway and toss/sell the replacement ones they send.

So with the memtest, all those errors (63000 lol) thats issues with the RAM? causing all the crashes I had?
But then there's "Error confidence value 113" "max contiguous errors" etc, also bad I take it?

 

[peebee]

Yes, the memory is definitely bad. You might even want to save the picture you took to show the company where you got your system.

Any memory error is bad. MemTest's "confidence value" states that any value over 100 is considered highly confident that the memory errors detected were valid.

 

[glenjj]

Ah ok, so ideally the 63000 errors on the right hand side should be zero? or very minimal errors

I'm in the process of getting new ram, the seller responded straight away and is working to fix my issue.

And cheers for all the info mate, appreciated.

 

[glenjj]

Turns out it was one stick that was screwed, ran memtest on both sticks separately
And the seller told me the brand is:

APACER DDR3 1600MHz 8GB x2.

 

[peebee]

Glad you were able to narrow it down. It's also really nice that the seller is doing you right and taking care of it. Once the memory is replaced you should be good to go.