kernel problem ba... znatel vi uopste sta je kernel... ccc...
problem ti je sa OS-om, nista hardware ba... znaci neki driveri nisu dobro instalirani koji hbaju kernel itd...
citiram jednog coeka:
" Ono sto windows moze ladno da srusi su neispravni driveri. Zasto? Zato sto je user dio odvojen od kernel gdje su instalirani driveri. Ti bilo kojim pozivima sistemskih funkcija, tj instaliranjem bilo kakvih aplikacija NE mozes da dopres do kernel dijela. Medjutim ako imas losh driver, koji se nalazi u kernel dijelu logicno je da bilo koje prozivanje neispravno instaliranog uredjaja ce dovesti do rusenja sistema. "
jesi sad skonto
EDITED:
ao ti jos nesto jako korisno... ako znas engleski, ovdje ti je opisano rijesenje problema
Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR
The KERNEL_DATA_INPAGE_ERROR bug check has a value of 0x0000007A. This indicates that the requested page of kernel data from the paging file could not be read into memory.
Parameters
The four parameters listed in the message can have two possible meanings. If the first parameter is one, two, or three, the following definitions should be used:
Parameter Description
1 Lock type that was held (1, 2, or 3)
2 Error status (usually an I/O status code)
3 If Lock Type is 1 or 2: current process
If Lock Type is 3: virtual address
4 Virtual address that could not be paged into memory
Otherwise, use the following definitions:
Parameter Description
1 Page Table Entry (PTE) address
2 Error status (usually an I/O status code)
3 Virtual address
4 Virtual address that could not be paged into memory
Cause
Frequently, the cause of this error can be determined from the error status (Parameter 2). Some common status codes are:
* 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, is caused by lack of nonpaged pool resources.
* 0xC000009C, or STATUS_DEVICE_DATA_ERROR, is typically due to bad blocks (sectors) on the hard disk.
* 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or the controller not seeing the hard disk.
* 0xC000016A, or STATUS_DISK_OPERATION_FAILED, is also caused by bad blocks (sectors) on the hard disk.
* 0xC0000185, or STATUS_IO_DEVICE_ERROR, is caused by improper termination or defective cabling on SCSI devices, or two devices attempting to use the same IRQ.
These codes are the most common ones for which specific causes have been determined. For information about other possible status codes that can be returned, see the file ntstatus.h in the Windows DDK.
Another common cause of this error message is defective hardware or failing RAM.
This bug check can also be caused by a virus infection.
Resolving the Problem
Resolving a bad block problem: An I/O status code of 0xC000009C or 0xC000016A normally indicates that the data could not be read from the disk due to a bad block (sector). If you can restart the system after the error, Autochk runs automatically and attempts to map the bad sector to prevent it’s further use.
If Autochk does not scan the hard disk for errors, you can manually launch the disk scanner. Run Chkdsk /f /r on the system partition. You must restart the system before the disk scan begins. If you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r.
Warning If your system partition is formatted with the FAT file system, the long filenames used by Windows can be damaged if Scandisk or another MS-DOS-based hard disk tool is used to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your Windows version.
Resolving a defective hardware problem: If the I/O status is C0000185 and the paging file is on an SCSI disk, the disk cabling and SCSI termination should be checked for problems.
Resolving a failing RAM problem: Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on 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 pinpoint the device that is causing the error. Disabling memory caching of the BIOS might also resolve this error.
Make sure that the latest Windows Service Pack is installed.
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: You should check your computer for viruses using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. All Windows file systems can be infected by viruses.
