Does windows shut off HDD before BSOD?

[Linux711]

I am trying to diagnose a BSOD that says something about winlogon being corrupted. Before the BSOD occurs, I can hear the hard drive spinning down. Is it meant to do that or not? If not, I am assuming there is something wrong with the hard drive, it's shutting down, and then causing the BSOD because the files can't be read.

I am going to attempt a chkdsk while we discuss this because I am thinking it might just be a corrupted file system.

EDIT: Completed chkdsk with no problems found.

[Allan]

1) If you are going to run checkdisk, the correct command is chkdsk /r

20 Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

[Linux711]

I think I figured it out already. I had installed some additional RAM in the system when the problem started occurring. I did a RAM test (and it was good), so I assumed the problem was something else, however I just took out one stick of RAM and it works now. It's weird though because it doesn't matter which stick I take out. I guess it simply can't handle more than 3 RAM sticks at a time.

[truenorth]

Given your concerns re the computer's abilities in the area of RAM.I suggest rather than guess you run a crucial scan with whatever you had in the computer originally and the test should tell you what you do have and what amount and type you can add.We don't know the computer brand and model nor what you had/what you added.Both with regards to compatibility and how much more(if any) you can add.truenorth

[Linux711]

what you do have and what amount and type you can add

I know what I have and how much I can add, that's how I purchased it. I am not going to randomly start buying RAM.  It is still working perfectly, so I am almost positive the problem has been fixed. After some research, I found out that some older motherboards can not have all RAM slots filled because it causes a drop in voltage to the RAM, thus causing errors.