Solved Startup problems, BSODs, critical error shutdowns

[SGrundy]

I have been having problems for about 3 weeks now. BSOD's, critical error shutdowns, unable to startup problems.

The startup repair usually fixes startup by restoring back to a time when the computer was properly configured. Then it works for awhile and then more problems.

So far I have run a chkdsk \r (224 kb in bad sectors), run a memory diagnosis(supposedly fine), updated drivers with a driver updater, run a registry fixer, downloaded "BlueScreen Viewer"(nice program), ran Virus Scan(Avast, Malwarebyte Anti-Malware, Super Anti Spyware), and did allot of research.

Usually the crashes are supposedly due to IRQL_NOT_LESS_OR_EQUAL, or memory management. The drivers are NTKNLPA.exe, hal.dll(usually one of these) but others are, Ntfs.sys, aswSP.SYS, nvstor 32.sys

Do not know what else to do.
I would appreciate any and all help!!!

 

[richc46]

Welcome
Looks like a memory problem. Take memtest 86 to be sure. Run for 8 passes. Then take each stick and test it in a good slot for 6 passes.
http://www.geekstogo.com/forum/topic/246994-guide-to-using-memtest86/

 

[Lottiemansion]

Hi,

Try updating the various Nvidia drivers for your system: -

Drivers - Download NVIDIA Drivers

I would suggest you select the auto detect option on the page above.

 

[NoelDP]

If your disk is showing 224 bad sectors you have a major hard drive failure - back up your data NOW, then go out and purchase a new HD and clean install.

 

[richc46]

LOL read your post too quickly. Missed the hard drive problems. I agree with the above post.

 

[SGrundy]

I talked to Staples and they told me that every hard drive has bad sectors. Is this true?
But, I can take my computer in and they run diagnostics for around $70 and if they find something wrong the $70 will go towards the part. You're pretty sure this is the hard drive.

It would not startup today and went in to startup repair only it would not load. So, I rebooted and it booted up fine.

 

[NoelDP]

Staples/Arse/Elbow - pick any two (not three!)

All disks have bad sectors, yes - but they are hidden from view until they get to the point where all excess sectors have been marked as bad, and the effective capacity of the drive is affected. This excess can be quite large (easily a couple of thousand) depending on the size of the disk. Windows does not see them (they are handled by the drive itsekf) until this excess is used up. No disk should ship with bad sectors shwing to Windows CHKDSK.
Therefore the 224 bad sectors CHKDSK found has to be added to the potentially hundreds or thousands of bad sectors already on the disk.
This means that you have a creeping failure on the drive and it WILL fail completely, and probably sooner rather than later.

I'd almost take odds, that if you were to run another CHKDSK /R now the number would be higher.

 

[SGrundy]

I'll give it a try and let you know!!!

Probably have to buy a new harddrive!!!!

 

[NoelDP]

BACK UP YOUR DATA FIRST!!!!
Running another CHKDSK may be the straw that breaks the camel's back!

 

[SGrundy]

Actually I was mistaken. The chckdsk which file I attached reads 224 kb in bad sectors, not 224 bad sectors. Sorry!!!

I have made an image with Macrium before this started happening. I periodically make one just in case of any problems.

 

[NoelDP]

That still means 56 bad sectors @4KB/sector.

It's still bad enough to be very gentle with the drive until it's replaced, and/or you have all data backed up externally.

 

[SGrundy]

It seems to do this on initial bootup. I can boot it up all day long and it works fine.

I have backed it up to a portable drive.

It is always the same drivers when I get BSODs. Does this point to anything?

 

[NoelDP]

Yes - but until you have a firm base to work on, it's a rather pointless exercise, IMHO.

I'm not a BSOD specialist - so you'll have to wait for someone else to comment in detail, and we're rather short-staffed at present.

 

[SGrundy]

Thank you!!!
Much appreciated!!!

 

[richc46]

Ill check your files, again, tomorrow. Post any new reports.

 

[SGrundy]

Thank you!!!

 

[SGrundy]

Every morning my computer either shuts down or goes to blue screen and then wants to run computer repair. I usually tell it to start windows normally and it usally works from then on.
However it has gone into critical error later on in the day for no reason i can see.

When I check the Event View logs it gives me Event 0.
The description for Event ID 0 from source (gupdate, hpqcxc08, hpqddsvc, HPSLPSVC, one of these) cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

It has been gupdate the most. Do you think I have corrupted files or maybe a rootkit virus.
I tried running a rootkit scan with Avast but the computer crashed when it got to a certain point

 

[richc46]

Try an online scanner, such as this
ESET Online Virus Scanner | ESET
I use this one, too, for extra protection. You can keep this one and use another such as Microsoft Security Essentials etc, in the future.

 

[SGrundy]

I' ll give it a try.

 

[SGrundy]

The Virus scanner found an infected file called
a variant of Win32/SweetIM.B application. Have you heard of it?