• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Blue screen Memory_Managment

scypheroth

scypheroth

Member
well i formatted my old computer and reinstalled windows 7 because im selling it so i wanted a fresh new install of it for the customer.

-windows 7
-300G HDD
-350watt power supply
-msi mobo
-AMD semperon 2.8GHz
-2G DDR3 RAM

It will run then at random when it feels like it, it will crash to bluescreen and start dumping memory and restart....any ideas? i ran MemoryTest64 or whatever 4 times and passed with no issues...
 
here r the latest dumps

On Fri 10/18/2013 4:11:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101713-41433-01.dmp
This was probably caused by the following module: shareduserdata.sys (SharedUserData+0x0)
Bugcheck code: 0x1A (0x3452, 0x3175000, 0xFFFFF700010B5758, 0x25A000005BB92424)
Error: MEMORY_MANAGEMENT
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: shareduserdata.sys .
Google query: shareduserdata.sys MEMORY_MANAGEMENT



[FONT=Segoe UI, Arial]On Sun 10/13/2013 3:27:23 AM GMT your computer crashed
crash dump file: C\Windows\Minidump\101213-35053-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x6F880)
Bugcheck code: 0x4E (0x99, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sun 10/13/2013 1:43:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101213-29156-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x6F880)
Bugcheck code: 0xA (0xFFFFF6FB82202000, 0x0, 0x1, 0xFFFFF800028AA780)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sun 10/13/2013 12:20:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101213-35661-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x6F880)
Bugcheck code: 0x1A (0x41284, 0x4A10001, 0x76FD3, 0xFFFFF70001080000)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 10/12/2013 8:35:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101213-34226-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x4A359C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8002C86038, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]WHEA_UNCORRECTABLE_ERROR[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 10/12/2013 8:22:21 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101213-49701-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x6F880)
Bugcheck code: 0x1A (0x41284, 0x465C001, 0x6F309, 0xFFFFF70001080000)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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 that cannot be identified at this time. [/FONT]
 
I see three possible causes for those error codes:

Did you install any additional drivers after you formatted?

Find a SMART testing utility and (even better) a diagnostic program from the hard drive manufacturer. See if they report any issues.

If both of those check out (all Windows certified drivers and no hard drive problems) you are probably looking at a bad stick of RAM, memtest just didn't catch it.
 
ok so ran seagates S.M.A.R.T scan 6 times and it passed them all. and ran a short DTS test with a pass...im going to run the memory test a few more times before i its memory...
 
Well it passed another 10 Memory tests...and 5 more SMART tests...i dont know wtf to do...im going to swap out harddrive to see if that helps then if that dont work guess ill swap out memory and go from there
 
Did the system only start manifesting this issue when you reformatted? Meaning, did it function normally until then?

And, in the past, were you also running W7 64-bit?(I do see you said "REINSTALL").... And with only 2 GBs of DDR3?

If yes re all of the above, then, despite yr ram passes technically, and if yr 2GBS comprises two sticks and not one....I would test each stick alone in each slot and try to boot, as per KETCHUP.

Might you have other compatible sticks somewhere?

Kinda broke my heart you ran TEN mem tests. But also reminds me of me a little.:\🙁

Re SMART diagnostics for a drive, I always start with the fastest: the one in SpeedFan.

Very frustrating this is, for sure.:\
 
Last edited:
Well today i put on new CPU paste. Swapped out the hard drive for 2 different ones and swapped out the RAM for the RAM out of my WORKING PC that i am currently typing on...and im STILL getting the same blue screens (IRQL_NOT_LESS_OR_EQUAL or MEMORY_MANAGEMENT) or random restarts....im starting to think its the power supply...why you ask? this setup worked PERFECT when i had it in my old case...only thing that is now different is the power supply...would a bad PS throw these blue screens or cause random restarts?
 
Bad power supply can throw all sort of problems. Makes it difficult, as there is no error that would specifically interpret to "not enough power."

What ps are you running?
 
a crappy factory antec that came with the case...shud have noted that the case n p/s r almost 6 years old...350watt...i had to replace on fan internally in the PS...BUT its strange...when im running memory test overnight for 8+hrs the computer never shuts off...but iff i start it up and run windows it will either throw blue screens or randomly restart...
 
Last edited:
denis280 said:
Hey if you don't like my comment then mind your own business
Click to expand...

Don't get defensive. Every thread I've seen you in, you're barking about the PSU, no matter what the problem is. That, and you call them "rams." Something tells me that we'd be better suited getting repair advice from some of the more seasoned members.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top