Sign in with
Sign up | Sign in
Your question

BSOD's since yesterday

Last response: in Windows 7
Share
February 11, 2012 10:40:26 AM

Yesterday my computer started to give me some BSOD's related that is something wrong with my HDD.

First BSOD:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000024 (0x00000000001904fb, 0xfffff88009b09158, 0xfffff88009b089b0, 0xfffff80003336142).

Second BSOD:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffffffffffffff0, 0x0000000000000000, 0xfffff800030c597a, 0x0000000000000000).

Third BSOD:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000003, 0xfffffa8006bd1600, 0xfffffa80063d1600, 0xfffffa8006bd1600).

Minidump for the last BSOD:http://www.mediafire.com/?0s463edc57yhksf

I must say that I didn't install anything for about one week before I started to get this BSOD's.

More about : bsod yesterday

February 11, 2012 10:52:50 AM

Another BSOD:

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2 (0x0000000000000007, 0x000000000000109b, 0x0000000000000010, 0xfffffa8009060320).

Minidump:http://www.mediafire.com/?9r2hz76nvpsld9j
Related resources
a b $ Windows 7
February 11, 2012 12:20:51 PM

You have serious problems with your computer if you are getting these errors, The reason that you are getting these errors is because the NTFS filling system has become badly corrupted which could have been caused by a root virus or faulty memory.
The first thing to do is to run chkdsk c: /p /r preferably from the recovery console but you could try it from the search box. it would also be a good idea to run SFC /scannow for the command box as the administrator. It may be better to simply reinstall the operating system. Don't forget to test your memory with memtest86 4.0a for at least three passes and if you are not going to reinstall your operating system then scan your computer with a virus scanner that checks for root viruses.
February 11, 2012 12:33:16 PM

Thank you guys. I will try to run memtest now and see if I find something. I have build this computer 2 months ago and this are my first problems.
February 11, 2012 4:24:32 PM

I have run memtest and it showed a lot of errors. I don't know what is not working but from pictures I think it is the CPU.
Pictures: http://imgur.com/a/6qJ6v#0
February 11, 2012 4:38:06 PM

RMA your ram
February 11, 2012 4:40:54 PM

eggbrook said:
RMA your ram

So all BSOD's are from ram? Thank you for your quick answer!
I used memtest86 4.0 and memtest86+ 4.20
a b $ Windows 7
February 11, 2012 7:03:35 PM

Quote:
I have run memtest and it showed a lot of errors. I don't know what is not working but from pictures I think it is the CPU.


It is highly unlikely that your CPU is at fault the problem is much more likely to be caused by your memory, although a faulty power supply can can cause memory problems. Try testing the memory one stick at a time to see if it is only one memory stick that is causing your problem.
Don't forget that even if you sort the memory error you will still need to fix the filing system corruption, but at least it won't happen again..
February 11, 2012 7:29:08 PM

pjmelect said:
Quote:
I have run memtest and it showed a lot of errors. I don't know what is not working but from pictures I think it is the CPU.


It is highly unlikely that your CPU is at fault the problem is much more likely to be caused by your memory, although a faulty power supply can can cause memory problems. Try testing the memory one stick at a time to see if it is only one memory stick that is causing your problem.
Don't forget that even if you sort the memory error you will still need to fix the filing system corruption, but at least it won't happen again..


And how I fix that ? Is really needed to fix that if I will not get any BSOD's ?
a b $ Windows 7
February 11, 2012 7:40:14 PM

If you fix the memory problem you may still get blue screens because your NTFS filling system is corrupt and you need to fix it with chkdsk. However it is the memory error that is causing the file corruption in the first place
February 11, 2012 7:43:20 PM

I did a check on my HDD too but no error. Can you please tell me how I can repair my NTFS file system ?
a b $ Windows 7
February 11, 2012 7:46:17 PM

If chkdsk found no error and SFC /scannow found no problems then any blue screens will be caused by the faulty memory.
February 11, 2012 7:48:38 PM

pjmelect said:
If chkdsk found no error and SFC /scannow found no problems then any blue screens will be caused by the faulty memory.

I type sfc /scannow in cmd ? and THANK YOU for you fast response !
a b $ Windows 7
February 11, 2012 10:46:19 PM

Quote:
I type sfc /scannow in cmd ? and THANK YOU for you fast response !


Note, you must run the command box as the administrator, by right clicking on it and select run as administrator.
February 12, 2012 8:10:06 AM

pjmelect said:
Quote:
I type sfc /scannow in cmd ? and THANK YOU for you fast response !


Note, you must run the command box as the administrator, by right clicking on it and select run as administrator.

I did a chkdsk and sfc /scannow and no errors have been found. My computer seems to be ok now. I will close this thread if everything is working until tomorrow.
February 12, 2012 8:26:27 PM

Thank you guys for your time and your support!
a b $ Windows 7
February 13, 2012 11:17:17 AM

Bug Check 0x24: NTFS_FILE_SYSTEM

Caused by either HDD or RAM problems.

Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA

Caused by either HDD or RAM problems.

Bug Check 0x19: BAD_POOL_HEADER

Caused by either HDD or RAM problems.

Bug Check 0xC2: BAD_POOL_CALLER

Caused by either HDD or RAM problems.


Looking at some of the info, I'm leaning toward RAM. In the last two cases, it looks like the pool is getting corrupted, hence why I suspect a RAM problem rather then a HDD problem. Run memtest86 on each stick of RAM at a time, and hopefully you can isolate a bad stick.
February 15, 2012 1:22:14 PM

gamerk316 said:
Bug Check 0x24: NTFS_FILE_SYSTEM

Caused by either HDD or RAM problems.

Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA

Caused by either HDD or RAM problems.

Bug Check 0x19: BAD_POOL_HEADER

Caused by either HDD or RAM problems.

Bug Check 0xC2: BAD_POOL_CALLER

Caused by either HDD or RAM problems.


Looking at some of the info, I'm leaning toward RAM. In the last two cases, it looks like the pool is getting corrupted, hence why I suspect a RAM problem rather then a HDD problem. Run memtest86 on each stick of RAM at a time, and hopefully you can isolate a bad stick.


I did that and one of my RAM modules was the problem. Thank you for your support :D 
July 3, 2012 12:04:54 PM

I am unsure what the actual problem is. However I am from NY. I know multiple people including myself who this happened to yesterday. I do believe it has something to do with windows updates.

I have had similar issues like this in the past.

How I fixed it twice: First shutdown. Then restart the pc. After doing this it gives a few different options depending on your computers OS (operating system). It may say boot in safe mode boot in safe mode with networking....


Well try all of the options it gives you eventually one will try asking if you want to do a test of some sort I forget (I just did it and paid little to no attention). Then it will give you an option to do a system restore. Do the restore and everything will work correctly.

I know this works. I did it then said exactly what I just said to my sister in a txt message, who just so happens to know almost nothing about computers.

I hope this helps you as well.
!