Sign in with
Sign up | Sign in
Your question

BSOD Memory Management

Last response: in Windows 7
Share
September 18, 2011 1:37:31 AM

Im having trouble with this BSOD, Memory Management...

What i have done..

- Run Memtest86 it says i have memory troubles. I change them for new ones.
- I install Windows 7 Ultimate x86 again.
- Installed all drivers from it manufacturer.


After doing this i still getting the BSOD,

So, i put out the graphic card and start using the one that comes integrated in the motherboard and all seems to run OK. NO BSOD. So i thought was the Video Card.

I take my video card and test it on another computer, i was playing NBA 2k11 at maximum Resolution 1024*768.. and All high.

NO BSOD, No Problem all working Correctly.

I want to know what you think.. is this motherboard problems?


Computer spec:

Ati radeon HD4850 1GB Gddr3
I5 3.2Ghz 650
Motherboard msi H55m-p33
4-Memory 2GB OCZ PC3-8500

More about : bsod memory management

September 18, 2011 1:45:26 AM

These are WhoCrashed Logs

On Sun 18/09/2011 01:18:29 a.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\091711-19437-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0xA885)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF88393885, 0xFFFFFFFF960135D8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Administrador de filtros del sistema de archivos de Microsoft
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 18/09/2011 01:18:29 a.m. GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0xA8ED)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF88393885, 0xFFFFFFFF960135D8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Administrador de filtros del sistema de archivos de Microsoft
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 18/09/2011 12:51:42 a.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\091711-19936-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x859EB)
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 18/09/2011 12:43:48 a.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\091711-18969-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x9B936)
Bugcheck code: 0x1A (0x888A, 0xFFFFFFFF9D4F9B90, 0xFFFFFFFFC003D969, 0xFFFFFFFF83DFD1E4)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 17/09/2011 11:10:53 p.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\091711-15038-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCDFC)
Bugcheck code: 0x4E (0x99, 0x36D01, 0x2, 0x62E00)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 17/09/2011 08:54:50 a.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\091711-14898-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x1A (0x41289, 0x6B443001, 0x13A2, 0x6B543C05)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 17/09/2011 04:07:08 a.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\091711-13696-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x1A (0x411, 0xFFFFFFFFC0022B90, 0x393B3824, 0xFFFFFFFFC0023F61)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 17/09/2011 04:02:44 a.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\091711-15210-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x4E (0x99, 0x3FB19, 0x0, 0x3EC19)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 17/09/2011 01:14:31 a.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\091611-15225-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x4E (0x99, 0x35D9D, 0x0, 0x35F9D)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

m
0
l
September 19, 2011 8:46:36 PM

Someone can help me?
m
0
l
Related resources
a b $ Windows 7
September 19, 2011 9:37:36 PM

ejlt1991 said:
Im having trouble with this BSOD, Memory Management...

What i have done..

- Run Memtest86 it says i have memory troubles. I change them for new ones.
- I install Windows 7 Ultimate x86 again.
- Installed all drivers from it manufacturer.


After doing this i still getting the BSOD,

So, i put out the graphic card and start using the one that comes integrated in the motherboard and all seems to run OK. NO BSOD. So i thought was the Video Card.

I take my video card and test it on another computer, i was playing NBA 2k11 at maximum Resolution 1024*768.. and All high.

NO BSOD, No Problem all working Correctly.

I want to know what you think.. is this motherboard problems?


Computer spec:

Ati radeon HD4850 1GB Gddr3
I5 3.2Ghz 650
Motherboard msi H55m-p33
4-Memory 2GB OCZ PC3-8500


OK, who made the card?



http://support.amd.com/us/certified/graphics-cards/Page...



What PSU u have, what driver are u using?

m
0
l
a b $ Windows 7
September 19, 2011 9:49:43 PM

Are u using 8GB of RAM?

Is the RAM exchanged?
m
0
l
September 19, 2011 11:15:14 PM

Now im using just 4gb of ram, on slot dimm 1..

Yes i change them, i buy new one.

Thanks for your reply


Note: "Im running an old copy of windows xp home edition, and all is working correctly." i dont know what to do.
m
0
l
a b $ Windows 7
September 19, 2011 11:32:23 PM

U said it "Run Memtest86 it says i have memory troubles. I change them for new ones. "

Try to swap the RAM sticks around. Maybe only one is bad.

What PSU u have? Watts?
m
0
l
September 19, 2011 11:46:06 PM

I swap them and put a new Ram stick.

530 watt - Raidmax Hybrid

"I recently get another BSOD on XP of the same (Memory Management) these are the error codes.

Memory management
0x0000001 (0x00041284, 0x3a268001, 0100015ba5, 0xc0883000)
m
0
l
September 19, 2011 11:48:59 PM

I installed NBA 2k11 and was playing well, when i closed the game it just come the BSOD
m
0
l
a b $ Windows 7
September 19, 2011 11:51:06 PM

So RAM is error free in Memtest? Try Windows memory diagnostics. And what kind of video driver version are u using?
m
0
l
September 19, 2011 11:55:02 PM

Yes is free of error, im using Ati radeon catalyst the latest one in Ati Homepage
m
0
l
September 19, 2011 11:56:44 PM

Where is the Windows memory diagnostics?
m
0
l
a b $ Windows 7
September 19, 2011 11:57:51 PM

OK, but who made it? Not ATI(AMD).

Diamond,XFX or who?
m
0
l
September 20, 2011 12:00:48 AM

Powercolor, Ati Radeon HD4850 1Gb gddr3
m
0
l
a b $ Windows 7
September 20, 2011 12:01:54 AM

Also if u are using win7 x32 u don't have to use 8GB RAM, it can take advantage only 4GB at most, unless u have created Ram disk. Did u?
m
0
l
September 20, 2011 12:06:43 AM

No i didnt.

I have tested everything to get it working. Video cards, Memory, Power supply.

Dont know what more to do. im thinking on throwing it to the garbage.
m
0
l
September 20, 2011 3:02:30 AM

Ok thank you, ill be waiting for your response
m
0
l
October 6, 2011 12:47:46 AM

I resolved my problem i had 4 OCZ 2gb Memory, Change it for 2 New 4gb Memory.

What i think that my problem was is the motherboard was stressed because of the number of memory, so change it for two and voila!. Problem Fixed!

Thanks For your help
m
0
l
!