This will rollback the BIOS settings to default and you won't encounter the error anymore. The BIOS key can vary for different laptops. Many users encounter the BSOD error after installing a third-party application on their system. In this case, you can fix the error by uninstalling the third-party application. Follow these steps to uninstall a third-party program from your computer.
Step 2: Select the program that you want to remove and tap the "Uninstall" button. Now, restart your PC and check if the error persists or not. If you're unable to find the faulty third-party app, you can also use the "System Restore Point" to fix the error by restoring your system to a stable point in the past.
SFC is another built-in utility that will scan your system to find damaged system files and replace them with fresh copies. Step 3: The SFC utility will replace all the corrupted system files with fresh copies.
Once the process completes reboot your system and you won't see the annoying BSOD anymore. You don't have to install any third-party software for this as Windows has a built-in tool known as "Windows Memory Diagnostic" that'll help you find issues with your RAM.
Step 2: Double-click the search result and select "Restart now and check for problems recommended ". Another effective way to fix the Kernel Data Inpage Error is to automate the paging file size management in your system.
Step 1: Launch "Control Panel" and select "System". Now click on "Advanced System Settings". Step 4: Now, check the "Automatically manage paging file size for all drives" and click "Ok" to save changes. If none of the above methods fix the Windows stop code Kernel Data Inpage Error, the only troubleshooting method that'll help is to boot your system in safe mode.
Safe Mode is a state where your system will start with minimal settings and help you fix different BSOD errors. Here is how:. Step 1: Power on your system and instantly start pressing the "F8" key to launch Advanced Boot Options.
As we mentioned earlier, the term "Inpage" is related to storage-related issues. It means that due to the error, you may also lose valuable data from your hard drive. If that has already happened, don't worry as there are ways to recover this lost data. Wondershare RecoverIt is an excellent Windows tool, designed by leading software manufacturer - Wondershare. It doesn't matter if you've lost the data during the unexpected crash due to a BSOD error or have deleted it mistakenly, RecoverIt will help you restore all the deleted files quickly.
Examine Parameter 2 to see why the hive could not be linked in the registry tree. One common cause of this error is that the Windows operating system is out of disk space on the system drive.
Another common problem is that an attempt to allocate pool has failed. You must investigate other status codes. This bug check indicates that there is an error in the registry. This bug check can also occur if some critical registry keys and values are missing. These keys and values might be missing if a user manually edited the registry. Try restarting the computer by selecting "last known good configuration" in the boot options.
If the restart does not fix the problem, the registry damage is too extensive. This bug check should almost never occur, because the conversion of the hive file occurs early enough during system initialization so that enough pool should be available.
First, use the! This extension might find at least one memory descriptor list MDL that points to the current process. Next, use! From this IRP, you can identify which driver is leaking the pages. Otherwise, you can detect which driver caused the error by editing the registry:. The system then saves stack traces, so you can easily identify the driver that caused the problem. This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The four parameters that listed in the message have two possible meanings. If the first parameter is 0, 1, or 2, the parameters have the following meaning. If the first parameter is any value other than 0, 1, or 2, the parameters have the following meaning. If the first parameter is 0 or 1, the stack signature in the kernel stack was not found.
This error is probably caused by defective hardware, such as a RAM error. If the first parameter is 2, the driver stack returned an inconsistent status for the read of the page. For example, the driver stack returned a success status even though it did not read the whole page. If the first parameter is any value other than 0, 1, or 2, the value of the first parameter is an NTSTATUS error code that the driver stack returns after it tries to retrieve the page of kernel data.
Some common status codes include the following:. These status codes are the most common ones that have specific causes.
For more information about other possible status codes that might be returned, see the Ntstatus. Resolving a bad block problem: If you can restart the computer after the error, Autochk runs automatically and attempts to map the bad sector to prevent it from being used anymore.
If Autochk does not scan the hard disk for errors, you can manually start the disk scanner. You must restart the computer before the disk scan begins. Always use the version of Chkdsk that matches your version of the Windows operating system.
Resolving a failing RAM problem: Run the hardware diagnostics that the system manufacturer supplies, especially the memory scanner. For more information about these procedures, see the owner's manual for your computer. Check that all the adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean. Check the System Log in Event Viewer for additional error messages that might help identify the device that is causing the error.
You can also disable memory caching of the BIOS to try to resolve this error. If the preceding steps fail to resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can cause this error. Resolving a virus infection: Check your computer for viruses by using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. This bug check occurs when an unexpected break is encountered during HAL initialization.
This bug check indicates that the Hardware Abstraction Layer HAL revision level or configuration does not match that of the kernel or the computer. The following parameters appear on the blue screen. Parameter 1 indicates the type of mismatch. When Parameter 1 equals 0x2, the following build type codes are used:.
The error can also indicate that one of those two files is out of date. Or the computer might erroneously have a multiprocessor HAL and a single-processor kernel installed, or vice versa. The Ntoskrnl. However, these file names correspond to the files on the installation media. After you have installed the Windows operating system, the file is renamed to Ntoskrnl. The HAL file also uses the name Hal. Restart the computer by using the product CD or the Windows Setup disks.
At the Welcome screen, press F10 to start the Recovery Console. Use the Copy command to copy the correct HAL or kernel file from the original CD into the appropriate folder on the hard disk.
The Copy command detects whether the file that you are copying is in the Microsoft compressed file format. If so, it automatically expands the file that is copied on the target drive. The four parameters that are listed in the message can have three possible meanings.
If the first parameter is 1 or 2, or 3 and the third parameter is 0, the parameters have the following definitions. If the first parameter is 3 and the third parameter is nonzero or 4, the parameters have the following definitions.
For more information about other possible status codes that can be returned, see the Ntstatus. Another common cause of this error message is defective hardware or failing RAM. If you can restart the computer after the error, Autochk runs automatically and attempts to map the bad sector to prevent it from being used anymore.
Always use the version of Chkdsk that matches your version of Windows. If the preceding steps do not resolve the error, take the system motherboard to a repair facility for diagnostic testing.
This bug check indicates that the Microsoft Windows operating system has lost access to the system partition during startup. To determine the meaning of Parameter 1, look at the data that it points to.
The Length field gives the actual length of the string. The Buffer field points to the beginning of the string Buffer is always be at least 0x File system initialization might have failed because it did not recognize the data on the boot device.
Also, repartitioning the system partition or installing a new SCSI adapter or disk controller might induce this error. This error can also occur because of incompatible disk hardware. If the error occurred at the initial setup of the system, the system might have been installed on an unsupported disk or SCSI controller. These drivers require the user to do a custom installation.
This error always occurs while the system is starting. This error frequently occurs before the debugger connection is established, so debugging can be difficult or impossible. Resolving a failed boot device problem: If a boot device is at fault, you must edit the boot options. For more information about changing these options, see Configuring Software on the Target Computer. Resolving an incompatible disk hardware problem: If Setup autodetects the controller, you might have to skip detection and use a specific manufacturer's disk to load the driver.
Updates of this kind are typically available on the Web site or BBS of the hardware manufacturer. Remove any recently added hardware, especially hard disk drives or controllers, to see if the error is resolved. If the problematic hardware is a hard disk drive, the disk firmware version might be incompatible with your version of the Windows operating system. Contact the manufacturer for updates. Reconfigure the new device according to the manufacturer's instructions.
If you recently added a driver, restart your computer, and press F8 at the character-based menu that displays the operating system choices. This option is most effective when you add only one driver or service at a time. In addition, check your computer for viruses by using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk.
This error can also occur because of hard disk corruption. If you cannot start the system in the last known good configuration, you should try to start off the Windows CD. Then, you can run Chkdsk from the Repair Console. If your system has SCSI adapters, contact the adapter manufacturer to obtain updated Windows drivers.
Try removing all IDE devices except for hard disks. Finally, check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing the error. To analyze this error: Run an lm List Loaded Modules command in the debugger. You probably have pci or isapnp loaded.
Also make sure your controller drivers are loaded. That is, make sure Atapi. It is helpful to know as much as possible about the boot device that Windows is installed on. For example, you can investigate the following items:. Typically Plug and Play cannot assign resources to the boot device. You can verify this restriction by finding an entry for the service.
This bug check indicates that a problem occurred with an NDIS driver. If one of the bug check parameters specifies the address of the miniport block, you can obtain more information by using! If one of the bug check parameters specifies the address of the packet descriptor that the driver uses, you can obtain more information by using!
This bug check code occurs only on Microsoft Windows Server and later versions of Windows. This bug check indicates that there is not enough memory to start up the Microsoft Windows operating system. The Windows operating system does not have sufficient memory to complete the startup process. This bug check indicates that a system thread generated an exception that the error handler did not catch.
For a complete list of exception codes, see the Ntstatus. If you are not equipped to debug this problem, you should use some basic troubleshooting techniques. If you plan to debug this problem , you might find it difficult to obtain a stack trace.
Parameter 2 the exception address should identify the driver or function that caused this problem. If exception code 0x occurs, the trap frame supplies additional information. If you do not know the specific cause of the exception, consider the following issues:. If the driver is used as part of the system startup process in Safe Mode, you must start the computer by using the Recovery Console to access the file.
If such software is installed, you can remove the service by starting the computer by using the Recovery Console and then deleting the offending system service file.
Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x7E. You can also disable memory caching of the BIOS might to try to resolve the error.
You should also run hardware diagnostics, especially the memory scanner, that the system manufacturer supplies. A possible cause of the error is lack of disk space for installation and system BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk space, reduce the number of files on the target hard disk drive.
Check for and delete any temporary files that you do not have to have, Internet cache files, application backup files, and. You can also use another hard disk drive with more free space for the installation. This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap. This trap could be a bound trap a trap the kernel is not permitted to catch or a double fault a fault that occurred while processing an earlier fault, which always results in a system failure.
The first parameter that appears on the blue screen specifies the trap number. Bug check 0x7F typically occurs after you install a faulty or mismatched hardware especially memory or if installed hardware fails. A double fault can occur when the kernel stack overflows. This overflow occurs if multiple drivers are attached to the same stack.
For example, if two file system filter drivers are attached to the same stack and then the file system recurses back in, the stack overflows. Debugging: Always begin with the! If this extension is not sufficient, use the kv Display Stack Backtrace debugger command. After using one of these commands, use kv again to display the new stack. Troubleshooting: If you recently added hardware to the computer, remove it to see if the error recurs.
Run hardware diagnostics that the system manufacturer supplies to determine which hardware component failed. The memory scanner is especially important. Faulty or mismatched memory can cause this bug check.
For more informaiton about these procedures, see the owner's manual for your computer. These kind of updates are typically available on the Web site or BBS of the hardware manufacturer. If the error occurred after the installation of a new or updated device driver, you should remove or replace the driver.
If, under this circumstance, the error occurs during the startup sequence and the system partition is formatted with NTFS, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you have to start the computer by using the Recovery Console in order to access the file.
Also restart your computer, and then press F8 at the character-based menu that displays the operating system choices. Overclocking setting the CPU to run at speeds above the rated specification can cause this error. If you have overclocked the computer that is experiencing the error, return the CPU to the default clock speed setting. Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing the error.
You can also disable memory caching of the BIOS to try to resolve the problem. If you encountered this error while upgrading to a new version of the Windows operating system, the error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version. If possible, remove all third-party device drivers and system services and disable any virus scanners before you upgrade. Contact the software manufacturer to obtain updates of these tools.
Also make sure that you have installed the latest Windows Service Pack. Finally, if all the above steps do not resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can also cause this error. This bug check indicates that a hardware malfunction has occurred.
The exact cause is difficult to determine. Remove any hardware or drivers that have been recently installed. Make sure that all memory modules are of the same type. This bug check indicates that a fatal error occurred during setup.
Parameter 4 is not used. This bug check indicates that a mismatch has occurred in the MBR checksum. There are many forms of viruses and not all can be detected. Typically, the newer viruses usually can be detected only by a virus scanner that has recently been upgraded.
You should boot with a write-protected disk that contains a virus scanner and try to clean out the infection. This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
If you are not equipped to debug this problem, you should use some basic troubleshooting techniques:. If you plan to debug this problem, you might find it difficult to obtain a stack trace. If you do not know the specific cause of the exception, consider the following items:. If the bug check message lists a driver by name , disable or remove that driver.
Also, disable or remove any drivers or services that were recently added. If the driver is used as part of the system startup process in Safe Mode, you have to start the computer by using the Recovery Console to access the file. If such software is installed, you can remove the service by starting the system by using the Recovery Console and then deleting the offending system service file.
Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x1E. You can disable memory caching of the BIOS to try to resolve the error. This bug check indicates that the Plug and Play PnP manager could not be initialized. An error occurred during Phase 0 initialization of the kernel-mode PnP manager. An error occurred during Phase 1 initialization of the kernel-mode PnP manager. This bug check indicates that a uniprocessor-only driver has been loaded on a multiprocessor system.
A driver that is compiled to work only on uniprocessor machines has been loaded, but the Microsoft Windows operating system is running on a multiprocessor system with more than one active processor.
This bug check indicates that an invalid or protected handle was passed to NtClose. This bug check indicates that a thread exited while its kernel stack was marked as not swappable.
This bug check indicates that a queue entry was removed that contained a null pointer. Any queue misuse can cause this error. But typically this error occurs because worker thread work items are misused.
An entry on a queue can be inserted on the list only one time. When an item is removed from a queue, its flink field is set to NULL. Then, when this item is removed the second time, this bug check occurs. In most situations, the queue that is being referenced is an ExWorkerQueue executive worker queue.
To help identify the driver that caused the error, Parameter 4 displays the address of the worker routine that would have been called if this work item had been valid.
However, if the queue that is being referenced is not an ExWorkerQueue , this parameter is not useful. This bug check indicates that the trial period for the Microsoft Windows operating system has ended.
Your installation of the Windows operating system is an evaluation unit with an expiration date. The trial period is over. This bug check indicates that the software license agreement has been violated. The Microsoft Windows operating system detects a violation of the software license agreement.
A user might have tried to change the product type of an offline system or change the trial period of an evaluation unit of Windows. For more information about the specific violation, see the parameter list. This bug check indicates that a problem occurred in the UDF file system. This bug check might also occur if nonpaged pool memory is full. If the nonpaged pool memory is full, this error can stop the system.
However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver that requires nonpaged pool memory can also trigger this error. Disable any virus scanners, backup application, or disk defragmenter tools that continually monitor the system. You should also run hardware diagnostics that the system manufacturer supplies. This memory increases the quantity of nonpaged pool memory that is available to the kernel.
This bug check indicates that a fatal machine check exception has occurred. The four parameters that are listed in the message have different meanings, depending on the processor type. If the processor is based on a newer xbased architecture and has the MCA feature and the MCE feature for example, any Intel Processor of family 6 or higher, such as Pentium Pro, Pentium IV, or Xeon , or if the processor is an xbased processor, the parameters have the following meaning.
On an Itanium-based processor, the parameters have the following meaning. Note Parameter 1 indicates the type of violation. This bug check indicates that one or more critical user-mode components failed to satisfy a health check.
Hardware mechanisms, such as watchdog timers, can detect that basic kernel services are not executing. However, resource starvation issues including memory leaks, lock contention, and scheduling priority misconfiguration can block critical user-mode components without blocking deferred procedure calls DPCs or draining the non-paged pool.
Kernel components can extend watchdog timer functionality to user mode by periodically monitoring critical applications. This bug check indicates that a user-mode health check failed in a way that prevents graceful shutdown. This bug check restores critical services by restarting or enabling application failover to other servers.
The bug check occurs in this situation only if the user has set HangRecoveryAction to a value of 3. This bug check indicates that the driver is in an inconsistent or invalid power state. For a description of the possible causes, see the description of each code in the Parameters section. The errors that cause Parameter 1 to be 0x3, 0x, or 0x only exist in Microsoft Windows This bug check indicates that the power policy manager experienced a fatal error.
When Parameter 1 is0x8, a fatal error occurred while processing a system power event. In this situation, Parameter 2 indicates the cause of the error.
The meaning of the other parameters depends on the value of Parameter 2. The following procedures will help you debug certain instances of this bug check. Note the value of this argument. This command sets the register context to the proper value.
This bug check indicates that the PCI Bus driver detected inconsistency problems in its internal structures and could not continue. This bug check indicates that corruption has been detected in the image of an executable file in memory. A cyclic redundancy check CRC check on the memory range has failed. On a system wake operation, various regions of memory might be checked to guard against memory failures. This bug check indicates that the ACPI driver detected an internal inconsistency.
An inconsistency in the ACPI driver is so severe that continuing to run would cause serious problems. This bug check indicates that a problem occurred in the CNSS file system filter. If the nonpaged pool memory is completely full, this error can stop the system.
This memory sincrease the quantity of nonpaged pool memory available to the kernel. Four bug check parameters appear on the blue screen. Parameter 1 indicates the kind of the incompatibility.
If an interrupt routing failure or incompatibility has occurred, the following parameters are used. If a miscellaneous failure or incompatibility has occurred, the following parameters are used.
In this case, Parameter 3 specifies the exact problem, and the remaining parameters have the following definitions. In this situation, Parameter 3 specifies the exact problem, and the remaining parameters have the following definitions. In this situation, Parameter 2 specifies the exact problem, and the remaining parameters have the following definitions. If you are debugging this error, use the! This extension displays all the relevant data device extensions, nsobjects, or whatever is appropriate to the specific error.
If you are not performing debugging, this error indicates that you have to obtain a new BIOS. Contact your vendor or visit the internet to get a new BIOS. The system does not notify you that the F7 key was pressed, but it silently disables ACPI and enables you to continue your installation.
This bug check indicates that the kernel-mode handle table detected an inconsistent handle table entry state. This bug check indicates that a session unload occurred while a session driver still held memory.
This bug check indicates a bug in Win32k. This bug check indicates that the hardware abstraction layer HAL could not obtain sufficient memory. The HAL could not obtain non-paged memory pool for a system critical requirement. This bug check probably indicates some other critical error such as pool corruption or massive consumption. This bug check indicates that the video port created a non-fatal minidump on behalf of the video driver during run time.
The video port created a non-fatal minidump on behalf of the video driver during run time because the video driver requested a debug report. This indicates that Windows was unable to enter graphics mode. The system was not able to go into graphics mode because no display drivers were able to start. This usually occurs when no video miniport drivers are able to load successfully.
This indicates that an illegal operation was attempted by a delayed procedure call DPC routine. A wait operation, attach process, or yield was attempted from a DPC routine. This is an illegal operation. The stack trace will lead to the code in the original DPC routine that caused the error.
This indicates that a session driver still had mapped views when the session unloaded. This error is caused by a session driver not unmapping its mapped views prior to a session unload. This indicates a bug in win32k. This indicates that Windows failed to successfully boot off a network. This indicates that a duplicate IP address was assigned to this machine while booting off a network.
Note When Parameter 4 equals zero, this indicates an Ethernet connection. This is issued if a driver attempts to write to a read-only memory segment. This indicates that a thread attempted to acquire ownership of a mutex it already owned.
This indicates that the driver wrote to an invalid section of the special pool. Parameter 4 indicates the type of violation. In particular, zero indicates nonpaged pool and one indicates paged pool. Obtain a backtrace of the current thread. This backtrace will usually reveal the source of the error. For information about the special pool, consult the Driver Verifier section of the Windows Driver Kit.
This indicates that the current thread is making a bad pool request. In particular, 0 indicates nonpaged pool and 1 indicates paged pool. Activate Driver Verifier to obtain more information about these errors.
This is the general bug check code for fatal errors found by Driver Verifier. Four bug check parameters are displayed on the blue screen. Parameter 1 identifies the type of violation.
The meaning of the remaining parameters varies with the value of Parameter 1. The parameter values are described in the following table. See the description of each code in the Parameters section for a description of the cause. Note that values 0x through 0x for Parameter 1 are deadlock verifier error codes. Further information can be obtained by using the! This bug check can only occur when Driver Verifier has been instructed to monitor one or more drivers. If you did not intend to use Driver Verifier, you should deactivate it.
You might consider removing the driver which caused this problem as well. If you are the driver writer, use the information obtained through this bug check to fix the bugs in your code. After a Memory Allocation Tracking bug check, use the following command in the kernel debugger:.
Then use the the! The value of Parameter 1 is limited by the Driver Verifier options that are activated. In particular, 0 zero indicates nonpaged pool and 1 one indicates paged pool. This indicates that the system attempted to access invalid memory at a process IRQL that was too high. The kernel attempted to access pageable memory or perhaps completely invalid memory when the IRQL was too high.
The ultimate cause of this problem is almost certainly a driver that has corrupted the system pool. If you have recently installed any new software, check to see if it is properly installed. Check for updated drivers on the manufacturer's website. To debug this error, use the special pool option of Driver Verifier.
If this fails to reveal the driver that caused the error, use the Global Flags utility to enable the special pool by pool tag. This indicates that the driver attempted to access a freed memory pool.
This is done because the potential exists for damage to your system - and Windows is designed to "fail fast" in order to protect your hardware. STOP error numbers can either be the full number 0xB for example , or in "shorthand" 0x7B is shorthand for 0xB. Capitalization doesn't usually matter. It's been my experience that most STOP errors are caused by 3rd party drivers - either device drivers, or drivers that are a part of a software installation.
The next most common reason again, IME is hardware troubles - either broken hardware or compatibility problems. Finally, there's Windows corruptions - this is rarer than the other 2 but it does happen. To make this easy on you, just follow through the pages here. If you don't understand something, ask on the forums. Quite often you won't get any response back - but if you do, it'll be worth the trouble. The most common reason to see this bugcheck is when a filesystem or a driver has a mismatched number of calls to disable and re-enable APCs.
This check is made on exit from a system call. To resolve an error caused by a faulty device driver, system service, or BIOS. To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool.
This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Resolving the Problem. Arg2: , Unknown floating point exception. Arg3: , The enabled and asserted status bits see processor definition. Arg4: Each time a driver uses a pointer to an object the driver calls a kernel routine to increment the reference count of the object.
When the driver is done with the pointer the driver calls another kernel routine to decrement the reference count. Drivers must match calls to the increment and decrement routines. This bugcheck can occur because an object's reference count goes to zero while there are still open handles to the object, in which case the fourth parameter indicates the number of opened handles.
It may also occur when the object? This may or may not be due to the caller. The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver. Arguments: Arg1: , a pool block header size is corrupt. Arg2: 89dd8, The pool entry we were looking for within the page. Arg3: 89d, The next pool entry.
Arg4: , reserved. Arguments: Arg1: , The subtype of the bugcheck. Please help me! I'm really worried because it's a new computer! I haven't even used to for a year yet! This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :. Cancel Submit.
0コメント