Windows 7 BSOD - ntoskrnl.exe (nt + 0x7F1C0)

Similar Questions

• Windows 7 BSOD ntoskrnl.exe question

  Hello.  I'm having the same problem as the next person - http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/ntoskrnlexe-1040b-e58d2-6d5be/ea3a3e93-69bd-47c7-9f31-ddb723120912.  I ran Driver Verifier and then encountered the problem of not being able to access my laptop normally.  I disabled the driver verifier now.

  I redid my laptop about 3 times in the hope of solving my BSOD problem, but it is ongoing.

  Any help is appreciated.

  David Martinez

  THE

  They are related to your video driver.  I would like to begin by updating to the latest driver that yours is ~ 1 year.

  Microsoft (R) Windows debug 6.3.9600.17029 AMD64 Version
  Copyright (c) Microsoft Corporation. All rights reserved.

  Loading dump file [C:\Users\Ken\Desktop\052814-20592-01.dmp]
  The mini kernel dump file: only registers and the trace of the stack are available

  Symbol of validation of the path summary *.
  Location of response time (ms)
  Deferred SRV * H:\symbols* http://msdl.microsoft.com/download/symbols
  Symbol search path is: SRV * H:\symbols* http://msdl.microsoft.com/download/symbols
  Executable search path is:
  Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) free x 64
  Product: WinNt, suite: TerminalServer SingleUserTS
  By: 7601.18409.amd64fre.win7sp1_gdr.140303 - 2144
  Computer name:
  Kernel base = 0xfffff800'02e63000 PsLoadedModuleList = 0xfffff800'030 was 6890
  The debugging session: 14:44:02.483 Wed 28 may 2014 (UTC - 04:00)
  System Uptime: 0 days 0:02:46.482
  Loading the kernel symbols
  ...............................................................
  ................................................................
  ..................................................
  Loading user symbols
  Loading unloaded module list
  ....
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  BugCheck C4, {c0, fffffa800a546340, f6, fffff8800f2b9879}

  WARNING: Unable to verify timestamp for nvlddmkm.sys
  ERROR: Module load completed but symbols can be loaded for nvlddmkm.sys
  Probably caused by: nvlddmkm.sys (nvlddmkm + 9a 879)

  Follow-up: MachineOwner
  ---------

  2: kd >! analyze - v
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
  A device driver attempting to corrupt the system has taken.  It comes
  because the driver was specified in the registry as being suspect (by the)
  Administrator) and the kernel has allowed substantial control of this driver.
  If the pilot attempts to corrupt the system, looking for bugs, 0xC4, 0xC1, and 0xA
  Be one of the most commonly seen crashes.
  Arguments:
  Arg1: 00000000000000f6, handle user SEO as the core.
  Arg2: 00000000000000c 0, the value of Handle referenced.
  Arg3: fffffa800a546340, address of the current process.
  Arg4: fffff8800f2b9879, address inside the pilot making the incorrect reference.

  Debugging information:
  ------------------

  BUGCHECK_STR: 0xc4_f6

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

  Nom_processus: rundll32.exe

  CURRENT_IRQL: 0

  ANALYSIS_VERSION: 6.3.9600.17029 (debuggers (dbg). 140219-1702) amd64fre

  LAST_CONTROL_TRANSFER: from fffff800033654ec to fffff80002ed8bc0

  STACK_TEXT:
  "" fffff880 ' 0 c 315308 fffff800 ' 033654ec: 00000000 ' 000000 c 4 00000000' 000000f6 00000000'000000 c 0 fffffa80 ' a 0, 546340: nt! KeBugCheckEx
  "" fffff880 ' 0 c 315310 fffff800 ' 0337abf4: 00000000 ' 000000 c 0 fffffa80 ' 0a 546340 00000000'00000004 fffff880'0 c 317000: nt! VerifierBugCheckIfAppropriate + 0x3c
  fffff880 ' 0 c 315350 fffff800' 03132890: fffff8a0 '000016-0 fffff880' 0c3155a0 fffff880 '0 c 315700 fffff880' 0c 315930: nt! VfCheckUserHandle + 0x1b4
  "fffff880 ' 0 c 315430 fffff800 ' 031a95b5: 00000000 '00000000 fffff880' 00000001 fffffa80 '06067f30 fffff8a0' 05c08a00: nt! : NNGAKEGL: 'string' + 0x2027e
  "fffff880 ' 0 c 315500 fffff800 ' 02ed7e53: fffffa80 '0aa1e060 fffff880' 0c3158b8 00000000'00000002 00000000'00000000: nt! NtQueryValueKey + 0 x 115
  "" fffff880 ' 0 c 315690 fffff800 ' 02ed4410: fffff800 ' 03369 d 96 fffff880 ' 0f2b9879 fffff880 '0 c 315930 fffff880' 0c 315928: nt! KiSystemServiceCopyEnd + 0x13
  fffff880 '0 c 315898 fffff800' 03369d 96: fffff880 ' 0f2b9879 fffff880 '0 c 315930 fffff880' 0c 315928 fffff800 ' 02ed4410: nt! KiServiceLinkage
  "fffff880 '0c3158a0 fffff880' 0f2b9879: fffff880 ' 0c3168ca fffff880 ' 0 c 315970 fffff880 ' 0c3168b8 fffffa80 ' 0591ff18: nt! VfZwQueryValueKey + 0 x 76
  fffff880 '0c3158f0 fffff880' 0c3168ca: fffff880' 0591ff18 fffff880 '0c3168b8 fffffa80' 0 c 315970 00000000 00000000': nvlddmkm + 0x9a879
  fffff880'0c3158f8 fffff880'0 c 315970: fffff880 '0c3168b8 fffffa80' 0591ff18 00000000 00000000' fffff880 0'c 315920: 0xfffff880'0c3168ca
  "fffff880 ' 0 c 315900 fffff880 ' 0c3168b8: fffffa80'0591ff18 00000000 00000000' fffff880 ' 0 c 315920 fffff980' 00000000: 0xfffff880'0 c 315970
  "fffff880 ' 0 c 315908 fffffa80 ' 0591ff18: 00000000 '00000000 '0c 315920 fffff980'00000000 00000000 fffff880' 000000 c 0: 0xfffff880'0c3168b8
  fffff880'0 c 315910 00000000 00000000': fffff880 '0 c 315920 fffff980' c 0 00000000 00000000'000000 ' 00280026 fffffa80: 0xfffffa80'0591ff18

  STACK_COMMAND: kb

  FOLLOWUP_IP:
  nvlddmkm + 9 has 879
  fffff880'0f2b9879 3d340000c0 cmp eax, 0C0000034h

  SYMBOL_STACK_INDEX: 8

  SYMBOL_NAME: nvlddmkm + 9 has 879

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: nvlddmkm

  Nom_image: nvlddmkm.sys

  DEBUG_FLR_IMAGE_TIMESTAMP: 5280da75

  FAILURE_BUCKET_ID: X64_0xc4_f6_nvlddmkm + 9 has 879

  BUCKET_ID: X64_0xc4_f6_nvlddmkm + 9 has 879

  ANALYSIS_SOURCE: KM

  FAILURE_ID_HASH_STRING: km:x64_0xc4_f6_nvlddmkm + 9 has 879

  FAILURE_ID_HASH: {0c031110-986a-b405-c565-3ead8c9b6e45}

  Follow-up: MachineOwner
  ---------

