[SOLVED] Repeated BSOD Win Vista Starter 32 bit

[Bright Future]

Yes...did it...but not all..

The Monitor was found faulty. Upon checking it from inside, it was seen that the adapter (power supply from plug point) was not proper and there were some sparking within the monitor at button (on-off, menu, brightness control , etc area) While checking and testing, the inside circuit burned down making monitor completely unusable/unable to power on. REPLACED the monitor with a new one. Yes.... I spent money... (You can't call me a miser).

Then set everything right and wanted to check 2x 1GB RAM. Removed 1 RAM and run Win Mem Diagnostic Tool (inbuilt in Vista). The test with 2 pass ran okay but upon restart did not display result. Checked eventview log ...did not open log ...says .. process used by another process.... this particular log never opens..

As such my PC has a problem ....no logs ever... no matter what all settings I do ... I never get to see a log ..minidump log..etc

Next STOP Error A5 with parameters 11,06, 00, 00 came in upon restart.... inspite of all these repairs (BIOS update, SSD , re-install OS, New Monitor..)....this particular error does not go. It has become a permanent feature of MS OS. MS must include BSOD as a default feature for its OS... as the latest , most modern and innovative technological development of their OS...a kind of a trade mark ... no a new logo...

Did some research -- found the root cause as --- System could not enter ACPI mode --- SCI_EN never becomes set in PM1 Control Register.
Now what is this error and how to correct it ?

Next (Later) we will also check why Mem Diag Tool does not display results....? or else I will never get to check memory...and no minidump log, etc no matter what settings I do.

In the meantime...on the positive side ... MS Security Essentials caught hold of 2 virus.....see the attached file.

 

[Sysnative Windows Update]

Good to hear that at least the monitor has been replaced. Memory should be tested with Memtest86 from Passmark, one stick at a time and you should alternate slots:

Test RAM with PassMark MemTest86

If you see errors coming up, either the motherboard or the RAM is dead.

The error you are seeing is not OS dependent, there's a piece of hardware that's failing.

Continue testing the hardware.

The malware you saw was likely something that you attempted to download from the internet and was blocked.

The other detection is a bundleware, that is a piece of software attached to installers that tries to install itself onto the system while you are trying to install something else. That's not malicious in itself.

 

[Bright Future]

You did not say anything about the great research that I did without getting hold of any log or so and that is, to find the root cause based simply on the STOP ERROR info A5 (11,06,00,00). Finally I (please note -- capital I) could find the root cause as -- System could not enter ACPI mode --- SCI_EN never becomes set in PM1 Control Register.

And all that you are interested in is -- buy ...buy ... buy.. when the error is in front of you... my bet is neither MB nor RAM is failing. Now it is only some settings and OS..... or at the most ... some drivers or simply registry errors..... system file errors, disk errors, dll file error, some leftover junk... it has to be now software related issues and not hardware. It cannot be anything more complicated than that.

Besides what do you expect from memtest86+ when the result cannot be found on any log..... ??? I must get some credit for my research....
Awaiting your reply. Memtest86+ can wait...

 

[Bright Future]

But experts are experts. I could not wait.... My PC has 2 slots enough to hold 2GB RAM that is 2 X 2GB = 4 GB total. But I use 2x 1 GB RAM in 2 slots. And the PASSMARKSMEMTEST86 was to be done with 1 GB RAM at a time in 1 slot as per your instructions. So that makes 4 tests to be done in total with 1 GB RAm changing position in 2 slots one after the other. Yes PC was run only on 1 GB all the time. And the tests were made in default mode only. The best part is that all 4 tests passed with zero errors. So the RAMs or its slots are not the culprit. What next? I ..... the capital I ... leave it to the experts.

But my bet is that there is something to do with Power Management -- BIOS or Win Vista Settings ... or drivers... or something ,, on software side ..
The only hardware now left according to me is the keyboard, mouse, loudspeaker ... The monitor, RAM , SSD are already checked and through.... passed.
The motherboard ..... well we updated the BIOS.... anything more ???

And this brings us once again to the question on BSOD -- the root cause -- System could not enter ACPI mode --- SCI_EN never becomes set in PM1 Control Register. What about it ????

What is ACPI mode and EUFI mode ? Will Vista start with ACPI disabled ? Whats the mis-match? Help me out..

 

[Sysnative Windows Update]

Hi!

There is only one article about it online with no additional information, so take that with a grain of salt. Over the course of the thread we've identified several broken parts that needed to be and were replaced.

The beauty of Memtest86 is the fact that it doesn't need logs, it reports everything and anything directly.

I suspected the BIOS myself at first (settings/version), that's why I had you flash the latest version and as part of that is resetting the BIOS to defaults (which would rule out a settings issue on your/technician's end when setting things up.

You reinstalled the OS to rule out software as well...

While the error is indeed called ACPI_BIOS in the system is not fully compliant, it can have nothing to do with the BIOS, one example is the following:

https://support.microsoft.com/en-us...bios-in-the-system-is-not-fully-compliant-wit

You can find out more about ACPI/UEFI here: ACPI and UEFI forum join forces: here's why it matters - fixedByVonnie

 

[Bright Future]

Amazing.....We are on the same page. I also had looked in to this webpage just a few moments ago --

https://support.microsoft.com/en-us...bios-in-the-system-is-not-fully-compliant-wit

Gone through in detail.

Start from either end .... but we came to the same spot.

I fully agree -- there were hardware issues... hard disk, monitor, RAM also checked out. Yes, PassmarkMemtest86 worked well ... better than Win Vista inbuilt Mem Diagnostic Tool. But both hunches were right -- something to do with RAM and other hunch -- Power Management settings. Both things go off to create BSOD with the very same errors that is mentioned in the above link you have forwarded. The lesson is -- Add RAM with PC shutdown.

Forget all the rantings about money, technology, etc... at the end of the day ... it was a learning experience.... a very costly though..time consuming as well...

Now let me try out the solution -- Delete Hiberfil.sys and check for some time if BSOD vanishes from system.

ACPI and UEFI another game on technology front.... yes... paid v/s free ... flexible v/s fixed settings... it will go on...

When this thread is solved and/or reaches a logical conclusion ... I think I will be more than happy ... that atleast I tried....attempted...even if success is not long lasting...

LET's TRY!!!!! What am I waiting for ???? Another BSOD????? Here I come.... Hasta La Vista !!!! (Did you hear ..... VISTA ... VISTA )

 

[Sysnative Windows Update]

Try it if you wish.

 

[Bright Future]

..if you wish? ..... Are you holding something back?

Yes I tried. After a while I got the MS logo ... BSOD - Stop Error A5 (11.06.00.00). Now what the Graphics driver is outdated...
Lets go step by step.... what do you say? Your wish...?

 

[Sysnative Windows Update]

I said that because I don't believe that will help because like I said I really do not believe that this is a software issue. Where did you see anything related to the graphics card driver?

 

[Bright Future]

Oh oooo .... it is a long story on surfing.... or shall I say ...research....

After deleting Hiberfil.sys file, I was looking for Power Management errors causing BSOD... and I had come across some mention that Video card could be the one ... if outdated ... needs update... it has some hold over power management... then I kept surfing ...

Aha yes here it is ...https://www.vistax64.com/threads/hibernation-enable-or-disable.165508/

It is something like this... that video card.. when updated will change the sleep modes...and hence the power management settings and ACPI may get affected in BIOS..
My PC being Win Vista Starter 32 bit ... a lot is controlled by Group Policy to which user has no access.. but in BIOS settings I could locate S1/POS for ACPI settings ... then I found that my PC has only one setting --for sleep state .. S1-- And what is that S1 -- Standby Hibernate. The other settings S2, S3 -- Firmware does not support and not Hybrid Sleep as well. And all the Bios Settings for Ports were also seen ... some say that by changing Bios port settings things get better ... but I don't know which port setting is proper .. so did not get into it...

Then I got lost in computer jargon... video card .. graphic card.. both are same... etc...

If you think ...it is not software problem, then how to check graphic card ... if not graphic card driver? and any updates..now that BIOS is updated .. and I have not tried Graphic card update there after...

Since you are an expert... whats your take on this case now...

 

[Sysnative Windows Update]

You reinstalled the OS. If drivers weren't installed after the fact, problems indeed can occur with limited functionality of the devices like the GPU, but under no circumstances should you be getting a BSOD, even when you are not using the GPU with its driver (but the Microsoft Basic Display Adapter). Not all BIOS manufacturers label their settings the same, nor do all the motherboards have the same functionality. The power states depend on your PSU as well. Certain PSUs did not support certain power states on Haswell CPUs a few years ago.

If there are no yellow exclamation marks in the device manager, then the drivers should be ok: How to Open Device Manager in Windows 10, 8, 7, Vista, or XP

My point is, the drivers, when installed, should mostly work okay. By mostly, I mean that there are very few exceptions with buggy releases, but that's a rare sight.

I'm just confused, if you said that sb had replaced the HDD, the monitor, why didn't that person try out the rest of the components until they figured out what is broken. I can only do some much here and I am almost certain that this is some kind of a hardware failure. I cannot guarantee that your RAM/mobo/video card are good because I don't have access to spare parts nor to your computer to test them out. It would be best to take it to a shop and have it properly diagnosed and see what else (if anything) is broken in order for you not to spend money on parts that you may not need after all.

Here is the GPU test, but be very careful if trying to run it alone, because it can damage your GPU if the temp gets too high.

FurMark Display Card Stress Test

 

[Bright Future]

You don't get it... I could have taken PC to any shop and got it repaired. Do you know, for example HP authorized service center takes 1 month to diagnose the problem... first they don't understand -- what is it that user is complaining-- then after a month 2,3 issues pop up again... another 1 month and if user don't pursue your PC is forgotten...The fact is --- nobody in computer industry knows how to repair and maintain. They all belong to use and throw way of working.But one thing is for sure -- all are highly paid. And user is the one with a junk - even when he buys the latest model and goes to service center with some issue.

The users are treated as uneducated, illiterate, ill-mannered dumb people.
So I had to take up repairing on my own.

And why didn't he check Graphic Card -- because this PC works very well for 2 days and shows problems on 3rd day... everytime I feel it is done and something comes up next...Or shall I say even if we are going for an hardware upgrade ... go step by step... money spent more that way ..yes but we know what we are doing...

Driver update I thought ... after doing BIOS update .. I did not do driver update...
But then you are right... device manager does not show yellow exclamation mark or red cross anywhere...

I would not have contacted the forum either... but I consider -- if at all some proper guidance I will get it will be from forum... and why sysnative .. because I had used it earlier as well with positive results. But I can try others if you wish ....

Any way I downloaded it ... and yes I will be running it alone.... What am I supposed to do..?

 

[Bright Future]

Now as far as RAM is concerned... I tested it ... yes... Passmarkmemtest86. Both RAM passes in both slots -- tested one at a time in each slot.
RAM as culprit is ruled out.
My guess is ... as good as yours ... something is wrong...BSOD is not getting off and I don't have logs to refer to. Is that OS problem or hardware?
I am sure .. when all testing is over ... I may have to reinstall OS ... vista or new one...
Yes I will test and repair PC on my own... I will find help from wherever possible...yes not frustrated .. but desperate...

Alright ...to take off the pressure... I shall take it to a computer repair shop... to start with...

This thread may be closed.... IF YOU WISH!!!

 

[Sysnative Windows Update]

I am familiar with the servicing practices, because sadly it is the same in my country.

Let's try driver updates then. Please take a screenshot of your Device Manager fully expanded.

 

[Bright Future]

Sadly...you said ..sadly... IT IS ALL OVER THE WORLD !!!

Now ... all of us .. say together ..in one voice ... Heave!!

and here we go...

Device Manager - Fully Expanded -- means it will go out of screen....

So ... now..... take a look... in 7 pieces.... and put it together ....appropriately...
See the attached files..

 

[Sysnative Windows Update]

It looks like that all the drivers have been correctly installed to the system.

Please do the following next:

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 32-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

 

[Bright Future]

Something terrible happened.....
After running FRST ... it prompted for restart but before PC could restart, MS Security Essential swallowed FRST tool and restart came up with the fixlog.
See the attached files. I am not sure if the repairs after restart were completed....

 

[Bright Future]

After some time, I put the MS Security Essentials -- uncheck Real Time Protection and made a re-run of FRST + FixList and the PC went for a Restart and came up smoothly. The fixLog is attached.

 

[Sysnative Windows Update]

Yes, it was. Some AV vendors flag FRST as malware because of the way it was developed. Please run a fresh FRST Scan:

Step#1 - FRST Scan

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 32-bit Version so please ensure you download that one.
2. Right-click FRST.exe and click Run as Administrator to run it as administrator. When the tool opens, click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already checked).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please attach the log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.

 

[Bright Future]

Yes ... here it is ... see the attached files