Multiple bluescreens

The memory isn't in the list on Biostars website but I've been told it should work, and I am from the UK. Someone just informed me they think the Hard Drive may be the cause of all this, do you think this is possible? Also if the new RAM doesn't solve anything I'm just going to format and hope for the best.

I am trying to figure out how a harddrive issue is giving you memory issues; in other words, how does this person logically conclude this?

We know that a) you are getting continuous memory corrupt reads though memory itself probably isn't corrupted, b) that your motherboard according to the manual and BIOS has your RAM set to the wrong voltage because of the motherboard voltage specs, and c) your RAM is designed for 1.8v but your motherboard's default voltage is 1.95 and, yes, that will cause memory issues.

You could run a harddrive diagnostics by using the harddrive manufacture's free harddrive diagnostic utility.

I think my desktop has had it, I'm having to type this from my laptop. I booted up my desktop and was greeted to a 6 minute boot, once I had successfully entered Windows a pop-up appeared telling me that "The system has recovered from a serious error" I dismissed this pop-up by clicking do not send, but then it came up again. I kept clicking do not send until I finally caved in and sent an error report, but then it popped up yet again. No matter what I did I could not get rid of the window. Also my desktop now has a serious delay doing anything, opening a window, right clicking or even moving the mouse will cause the computer to become unresponive for a good 30 seconds or so.

If that error report pops up again tell us what it says, i.e. what does it poit to as the problem.

This sounds like a different problem now. Find the make of your harddrive. Go to the manufacture's site and get their harddrive diagnostic utility and burn it to a CD using your laptop. Place it in your desktop DVD drive and reboot. It should take over without having to load to Windows.

I'm on my desktop now finding out what make my hard drive is, as for the error message it hasn't appeared again. I'm just checking Event Viewer and I have a lot of errors relating to my hard drive. The painful unresponsiveness is still here.




UPDATE: I've ran the tests on Seatools and these are my results:

S.M.A.R.T. Check - Passed
Short Drive Self Test - Failed
Long Drive Self Test - Failed
Short Generic - Failed
Long Generic - Failed

Excellent diagnostic work on your part. If you can, back up everything now A.S.A.P.!

If you can't access the harddrive slave it into another system and access it that way. You've got a failing harddrive.

Do you think the hard drive in anyway could be related to some of the bluescreens I've been having? I'm going to try to transfer the most important files over LAN to my laptop, or maybe on some CD-R's if I can find any. So I guess I'm going to have to buy a new one?

The minidumps always pointed elsewhere and as has been discovered your RAM voltage and the motherboard's RAM voltage default setting were causing issues.

So to say could the harddrive cause the blue screens I would have to say no. However, your most recent symptoms did point to your harddrive which SeaTools confirmed. It is not unheard of to have more than one problem at the same time.

Yes, you will need to buy a new harddrive.

I just ordered my new Hard Drive, 500GB Seagate for £35 and £7 next day delivery. I'm going to attempt running my PC with the current RAM installed but a single blue screen relating to memory and I'm going to change it, to be honest I've had enough of these errors. As for my current hard drive should I wipe it and store it somewhere or could I use it as storage?

Unless by some miracle you can repair the physical damage toos it after you wipe it. By the way, is your new harddrive the 11 series or 12?

It's this one:

http://tinyurl.com/35ugzhj

I believe it's series 12.

Yes, it is the 12 series and that is good. Their 11 series had serious issues but the 12 is good.

Just had a blue screen on my new hard drive. I checked for the .dmp file but my Windows folder doesn't have a Minidump section?

STOP: 0x0000007E sr.sys

Good thing is it has nothing to do with your new harddrive.

sr.sys ystem Restore Filesystem Filter Driver belongs to the software Microsoft Windows Operating System.

0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues.

Check Event Viewer Start > Run > EventVwr.msc > Okay for additional information.
What do you find?