• Windows 8 unexpected Kernel Mode trap BSOD (ntoskrnl.exe)

  Hello, I got the blue screen that gives me the error code: UNEXPECTED_KERNEL_MODE_TRAP (ntoskrnl.exe). I have had this problem since I got my computer, but it happens that all the other day. I tested my RAM with memtest and everything was good. I also use on all drivers updated. I recently installed "WhoCrashed" hoping to get more information as to what was causing this error. Here's the report;

  Thursday, June 26, 2014 6:31:37 PM GMT crashed your computer
  crash dump file: C:\WINDOWS\Minidump\062614-28703-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x153FA0)
  Bugcheck code: 0x7F (0 x 8, 0xFFFFF802935ABE70, 0xFFFFF80293592FF0, 0xFFFFF80291C5AB6E)
  Error: UNEXPECTED_KERNEL_MODE_TRAP
  file path: C:\WINDOWS\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: this bug check indicates that the Intel CPU generated a trap and the kernel could not catch this trap.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Any help will be much appreciated.

  Thank you

  Ryan

  Ryan

  The DMP was inconclusive pointing to memory.  My gut says it's Symantec.  I would like to do two things.  Run the driver verifier and remove Symantec and use the built in Defender.

  These accidents were related to the corruption of memory (probably caused by a driver).

  Please run these tests to check your memory and find which driver is causing the problem.

  
  

  If you're overclocking (pushing components beyond their design) return you to default at least until the crash is resolved. If you don't know what it is that you're probably not overclocking.

  
  

  Since then, it is more likely to be a pilot run everything first.

  1-Driver Verifier (for full instructions, see our wiki here)

  
  

  If the auditor does not have the issue we move to it.

  2-Memtest. (You can learn more about running memtest here)

  
  

  If you cannot start after you have enabled the auditor reboot in safe mode

  In Vista & victory (F8)

  When win 8 http://www.howtogeek.com/107511/how-to-boot-into-safe-mode-on-Windows-8-the-easy-way/

  
  

  Co-written by JMH3143

  .

