ntoskrnl.exe BSOD Randomly every few days

[gregrocker]

What is the exact AMD display driver that you have installed in Device Manager? How is it listed and what are its date and version?

Where did you get this driver?

 

[Broken Hyoid]

What is the exact AMD display driver that you have installed in Device Manager? How is it listed and what are its date and version?

Where did you get this driver?

This is the display driver. It was part of windows updates after I had removed my dedicated GPU from the PC and the dedicated GPU's drivers.

 

[Slartybart]

I'll try and clarify things a bit regarding the licensing situation....

One of the things about an OEM System Builder license is that you agree to supplementary licensing terms BEFORE opening the packet to install or read the Key - the act of opening the packet indicates acceptance of the terms.

Obviously, with the Key coming by email it's not possible for you to agree or disagree to those terms - which automatically makes the license invalid, whatever any technical/activation/validation results may be.

There is also the distinct possibility that the Key and the package are counterfeits - high quality ones, maybe, but counterfeits - and/or that the Key has been duplicated and sold many times, which will result in major problems down the line.

As Essenbe says, your best option is to RMA the product and inform Amazon.

Thanks for the clarification on the OEM System Builder license.

 

[essenbe]

I'll try and clarify things a bit regarding the licensing situation....

One of the things about an OEM System Builder license is that you agree to supplementary licensing terms BEFORE opening the packet to install or read the Key - the act of opening the packet indicates acceptance of the terms.

Obviously, with the Key coming by email it's not possible for you to agree or disagree to those terms - which automatically makes the license invalid, whatever any technical/activation/validation results may be.

There is also the distinct possibility that the Key and the package are counterfeits - high quality ones, maybe, but counterfeits - and/or that the Key has been duplicated and sold many times, which will result in major problems down the line.

As Essenbe says, your best option is to RMA the product and inform Amazon.

Thanks for the clarification on the OEM System Builder license.

I agree. I learned something from that one.

 

[essenbe]

What is the exact AMD display driver that you have installed in Device Manager? How is it listed and what are its date and version?

Where did you get this driver?

This is the display driver. It was part of windows updates after I had removed my dedicated GPU from the PC and the dedicated GPU's drivers.

The FX 6300 was not even released until a year after that driver is dated.

 

[Broken Hyoid]

The FX 6300 was not even released until a year after that driver is dated.

Lol, well I don't know whats going on there, but thats the only driver for the intergrated graphics and it was from windows updates itself.

The GPU or the Motherboard pcie slot.

Okay this has got me thinking. When I built my PC it had a PCIE wireless card. This card made my internet go crazy, ping issues, latency in game, etc. So I assumed it was just a bad card(the company wasn't well known either, so I didn't think too much about it) and returned it to amazon, at which point I just started using my old belkin wireless dongle instead as it was easier to install. I made nothing of it till now. Maybe the wireless card wasn't faulty at all? Maybe it was my mobo PCIE slot? Maybe my mobo is the cause. Anyway if no BSODs happen within 24 hrs we can confirm the PC is now stable(no bsods so far), so I will get my friends old GPU at one point and try it on my PC, if the PC BSODs after that, we can assume it is my mobo, if it doesn't I RMA the gpu. Thoughts?

 

[gregrocker]

Once again, you tried every available driver for the card for long enough to know it didn't help, correct? This is important enough to ask twice.

 

[Broken Hyoid]

Once again, you tried every available driver for the card for long enough to know it didn't help, correct? This is important enough to ask twice.

The only driver changed I made to my dedicated GPU when it was installed on the system were the following:

No drivers- BSODs still occured
Latest Driver(full package)- BSODs still occured
Latest Driver(without ''bloatware'')- BSODs still occured

Just to clarify I never tried any older version of the driver as I thought removing the GPU, as essenbe suggested, for 2 days would have been easier to identify whether it was the cause of the BSODs. So far it seems like so as it has almost been a day and no BSODs. If you wish I can install the GPU after this 2 day period with an older version of the driver to see if that does anything.

 

[essenbe]

Yes, that is probably the best test. If you can run another card without the BSODs, that would Make it either the card or the mobo. If you get BSODs with another, known good working card, then I would have to assume it is the mobo. And, I emphasize a known good working card. Now, if you could convince your friend to run your card in his machine and his card in your machine, the results would be pretty definitive. Just remember to do a driver uninstall to make it a clean install. Mixed drivers will make almost any card have issues.

 

[Broken Hyoid]

Yes, that is probably the best test. If you can run another card without the BSODs, that would Make it either the card or the mobo. If you get BSODs with another, known good working card, then I would have to assume it is the mobo. And, I emphasize a known good working card. Now, if you could convince your friend to run your card in his machine and his card in your machine, the results would be pretty definitive. Just remember to do a driver uninstall to make it a clean install. Mixed drivers will make almost any card have issues.

Yes I will confirm with him whether the card is reliable and see if he is up for using it for a couple days. He only replaced it as he got an upgrade, not because it was malfunctioning but I will confirm.

 

[Broken Hyoid]

Just a quick update. It has been 2 nights and no BSOD, therefore I can confirm that my system is now stable. The problem either lies with the GPU itself or the mobo's PCIE slot. I will confirm this by testing a replacement GPU. Thanks to everyone who helped, it took alot of time and effort from you guys and I appreciate it. Thanks especially to essenbe who put alot of effort into this.

 

