Solved new cpu BSOD, error 0xA, 0x50, 0xD1

[ration]

you could follow Golden's suggestion too an stress test that CPU.

yeah, i did, everything went fine during a 5 minute stress for both the cpu and gpu (tested one at once, then both)
also thanks for the link, i'm gonna reinstall the os again to see if it stops the bsods.
and just as a funny story i guess, yesterday i played a game for like 5 hours straight, temperature was fine, but at some point i restarted it, and i got an error, which i found weir because from the little google research i did, it's supposedly because of low paging file size, which shouldn't be possible, since i have 3 gbs file size.anyway, here's the funny part: about 10 minutes after i closed the game i went to youtube and 2 minutes into the first video i watched i got another 0x101.
i'm planning on trying to trying to get the error again, and if i do i might just reinstall my os again, or maybe try win10

 

[ICIT2LOL]

OK mate I suggest to do what I always do is to clean the drive before you reinstall do that on another machine using DISKPART that way I am sure nothing is left over form the previous system install
Disk - Clean and Clean All with Diskpart Command

Now the last dump showed up inconclusive and a Google on that came up with no answers so I am wondering now if there may be a problem with the hard drive - just how old is it?

 

[ration]

my hdd is pretty old too, at least 8 yrs old. crystal disk info says it has 85 reallocated sectors.

 

[ICIT2LOL]

Ok personally I would go for a new one and depending on the budget - an SSD or hybrid or straight spinner but that would have to be a 7200rpm model.

Most of those options are reasonably priced now the spinners of course are the cheapest but if you like performance the others would be the go the SSD way ahead of the other two types.

I like Seagate myself for spinners (if I ever have to buy one) and also the hybrid and Samsung for the SSD the 850 EVO being good value.

 

[ration]

Ok personally I would go for a new one

right, but i wouldn't, unless it'd fix the bsod. do you think it's the hdd that causes it?

 

[ICIT2LOL]

Well mate there are a couple of tests that I suggest you can try to see if the drive is ok or not
SeaTools for Windows |
Seagate

and this Best Free Partition Manager for Windows | MiniTool Partition Free this one will check the actual surface of the platters and in part the read/write heads on the actuating arms plus any problems that these arms are themselves are not functioning . It will not say exactly what it is except that it is positive about the surfaces see pic

But run the Seatools first.

If these come back clear then we can rule out the drive pretty well.

 

[ration]

Well mate there are a couple of tests that I suggest you can try to see if the drive is ok or not

alright, i'll run them tomorrow morning and post the results. also, just now when i turned the pc on i got 0x101 about 30s after startup, so it seems it's not yet solved.

 

[ration]

i just ran each test of seagate, both passed, should i try the other program as well? also got something new.
a bsod i had earlier today:
0x00000101 caused by nvstor.sys, and ntoskml.exe and nvlddmkm.sys were involved as well, shall i post another zip file?

 

[ICIT2LOL]

Hello mate the errors you have are to do with vmsoftware vstor2.sys
VMware Virtual Storage Volume Driver
ntosext.sys could be anything and is nearly always listed to do with a Windows update.

nvlddmkm.sys is the NVIdia driver issue
Now the NVidia driver is a fixable the VM software I am not sure about will have to research it and the update one as I said can be due to one of he other two or something else again

 

[ration]

Hello mate the errors you have are to do with vmsoftware vstor2.sys
VMware Virtual Storage Volume Driver
ntosext.sys could be anything and is nearly always listed to do with a Windows update.

thanks, i didn't actually manage to find that, i thought it was only because of the nvidia storage driver, i'll look into updates for win7 driver storage when it's gonna be the case again.

nvlddmkm.sys is the NVIdia driver issue
Now the NVidia driver is a fixable the VM software I am not sure about will have to research it and the update one as I said can be due to one of he other two or something else again

that's fine, no need to hurry. i looked this up and didn't manage to find something other than the 2010 driver.
however, for now, it's not the case, i think. i upgraded to windows 10 to see if i'll get the blue screen errors again. i didn't get to test it for too long, but everything seems fine so far, i'll keep you updated.

 

[ICIT2LOL]

Ok mate well if it means staying with 10 then it can be customised a fair bit by you to resemble 7 I have my Sandy Bridge set up as in my pic and frankly it runs fines and is quite a bit faster than even my clocked Ivy Bridge 7 (Sandy is unclocked)

 

[ration]

yeah, no worries, i'm fairly good at optimizing windows. i actually removed cortana completely (although i did keep a backup of the files) even tho it's a bit annoying it's better than wasting cpu usage (right now i get 5% cpu usage at most idle, but generally not even that). also, so far, no bsods, but who knows, might be just like the last time.

 

