BSOD-Help

Author
Discussion

exelero

Original Poster:

1,890 posts

89 months

Monday 23rd January 2017
quotequote all
I have a PC which has been causing me a lot of problems lately.
I can not put up the full cfg, but I will try
CPU- AMD Athlon (?) X4
RAM-8GB 1600 mhz (msi or corsair)
VGA- Radeon R7 2GB DDR5

Back like 4 months ago, started with giving random BSOD's for Atikdmag.sys but then I checked the VGA cable and it was half-burnt so fair enough I said. Now right after that it was giving me BSOD with error code 0x000003b and wouldn't finish it until I eventually bought a new HDD. With those sorted I had no worries up until like last week when at random gave me the 0x000003b error code again and just wouldn't start. When it did eventually I tried to find out what caused it but couldn't. I checked the tower, removed the SATA cable from the MoBo and reconected and everything was OK!. Please note that these problems occur only on startup, so when I need it, in fear that it won't start up I'll just put it on standby and then everything is just fine.
While just watching some youtube vids it died again giving me error code 0x0000003f like a couple of times and then 0x000003b until I have up on it.

I think the issue might be with the SATA cable, since the HDD is almost brand new and I still have like 10 months warranty on it, cables ordered, now just waiting, I don't need to use it until the weekend anyway. (I work 12 hrs on nights so I don't have the time). Hopefully when the new cables come, I'm just going to swap them install a O/S on it and everything should be spot on.
BUT what if this does not solve the issue? I have checked forums etc about the error code 0x0000003f but couldn't find anything usable. According to memtest86 my rams are fine. It just cracks me up, because this is my first so-so up to date computer and ever since I bought it(2nd hand) it just causes me headaches.
Any pro IT-hardware guys around?

TonyRPH

12,972 posts

168 months

Tuesday 24th January 2017
quotequote all
Looks like a driver issue to me.

Most likely video driver as well I'd would say.

Given that your VGA cable was 'burnt' it could even be an issue with your graphics card.

My starting point would be to update the ATI drivers (it looks as though you have an ATi / AMD or similar clone graphics card).

Failing that, see if you can try another graphics card.

It's highley unlikely to be the SATA cable.


Kenny6868

335 posts

145 months

Tuesday 24th January 2017
quotequote all
Replacing hardware is only going to cost you money. It won't fix the fault. The reason it went away for a bit after you replaced your HDD is because you had to reinstall everything fresh onto the new disk. You mentioned that you will fit new SATA cables and then reinstall a new OS. Why? the OS will still be on the hard disk. No need to reinstall.

BSODs are almost always a driver issue. Make sure everything is up to date. Check the make and model of the motherboard and video card and go to their web site and download EVERYTHING from the list of drivers. Make sure the BIOS is up to date. Run Windows update to get all the latest patches and then see how it goes.

On a rare occasion it can be a setting within the BIOS. Hard disk modes have been known to cause BSOD.







LeeThr

3,122 posts

171 months

Tuesday 24th January 2017
quotequote all
Given that the original fault was caused by an ATI related file, I would be looking at the GPU. Sounds like it's on it's last legs, and the burnt out cable may have caused more damage to the GPU as well.

Try running it without the ATI drivers, and just on the windows generic drivers. This prevents the GPU from running some of the more "advanced" features and getting up to the full power of the card. If it stays stable like that then it tends to suggest it's days are numbered.

exelero

Original Poster:

1,890 posts

89 months

Tuesday 24th January 2017
quotequote all
What I did so far is update the BIOS and all the drivers. The reason why I want a new OS is that It might be infected, because for some reason is really really slow. If the GPU is the issue, at least I have the reason to upgrade to an nvidia, ADM GPU's are cheap, but st biggrin


Edited to add: I don't think the GPU is bad though, because it's been working perfectly ever since I changed the cables

Edited by exelero on Tuesday 24th January 18:13

djfaulkner

1,103 posts

218 months

Tuesday 24th January 2017
quotequote all
If you got another machine, you could trying reading the mini dump, if one is created.
http://www.sevenforums.com/crash-lockup-debug-how/...



TonyRPH

12,972 posts

168 months

Tuesday 24th January 2017
quotequote all
djfaulkner said:
If you got another machine, you could trying reading the mini dump, if one is created.
http://www.sevenforums.com/crash-lockup-debug-how/...
Or you could just use Blue Screen View from Nirsoft.

Much easier.

Whether or not you'll understand it though...

exelero

Original Poster:

1,890 posts

89 months

Wednesday 25th January 2017
quotequote all
TonyRPH said:
Or you could just use Blue Screen View from Nirsoft.

Much easier.

Whether or not you'll understand it though...
I'll try this one. If I can not understand it than there is always Google and if Google can't help, I got Pistonheads. smile

Btw when you turn on your pc after a crash usually a message pops up with the minidump.tmp, well I tried loads of times to copy the whole address of the minidump and then copy-pasted it in the cmd.exe but no results.

exelero

Original Poster:

1,890 posts

89 months

Wednesday 25th January 2017
quotequote all


Ok. So this is what came up, looks like it has something to do with DirectX and the well mentioned GPU.
Any ideas?

WinstonWolf

72,857 posts

239 months

Wednesday 25th January 2017
quotequote all
If you've updated everything to do with the video card drivers and firmware I'd try a different one. The fact that the cable was burnt has my spidey senses tingling...

exelero

Original Poster:

1,890 posts

89 months

Wednesday 25th January 2017
quotequote all
That was like 4-5 months ago IIRC

WinstonWolf

72,857 posts

239 months

Wednesday 25th January 2017
quotequote all
exelero said:
That was like 4-5 months ago IIRC
Which coincides with the problems starting?

exelero

Original Poster:

1,890 posts

89 months

Wednesday 25th January 2017
quotequote all
Well, after changing the power cable for the GPU the problems came to a hold, HDD problems started then, and after replacing the HDD with a brand new one the problems came to a hold for about 3 months, but all of a sudden they started again.

TonyRPH

12,972 posts

168 months

Wednesday 25th January 2017
quotequote all
Long shot, but it could even be the PSU.

I've had all sorts of weird issues caused by noisy / fault PSUs over the years.


davepoth

29,395 posts

199 months

Wednesday 25th January 2017
quotequote all
TonyRPH said:
Long shot, but it could even be the PSU.

I've had all sorts of weird issues caused by noisy / fault PSUs over the years.
Years ago I had a mate with one of the very first Pentiums (66mhz if I recall!) and he had every single part on it apart from the case swapped before someone thought of changing the PSU.

exelero

Original Poster:

1,890 posts

89 months

Thursday 26th January 2017
quotequote all
A PSU is pretty cheap, probably I'll change that if it keeps going. Looks like I've got a malware though...