Many problems, computer unstable. Need Help

[kimsland]

@labateca have you read all posts here?

Also

It is likely to be a problem of excessive temperature processor

You're saying what exactly?

It is possibly likely to be a problem of excessive temperature within your processor.

And any recommendation? What would you have the member do exactly?

Please be very clear with your support replies.

 

[Nick_krambo]

So how exacty do I change the video memory in Bios? I haven't been able to find the setting.

Also in bios there is an option that says "OS select for DRAM > 64MB" and it can either be "OS2" or "Non-OS2." It says use OS2 for more than 64mb so i set it to that a couple of days ago. Is that the right option?

Still getting BSODs randomly.

And should the plug & play setting be on or off in bios?

 

[Nick_krambo]

One more thing to add...

The last 2 crashes were 0x0000001E errors and debugged the minidumps and found the first was caused by ntfs.sys and the second by amdk8.sys.

Anyone know if there is an update for my AMD Athlon x2 4600+ processor for Vistax64?

 

[kimsland]

Set it to Non-OS2
And 64 Meg

Then restart

 

[Nick_krambo]

I can't figure out how to change my video card memory. There doesn't seem to be an option in bios or in nvidia

 

[kimsland]

So how exacty do I change the video memory in Bios? I haven't been able to find the setting.
Also in bios there is an option that says "OS select for DRAM > 64MB"

Yes that's it. And seems to be fine with that setting

Also can you please give an update. ie how's it going (or not going) still ?

 

[Nick_krambo]

Here's my last 5 minidumps. Still getting BSODs.

Same two error codes I have been getting lately.

 

[kimsland]

Inside the 5 MiniDumps:

BugCheck 1E, {ffffffffc0000005, fffff80001f50d3a, 0, 0}
Probably caused by : fileinfo.sys

Probably caused by : amdk8.sys

Probably caused by : ntkrnlmp.exe

BugCheck 3B, {c0000005, fffff80001e87fd9, fffffa600a640280, 0}
Probably caused by : win32k.sys

BugCheck 3B, {c0000005, fffff80001f82d3a, fffffa6008130100, 0}
Probably caused by : ntkrnlmp.exe

C0000005 Access Violation

fileinfo.sys possible fault DirectX

It could be a great number of things. Common culprits include virus's/spyware, hard drive going bad, driver installation errors, Micro$oft/Windows error

amdk8.sys (usually processr.sys) This concerns me, looks like your motherboard bios settings for your CPU could be wrong (please check for automatic setting only in bios) or sad to say - but possible update bios to current version.

 

[Nick_krambo]

My cpu settings in bios are automatic and i updated my bios not too long ago as an attempt to fix this. I'm hoping this isn't a faulty processor. I'll try shutting down anti-virus stuff and see if that helps. Any way to test hardware?

 

[kimsland]

Go to your manufacture support page for your motherboard.
Some have excellent diagnostic tools available

 

[Nick_krambo]

I got an interesting BSOD I haven't seen before. STOP: 0x000000E4 (0x0000000000000001, 0xFFFFF8002011540, 0x00000000000000E5, 0x0000000000000000)

It hasn't been making a crash dump, its just frozen, so i'll wait a little longer and see if it recovers. I'm quite confused

 

[kimsland]

http://support.microsoft.com/kb/945577

Please follow the steps in "Resolution"

 

[Nick_krambo]

The microsoft fix was already changed in my registry, Here is a newer dump.

 

[Nick_krambo]

Here are a few more dumps I have gotten in the past couple of mins, I am leaning towards a clean install, but because I still don't know if this is hardware related, I don't know what to do.

 

[Route44]

Your first two dumps point to memory corruption while the other four cited MS core drivers for your OS citing possible hardware incompatibility as well as a corrupted driver pool.

I know you have run MemTest, but from personal experience when I had corrupted RAM my BSODs were all over the place saying all kinds of reasons; your BSODs are 0x0A (twice), 0x4E, 0x24, 0xC5 and 0xD1.

