New
#11
Attached is a screenshot of my temps via speccy and my furmark results, I'll try memtest overnight
Attached is a screenshot of my temps via speccy and my furmark results, I'll try memtest overnight
Ok mate after that I might ask for help if the memtest comes up with nothing but please let it run for at least 8 passes any less and you may as well not bother .
Having said that if errors come up before 8 passes then it means narrowing it down to the stick or slot /s that are the problem ones.
I ran the test for 13 passes. No errors showed up.
Ok mate now we had better take a look at the PSU just to rule it out if nothing else
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 handwindow select Sensors and scroll down to the power section where you will seewhat the volts are doing see my pic. Now the section you want will be labeled- for 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 thatbut for looking at the components in some detail close it and use the main lefthand side panel
FOR OTHER COMPONENTS
PART B:
Open each small square with + in it on the section the components are in andthen click on the individual component/s (it will highlight in blue) - in theright hand side will appear all sorts of details including brands speeds andother essential info that particular device. See pic for example.
When looking at the psu and other components, what exactly am I looking for?
Sorry late reply mate now what is critically important is that 5% + (pos) or - (neg) on each of the rails. Anything under or over what the rail voltage is supposed to be will cause the machine to malfunction or not function at all.
So for example if the 12 volt rails do not measure up to above 11.4v or they are over 12.6v then it becomes unusable to the machine components simply because a lot of them rely on very tight tolerances to work properly if at all. In some cases it can ruin them. One only has to look at the tiny increments in the voltage in overclocking the CPU for example can make huge differences to the stress placed on that component.
Now if you read that link re power supplies Power Supply 101: A Reference Of Specifications - Power Supplies - sorry I thought I has included it in my ditty it will describe how the PSU has in the first instance a safety feature which will self test itself and if the rails are not right it will not allow the CPU / system to power up - it is the ok signal sent to pin 8 on the 24 pin plug on the motherboard (grey cable). The CMOS voltage is not critical but if it is less than what is normally required one just has to replace it but then the BIOS will revert back to default.
Please don't hesitate if you need to have more info on this critical component - PSU without it nothing is going to work
All the voltage levels are fine. Any other ideas?
Sorry late reply Sam now we have done some of the nuts and bolts bits I like to get out of the way and now am looking at the error in the Code window
This is looking at something to do with the Direct X system and one search came up with this which asking for that dxgkrnl.sys to be uninstalled and reinstalled What is the dxgkrnl.sys file? but will have to wait until tomorrow before I can search anymore - if you can go through the links within that article it will give you some idea of what it is about.Code:************* Symbol Loading Error Summary ************** Module name Error ntoskrnl The system cannot find the file specified You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded. You should also verify that your symbol search path (.sympath) is correct. *** WARNING: Unable to verify timestamp for dxgkrnl.sys *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Right now I am going offline but just can you let us know if there have been more BSOD's since the originals and if so post them on please.
The only new bsod's have been me replicating the results after uninstalling the catalytic control center. Do you want me to give you the dump files or scan another pc log?
Yes please Sam we just need to be sure that it is the same problem / issue.
I shall have another look at that Direct X stuff in a while and get back to you when and if I can find anything else but at the moment it is all pointing something in the graphics system it just needs teasing out a bit and if I cannot find anything positive I shall ask for help.