• BSOD ntoskrnl.exe + 72 0x0000009f DRIVER_POWER_STATE_FAILURE has 40

  I almost brand new HP ProBOOK 450 G2 with Windows 7 Enterprise, just noticed today the first Memory Dump, thought then to ask... like the laptop is under warranty... laptop computer is on battery power and the battery is dead so saw the light flashing 'orange' and he got the memory dump and he came down, the battery was finished It happened... but its still not the right way to go then... I have through the app "BlueScreenView" about something, but he could not say exactly... searched thing many error BSOD here in the office, but none had the same error, sharing so if someone is kind enough to help.

  Dump file 050415-21028 - 01.dmp
  Time of the accident 04/05/2015-11:01:32
  Bug Check String DRIVER_POWER_STATE_FAILURE
  Bug check code 0x0000009f
  Parameter 1 00000000'00000003
  Parameter 2 fffffa80'07f37a10
  Parameter 3 fffff800'048943 d 8
  Parameter 4 fffffa80'08da0010
  Caused by the driver Ntoskrnl.exe
  Caused by the address ntoskrnl.exe + 72 has 40

  DMP file: http://1drv.ms/1K9FKRC

  Thanks in advance

  ONE

  This phenomenon was related to rtlane.sys NDIS Driver of Realtek Semiconductor Corporation.  I remove the current driver and install the latest driver available.

• Please help me solve this BSOD ntoskrnl.exe, ntkrnlmp.exe

  Hello

  I have problems with my new computer since I bought it, it started giving problems. Now this BSOD. I am totally frustrated with it. Please help me get rid of this questions.
  Here is the link of the minidump file:
  https://SkyDrive.live.com/redir?RESID=1F218460C89B0917%21114
  I guess that the culprit is wireless driver. With the old version of the wireless driver, I got another BSOD, so I uninstalled and installed the most recent version. Still problem persists.
  With whoCrashed, I found this information:
  Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
  Windows dir: C:\Windows
  CPU: GenuineIntel Intel (r) Core i7-3610QM CPU @ 2.30 GHz Intel586, level: 6
  8 logical processors, active mask: 255
  RAM: 8469991424 total
  VM: 2147352576, free: 1902690304

  Crash Dump Analysis
  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

  Tuesday, December 23, 13 9:36:04 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\122313-27736-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0 x 72680)
  Bugcheck code: 0x9F (0x3, 0xFFFFFA8007539060, 0xFFFFF80000B9C3D8, 0xFFFFFA800FE606B0)
  Error: DRIVER_POWER_STATE_FAILURE
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: this bug check indicates that the driver is in an inconsistent or invalid power state.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Tuesday, December 23, 13 9:36:04 CEST your computer crashed
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
  Bugcheck code: 0x9F (0x3, 0xFFFFFA8007539060, 0xFFFFF80000B9C3D8, 0xFFFFFA800FE606B0)
  Error: DRIVER_POWER_STATE_FAILURE
  Bug control description: this bug check indicates that the driver is in an inconsistent or invalid power state.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Please help me. Thanks in advance.

  Apvmz

  This phenomenon was related to the device driver wireless Extensible athrx.sys of Atheros Communications, Inc.  Yours is almost 2 years so not the most recent.

  I would like to re - install the latest driver available