[ICIT2LOL]

Yep well I sent Cortana somewhere myself as you can see from my pic - just another unnecessary piece of clutter. As for saving it well I just made a rescue disk a but am not even contemplating using it only if I really need to and only because two of my machine are upgrades.

 

[ration]

well, it seems i have no luck. just got another bsod, same as the last time.
the good side is that it appeared only today, and i know the programs i installed yesterday, so i might be able to fix it, if it's software related. else, i might just have to live with it.
update: no such luck, at least not any program installed yesterday.
at this point i'd kinda give up. i can live with a random bsod for now, i guess, since i imagine it's a hardware issue at this point, and i can't really afford buying anything else right now.

 

[ICIT2LOL]

Ok without wanting to appear nosey just what where those programs I would be very loathe to install anything that promised a clean up of the registry or tune up software??

Can you send the dump again please?

 

[ration]

Ok without wanting to appear nosey just what where those programs I would be very loathe to install anything that promised a clean up of the registry or tune up software??

Can you send the dump again please?

sure, and no problem, if you have any ideas i'm happy to cooperate.
the program i installed two days ago was adobe photoshop cs6, but it also installed some runtimes that i already had, which i uninstalled as well just to make sure.

 

[ICIT2LOL]

Ok now I am assuming this is an older machine? only because I see it is a dual core CPU in a desktop - not that that is unusual but again my gut feeling.

Now if you will bear with me can you again run the HW Info as per post#2 only please run PART A:
Using HW Info
PART A:
You can test the volts on the PSU with HW Info HWiNFO, HWiNFO32/64 - Download < download the right bit version and close the right hand window select Sensors and scroll down to the power section where you will see what the volts are doing see my pic. Now the section you want will be labelled - fpr example Asus boards usually have "Nuvoton" and Gigabyte boards "ITE" in any case the section you want will have Vbatt or VBAT in it (dead give away)
The original right hand window shows the machine running and is handy for that but for looking at the components in some detail close it and use the main left hand side panel
see my pic for what that section looks like

Now this was present in the dumps

[COLOR="Red"]FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE[/COLOR]

BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:clock_watchdog_timeout_2_proc_analysis_inconclusive

Which at first look seems to have something to do with the processor BSOD

FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_nvlddmkm_IMAGE_pci.sys

BUCKET_ID:  0x9F_3_POWER_DOWN_nvlddmkm_IMAGE_pci.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  [COLOR="red"]km:0x9f_3_power_down_nvlddmkm_image_pci.sys[/COLOR]

Plus this is pointing to the graphics driver or more likely the OS
http://threadposts.org/question/2267079/Random-BSOD-after-start-up.html

Now we have been going on here for a while and to get you sorted I might call in some help because I am no real expert if that is ok with you.

 

[ration]

yeah, my setup is about 8 years old, except for the cpu fan, graphics card and ram.
i don't think my mobo has the sensors to correctly display the voltages (see the pic). also cpu was 1.300~ and gpu 1.075V.
as i said, if you are still motivated i can keep going as well, at this point i'd like to know what the cause of this issue is, since the bsods i got seem to be very general.

 

[ICIT2LOL]

Ok mate I admire that you have stuck it out this long - all credit to you as there have been times when folks start to whinge about nothing getting done.
Now I don't know if you have a digital multimeter (usually can pick one up for about $5 - $10 if you have or can get one they are handy for other jobs too then you could physically test that 24 pin board plug using any of the black cables to test the volts on the other colours.
I am asking because as Scott Mueller (an authority on computer stuff) says the PSU is very often overlooked as a source of a lot of problems and issues and is probably the most important component in any machine because with no power then no function - it isn't rocket science
Now to find what is what in those colours see this Power supply unit (computer - Wikipedia)
If you scroll down the page you will find the map of the colours for the different voltages. You can also use one of the mobo fixing points as the ground reference (black lead) to test the volts as this will also give you an idea of how good the connections are in that plug and socket.
The meter will also have a resistance setting that can be used to test the continuity between the incoming black lead from the PSU to the board if that is faulty them there is a another problem to be sorted but it is in most machines usually ok.
As I mentioned the meter black lead to any black on that plug and the red lea to the other colours. It is also handy to test the power to any cards too.

 

[ration]

thanks, the least i can do, since i'm the one who asked.
i looked it up, and in country at least, there's nothing decent that would cost less than half of the money i put in the cpu, so to run this test, it might take me a few weeks if i can't get it done today.
still, opened to opinions.
update: seems like no luck with this either. gonna have to wait.