Could not allocate page table memory при обновлении bios
Система не видет всей памяти! БИОС определяет 3328 МБ,
в FM написано:
Due to chipset resource allocation, the system may detect less than 4 GB system memory when you installed four 1 GB DDR2 memory modules.
Проблема в том, что БИОС не желает работать с памятью больше 3328МБ
Вот сто пишет раздел БИОС system information:
System memory
Total: 4096 MB
Appropriated: 768MB
Available: 3328 MB
И что, ничего нельзя поделать?
Обрати внимание на два пункта.
По пунктам - "обрезание" памяти происходит ДО загрузки операционки (у меня, кстати, Linux). Так что смена операционки не поможет.
Память резервирует именно материнка. Вот точная цитата того, что выдается на самом первом экране, до загрузки каких бы то ни было операционных систем:
Memory consumed by system resources: 1120Mb System RAM
Available memory: 2912MbSystem RAM
Кстати, после апдейта BIOS, цифры немного изменились, Available memory: 3168, consumed memory: 896.
-
Железо:
- поддерживается до 4 гигов - ничего не поделать, забей. О чем написано в мануале и на оф сайте.
- поддерживается более 4 гигов - ставь в БИОСе memory remap, определится весь объем
-
ОС:
- стоит XP/Vista 32-bit - она по определению не видит 4 гига, ставь 64-bit версию
- стоит Win 2003 - спроси, напишу как там с PAE дело обстоит
Есть ещё вопросы?
В документации к материнке написано - поддерживается до 4Г. Реально видит 3.2Г. Рядом стоит 64-разрядный Athlon, у него в документации тоже написано до 4Г, реально видит 3.4Г. Пообщавшись с представителями разных компьютерных фирм, я узнал, что это - довольно частая ситуация. От операционки тут вообще ничего не зависит, поскольку BIOS не зависит от операционки. Для справки, у меня стоит ScientificLinux4.4, на соседней машине ХР 32-разрядная (и она, кстати, все 3.4Г, сколько даёт BIOS, видит) и Kubuntu - видит те же 3.4Г.
ЗЫ. Изменение различных настроек в BIOS позволяет чуть-чуть (где-нибудь на 100М) увеличить или уменьшить объём видимой памяти, но принципиально картину не меняет.
This article provides a resolution for the issue that it is unable to allocate memory from the system paged pool.
Applies to: Windows Server 2012 R2
Original KB number: 312362
Symptoms
When your server is under a heavy load, the Server service may repeatedly log the following error in the System Event log. It indicates that the server is out of paged pool memory:
Source - SRV
Type - Error
Event ID - 2020
Description -The server was unable to allocate from the system paged pool because the pool was empty.
Data -
0000: 00040000 00540001 00000000 c00007e4
0010: 00000000 c000009a 00000000 00000000
0020: 00000000 00000000 0000000b
Cause
Several factors may deplete the supply of paged pool memory. Enabling pool tagging and taking poolsnaps at different time intervals may help you to understand which driver is consuming paged pool memory. If the poolsnaps indicate that the MmSt tag (Mm section object prototype PTEs) is the largest consumer and paged pool memory has been depleted or the system is logging error event 2020s, there is a large probability that there are a large number of files that are open on the server. By default, the Memory Manager tries to trim allocated paged pool memory when the system reaches 80 percent of the total paged pool. Depending on the system configuration, a possible maximum paged pool memory on a computer can be 343 MB and 80 percent of this number is 274 MB. If the Memory Manager is unable to trim fast enough to keep up with the demand, the event that is listed in the "Symptoms" section of this article may occur. By tuning the Memory Manager to start the trimming process earlier (for example, when it reaches 60 percent), it would be possible to keep up with the paged pool demand during sudden peak usage, and avoid running out of paged pool memory.
Resolution
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
The following tuning recommendation has been helpful in alleviating the problem:
Start Registry Editor (Regedt32.exe).
Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management
On the Edit menu, click Add Value, and then add the following registry value:
Value name: PoolUsageMaximum
Data type: REG_DWORD
Radix: Decimal
Value data: 60
Setting the value at 60 informs the Memory Manager to start the trimming process at 60 percent of PagedPoolMax rather than the default setting of 80 percent. If a threshold of 60 percent isn't enough to handle spikes in activity, reduce this setting to 50 percent or 40 percent.
Value name: PagedPoolSize
Data type: REG_DWORD
Radix: Hex
Value data: 0xFFFFFFFF
Setting PagedPoolSize to 0xFFFFFFFF allocates the maximum paged pool in lieu of other resources to the computer.
The 0xFFFFFFFF PagedPoolSize setting is not recommended for use on 32-bit Windows Server 2003-based computers that have 64GB of RAM. This will potentially bring the Free System PTE entry down and can cause continuous reboot of the computer. For this configuration, carefully choose a value based on the requirements and available resources.
Quit Registry Editor.
Restart the server for the changes to take effect.
Status
Microsoft has confirmed that it's a problem in the Microsoft products that are listed in the "Applies to" section.
HP Recommended
- Mark as New
- Bookmark
- Subscribe
- Email to a Friend
I want to update the Bios of a Probook 640 G2, Win 7 Pro 64.
On the HP site there is a download, for v01.02
Downloaded the SP74154 file, ran it, when asked restarted the laptop: the result I got after starting up:
"The system could not find one of the BIOS Update binary files. Please make sure the correct BIN file
is located on the system hard drive or on removable USB Key under the "Hewlett-Packard\BIOS\New" folder
or under the "EFI\HP\BIOS\New" folder. It may also be placed under the "Hewlett_Packard\BIOS\Previous" folder
or under the "EFI\HP\BIOS\Previous" folder.
Even if I made the folders and put in the .bin files, ran the SP74514 file again, I got the same message and the BIOS is not updated.
Would gladly have it because we have issues with wifi not working after we undock it and take it to a conference room.
So anybody has a solution.
IT_WinSec
HP Recommended
- Mark as New
- Bookmark
- Subscribe
- Email to a Friend
Can you manually create a folders EFI\HP\BIOS\New
on the flash drive, then paste N87_0102.bin there
Then, reboot, enter F10 to update the BIOS and see if it will work ?
Can you also reboot the computer, keep press F1 for System Information. Once it opens, please copy/paste all the information here, especially product number, motherboars info and ROM version or something similar - whatever is there.
Looking forward to your reply.
>> Your FEEDBACK is important. Use the interactive buttons below and let me know if the post helps <<
*** I work for HP *** I express personal opinion only *** HP Expert volunteer since 2013<>
IT_WinSec
HP Recommended
- Mark as New
- Bookmark
- Subscribe
- Email to a Friend
Welcome to the HP Support forum.
Thank you for posting.
Could you elaborate for me when exactly you get this message - during PC start-up before Windows is loaded OR after Windows is loaded ?
There are multiple ways to update the BIOS - try with other methods:
Use HP Support Assistant to download updates for this HP computer including BIOS/UEFI updates as mentioned in the product's manual. Here is how to use HPSA:
Try the other option to update the existing BIOS from within the existing BIOS/UEFI:
Let me know if this works.
>> Your FEEDBACK is important. Use the interactive buttons below and let me know if the post helps <<
*** I work for HP *** I express personal opinion only *** HP Expert volunteer since 2013<>
HP Recommended
- Mark as New
- Bookmark
- Subscribe
- Email to a Friend
The message comes after a restart, before Windows (Pro 64 US) starts.
No mentioning of a Bios update.
Downloading the SP74154.exe file, and installing it on the E:HP_Tools in the folder "Hewlett_Packard\BIOS\New".
I saw that there was now a N76_0102.bin file in that directory.
After the install a window "HP BIOS update and recovery" asked me to update the BIOS. I checked the first option (update) and the last windows said:
"The BIOS update was prepared succesfully.
Please restart this device to complete the update
Again no Bios update:
"The system could not find one of the BIOS Update binary files. Please make sure the correct BIN file
is located on the system hard drive or on removable USB Key under the "Hewlett-Packard\BIOS\New" folder
or under the "EFI\HP\BIOS\New" folder. It may also be placed under the "Hewlett_Packard\BIOS\Previous" folder
or under the "EFI\HP\BIOS\Previous" folder.
I did the same writing the .bin files to a USB stick:
(Choose second option Create Recovery USB flash drive)
Pressed Esc, Entered Startup menu, choose F10 (Bios Setup), Update System Bios, Update Bios Using Local Media :
Again no Bios update:
"The system could not find one of the BIOS Update binary files. Please make sure the correct BIN file
is located on the system hard drive or on removable USB Key under the "Hewlett-Packard\BIOS\New" folder
or under the "EFI\HP\BIOS\New" folder. It may also be placed under the "Hewlett_Packard\BIOS\Previous" folder
or under the "EFI\HP\BIOS\Previous" folder.
MS Windows BitLocker Drive Encryption (BDE) may be enabled on your system.
HP requires that BDE be suspended temporarily before the BIOS is flashed and
that you obtain your BDE recovery password or recovery PIN before suspending BDE.
After the BIOS is update, BDE can be resumed
(no BDE on this laptop. so continue)
Current bios version 1.00
Downloading file bios catalog
failed during data transfer (the resource referenced in the url does not exist)
HPSA failed (no Bios in list),
On the HP website for the 640 G2:
Installing SP74154.exe failed,
(though you can manually add a path to the downloadable .bin files. but where can I find them??)
BIOS update from the BIOS on local media failed.
Last resort: HP Softpaq Manager: It recommend a critical update for the Bios: SP74154.
Again no Bios update:
"The system could not find one of the BIOS Update binary files. Please make sure the correct BIN file
is located on the system hard drive or on removable USB Key under the "Hewlett-Packard\BIOS\New" folder
or under the "EFI\HP\BIOS\New" folder. It may also be placed under the "Hewlett_Packard\BIOS\Previous" folder
or under the "EFI\HP\BIOS\Previous" folder.
So now I am out of options.
2016/07/08 16:52:37.438|000011CC|Information|CHPBiosUpdateApp::InitializeProperties|******************************************************************
2016/07/08 16:52:37.453|000011CC|Information|CHPBiosUpdateApp::InitializeProperties|** Start of HPBIOSUPDREC session, version 1.1.20.1 **
2016/07/08 16:52:37.453|000011CC|Information|CHPBiosUpdateApp::InitializeProperties|******************************************************************
2016/07/08 16:52:37.453|000011CC|Information|CHPBiosUpdateApp::InitializeProperties|Command line:
2016/07/08 16:52:37.453|000011CC|Information|CHPBiosUpdateApp::InitializeProperties|DASL PnP ID NOT found
2016/07/08 16:52:37.484|000011CC|Information|HPBiosUpdate::SmbiosInfo::GetSmbiosInfo|Getting SMBIOS information
2016/07/08 16:52:37.500|000011CC|Information|HPBiosUpdate::SmbiosInfo::GetSmbiosInfo|Successfully retrieved SMBIOS settings: BIOS Family = N76, version = 01.00
2016/07/08 16:52:37.500|000011CC|Information|HPBiosUpdate::SmbiosInfo::GetSmbiosInfo|PCID: ' ', AT-p supported: no, portable: yes
2016/07/08 16:52:37.562|000011CC|Information|HPBiosUpdate::PrivateWmiInfo::GetPrivateWmiSettings|Successfully retrieved Private WMI settings
2016/07/08 16:52:37.562|000011CC|Information|HPBiosUpdate::PrivateWmiInfo::GetPrivateWmiSettings|m_isEfiUpdateSupported = 1, m_isEspDriveSupported = 1, m_isEncryptionSupported = 1
2016/07/08 16:52:37.578|000011CC|Information|HPBiosUpdate::PrivateWmiInfo::GetPrivateWmiSettings|m_isBiosUpdateSet = 0, m_isUefiToolsRequired = 0
2016/07/08 16:52:38.077|000011CC|Information|HPBiosUpdate::PublicWmiInfo::CheckWmiSettingSetupLogIn|Setup Password is NOT set.
2016/07/08 16:52:40.230|000011CC|Information|HPBiosUpdate::PublicWmiInfo::GetBiosSettingValue|Setting not found: Lock BIOS Version
2016/07/08 16:52:41.322|000011CC|Information|HPBiosUpdate::PublicWmiInfo::GetBiosSettingValue|Setting not found: Update Base Embedded Controller Firmware
2016/07/08 16:52:41.338|000011CC|Information|HPBiosUpdate::PublicWmiInfo::GetPublicWmiSettings|Successfully retrieved Public WMI settings
2016/07/08 16:52:41.338|000011CC|Information|HPBiosUpdate::CabFile::FindUpdateFile|Checking filename 'N76_0102'.
2016/07/08 16:52:41.338|000011CC|Information|HPBiosUpdate::CabFile::ParseUpdateName|Processing image filename 'C:\Users\admin\Desktop\N76_0102.bin'.
2016/07/08 16:52:41.338|000011CC|Information|CHPBiosUpdateApp::InitInstance|Update BIOS Family = N76, version = 01.02
2016/07/08 16:53:14.332|000011CC|Information|CHPBiosUpdateApp::PerformWizard|User cancelled wizard.
2016/07/08 16:53:14.363|000011CC|Information|CHPBiosUpdateApp::ExitInstance|HPBIOSUPDREC Return Code = 1602
2016/07/08 16:53:14.363|000011CC|Information|CHPBiosUpdateApp::ExitInstance|****************** End of HPBIOSUPDREC session ******************
2016/07/08 16:53:14.378|000011CC|Information|CHPBiosUpdateApp::ExitInstance|
2016/07/08 16:54:16.638|00001A3C|Information|CHPBiosUpdateApp::InitializeProperties|******************************************************************
2016/07/08 16:54:16.654|00001A3C|Information|CHPBiosUpdateApp::InitializeProperties|** Start of HPBIOSUPDREC session, version 1.1.20.1 **
2016/07/08 16:54:16.654|00001A3C|Information|CHPBiosUpdateApp::InitializeProperties|******************************************************************
2016/07/08 16:54:16.654|00001A3C|Information|CHPBiosUpdateApp::InitializeProperties|Command line:
2016/07/08 16:54:16.654|00001A3C|Information|CHPBiosUpdateApp::InitializeProperties|DASL PnP ID NOT found
2016/07/08 16:54:16.700|00001A3C|Information|HPBiosUpdate::SmbiosInfo::GetSmbiosInfo|Getting SMBIOS information
2016/07/08 16:54:16.700|00001A3C|Information|HPBiosUpdate::SmbiosInfo::GetSmbiosInfo|Successfully retrieved SMBIOS settings: BIOS Family = N76, version = 01.00
2016/07/08 16:54:16.700|00001A3C|Information|HPBiosUpdate::SmbiosInfo::GetSmbiosInfo|PCID: ' ', AT-p supported: no, portable: yes
2016/07/08 16:54:16.763|00001A3C|Information|HPBiosUpdate::PrivateWmiInfo::GetPrivateWmiSettings|Successfully retrieved Private WMI settings
2016/07/08 16:54:16.763|00001A3C|Information|HPBiosUpdate::PrivateWmiInfo::GetPrivateWmiSettings|m_isEfiUpdateSupported = 1, m_isEspDriveSupported = 1, m_isEncryptionSupported = 1
2016/07/08 16:54:16.763|00001A3C|Information|HPBiosUpdate::PrivateWmiInfo::GetPrivateWmiSettings|m_isBiosUpdateSet = 0, m_isUefiToolsRequired = 0
2016/07/08 16:54:17.246|00001A3C|Information|HPBiosUpdate::PublicWmiInfo::CheckWmiSettingSetupLogIn|Setup Password is NOT set.
2016/07/08 16:54:19.274|00001A3C|Information|HPBiosUpdate::PublicWmiInfo::GetBiosSettingValue|Setting not found: Lock BIOS Version
2016/07/08 16:54:20.335|00001A3C|Information|HPBiosUpdate::PublicWmiInfo::GetBiosSettingValue|Setting not found: Update Base Embedded Controller Firmware
2016/07/08 16:54:20.351|00001A3C|Information|HPBiosUpdate::PublicWmiInfo::GetPublicWmiSettings|Successfully retrieved Public WMI settings
2016/07/08 16:54:20.351|00001A3C|Information|HPBiosUpdate::CabFile::FindUpdateFile|Checking filename 'N76_0102'.
2016/07/08 16:54:20.351|00001A3C|Information|HPBiosUpdate::CabFile::ParseUpdateName|Processing image filename 'C:\Users\admin\Desktop\N76_0102.bin'.
2016/07/08 16:54:20.351|00001A3C|Information|CHPBiosUpdateApp::InitInstance|Update BIOS Family = N76, version = 01.02
2016/07/08 16:54:23.752|00001A3C|Information|HPBiosUpdate::Partition::FindEspPartition|PartitionStyle == PARTITION_STYLE_GPT, PartitionCount: 5
2016/07/08 16:54:23.752|00001A3C|Information|HPBiosUpdate::Partition::FindEspPartition|ESP partition found
2016/07/08 16:54:23.908|00001A3C|Information|HPBiosUpdate::Partition::AccessEspPartition|ESP drive already mounted as C:\.
2016/07/08 16:54:23.908|00001A3C|Information|HPBiosUpdate::Partition::CreateHpBiosFolderHierarchy|Creating folder structure in C:\EFI\HP\
2016/07/08 16:54:23.923|00001A3C|Information|CHPBiosUpdateApp::PrepareEfiFlash|Found ESP partition: C:\EFI\HP\
2016/07/08 16:54:25.530|00001A3C|Information|HPBiosUpdate::Partition::CopyBiosUpdate|Update successfully copied.
2016/07/08 16:54:25.592|00001A3C|Information|CHPBiosUpdateApp::DoEfiFlash|Update will occur on restart
2016/07/08 16:55:02.935|00001A3C|Information|CHPBiosUpdateApp::ExitInstance|HPBIOSUPDREC Return Code = 3010
2016/07/08 16:55:02.951|00001A3C|Information|HPBiosUpdate::RestartSystem|************* End of HPBIOSUPDREC session - restarting *************
2016/07/08 16:55:02.966|00001A3C|Information|HPBiosUpdate::RestartSystem|
This article provides a workaround for errors that occur when applications frequently allocate memory.
Applies to: Windows 10 - all editions
Original KB number: 4055223
Symptoms
Applications that frequently allocate memory may experience random "out-of-memory" errors. Such errors can result in other errors or unexpected behavior in affected applications.
Cause
Memory allocation failures can occur due to latencies that are associated with growing the size of a page file to support additional memory requirements in the system. A potential cause of these failures is when the page file size is configured as "automatic." Automatic page-file size starts with a small page file and grows automatically as needed.
The IO system consists of many components, including file system filters, file systems, volume filters, storage filters, and so on. The specific components on a given system can cause variability in page file growth.
Workaround
To work around this issue, manually configure the size of the page file. To do this, follow these steps:
- Press the Windows logo key + the Pause/Break key to open System Properties.
- Select Advanced system settings and then select Settings in the Performance section on the Advanced tab.
- Select the Advanced tab, and then select Change in the Virtual memory section.
- Clear the Automatically manage paging file size for all drives check box.
- Select Custom size, and then set the "Initial size" and "Maximum size" values for the paging file. We recommend that you set the initial size to 1.5 times the amount of RAM in the system.
- Select OK to apply the settings, and then restart the system. If you continue to receive "out-of-memory" error messages, increase the "initial size" of the page file.
Status
Microsoft has confirmed that this is a problem in Windows 10.
More information
You might see intermittent build errors like the following if you encounter this problem when using the Microsoft Visual C++ compiler (cl.exe):
- Fatal error C1076: compiler limit: internal heap reached; use /Zm to specify a higher limit
- Fatal error C1083: cannot opentypefile: 'file': message
- Fatal error C1090: PDB API call failed, error code 'code': 'message'
- Compiler error C3859: virtual memory range for PCH exceeded; please recompile with a command line option of '-ZmXXX' or greater
For more information about the Visual C++ compiler errors and how to work around them, see Precompiled Header (PCH) issues and recommendations.
Конфигурация компьютера | |
Процессор: Intel G840 | |
Материнская плата: GA-H61M-S2P | |
Память: Kingstone pc1333 2*1024Mb Kit | |
HDD: WD 500Gb 16M SATA-II | |
Видеокарта: NVIDIA GeForce 9500 128Mb | |
Звук: VIA HD Audio | |
Блок питания: InWin FSP-300BPF | |
CD/DVD: Multi-DVD Samsung SH-S223F | |
Монитор: 20 Samsung 2033N | |
ОС: Windows XP Professional SP3 |
innotek VirtualBox - бесплатная альтернатива VMWare и прочим продуктам виртуализации. Платформа представляет собой систему виртуализации для host-систем Windows, Linux и Mac OS и обеспечивает взаимодействие с гостевыми операционными системами Windows (2000/XP/2003/Vista/Seven/8), Linux (Ubuntu/Debian/ OpenSUSE/ Mandriva и пр.), OpenBSD, FreeBSD, OS/2 Warp. Так же поддерживается работа серверных версий ОС Windows 2k/2k3/2k8. В данной теме обсуждается работа на Windows-host.
Версия - 4.1.8 (released 2011-12-19)
Читать о VirtualBox на OsZone: Oracle VirtualBox
F: как на виртуальной машине подключить папку с реального компа для пользования?? »
Q: Читаем этот пост
F: Брандмауэр блокирует доступ к сети интернет, как настроить?
Q: Читаем этот пост
F: Настройка сетевой папки?
Q: Читаем этот пост
F: Как пробросить порт с гостевой машины?
Q: Читаем краткое пояснение на opennet.
F: У меня проблемы с запуском/импортом/экспортом конфигурации машины?
Q: Основная проблема в данном случае - Вами указан путь к ресурсу содержащий кирилицу и пробелы - это недопустимо.
Благодарности за поддержку ветки (пока я занят или сплю ): gora, maik5, Petya V4sechkin, Morpheus и другим коллегам по форуму.
Читайте также: