Sign in with
Sign up | Sign in
Your question

BSOD 0x00000024 Help please

Last response: in Windows 7
Share
January 26, 2012 5:21:24 PM

So I started getting this bsod message today, BSOD 0x00000024 and it has happened 2 times already. I have been searching online and getting many different answers. But one common response was that it might be corruption of the NTFS file system. I have done a disk check on my HDD that runs my windows 7 but was unsure if it found errors and fix them. It hasn't happened in a solid 40min as of writing this post. I have recently added a 60gb SSD to my system as well has new ram sicks. I went from 4GB to 8 GB. I removed the old 4GB and replaced with the 8GB. I read somewhere that it might be my ram. Maybe a bad stick? If it is I would like to know so I can throw my old sticks back in and purchase a new set of RAM later. Of course only if it's an issue with my ram. Anyways I'm really unsure of what exactly is causing this issue. Somethings I've been noticing is that my google chrome has been crashing a lot lately and my windows explorer stopped working the other night. My computer has just been a little shaky lately. Any help would be greatly appreciated!

More about : bsod 0x00000024

a b $ Windows 7
January 26, 2012 5:46:05 PM

Try running memtest: http://www.memtest.org/ and see if any errors show up, RAM issues tend to be the leading cause for BSOD's.

Also try the chkdsk /f command for error checking, you can also just try reinstalling the OS too.

m
0
l
January 26, 2012 5:48:01 PM

Run memory test. I would bet its your RAM. Anytime you upgrade your RAM and start to see BSOD thats what it will be 95 percent of the time. Very common. I've bought 10 sticks of ram over 2 years from all of the major sellers and have had 2 of them bad straight out of the box. Run the memory test with both sticks first. If it shows errors RMA the ram. If you really want you can run the test with the sticks individually to find out which is the bad one, but likely you're sending them both back anyway!
m
0
l
Related resources
Can't find your answer ? Ask !
January 26, 2012 5:53:21 PM

Here is the problem. When I bought the RAM I wanted to memtest it right away but my shitty ass OEM mobo from HP just wont let it work. Anytime it tries to boot from the CD drive it loads it up and then it just says "loading test" and nothing happens. I'm upgrading my mobo and cpu in about 4-5days so I'm going to be re-installing windows anyways...It's just that this HP computer came preloaded with windows 7 so I think I have to buy a copy of the OS.
m
0
l
January 26, 2012 6:27:20 PM

Locate the .dmp files in C:\windows\minidump then download Windows debugging tools. Or if some one has the software already installed you can give them the files in the folder and they can determine the cause of the BSOD.

If could very well be corrupt system files or file structure. Teh Google points towards something related to those two.
m
0
l
January 27, 2012 12:27:02 AM

I just started getting these BSODs today Both 0x00000024 and 0x00000050. I have the bluescreenview program if anyone could tell me how to share my dump files so you can see. I'm not sure as to what the problem is. I have recently installed a GTX560 ti 448 cores video card and SSD for games and 8GB of ram. I think it's my RAM. I have tried Memtest but it wont ever load up and i think thats because my mobo is a OEM crap hole from HP. anyways any help on this 2 errors would be awesome. Please!
m
0
l
January 27, 2012 12:28:34 AM

These were my files just from today:


==================================================
Dump File : 012612-20155-01.dmp
Crash Time : 1/26/2012 12:48:15 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff6f8`50069af0
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`036a9238
Parameter 4 : 00000000`00000005
Caused By Driver : rasl2tp.sys
Caused By Address : rasl2tp.sys+161c7d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012612-20155-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 301,519
==================================================

==================================================
Dump File : 012612-15022-01.dmp
Crash Time : 1/26/2012 1:36:55 PM
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 00000000`001904fb
Parameter 2 : fffff880`038f33f8
Parameter 3 : fffff880`038f2c50
Parameter 4 : fffff880`010f8366
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+aa366
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012612-15022-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 301,519
==================================================

==================================================
Dump File : 012612-22230-01.dmp
Crash Time : 1/26/2012 9:09:26 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff0a0`1c454728
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`036aefd0
Parameter 4 : 00000000`00000007
Caused By Driver : raspppoe.sys
Caused By Address : raspppoe.sys+294c340
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012612-22230-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 301,519
==================================================
m
0
l
January 27, 2012 1:53:43 AM

Ahh ty. Very helpful thread. Well my video card was working fine when i got it. Then I got new RAM after so I could have 8GBs so I'm assuming from what you linked that this is indeed an issue with my current RAM sticks. I kept my old ones which worked fine so I have backups.
m
0
l
January 27, 2012 2:03:47 AM

It's just hard for me at the moment to determine what it is. I'm more then likely sure it's my ram as I have just recently installed it. Not sure if it's the vram on my gtx 560 ti 448 or a corrupted NTFS volume. I got the NTFS bluescreen as well as you can see from my list but I ran disk check so if there were any errors it should have been repaired right? It also says security software can cause this bluescreen. I'm running Avast. I have been using it for a while and it has never given me much of a problem. It updates on a regular basis. You know now that i mention I was running a scan on avast when I got my last bluescreen. Maybe it's an issue with avast, maybe my RAM is okay.
m
0
l
a b $ Windows 7
January 27, 2012 1:28:29 PM

using avast also never had a blue screen with it do a memtest for memory sticks one at the time
m
0
l
a b $ Windows 7
January 27, 2012 2:10:26 PM

0x24 = NTFS_FILE_SYSTEM. Usually indicates a problem with the HDD, though shoddy RAM can cause this BSOD to appear under some circumstances.

Since you upgraded two things at once, I would put back the 4GB sticks and see if the issue goes away. If so, one of the new sticks you have is probably bad. If not, then the new SSD you got could be a problem. [Speaking of which, check for firmware updates, since some brands have known issues with corruption...]
m
0
l
a b $ Windows 7
January 27, 2012 2:17:24 PM

Quote:
PAGE_FAULT_IN_NONPAGED_AREA


This typically points to RAM, though the fact you also got "NTFS_FILE_SYSTEM" means it could be the HDD...

My guess is a memory problem thats causing corruption of a critical NTFS file structure. Run memtest86 on each stick of RAM.
m
0
l
January 27, 2012 5:42:03 PM

Well for some reason memtest never loads and I think it's b/c me Mobo is an OEM piece of crap from HP. Anyways I removed the RAM sticks and put the old ones back in and the problems seemed to have stopped. I'm guessing the RAM was causing all those issues, like the NTFS file corruption. I was also getting a lot of browser crashes which I read is caused by bad memory. So yea removing the new ram seemed to fix it. Thanks guys!
m
0
l
January 27, 2012 5:43:29 PM

I removed my new RAM sticks and put my old ones back in and the problems have since stopped. My new RAM seemed to be causing all those errors. Thanks for all the help everyone!
m
0
l
a c 395 $ Windows 7
January 27, 2012 5:45:49 PM

This next topics has been merged by Area51reopened
  • BSOD 0x00000050 +0x00000024
    m
    0
    l
    a b $ Windows 7
    January 27, 2012 6:19:47 PM

    If the issues went away, then its likely one of the two sticks was bad. You can try testing with one at a time to isolate the bad stick.

    You can also give Windows Memory Diagnostic a shot. Not as good as memtest, but it might find the error if memtest refuses to run.
    m
    0
    l
    January 27, 2012 6:20:49 PM

    OK I'll give that a try, thanks
    m
    0
    l
    !