New
#21
Worst case scenario is that the update fails and that it can render your mobo inaccessible. If that happens you might be able to reflash it back to the older version, but that doesn't always work. If you'd like I can ask one of our BIOS experts to give a more thorough explanation?As for the BIOS , what "could" happen if i installed the newer version, could my Mobo flank out , (Since it isn't compatible with my Cpu) What are the possibilities ?
When you run Furmark without closing it, it will create a pop up with your "score" once it completes. To my knowledge there is no other way to see the results besides completing the test.I would also like to know if , theres some other way to read the results of the test ?!
This is completely up to you. If you feel comfortable with running it with temperatures that high, then you can do it, but if you don't, then don't.Let me know if i should do the Furmak , and leave it run until it bsod's or if i should do like i did earlier close it when reaching 100degree's
----------
You have five dump files from today, I will read them from latest to first;
Usual cause: Faulty driver, failing service, faulty BIOS.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {ffffffff8902b5d2, d, 0, fffff800030b73b1} Probably caused by : amdppm.sys ( amdppm!C1Halt+2 ) Followup: MachineOwner ---------
More info Bug Check 0xA
amdppm.sys is a Windows driver and shouldn't crash on it's own, so let's see if we can pinpoint the failing driver.
----------
Just as the dumps I checked in my previous post, your GPU driver is put to blame.Code:2: kd> dps fffff88003186000 fffff8800318c000 fffff880`0318ba58 00000000`00000000 fffff880`0318ba60 00000000`00000000 fffff880`0318ba68 00000000`00000000 fffff880`0318ba70 fffff880`0318bb00 fffff880`0318ba78 fffff880`05959542Unable to load image nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0xb8542
----------
Usual cause: Memory management error.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41790, fffffa8000bb3860, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 ) Followup: MachineOwner ---------
More info Bug Check 0x1A_41790.
Again, a Windows driver is put to blame.
As per my knowledge this dump file doesn't show any finite cause.
----------
The third dump file is another 0x1E bug check, this time it points to the nvmf6264.sys, the nvstor.sys and the nvraid.sys driver.
----------
The fourth and fifth dump files are more 0x1A bug checks.
----------
I am suspecting that your GPU might be the problem, do you have a spare GPU to test this with?
If so, please install it and run Furmark as displayed in my previous post. If it doesn't crash then use it as you normally would for a day or two and report back anything.
If you don't, please install the 331.82 WHQL driver from here following the procedure from my last post and rerun Furmark to rule out a faulty driver.
Good luck and keep us posted,
Nommy