BSOD Stop error, BSOD |
![]() ![]() |
BSOD Stop error, BSOD |
Feb 24 2008, 11:48 PM
Post
#1
|
|
|
Member ![]() ![]() Posts: 91 From: PA OS: (x64) Windows Vista™ Ultimate (6.0, Build 6000) (6000.vista_gdr.071023-1545) |
CACHE_MANAGER STOP: 0x00000034 & PFN_LIST_CORRUPT STOP: 0x0000004E but i read on another forum it could be a memory issue I have 8gigs of ram look at my sig for system spec also i'm running bios version 904 for my mobo should i flash to the beta 905? nad see if it makes a difference? This post has been edited by Mr.Logic: Feb 24 2008, 11:56 PM |
|
|
Feb 25 2008, 04:59 AM
Post
#2
|
|
![]() Tech Staff Posts: 2,201 From: Frankfort, Ky OS: vista home premium |
Hello, and welcome to Geeks To Go.
This is from a Microsoft article, it is about Windows 2000, but may get you headed in the right direction. QUOTE Error Message: STOP: 0x0000004E (parameter, parameter, parameter, parameter) PFN_LIST_CORRUPT Explanation: This is a Windows 2000 Executive character-mode STOP message. It indicates the memory management page file number (PFN) list is corrupted. User Action: If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Microsoft Hardware Compatibility List to verify that the hardware and its drivers are compatible with Windows 2000. For information about the hardware, contact the supplier. If you are installing Windows 2000 for the first time, check the Windows 2000 system requirements, including the amount of RAM and disk space required to load the operating system. Also, check the Hardware Compatibility List to verify that the system can run Windows 2000. If Windows 2000 is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file. If the message continues to appear, select the Last Known Good option when you reboot. If there is no Last Known Good configuration, try using the Emergency Repair Disk. If you do not have an Emergency Repair Disk, contact your technical support group. The article can be found here. |
|
|
Feb 26 2008, 12:14 AM
Post
#3
|
|
|
Member ![]() ![]() Posts: 91 From: PA OS: (x64) Windows Vista™ Ultimate (6.0, Build 6000) (6000.vista_gdr.071023-1545) |
article = crap
i ran memtest86 v3.4a and picked up that both memory sticks in slot a1 and a2 where bad i'm going to check the stick indivualy now and see if its not just one of them they came out of the same pack so its going to be weird if they are both bad. |
|
|
Feb 26 2008, 05:48 AM
Post
#4
|
|
![]() Tech Staff Posts: 2,201 From: Frankfort, Ky OS: vista home premium |
QUOTE article = crap The article was meant to give a general idea as to the problem area, not a specific fix.. |
|
|
Feb 26 2008, 07:39 PM
Post
#5
|
|
|
Member ![]() ![]() Posts: 91 From: PA OS: (x64) Windows Vista™ Ultimate (6.0, Build 6000) (6000.vista_gdr.071023-1545) |
they should mention something in that article such test your memory the thing it says is it deals with a memory page file issue microsoft gives the biggest crap answers to some of there BSOD's why don't they give us that info on the BSOD? lol
ok i got a new error 0x00000101 what does that deal with is it an error in my OS or what the memory error stoped and both stick turned out to be crap This post has been edited by Mr.Logic: Feb 26 2008, 07:59 PM |
|
|
![]() ![]() |
Similar Topics
| Topic Title | Replies / Views | Topic Information | |||||
|---|---|---|---|---|---|---|---|
![]() |
1 / 654 | 12th May 2008 - 06:11 AM ibanez7 started - last by ibanez7 |
|||||
![]() |
0 / 447 | 18th August 2008 - 08:25 PM ITDAD started - last by ITDAD |
|||||
![]() |
3 / 672 | 3rd September 2008 - 09:50 AM Ang0769 started - last by SRX660 |
|||||
![]() |
2 / 891 | 3rd October 2008 - 07:25 AM argylecomputer started - last by AitrusSkyy |
|||||
|
Time is now: 8th January 2009 - 02:30 AM |
| Advertisements do not imply our endorsement of that product or service. The forum is run by volunteers who donate their time and expertise. We make every attempt to ensure that the help and advice posted is accurate and will not cause harm to your computer. However, we do not guarantee that they are accurate and they are to be used at your own risk. |