[essenbe]

Just a quick update. It has been 2 nights and no BSOD, therefore I can confirm that my system is now stable. The problem either lies with the GPU itself or the mobo's PCIE slot. I will confirm this by testing a replacement GPU. Thanks to everyone who helped, it took alot of time and effort from you guys and I appreciate it. Thanks especially to essenbe who put alot of effort into this.

That's no problem at all. That's what we are here for. Just keep us posted on the progress. Inquiring minds want to know.

 

[Broken Hyoid]

Hi,
A quick update on my part sorry for the delay, took quite a while for me to get my hands on a replacement GPU.

Summary of what happened:

-Random BSODs occuring daily multiple times
-Did all tests, nothing conclusive
-Took out GPU, BSODs stopped
-Added different GPU, BSOD occured again
-Currently have no GPU in my pc and will leave it like this for 3 days straight, ensuring the system is stable.

So I assume if no BSODs occur now, that it is my PCIE slot that is faulty, and I have to RMA my mobo completely? No way around this, or anything else I can do?

 

[gregrocker]

Wait to hear what Steve says.

 

[essenbe]

As I see it, if you got BSODs on 2 cards and none with the on board graphics, It's a mobo or PSU issue. But, please run the SF diagnostic again. http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[Broken Hyoid]

Okay another twist... BSOD just happened using on board graphics. So I don't know if this means if the mobo isn't at fault, or if it still is a faulty mobo that has a faulty PCIE as well as faulty on board graphics. I ran the PC on just on board graphics a couple weeks ago aswell and it didnt BSOD for 3 days straight, I thought that meant it was stable, but I guess it was just a lucky(or unlucky) coincidence. BSODs have now happened with 2 different GPUs and on board graphics.

Attached are the dump files. They are all the generic Stop 0x24 BSODs I think, and there are lots of them. Don't know how much use they will be to you, they didn't tell us anything before. here they are anyway.

 

[essenbe]

OK, the dump files showed nothing other than 0X124, a generic hardware fault. Lets try this. First, create a restore point, to enable you to get back to where you are right now, if needed http://www.sevenforums.com/tutorials/697-system-restore-point-create.html then

Enable driver verifier but only enable the options: Standard settings, IRP logging and Force pending I/O requests step 3.

Enable Driver Verifier to monitor the drivers. Follow this Tutorial for instructions:
Driver Verifier -Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

http://www.sevenforums.com/images/infosmall1.png Information

We use Driver Verifier as it puts a stress on the drivers, and so it makes the unstable drivers crash. This should flag the driver responsible in the dump file.
It

Driver Verifier will make the system laggy, this is normal so don't worry.

Before enabling DV, make sure that you have earlier System restore points made in your computer. make a System Restore Point Manually

If there are no points, make one

 

[Broken Hyoid]

OK, the dump files showed nothing other than 0X124, a generic hardware fault. Lets try this. First, create a restore point, to enable you to get back to where you are right now, if needed http://www.sevenforums.com/tutorials/697-system-restore-point-create.html then

Enable driver verifier but only enable the options: Standard settings, IRP logging and Force pending I/O requests step 3.

Enable Driver Verifier to monitor the drivers. Follow this Tutorial for instructions:
Driver Verifier -Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

http://www.sevenforums.com/images/infosmall1.png Information

We use Driver Verifier as it puts a stress on the drivers, and so it makes the unstable drivers crash. This should flag the driver responsible in the dump file.
It

Driver Verifier will make the system laggy, this is normal so don't worry.

Before enabling DV, make sure that you have earlier System restore points made in your computer. make a System Restore Point Manually

If there are no points, make one

I already ran driver verifier for 48 hours with my original GPU in, and it had no effect on the BSODs, they occured at roughly the same frequency. Do you want me to run it again while using on board graphics? The only driver difference between the first time and now would be the on board graphics driver.

 

[essenbe]

Yes, try it again now that you are using on board graphics. It's easier than RMAing the board. Certainly worth a try.

 

[Broken Hyoid]

Yes, try it again now that you are using on board graphics. It's easier than RMAing the board. Certainly worth a try.

Okay I ran driver verifier for 24hrs roughly and it didnt make much of a difference, there was a slight increase in the number of BSODs(the errors were the same 0x124) but then again it is probably coincidence, nothing major. I re did the Memtest for my RAM(7 passes 0 errors), and prime95 for CPU(test ran 2 hrs, temp stayed stable and all cores were fine). I had replaced the HDD prior to this as during the tests it was found to have bad sectors, so I RMA'd it, but that clearly wasn't the cause of the BSODs and was just a red herring. I carried out the SeaTools for DOS short and long test on the replacement HDD now and it passed both. And for the GPU, since both GPUs and on board graphics caused the BSODs it isn't the GPU either. So unless the tests have been false negatives or just not testing the right things we have ruled out CPU, HDD, GPU, RAM. That leaves Mobo and PSU. I dont see any way to test either, so I think my best bet now is to RMA the mobo and see if that fixes it, I am leaning towards the mobo being the problem rather than the PSU anyway, the voltages seem adequate. Thoughts?