I ran Event Viewer but I couldn't find any record of the bluescreen anywhere, also I still don't appear to have a Minidump folder. To hopefully save myself in the future I have ordered some new RAM, this to be exact:

http://www.crucial.com/store/partspecs.aspx?IMODULE=BL2KIT25664AA80A

Do you think it will work correctly with my motherboard?

Also I have bad news regarding my old hard drive. Whenever I try to boot my machine it will hang on the Windows XP splash screen for around 8 minutes, then I will get a bluescreen with this error code: STOP: C0000021A {FATAL SYSTEM ERROR} I tried inserting my Windows XP disc and selecting repair but I still get the same error screen. I was hoping to save a few more files from that hard drive but I suppose I can live without them. Would you say that it has officially died?

0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
This occurs when Windows switches into kernel mode and a user-mode subsystem, such as Winlogon or the Client Server Runtime Subsystem (CSRSS), is compromised. Security can no longer be guaranteed. Because Win XP can’t run without Winlogon or CSRSS, this is one of the few situations where the failure of a user-mode service can cause the system to stop responding. This Stop message also can occur as a result of malware infestation or when the computer is restarted after a system administrator has modified permissions so that the SYSTEM account no longer has adequate permissions to access system files and folders.

This is a serious error and I would have to say your harddrive is dead. However, there may be another way to access it but it will take a friend with tech knowledge and his/her system. Take your harddrive and "slave" it into his system and access your harddrive through his system. It may work.

As for the memory it isn't listed on Biostar's memory supported list but no list is ever exshaustive. Crrucial is a Tier 1 memory maker and one of the largest memory makers in the world Keep in mind their Ballistix line is a gamers/overclockers memory. It is 2.0v which is good as well as being DDR2-800 which fits the boards specs.

By the way, I was on another tech site yesterday and there was one thread with the poster raging of the fact that his Biostar board wouldn't allow him to run 1.8v of RAM. The default setting: 1.95v He was getting Blue Screens a plenty. It seems Biostar has many models that have this as the minimum setting. So you are not alone.

Earlier today I installed Windows 7 on my computer hoping this may fix some of the problems I've been having, but just five minutes ago I had a blue screen. I forgot to disable automatic restart so I don't know what the error message was.

0x00000109: CRITICAL_STRUCTURE_CORRUPTION
The kernel has detected critical kernel code or data corruption.

It cited memory corruption as the cause. In researching this error code the two standard diagnostic steps are Memtest for memory and a Harddrive diagnostics.

No surprise I just had another bluescreen, although this time I don't think it's related to the RAM.

STOP: 0X00000109

Modification of system code or a critical structure was detected.

Stop 0x109: CRITICAL_STRUCTURE_CORRUPTION
This indicates that the kernel has detected critical kernel code or data corruption.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 Reserved
2 Reserved
3 Reserved
4 The type of the corrupted region. You recieve this information in the dump: Modification of a function or pdata


The value of Parameter 4 indicates the type of corrupted region.

Parameter 4 Type of Corrupted Region, Type of Corruption, or Type of Action Taken That Caused the Corruption
0x0 A generic data region
0x1 A function modification or the Itanium-based function location
0x2 A processor interrupt dispatch table (IDT)
0x3 A processor global descriptor table (GDT)
0x4 A type-1 process list corruption
0x5 A type-2 process list corruption
0x6 A debug routine modification
0x7 A critical MSR modification



Cause
There are generally three different causes for this stop error code:

1. A driver has inadvertently, or deliberately, modified critical kernel code or data. Microsoft Windows Server 2003 with Service Pack 1 (SP1) and later versions of Windows for x64-based computers do not allow the kernel to be patched except through authorized Microsoft-originated hot patches. For more information, see Patching Policy for x64-based Systems.


2.A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was started. Normal breakpoints (bp) can only be set if the debugger is attached at start time. Processor breakpoints (ba) can be set at any time.


3. A hardware corruption occurred. For example, the kernel code or data could have been stored in memory that failed.