If you do a clean install and your RAM is corrupted you'll have the same issues all over again.

Did you run a harddrive diagnostics?

 

[kimsland]

Inside the last 4 MiniDumps:

Probably caused by : ntkrnlmp.exe

BugCheck 24, {1904aa, fffffa60019e6d28, fffffa60019e6700, fffff80001f92d3a}
Probably caused by : Ntfs.sys

Probably caused by : storport.sys

Probably caused by : USBPORT.SYS

Route44 just got in before me!

 

[Nick_krambo]

I haven't run harddrive diagnostics because Western Digital Data Life Guard doesn't pick up physical drives (possibly cause of RAID?). I ran a 2 pass windows memory diagnostic for a comparison to memtest and no errors as well.

 

[kimsland]

I would also recommend Check Disk:

Manual steps to run Chkdsk from My Computer or Windows Explorer

• Open My Computer, and then right-click the hard disk that you want to check.
• Click Properties, and then click Tools.
• Under Error-checking, click Check Now. A dialog box that shows the Check disk options is displayed

Use one of the following procedures:

• • To run Chkdsk in read-only mode, click Start.
• • To repair errors without scanning the volume for bad sectors, select the Automatically fix file system errors check box, and then click Start. (tick)
• • To repair errors, locate bad sectors, and recover readable information, select the Scan for and attempt recovery of bad sectors check box.

Note If one or more of the files on the hard disk are open, you will receive the following message:

The disk check could not be performed because the disk check utility needs exclusive access to some Windows files on the disk. These files can be accessed by restarting Windows. Do you want to schedule the disk check to occur the next time you restart the computer?

Click Yes to schedule the disk check, and then restart your computer to start the disk check.

Wait until Chkdsk finishes Checking / Repairing any faults
Windows will then either restart your computer or continue loading Normally.

 

[Nick_krambo]

I have started a full chkdsk, and it looks like it will be running for a while still. I'll leave it over night and give an update in the morning.

 

[Nick_krambo]

chkdsk is done, reports volume is clean. Memtest wouldn't pick up good ram that just isn't compatible right? Cause i have a feeling that might be what this comes down to.

 

[kimsland]

In-compatible ram just won't work, at all. So therefore don't worry too much. But, in saying that, it is recommended to use the same manufacture and rating, ram cards (as there may be issues that even Memtest might not pick up).

So far the harddrive diagnostics are not done (due to your Raid configuration)
And Memtest really requires 7 passes to fully (as much as Memtest can) confirm ok

You could take your harddrives out of Raid configuration and test one at a time.
Even the data cables can be an issue

Looking back over the Minidumps, you may also want to update your drivers, directly from the manufactures support page (for your computers motherboard)

By the way, these issues can be related to software (Lets say Norton, or disk monitoring/backup software) so re-confirm that your software, running, is required

That about covers it. Please do lots more testing!

 

[Nick_krambo]

My drivers are up to date, and I would have to wipe my hard drive to take them out of raid, so i don't want to do that. I am going install each stick of RAM one at a time and run memtest. I'll get back with the results soon.

 

[Nick_krambo]

First stick of RAM ran 3 memtest passes with no errors. So i booted up and attempted to run 3dmark a couple of times which froze up and the display driver stopped working both times (had to force quit). Then I got a 0x000000c4 crash and went to driver verifier and turned on all checks but deadlock detention and to check all drivers on the computer. Upon reboot I recieved a BSOD: 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL.

What I'm pretty much getting out of all of this is that my problem is driver related and not hardware. No idea how to find it though.

 

[kimsland]

Here's MS fix for that error: http://support.microsoft.com/kb/325672 using verifier

 

[Nick_krambo]

After lots of testing, I still can't find the cause. BSODs point to kernel related drivers. Switched out ram a couple of times and never any memtest 3.4 errors. Tried a different keyboard and a different mouse with no improvement. Uninstaled and reinstalled graphics drivers. Is it possible that my motherboard dimm slots are shot? Or would that produce memtest errors?

Am i at the point of a full reinstall? Even so, will that actually help?