• "ntoskrnl.exe" BSOD's; "MEMORY_MANAGEMENT"
    8 replies, posted
Apparently for the past year I've been getting BSOD's every now and then. Why in the world my brother decided to tell me now, what the hell. He should've told me the first time he saw one, for all I know my system could slowly be rotting away by the minute. Anyways, 22 of them. I used BlueScreenViewer to see what I could come up with. Most of them are under the bug check string "MEMORY_MANAGEMENT" and a few are "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED." Here's some information on the first one that ever happened: 032012-38657-01.dmp 3/20/2012 7:52:21 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00041790 fffffa80`02414790 00000000`0000ffff 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+7cd40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17835 (win7sp1_gdr.120503-2030) x64 ntoskrnl.exe+7cd40 C:\Windows\Minidump\032012-38657-01.dmp 4 15 7601 292,000 Whatever they are, they're coming from the "ntoskrnl.exe" driver. I've done a little researching and it looks like it could be anything; most likely something with my ram or disk? Something corrupt with the .exe? I've tried the chckdsk /r and even other tools to look at the condition of my hard-drive, but everything seems to be good. I'll run more scans when I get the chance of course. Other than that, I can run the computer fine. With the exception of a BSOD in a very rare once in a while. Windows 7 64-bit 8GB Ram GTX 550 Ti Core 2 Quad Realtek Sound Hell, take my model number: CG5270 Honestly I'm not too computer savvy, especially when it comes to troubleshooting. But obviously whatever it is it's pretty serious. Well from the looks of it. Do you guys have any ideas? What should I do about this? I'd hate to start fresh, but I gotta do what I gotta do. I'll give you any other information you'll need at your request.
[QUOTE=zacht_180;36743531]Apparently for the past year I've been getting BSOD's every now and then. Why in the world my brother decided to tell me now, what the hell. He should've told me the first time he saw one, for all I know my system could slowly be rotting away by the minute. Anyways, 22 of them. I used BlueScreenViewer to see what I could come up with. Most of them are under the bug check string "MEMORY_MANAGEMENT" and a few are "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED." Here's some information on the first one that ever happened: 032012-38657-01.dmp 3/20/2012 7:52:21 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00041790 fffffa80`02414790 00000000`0000ffff 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+7cd40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17835 (win7sp1_gdr.120503-2030) x64 ntoskrnl.exe+7cd40 C:\Windows\Minidump\032012-38657-01.dmp 4 15 7601 292,000 Whatever they are, they're coming from the "ntoskrnl.exe" driver. I've done a little researching and it looks like it could be anything; most likely something with my ram or disk? Something corrupt with the .exe? I've tried the chckdsk /r and even other tools to look at the condition of my hard-drive, but everything seems to be good. I'll run more scans when I get the chance of course. Other than that, I can run the computer fine. With the exception of a BSOD in a very rare once in a while. Windows 7 64-bit 8GB Ram GTX 550 Ti Core 2 Quad Realtek Sound Hell, take my model number: CG5270 Honestly I'm not too computer savvy, especially when it comes to troubleshooting. But obviously whatever it is it's pretty serious. Well from the looks of it. Do you guys have any ideas? What should I do about this? I'd hate to start fresh, but I gotta do what I gotta do. I'll give you any other information you'll need at your request.[/QUOTE] It could be faulty RAM. If you have multiple sticks, try taking one out and seeing if you get the BSOD. This might pose the problem of waiting though, because you said it happens very rarely. You could also go into your BIOS (F8 or delete when your machine boots up, there should be a prompt that tells you the key, sometimes called setup) and run a memory test.
[QUOTE=Gnomical;36745522]It could be faulty RAM. If you have multiple sticks, try taking one out and seeing if you get the BSOD. This might pose the problem of waiting though, because you said it happens very rarely. You could also go into your BIOS (F8 or delete when your machine boots up, there should be a prompt that tells you the key, sometimes called setup) and run a memory test.[/QUOTE] Windows memory test is hilariously shit, don't waste your time with it. Get memtest [url]www.memtest.org[/url]
This is almost certainly a RAM problem. I had the exact same thing and I solved it by getting new RAM, but try taking out all but 1 stick, and moving said stick around to different channels and see what happens.
Alright guys, thanks. I'll try doing what you mentioned and get back to you.
are you sure about that rajan? are you SURE about that?
Hey BigPalooka, Is there any solution other than replacing RAM? I don't want to spend money right now.
Disable overclocks (just in case), or remove RAM modules one by one until you find a bad one. In my experience, 9 out of 10 times, you have defective memory stick(s). So there's no real way to fix it without spending money.
Sorry, you need to Log In to post a reply to this thread.