|17 Jun 2012||#1|
| || |
Bsod problem ntoskrnl.exe
Hi i am fairly new to this and i am been getting a bsod for some time, it seems like it has something to do with my harddrive. to this date it has been a problem to even get pass the windows logon.... .
i am grateful for any help i can get : ))
Filename : ntoskrnl.exe
Address In Stack : ntoskrnl.exe+ec542
From Address : fffff800`03060000
To Address : fffff800`03648000
Size : 0x005e8000
Time Stamp : 0x4fa390f3
Time String : 04.05.2012 09:18:59
Product Name : Microsoft® Windows® Operating System
File Description : NT Kernel & System
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Company : Microsoft Corporation
Full Path : C:\Windows\system32\ntoskrnl.exe
got this info from a blue screen view i managed to download.
any help much appriciated!!
|My System Specs|
|17 Jun 2012||#2|
| || |
Intel(R) Management Engine Interface PCI\VEN_8086&DEV_1C3A&SUBSYS_844D1043&REV_04\3&11583659&0&B0 39 eLicenser ROOT\SYNCROSOFT_PROTECTION_DEVICE\0000 This device cannot start.
The Intel drivers can be downloaded from your motherboard support site or vendor support site. If you need help, please fill in your system specs in your profile and not in a post in this thread: System Info - See Your System Specs
You have both AVG and Microsoft Security Essentials installed. Install one or the other; having both leads to both trying to access the same system files or system resources simultaneously and causing instability of the system.
Update the following driver:
netr28ux.sys Wed Feb 25 19:49:17 2009 (49A6032D)
Quote: Originally Posted by Windows Dev Center - Hardware
Frequently, you can determine the cause of the KERNEL_DATA_INPAGE_ERROR bug check from the error status (Parameter 2). 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 can be returned, see the Ntstatus.h file in the Microsoft Windows Driver Kit (WDK).
Another common cause of this error message is defective hardware or failing RAM.
A virus infection can also cause this bug check.
Resolving a bad block problem: An I/O status code of 0xC000009C or 0xC000016A typically indicates that the data could not be read from the disk because of a bad block (sector). 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. Run Chkdsk /f /r on the system partition. You must restart the computer before the disk scan begins. If you cannot start the computer because of the error, use the Recovery Console and run Chkdsk /r.
Warning If your system partition is formatted with the FAT file system, the long file names that the Windows operating system uses might be damaged if you use Scandisk or another MS-DOS-based hard disk tool to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your version of Windows.
Resolving a defective hardware problem: If the I/O status is C0000185 and the paging file is on an SCSI disk, check the disk cabling and SCSI termination for problems.
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.
Make sure that the latest Windows Service Pack is installed.
If the preceding 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 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. All Windows file systems can be infected by viruses.
0x7A, generally indicates hard disk problems. This could mean hard disk corruption, bad sectors, a failing hard disk, Windows files or registry corruption, viruses, or memory problems.
|My System Specs|
|Similar help and support threads for2: Bsod problem ntoskrnl.exe|
|BSOD problem, to do with ntoskrnl.exe||BSOD Help and Support|
|dxgmms1.sys, ntoskrnl.exe and win32k.sys BSOD and freezing problem||BSOD Help and Support|
|BSOD problem for months, getting worse, caused by ntoskrnl.exe||BSOD Help and Support|
|Recent BSOD ntoskrnl.exe seems to be the problem?||BSOD Help and Support|
|random BSOD's and cant do .dmp ntoskrnl.exe ( nt+7cc40 ) problem||BSOD Help and Support|
|BSOD PROBLEM ntoskrnl.exe||BSOD Help and Support|
|BSOD problem with a new PC: ntoskrnl.exe||BSOD Help and Support|
|Our Sites ||Site Links ||About Us ||Find Us |
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
All times are GMT -5. The time now is 07:06 AM.