• Free download windows root system32/ntoskrnl.exe

  My pc using windows XP Home Edition will not start massage says file missing or corupt /system32/ntoskrnl.exe is it possible to download this file on a cd on a different pc and install the file in the pc easily?  Thanks for any HELP!

  Hi LorraineParker-Jackson,

  ·         What is the number and the model of the computer?

  ·         Do you remember any recent changes made before the show?

  ·         What is the service pack installed?

  I suggest you follow the steps in the link below and check if it solves the problem.

   

  Error message: "Windows did not start because of a configuration of the disk of the computer problem.

  http://support.Microsoft.com/kb/314477

  I hope this helps.

• Different random BSOD, ntoskrnl.exe

  Hello

  I am getting random BSOD in ntoskrnl.exe + 75c00
  Can occur at any time and not necessarily in charge. I tried testing my ram, hard drives to find errors & ran sfc/scannow without error.
  I downloaded the minidumps on skydrive @ https://skydrive.live.com/#cid=539E2424E35481DA&id=539E2424E35481DA%21105
  A big thank you to all those who can help.

  Brett

  Two different causes.  First and foremost your Kaspersky.  I would like to delete and replace it with MSE

  Kaspersky is a common cause of BSOD.

  
  

  I remove and replace it with Microsoft Security Essentials at LEAST FOR TESTER.

  http://support.Kaspersky.com/downloads/utils/kavremover10.zip
  http://www.Microsoft.com/security_essentials/

  Second is related to keyscrambler.sys KeyScrambler keyboard driver.  I remove if not required or update to the latest if it is.

• Windows 8 gel (ntoskrnl.exe)

  So I've recently updated to windows 8 Pro in Windows 7 using only a key code and Setup. I first install Windows 8 questions, but it finally installed and I thought that it would be the end of my problems but as soon as I start windows, it works perfectly for 5 or so minutes and then I completely freeze not been able to do anything on my computer

  I installed a program called Blue Screen View and had a look at the dump files and every single one said that the accident was caused by the address 'ntoskrnl.exe + 52faa1' I know this has something to do with the core of windows and how to fix it is to reinstall windows, but I don't want to do that , so is perhaps all the other fixes, I could try to get Windows running again?
  Danny has soon

  Hi Patrick, remarkably my computer just started working fully again. I think he can turn off the hard drive because there always used to say 100% use of the disc when I was not doing something and now its stay a comfortable constantly and maybe a little more than 5-10% when you play in the summer games.

  If it stops working again as she hopefully will not I will use the information.
  Danny has soon.

• BSOD - ntoskrnl.exe Critical_process_died 0x000000ef

  Got BSOD problems on windows 2012 R2 server, Viewer bliuescreen points to critical_process_dies - ntpskrnl.exe

  DMP file is linked here https://onedrive.live.com/redir?resid=CE9C8B0A89BD1546! 111 & authkey =! ABWSymb0WgE6tJA & ithint = the file % 2cdmp

  Please notify

  These accidents were related to the corruption of memory (probably caused by a driver).

  Run these two tests to check your memory and find which driver is causing the problem.  Launch auditor.  You don't need to run memtest again unless the auditor is not the cause, or you want to.

  If you are overclocking anything reset by default before running these tests.
  In other words STOP! If you don't know what it means that you're probably not  
  
  
  
  
  1-Driver Verifier (for full instructions, see our wiki here)
  2-Memtest. (You can learn more about running memtest here)

• How to replace the < root windows > file \system32\ntoskrnl.exe on a system running Windows Server 2003 for Small Business Server when the system does not boot without it?

  I use an old server.  I've been reading that you can fix the file for XP if you have the disc but Server 2003 a 5 disk, that you would use, or would you use even one of them?

  Hi BrianStoll,

  Your question of Windows is more complex than what is generally answered in the Microsoft Answers forums. Appropriate in the TechNet forums. Please post your question in the TechNet forums.

  You can follow the link below to ask your question:
  http://social.technet.Microsoft.com/forums/en-us/winservergen/threads

   

  I hope that helps!

