P55A-UD4 startup "BSD" ~ why?

[Searcher1]

Yes I would agree. Probably best to disconnect the speakers totally.

HPET 64 bit mode should work fine even with programs running in 32 bit compatibility mode.

Set to HPET 64 and may be my imagination but things do seem to happen a tad wizzier:)

As for the BSD will have to just keep an eye on things?

FWIW when I was in the BIOS I inadvertantly F9 rather than F10 and got the "info" list and the motherboard was listed as P55A-UD4 B3  There is nothing else that I have seen associated with this board that mentions B3 ~ odd perhaps???  This is the rev 2.0 board by the way

So please remind (?) me what is the significance of B3 in the 'name'?

[Dark Mantis]

B1 but more so B2 and B3  are just the various build designations that are assigned by the manufacturer usually for in house use more than commercial application. Take no notice of it.

[Searcher1]

B1 but more so B2 and B3  are just the various build designations that are assigned by the manufacturer usually for in house use more than commercial application. Take no notice of it.

Ah! 

As for the BSD, well it did it again this evening.  The click I can hear is definitely coming from the case 'speaker' area.....so damned odd???  I forced the shutdown and turned off the PSU >>>>>>> on again  and booted up AOK.

[Dark Mantis]

What was the BSOD Stop code this time?

[Searcher1]

What was the BSOD Stop code this time?

Same one ending 101

Granted I reset the vCore to 'auto' but it was the same stop code during the testing with vCore set to the voltages mentioned???

[Dark Mantis]

I'm afraid I am out of ideas then as 101 should mean too little Vcore voltage setting. Possibly a faulty CPU

[Searcher1]

I'm afraid I am out of ideas then as 101 should mean too little Vcore voltage setting. Possibly a faulty CPU

But with such an odd fault just how does make a case for RMA'ing it or any suspect part(s).  Makes me think the only way forward to is to stick with and accept that there might be a complete failure of "something" sometime.

Not sure if I described this aspect of the BSD differences in the startup ~ normally you get POST, the HDD LED shows activity and you get the OS loading etc With the 'bad' start the HDD LED stays illuminated full time and I think not all that time is audible drive noises???  I do have all three HDDs fed off of the 3 SATA power plugs from a single cable...............should I put another cable in and split the load to a 2 & a 1 (The drive are all WD Black ~ a couple of 500GB and 1TB but sure their power demand is well met off one cable???)

As for whether the CPU has a fault I did run a stress test (Intel Burn 2.5) for only 5 loops in Standard mode and the results were deemed AOK.

If indeed the vCore is too low the only setting I did not try was "Normal" which if I understand it will set it to vCore 1.3v

If the PSU for acane reason well the motherboard cable and the CPU connector are hard wired not one of the modular ones so now to try a different socket on the modular set.

I do hate a msytery  

Just what is the power on to feed cycle i.e. if there is a delay in power being provided to the various components and the CPU & BIOS is detecting a too long a pause could be ID'ing it as low vCore so is it a sequence question ......could the BIOS itslef have a corruption......using the latest F15 should I downgrade to a slightly earlier version if the BIOS could be 'at fault'

Edit ~ The fact that (apparently) turning off the PSU and as such doing a fully cold boot means an AOK boot implies that something is "power" hot so to speak if the PSU is left turned on and that is having this random effect....but what components could it be that are involved???  Assuming such a premise is correct!

[Searcher1]

Been looking long and hard for other possible causes.

The fact that BSD refers to a clock interupt could it be more like this I found http://msdn.microsoft.com/en-us/library/ff557211%28VS.85%29.aspx rather than a vCore question???

In Googling I found a ref to "Clock Skew" settings and in the manual there is ref to CPU Clock Skew on the Advanced Settings Page but I have not touched this as obviously need your further feedback

Just what does this setting do and what setting (if OK to try???) do I set it to?

[Searcher1]

An update for what it is worth.

Booted this morning and my initial thought was that it was going to fail (slight click heard with a tad longer time til POST beep) but no it was OK.......used the web got emails etc.

Then ran the CPUID Hardware Monitor and while it was starting up and accessing the sensors the PC crashed with the now familiar BSD same error code et al.  First time it has done that whilst actually running 

Every time this has happened it 'says' about creating a dump file ~ just how does one read this/these files???

[Dark Mantis]

Hi

I have just re-read your entire thread to see if there was anything I could see that we had missed.

What PSU are you using make/model please?

Did you try as Lsdmeasap suggested regarding the voltage ?

If you want the voltage, and CPU speeds to remain the same always you have to disable Speedstep (C1E and EIST), then you will need to use 1.25-1.3+ for the voltage

The dump file should be readable with notepad

[Searcher1]

Hi

I have just re-read your entire thread to see if there was anything I could see that we had missed.

What PSU are you using make/model please?

Did you try as Lsdmeasap suggested regarding the voltage ?

If you want the voltage, and CPU speeds to remain the same always you have to disable Speedstep (C1E and EIST), then you will need to use 1.25-1.3+ for the voltage

The dump file should be readable with notepad

PSU is a Corsair HX 650W ~ no I think I missed the Lsdmeasap about disabling C1E and EIST (need to find that in the BIOS setup?)

What about my query that this actually a "clock" question not a vCore issue (see link in my post ^^)

I will open the dmp files with Notepad and see what they say???

[Searcher1]

The dump file can indeed be opened with Notepad but it is gobbledegook.  Notepad and indeed Wordpad can not interprte the special characters so the it is unreadable

[Searcher1]

Right found a freeware called "BlueScreenView" that opne the dmp files and identifies the trigger file

With the exception of this mornings BSD whilst launching the HW monitor a common file for al;l the BSDs is :_

ntoskrnl.exe and in the case of this morning addednvlddmkm.sys

Now the latter one if Nvidia driver related but the ntoskrnl is obviously a core W7 file

[Dark Mantis]

Now the latter one if Nvidia driver related but the ntoskrnl is obviously a core W7 file

I would say that you are correct in your assessment of the files.

The clock skew that you asked about is to help balance the timings if the signals take longer to reach one place than another but normally that is already worked out and the optimal timing set as standard.

[Searcher1]

Now the latter one if Nvidia driver related but the ntoskrnl is obviously a core W7 file

I would say that you are correct in your assessment of the files.

The clock skew that you asked about is to help balance the timings if the signals take longer to reach one place than another but normally that is already worked out and the optimal timing set as standard.

So with the error code is it a vCore or a clock function question???

I will disable the C1E and EIST and set the vCore to 1.25v and see how that behaves???