• Toot of Dell Inspiron 910 windows system32 ntoskrnl.exe error

  I booted up my laptop Inspiron 910 and got the following error message:

  Windows root system32 ntoskrnl.exe missing or corrupt please reload the disc.

  I tried several attempts through the advanced options [F8] and always comes back to the same error message.  I changed the BIOS to allow the disc to load first.  I put the Microsoft Windows XP Home Edition SP3 CD and you press a button to start.  Setup begins to install the files, but then I get the blue screen of death.

  It reads:

  A problem has been detected and windows has shut down to prevent damage to your computer.

  If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

  Check for viruses on your computer. Remove any newly installed hard drives or hard drive controllers. Check your hard drive to ensure that it is properly configured and completed. Run CHKDSK /F to check for hard drive corruption, and then restart your computer.

  Technical information:

  STOP: 0X0000007B (0XF7A5E63C, 0XC0000034, 0X00000000, 0X00000000)

  I also run diagnostics and got these error messages:

  Error Code 0F00:0244 Msg: DISK_0_Block 13533192 cannot read, replace the drive or remove the write protection

  I also have the same error codes in the following blocks:

  13533193

  13533194

  13533195

  13533196

  13533199

  13533208-13533215

  13533224

  13537707

  Any assistance or solutions would be useful!

  Thank you

  Hi rmina71,

  ·         Have you made changes on the computer before this problem?

  Follow the steps in the article.

  http://support.Microsoft.com/kb/2022960

• After sleep ntoskrnl.exe error 0x0000009f DRIVER_POWER_STATE_FAILURE

  DRIVER_POWER_STATE_FAILURE after sleep

  When I put my laptop to sleep by closing the lid or choosing sleep from the beginning, I get a bsod (ntoskrnl.exe 0x0000009f DRIVER_POWER_STATE_FAILURE) when the recovery.
  BlueScreenView report:http://dl.dropbox.com/u/12993257/bsod.htm
  Empty the file: http://dl.dropbox.com/u/12993257/091211-34538-01.zip
  Also, for some reason that I do not get the bsod when it puts itself in standby (IE after expire) but I understand when it hibernate itself.
  Any help is appreciated!
  Phil

  Hi chubble10,

  Method 1
  I suggest you try the steps from the following links:

  Stop error when you upgrade a computer that is running Windows 7 or Windows Server 2008 R2 standby or into hibernation, or when you restart the computer: "0x9F".
  http://support.Microsoft.com/kb/975599

  stop "0x0000009F" error message when a computer enters and fate of putting into hibernation in Windows 7 or Windows Server 2008 R2
  http://support.Microsoft.com/kb/981848

  Method 2
  This issue could be due to corruption of the graphics card driver. I suggest you to update the graphics card drivers.

  Updated a hardware driver that is not working properly
  http://Windows.Microsoft.com/en-in/Windows7/update-a-driver-for-hardware-that-isn ' t-work correctly

• My computer will not start - ntoskrnl.exe is missing

  Original title: my computer does not start upp

  my desktop does not load upward. I turned on and the following message appears.

  Windows didn't start because the following file is missing

  corrupted:

  Windows root>\system32\ntoskrnl.exe.

  Re - install a copy of the above file.

  is there something I can do?

  I don't have the boot disks.

  There were no power failure, etc.?

  The system is equipped with a CD/DVD player?

  I suspect that AVG has quarantined (effectively deleted) your way of thinking of ntoskrnl.exe file the file has been afflicted (it's perhaps), but there are copies on your system in other places, so you can simply replace the missing file.

  I would normally say that make you a XP Recovery Console bootable CD that you can create (no XP media required), but since you have XP Home Edition, which can frustrate you if you do not know the XP administrator password.  We can do the part later because it would be a good CD to have.

  Make a Hiren boot CD, boot your system on this CD and find your XP installation boot drive for a copy of ntoskrnl.exe and copy / paste the file into the c:\windows\system32 folder where it belongs.

  Places to find backups of critical files on the XP system are:

  c:\Windows\System32\dllcache

  c:\windows\ServicePackFiles\i386

  Answered in the affirmative if invited to replace the existing file.

  If that's all you need to do to get there, you should consider broadening your horizons beyond AVG antivirus antimalware if you do not have this or similar problems.

  Do you have a Hiren BootCD you can download here:

  http://www.hirensbootcd.org/

  On the left, click on download, scroll down, choose the most recent version

  The download link is a little difficult to see and find, for some reason, so here are some ideas (they seem to change around for a reason, but that might just me my interpretation).  If you can't understand it, let me know so that I can update my copy/paste route.

  On the page for the version the most recent are information pages on what has changed in the latest version.  Look to the bottom of the page and you will be on page 1 of a number of pages (1 of 2 of 9, 9, 9, 3)...  The link to download the ZIP file is on the last page that is now for version 12, page 9 (or click on the end button).

  The ZIP file is large, so the download will take probably some time to complete.  Then unzip the download to extract the Hirens.BootCD.ISO file that will be used to create your new bootable CD.

  Create a bootable CD. ISO file is not the same as simply copying the. File ISO onto a blank CD.  You must use software that includes how to burn a. ISO to a CD to create a bootable CD.

  File ZIP the Hiren is the file BurnToCD.cmd that you can double-click to launch it.  The BurnToCD.cmd will use the file BurnCDCC.exe to burn the. ISO file onto a blank CD using your existing CD burner.  You can also use your own burning software as long as your software is able to create a bootable CD. ISO file.

  More modern burning programs can create a bootable CD. ISO image.  Create a CD from an ISO image bootable is not the same as just the file on a CD burning.

  If you need a simple and CD burning, this is a free software popular software:

  http://www.ImgBurn.com/

  Here are some instructions for ImgBurn:

  http://Forum.ImgBurn.com/index.php?showtopic=61

  It would be a good idea to test your new bootable CD on a computer running.

  You may need to adjust the computer BIOS settings to use the CD-ROM drive as the first device to boot instead of the hard drive.  These adjustments are made before Windows tries to load.  If you miss it, you will need to restart the system again.

  When starting on the Hiren's CD, you will see a menu of options.  Choose Mini XP.  It will appear while Windows is loading and you will be presented with a desktop computer that has the look and feel of the interface of Windows Explorer, you are already accustomed to using.

  Using the Mini XP, you can access Internet, maneuvering around your system, search for files, copy files, replace the files and run the scans for malware, edit the text files (like the c:\boot.ini) etc.

  There are dozens of free and useful tools included in the CD that can be used to repair your system or copy your important personal files on another device (like a USB device or an external drive) in the case where you just give up and decide to reinstall your XP (I hope that you will not make this decision).

  Do, or do not. There is no test.

  I need YOUR voice and the points for helpful answers and propose responses. I'm saving for a pony!

• Windows BSOD KERNEL_DATA_INPAGE_ERROR 8; Ntoskrnl.exe + 7 has 040

  Hello world

  I had reinstall Windows 8 last month cause too many errors with the Windows 8 and I had still BOSD arrives with a new installation of Windows 8.

  The last that I have no will is this one:

  KERNEL_DATA_INPAGE_ERROR

  Ntoskrnl.exe + 7 has 040

  We arrive in surfing on the web and burning with IMGBURN. Many Disconnections occur when you use the dvd burner.

  The other at the moment that I solved is "atikmpag.sys" I read on the net that I need to update the file from a download of catalyst frensh.

  Here all DUMP files and the news of the computer:

  All files: https://skydrive.live.com/redir?resid=10F449F32E80D9B2! 390

  Thank you!

  8ternity

  They were related to the following

  KERNEL_DATA_INPAGE_ERROR (7A)
  The requested page of kernel data could not be read in.  Is usually caused by
  a bad block in the disk controller or paging file error.

  My gut feeling is that it is one of these drivers or your moy.  I would like to update the drivers and replace AVG with the built-in Defender

  000 fcl 26/09/2008 09:11:22
  ksaud.sys 2010-07-14 06:12:54
  ntk_PowerDVD_64.sys 03/08/2010 05:04:12
  PxHlpa64.sys 2011-10-17 10:29:34
  amdsbs.sys 21/02/2012 14:15:43

  AVG can be a cause of BSOD.

  http://www.Avg.com/us-en/utilities

  How to find drivers:
  -Google search for the name of the driver
  -compare Google results with what is installed on your system to determine on what device/program, it belongs to
  -Visit the web site of the manufacturer of the hardware or program to get the latest drivers (do not use Windows Update or Device Manager Update Driver function).
  s ' there is difficult to locate them, post back with questions, and someone will try and help you find the right program

  The most common drivers are listed on this page: driver reference

  http://www.carrona.org/dvrref.php

  http://SysNative.com/drivers/

  -Driver manufacturer links are on this page: http://www.carrona.org

• Windows 8 BSOD caused by ntoskrnl.exe

  Hello.

  I get a lot of the dreaded BSOD lately.
  From the beginning I thought that it's nvidia drivers. Update of those fixed everything except a BSOD I get.
  Now I get the same BSOD, and it is caused by ntoskrnl.exe and playback memory problems.
  I've been all around you are looking for assistance and use of memtest86 without result.
  The Msinfo32 and .dmp files are located here: DMP.zip 
  Anyone have any idea what may be causing this?
  I couldn't find the RAM that I use in the compatibility table for the motherboard. So that's what I think may cause the problem.
  Any help is greatly appreciated.
  Kind regards
  Arve

  Hi Arve,

  All attached files of the DMP are the bug check IRQL_NOT_LESS_OR_EQUAL (a) .

  This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.

  This bug check is issued if the memory paged (or invalid) is accessible when the IRQL is too high. The error that usually generates this bug check occurs after the installation of the faulty device driver or service system, BIOS.

  If we look at the call stack:
  
  STACK_TEXT:
  "fffff880 '0335caf0 fffff880' 06a4d817: fffff880 00000000' fffffa80 ' 00000008 fffffa80 ' 12fdbe10 00000005' 00001f80: nt! KeSetEvent + 0x2ad
  fffff880 '0335cb60 00000000 fffff880': fffffa80'00000008 fffffa80 '12fdbe10 00000005' 00001f80 fffffa80' 1458a6a0: MBfilt64+ 0 x 1817
  fffff880'0335cb68 fffffa80'00000008: fffffa80 '12fdbe10 00000005' 00001f80 fffffa80 '1458a6a0 fffff800' 9bc62d4c: 00000000' 0xfffff880
  fffff880 '0335cb70 fffffa80' 12fdbe10: 00000005' 00001f80 fffffa80'1458a6a0 fffff800 '9bc62d4c fffffa80' 1458a6a0: 0xfffffa80'00000008
  fffff880 '0335cb78 00000005' 00001f80: fffffa80 ' 1458a6a0 fffff800 '9bc62d4c fffffa80' 1458a6a0 fffffa80 ' 1458a6a0: 0xfffffa80'12fdbe10
  fffff880 '0335cb80 fffffa80' 1458a6a0: fffff800 ' 9bc62d4c fffffa80 '1458a6a0 fffffa80' 1458a6a0 fffffa80 ' 12fdbe10: 0 x 5 ' 00001f80
  fffff880 '0335cb88 fffff800' 9bc62d4c: fffffa80 ' 1458a6a0 fffffa80 '1458a6a0 fffffa80' 12fdbe10 fffff880 ' 02fc9f00: 0xfffffa80'1458a6a0
  fffff880 '0335cb90 00000000' 00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! ViPendingCompleteAfterWait + 0xc4

  Cannot load the image MBfilt64.sys, 0n2 error Win32
  WARNING: Unable to verify timestamp for MBfilt64.sys
  ERROR: Module load completed but symbols can be loaded for MBfilt64.sys
  Probably caused by: MBfilt64.sys (MBfilt64 + 1817)

  ^^
  Driver Realtek HiDefinition Audio (referred to as Creative Audio Driver file).

  If we run a lmvm on your:

  4: kd > lmvm MBfilt64
  start end module name
  fffff880 '06a4c000 fffff880' 06a5a000 MBfilt64 T (no symbol)
  Loaded symbol image file: MBfilt64.sys
  Image path: MBfilt64.sys
  Image name: MBfilt64.sys
  Timestamp: Thu Aug 30 23:40:32 2009 (4A7267B0)

  ^^, Yours is dated 2009 ~ The most recent is AFAIK as early as September 2013, via - Realtek site

  http://www.Realtek.com.tw/downloads/downloadsCheck.aspx?langid=1&PNid=24&PFID=24&level=4&Conn=3&DownTypeID=3&GETDOWN=false

  To update this driver as soon as POSSIBLE.

  -----------------------------------------------------------

  In addition, to provide peace of mind regarding your request of RAM. If you receive a card mother and they have a list of the RAM compatible in the manual, etc., this is called a QVL (qualified suppliers list). It is simply a list of RAM which has been tested internally and is PROVING to be quite compatible 100%. If the RAM is not on the list, it is not by all means, implies that the RAM will be inconsistent and cause problems. Actually today is very rare. Your RAM doesn't seem to be the issue at all in these accidents.

  Kind regards

  Patrick