Blue Screen 0x7A: KERNEL_DATA_INPAGE_ERROR

Similar Questions

• Blue screen error: KERNEL_DATA_INPAGE_ERROR

  Hello. Whenever I try to run a full scan of my computer I get a blue screen that says error: KERNEL_DATA_INPAGE_ERROR. Every time. Ever since I have ugraded my virus protection. What should I do?

  We need the DMP file because it contains the single record of the sequence of events that led to the accident, what drivers have been loaded, and what has been loaded.

  
  

  WE NEED AT LEAST TWO FILES DMP TO SPOT TRENDS AND TO CONFIRM THE DIAGNOSIS.

  You may be able to get the DMP files without crashing by booting in SafeMode (F8) with networking.

  If you are overclocking stop.  (chances are that if you are unsure if you are, you are not)

  To allow us to help you with symptoms BSOD on your computer, download the contents of your folder "\Windows\Minidump".

  The procedure:

  * Copy the contents of \Windows\Minidump to another location (temporary) somewhere on your machine.

  * Zip up the copy (compress)

  * Please download to a service like Skydrive or "Rapidshare" to share files and put a link to them in your answer.

  Link to find out how to download below.

  http://www.WikiHow.com/use-SkyDrive

  To ensure the minidumps are enabled:

  * Click Start, in the search box, type: sysdm.cpl, press ENTER.

  * On the Advanced tab, click Startup and recovery... Settings button.

  * Make sure that automatically restart is unchecked.

  * Under the writing debugging information header, select image partial memory (256 KB) in the list box drop-down (varies from 256kb).

  * Ensure to that small Dump Directory is listed as % systemroot%\Minidump.

  * OK your way out.

  * Reboot if changes have been made.

  Please also run MSinfo32 and download the output as well.

  To run MSinfo32 please go to start > run > MSinfo32

  Go to 'file', 'save' and download the PDF is saved with the DMP

  System specs are extremely useful then please include everything you know.

  
  

  Blue screen view and that crashed are often wrong and should only be used in case of emergency...

  
  

  You can learn more about BSOD here

  You will learn how to test your memory here 

  
  

  
  

  Team Zigzag3143.com  

• In Windows Xp SP2, I get the blue screen error KERNEL_DATA_INPAGE_ERROR

  Technical information:

  STOP: 0XC0000007A (0XC000000E, 0XCB6D59A13, 0XC02DB564, 0XC57671860)
  PortCls.sys - AddressB6D59A13 base at B6D3F000, DateStamp 40574e49
  Beginning physical memory dump

  Your plant is associated with a low-memory exception.  It's either your Ram, or more likely a driver.  You have some very old drivers including 2007 ESET.  I would like to update the drivers below AND update of Service Pack 3
  

  BIOS.sys 16/03/2005 02:23:52
  C:\windows\system32\drivers\eamon.sys 2007-12-21 03:17:22
  fetnd5.sys 07/20/2001 07:40:24
  ParVdm.SYS 17/08/2001 16:49:49

  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

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

• Blue screen 64-bit Vista - 0x7a-KERNEL_DATA_INPAGE_ERROR

  original title: 64-bit Vista of death blue screen

  I started to have blue screen errors.  I received a couple but 4 different ones.  One I have and I got different eras has been STOP: 0x000000F4 and that's all that I've got ACE for this one at a time.  He began by the freezing of my office and remained frozen for a few minutes until it gave me the blue screen.  I restarted went without failure then normal mode and it kept working for quite some time.

  Then he kept the freeze again.  Then he gave me

  KERNEL_DATA_INPAGE_ERROR memory options disable BIOS such as implementing caching or shading.  0x0000007A (0xFFFFFFFFC0000056, 0 x 0000000086509860, 0xFFFFF6FD30009778, 0xFFFFFA60012EF244)

  So I rebooted again and there once again in safe mode and back to normal.

  So I kept trying to see if my PC kept working.  Because I didn't have from time to time to post how I continued to use it as he continued to work.  Then it froze again and gave me

  STOP: c000021a {fatal system error} the initial session of the system or process ended unexpectedly with status 0x00000000 (0xC0000056, 0 x 00100500) the system has been turned off.

  So this time he send me to the Startup Repair and after trying to find a solution for a while, he couldn't fix and tried to allow me to restore but restore was not successful and gave me.

  StartRep.exe - Application Error

  The statement to the 0x7779b49e referenced memory at 0xff7f2f78.  Required data has not been placed in memory because of an error of e/s of 0xc0000185 status.  CLICK ON OK TO TERMINATE THE PROGRAM.

  So I keep on going and finally at some point it allows to restore only to give me another simialar to a previous error.

  STOP: 0X0000007A (0XFFFFFFFFC0000056, 0X000000002425E860, 0XFFFFF6FD30019408, 0XFFFFFA60032810EC)

  Oh Yes (EDIT) at some point during one of the Security Modes it froze and let nothing happen. Just thought I would add in it.

  Sorry it's a little long but any help or info would be appreciated.  I clean my registry and it kept my computer goes about a week before this last error.  Does not do anything for it since.  The only thing I could think that I installed because it started happening was Norton Internet Security 2011 but at the time I don't think it was a big deal, so do not know how long after or before there was that I installed and started having some bluescreens.

  All my drivers are up to date for.

  A little info extra snacks on the PC.

  OS 64 bit Vista Home premium

  Intel core 2 quad cpu q8200

  Processor speed - 2.33 ghz

  system memory - 4 GB

  Gateway model desktop sx2800

  Thanks in advance.

  Hello

  Nothing is 100% until you find the cause, sure seems like hard drive. Read the link below.

  More general fix is updated to the drivers, BIOS and chipset and different control software. Also
  check the wiring on the hard drive.

  BCCode: F4 0x000000F4<-- read="" this="">
  * 1241.html http://www.faultwire.com/solutions-fatal_error/A-process-or-thread-crucial-to-System-Operation-has-0x000000F4-

  BCCode: 7A 0x0000007A<-- read="" this="">
  * 1137.html? order = votes http://www.faultwire.com/solutions-fatal_error/kernel-Data-InPage-Error-0x0000007A-

  I hope this helps.

• Kernel_Data_Inpage_Error error blue screen

  Original title: recently, our PC had blue screen errors

  We have tried to update the BIOS, but we always get the Kernel_Data_Inpage_Error.  What else can we try?

  Hello

  1. are you able to boot to the desktop?

  2. when exactly you get this blue screen error?

  When you encounter a Blue Screen of Death (BSoD) in Windows, the computer saves information about the error message in a log file. This log file or minidump file is saved in the subdirectory of Windows Minidump (C:\Windows\MiniDump). Generally the information stored in the minidump file can help identify the cause of the blue screen error message and help you solve the problem.

  For more information on the reading of the memory dump files, see the following article:

  How read partial memory dump files that Windows creates for debugging

  Resolution:

  Error code KERNEL_DATA_INPAGE_ERROR STOP: 0x0000007A indicates that the data page of the kernel of the required paging file could not be read into memory. It seems that there are some problems with the hard drive.

  Use the check disk command for all errors on the hard drive.

  Warning: We recommend not to interrupt the CHKDSK process. Microsoft does not guarantee the integrity of the disk if the CHKDSK program is interrupted. Security, you can back up your data before using check disk drive.

  Use the drive control as follows:

  (a) click Start.

  (b) in the search box type 'cmd' and ENTER. Right click and select "Run as Administrator".

  (c) type at the prompt in the command CHKDSK/p and press ENTER to scan the drive.

  (d) then type CHKDSK C: /F /R and press ENTER to repair corrupt sectors, if there are.

  NOTE: The root drive must be C: and drive can schedule a task to start the system, if this is the case, press on is to schedule a task, and then restart the computer to run chkdsk.
  When chkdsk is finished, boot up to the desktop, and then check.

  You can check the link below for more details - mentioned
  http://msdn.Microsoft.com/en-us/library/ms793989.aspx

• Help, please! KERNEL_DATA_INPAGE_ERROR restart blue screen

  Hello

  I've known the KERNEL_DATA_INPAGE_ERROR blue screen which causes reboot at random times when I use my computer. I tried a number of options and have been in contact with a number of Microsoft employees to try to solve this problem, but so far nothing has worked. Here is a list of whathas was made up here, but all to no success. These actions are without particular chronological order:

  Ran CHKDSK /R in command prompt

  CHKDSK ran sfc and dism in command prompt

  A ran CHKDSK/X/r/f in the Safe Mode command prompt

  A ran CHKDSK /F /R in Safe Mode command prompt

  Analyses with HitmanPro, ESET, Norton and Malwarebytes

  A run MSDT while with the Microsoft Staff

  Update various drivers

  Convenience of Ran with Microsoft staff

  Finally, I performed the update on my PC, but little time action after I did, I had projected again blue.

  My OS was 8.1, now demoted to 8 since I refreshed.

  I'm ready to remove and reinstall windows as a last resort if nothing else can be done, if that would solve the question. I appreciate the help that can be given.

  Kind regards

  Josh

  We need the log files themselves (called a DMP files) because they contain the only record of the sequence of events that led to the accident, what drivers have been loaded, and what has been loaded.
  Please follow our instructions to find and download the files, we need to help you fix your computer. They can be found at here
  If you have any questions regarding the procedure, please ask

• Getting blue screen XP errors, "KERNEL_DATA_INPAGE_ERROR 0 x 00000077.

  I always get a blue screen even using computor that rises from the Kernal_stack_inpage_error and tech info stop: 0 x 00000077.  I tried to enter the cmd and typed chkdsk/r, but when he ran he was no problem staring at... Help, please

  I have windows XP

  Hi dennis6969,
   
  Follow the steps listed in the section below to resolve this issue:
  You receive an error message on a Windows XP-based computer: "Stop 0 x 00000077" or "KERNEL_STACK_INPAGE_ERROR"
   
  See also:
  Bug Check 0x77: KERNEL_STACK_INPAGE_ERROR

• Blue screen Crash 0x7a error - whenever I play a game fullscreen (in this case, Fallout New Vegas)

  original title: Blue Screen Crash - whenever I play a game fullscreen (in this case, Fallout New Vegas)

  For some reason that I was constantly blue screen crashes whenever I'm playing Fallout New Vegas on my computer. I'm positive my computer takes care of everything, I will list the specs below. He broke down twice today while I played for a good two and a half hours before the first, but then when I rebooted and went back into the game, he has frozen almost immediately so I ended the process. Then I tried once more, maybe got 10 minutes of play until a third crash...

  Here are my specs;

  Biostar H55 HD motherboard Intel

  Intel i3 to 2.93 GHz processor

  Mushkin 4 GB Ram DDR3 (1333 MHZ)

  500 GB Seagate HDD

  NVidia GeForce GTS 450 graphics card

  Orion HP650D 650W PSU

  I went into the Device Manager and ensured that all my drivers are up to date, that don't seem to not be.

  Here are the final details of the accident.

  1

  Signature of the problem:
  Problem event name: BlueScreen
  OS version: 6.1.7600.2.0.0.768.3
  Locale ID: 4105

  More information about the problem:
  BCCode: 7A
  BCP1: FFFFF6FC400070C8
  BCP2: FFFFFFFFC000000E
  BCP3: 00000000108BA860
  BCP4: FFFFF88000E19008
  OS version: 6_1_7600
  Service Pack: 0_0
  Product: 768_1

  Files helping to describe the problem:
  C:\Windows\Minidump\111010-25156-01.dmp
  C:\Users\Adam\AppData\Local\Temp\WER-51921-0.SysData.XML

  2

  Signature of the problem:
  Problem event name: BlueScreen
  OS version: 6.1.7600.2.0.0.768.3
  Locale ID: 4105

  More information about the problem:
  BCCode: f4
  BCP1: 0000000000000003
  BCP2: FFFFFA8005B20B30
  BCP3: FFFFFA8005B20E10
  BCP4: FFFFF800031855D0
  OS version: 6_1_7600
  Service Pack: 0_0
  Product: 768_1

  Files helping to describe the problem:
  C:\Windows\Minidump\111010-31187-01.dmp
  C:\Users\Adam\AppData\Local\Temp\WER-42468-0.SysData.XML

  If someone could give me a hand I would be very grateful, it became extremely frustrating :(

  Hi Adam,.

  This method works.

  the sfclog tells me that the files in this folder are damaged:

  C:\Program Files\Windows Sidebar\Gadgets\Weather.Gadget\images

  Replace them with the files of your DVDs:

  http://blog.NirSoft.NET/2009/09/17/how-to-extract-missing-system-files-from-the-DVD-of-Windows-7vista/

  BugCheck CRITICAL_OBJECT_TERMINATION (f4)
  A process or thread crucial to system operation has unexpectedly left or been
  terminated.

  1 crash is probably caused by: csrss.exe

  ExceptionCode: c0000005 (access violation)

  the second accident is caused by your HARD disk:
  MODULE_NAME: hardware_disk

  FAILURE_BUCKET_ID: X64_0xF4_IOERR _C000000E_IMAGE_hardware_disk

  Your disk has i/o errors causing Windows to fail. Back up all the data and check the HARD drive with a diagnostic tool.

  "A programmer is just a tool that converts the caffeine in code" Deputy CLIP - http://www.winvistaside.de/

• Blue screen frequently Crash on my desk. Help, please

  (Local) information system
  computer name: PNKJRANA-PC
  Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
  Windows dir: C:\Windows
  Material: Z87-D3HP, Gigabyte Technology Co., Ltd., CF-D3HP-Z87
  CPU: GenuineIntel Intel (r) Core i5-4670 CPU @ 3.40 GHz Intel586, level: 6
  4 logical processors, active mask: 15
  RAM: 8473726976 total
  VM: 2147352576, free: 1918525440

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

  Dumps are enabled on your computer.

  Wednesday, June 11, 2014 6:02:32 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\061114-8502-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bug check code: 0xF4 (0x3, 0xFFFFFA80093A2B30, 0xFFFFFA80093A2E10, 0xFFFFF800033D47B0)
  Error: CRITICAL_OBJECT_TERMINATION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a process or thread crucial to system operation has unexpectedly left or came to an end.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem may be due to a thermal problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, June 11, 2014 6:02:32 PM GMT crashed your computer
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
  Bug check code: 0xF4 (0x3, 0xFFFFFA80093A2B30, 0xFFFFFA80093A2E10, 0xFFFFF800033D47B0)
  Error: CRITICAL_OBJECT_TERMINATION
  Bug control description: This indicates that a process or thread crucial to system operation has unexpectedly left or came to an end.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem may be due to a thermal problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, June 11, 2014 17:36:08 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\061114-8611-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x7A (0xFFFFFFFFC000000E, 0x17A31DBE0, 0xFFFFF6FC4004A128, 0xFFFFF88009425000)
  Error: KERNEL_DATA_INPAGE_ERROR
  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 data page of the kernel of the required paging file cannot be read into memory.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Friday, June 6, 2014 3:28:28 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\060614-7737-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bug check code: 0xF4 (0x3, 0xFFFFFA8009EFBB30, 0xFFFFFA8009EFBE10, 0xFFFFF800033907B0)
  Error: CRITICAL_OBJECT_TERMINATION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a process or thread crucial to system operation has unexpectedly left or came to an end.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem may be due to a thermal problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Saturday, May 31, 2014 1:51:04 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\053114-8361-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0xEF3B0)
  Bugcheck code: 0x7A (0xFFFFFFFFC000000E, 0x22B999860, 0xFFFFF6FC4000A9A8, 0xFFFFF880015353B0)
  Error: KERNEL_DATA_INPAGE_ERROR
  file path: C:\Windows\system32\drivers\ntfs.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT file system driver
  Bug control description: this bug check indicates that the data page of the kernel of the required paging file cannot be read into memory.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Saturday, May 31, 2014 1:31:34 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\053114-8564-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bug check code: 0xF4 (0x3, 0xFFFFFA8009BE4B30, 0xFFFFFA8009BE4E10, 0xFFFFF800033D77B0)
  Error: CRITICAL_OBJECT_TERMINATION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a process or thread crucial to system operation has unexpectedly left or came to an end.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem may be due to a thermal problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Thursday, may 29, 2014 17:04:18 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\052914-10420-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bug check code: 0xF4 (0x3, 0xFFFFFA8009EEF9E0, 0xFFFFFA8009EEFCC0, 0xFFFFF800033897B0)
  Error: CRITICAL_OBJECT_TERMINATION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a process or thread crucial to system operation has unexpectedly left or came to an end.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem may be due to a thermal problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Friday, May 9, 2014 1:35:57 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\050914-33743-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bug check code: 0xF4 (0x3, 0xFFFFFA80097DDB30, 0xFFFFFA80097DDE10, 0xFFFFF800033E07B0)
  Error: CRITICAL_OBJECT_TERMINATION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a process or thread crucial to system operation has unexpectedly left or came to an end.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem may be due to a thermal problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, may 7, 2014 15:25:25 this computer crashed
  crash dump file: C:\Windows\Minidump\050714-7675-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bug check code: 0xF4 (0x3, 0xFFFFFA8009CBFB30, 0xFFFFFA8009CBFE10, 0xFFFFF800033E07B0)
  Error: CRITICAL_OBJECT_TERMINATION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a process or thread crucial to system operation has unexpectedly left or came to an end.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem may be due to a thermal problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, may 7, 2014 2:14:33 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\050714-8252-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bug check code: 0xF4 (0x3, 0xFFFFFA8009C66910, 0xFFFFFA8009C66BF0, 0xFFFFF8000337E7B0)
  Error: CRITICAL_OBJECT_TERMINATION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a process or thread crucial to system operation has unexpectedly left or came to an end.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem may be due to a thermal problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Conclusion
  23 dumps were found and analysed. Only 10 are included in this report. No offending third pilot have been found. Consider using WhoCrashed professional that offers a more detailed using symbol resolution. Also configure your system to produce a full memory dump can help you.

  Read the GENERAL WARNINGS for the failures of the system troubleshooting section for more information.

  Note that it is not always possible to say with certainty whether a reported driver is in fact responsible for crash your system or cause is in another module. However, it is suggested that you look for updates for the products that these drivers belong to and regularly visit Windows Update or activate the automatic updates for Windows. In case a piece of defective material is originally wrong, a Google search on the errors of control of bug with the name of the model and brand of your computer can help you to deepen this review.

  Hello

  I apologize for the late response.

  You can try to follow the steps mentioned in the link below and see if that helps.

  Resolve stop (blue screen) error in Windows 7

  http://Windows.Microsoft.com/en-us/Windows7/resolving-stop-blue-screen-errors-in-Windows-7

  Note: When you use system restore to restore the computer to a previous state, the programs and updates that you have installed are removed.

  Important: When running Chkdsk on the drive hard if bad sectors are found on the disk hard when Chkdsk attempts to repair this area so all available data on this risk be lost.

  If that is not helping then, open the link and follow the instructions to get the event logs, so that we can see which application is defective.

  http://Windows.Microsoft.com/en-us/Windows7/what-information-appears-in-event-logs-Event-Viewer

  I hope this helps. If not, please do not hesitate to write us again and we will be happy to help you.

  Thank you

• HP Compaq 8100 blue screen - server operating system

  We had a Hewlett-Packard / 8100 Elite SFF PC, installed Windows Server 2008 R2 Enterprise 64-bit edition and we are using as Team Foundation server (installed Team Foundation Server 2010) and containing approximately 25 team projects with 50 users who access this server, the server with 4 GB ram and Intel Core i5 750 2.67 GHz CPU processor. The problem is its fair in blue screen and restart. The system is in place to this day because we lack of WSUS and it automatically updates all the servers.here I'm asking an error log created using this software bluescreenview , due to this blue screen, we are facing a lot of problem .the below list of crash is created using above software and generated as HTML page but I can not post sound also exaced so I stuck text help, please

  List of crash
  
  Dump File	Crash Time	Bug Check String	Bug Check Code	parameter 1	parameter 2	parameter 3	parameter 4	caused by the pilot	caused by address	Description of the file	product name	company	File Version	processor	Crash address	stack address 1	stack address 2	stack address 3	name of the computer	full path	County of processors	Major Version	minor Version	size of the dump file	Dump of the file
  
  82462 052113 - 01.dmp	21/05/2013 07:56:28	IRQL_NOT_LESS_OR_EQUAL	0x0000000a	00000000'00000004	00000000'00000002	00000001 00000000'	fffff800'01ed6ac1	ntoskrnl.exe	ntoskrnl.exe + 71f00	NT Kernel & system of	operating system Microsoft® Windows®	Microsoft Corporation	6.1.7600.16385 (win7_rtm.090713 - 1255)	x 64	ntoskrnl.exe + 71f00	 	 	 	 	C:\Windows\Minidump\052113-82462-01.dmp	4	15	7600	288 016	21/05/2013-08:04:43
  
  050313-73148 - 01.dmp	03/05/2013 15:20:40	IRQL_NOT_LESS_OR_EQUAL	0x0000000a	00000000'00000004	00000000'00000002	00000001 00000000'	fffff800'01e9cac1	ntoskrnl.exe	ntoskrnl.exe + 71f00	NT Kernel & system of	operating system Microsoft® Windows®	Microsoft Corporation	6.1.7600.16385 (win7_rtm.090713 - 1255)	x 64	ntoskrnl.exe + 71f00	 	 	 	 	C:\Windows\Minidump\050313-73148-01.dmp	4	15	7600	288 016	03/05/2013 15:27:46
  
  032513-47751 - 01.dmp	25/03/2013 19:30:20	IRQL_NOT_LESS_OR_EQUAL	0x0000000a	00000000'00000004	00000000'00000002	00000001 00000000'	fffff800'01e8aac1	ntoskrnl.exe	ntoskrnl.exe + 71f00	NT Kernel & system of	operating system Microsoft® Windows®	Microsoft Corporation	6.1.7600.16385 (win7_rtm.090713 - 1255)	x 64	ntoskrnl.exe + 71f00	 	 	 	 	C:\Windows\Minidump\032513-47751-01.dmp	4	15	7600	288 016	25/03/2013 19:46:17
  
  031713-41948 - 01.dmp	17/03/2013-17:17:49	IRQL_NOT_LESS_OR_EQUAL	0x0000000a	00000000'00000004	00000000'00000002	00000001 00000000'	fffff800'01ea2ac1	ntoskrnl.exe	ntoskrnl.exe + 71f00	NT Kernel & system of	operating system Microsoft® Windows®	Microsoft Corporation	6.1.7600.16385 (win7_rtm.090713 - 1255)	x 64	ntoskrnl.exe + 71f00	 	 	 	 	C:\Windows\Minidump\031713-41948-01.dmp	4	15	7600	288 016	17/03/2013-17:26:13
  
  031613-47408 - 01.dmp	2013/03/16 04:24:16	IRQL_NOT_LESS_OR_EQUAL	0x0000000a	00000000'00000004	00000000'00000002	00000001 00000000'	fffff800'01edcac1	ntoskrnl.exe	ntoskrnl.exe + 71f00	NT Kernel & system of	operating system Microsoft® Windows®	Microsoft Corporation	6.1.7600.16385 (win7_rtm.090713 - 1255)	x 64	ntoskrnl.exe + 71f00	 	 	 	 	C:\Windows\Minidump\031613-47408-01.dmp	4	15	7600	288 016	16/03/2013-04:33:45
  
  021713-80746 - 01.dmp	17/02/2013 20:39:37	IRQL_NOT_LESS_OR_EQUAL	0x0000000a	00000000'00000004	00000000'00000002	00000001 00000000'	fffff800'01cd0ac1	ntoskrnl.exe	ntoskrnl.exe + 71f00	NT Kernel & system of	operating system Microsoft® Windows®	Microsoft Corporation	6.1.7600.16385 (win7_rtm.090713 - 1255)	x 64	ntoskrnl.exe + 71f00	 	 	 	 	C:\Windows\Minidump\021713-80746-01.dmp	4	15	7600	292 144	17/02/2013 20:47:11
  
  012213-80590 - 01.dmp	22/01/2013 04:09:11	IRQL_NOT_LESS_OR_EQUAL	0x0000000a	00000000'00000004	00000000'00000002	00000001 00000000'	fffff800'01ce2ac1	ntoskrnl.exe	ntoskrnl.exe + 71f00	NT Kernel & system of	operating system Microsoft® Windows®	Microsoft Corporation	6.1.7600.16385 (win7_rtm.090713 - 1255)	x 64	ntoskrnl.exe + 71f00	 	 	 	 	C:\Windows\Minidump\012213-80590-01.dmp	4	15	7600	288 016	22/01/2013 04:17:35

  
  010913-49530 - 01.dmp 09/01/2013-08:59:41 IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000'00000004 00000000'00000002 00000000 00000001' fffff800'01cd6ac1 ntoskrnl.exe ntoskrnl.exe 71f00 NT Kernel & system operating system Microsoft® Windows® Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713 - 1255) x 64 ntoskrnl.exe + 71f00 C:\Windows\Minidump\010913-49530-01.dmp 4 15 7600 288 016 09/01/2013 09:09:19
  123112-24804 - 01.dmp 31/12/2012-03:30:02 IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000'00000004 00000000'00000002 00000000'00000001 fffff800'01c9aac1 ntoskrnl.exe ntoskrnl.exe + 71f00 NT kernel & system Microsoft® Windows® operating system Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713 - 1255) x 64 ntoskrnl.exe + 71f00 C:\Windows\Minidump\123112-24804-01.dmp 4 15 7600 288 016 12/31/2012 03:40:34
  120312-43976 - 01.dmp 03/12/2012 01:14:13 IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000'00000004 00000000'00000002 00000000'00000001 fffff800'01aeaac1 ntoskrnl.exe ntoskrnl.exe + 71f00 NT kernel & system Microsoft® Windows® operating system Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713 - 1255) x 64 ntoskrnl.exe + 71f00 C:\Windows\Minidump\120312-43976-01.dmp 4 15 7600 292 144 12/3/2012 01:29:08
  111812-53243 - 01.DMP 18/11/2012-02:07:10 IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000'00000004 00000000'00000002 00000000'00000001 fffff800'0189aac1 ntoskrnl.exe ntoskrnl.exe + 71f00 NT kernel & system Microsoft® Windows® operating system Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713 - 1255) x 64 ntoskrnl.exe + 71f00 C:\Windows\Minidump\111812-53243-01.dmp 4 15 7600 312 816 11/18/2012 02:24:51
  "022912-108171 - 01.dmp 29/02/2012 01:02:50 KERNEL_DATA_INPAGE_ERROR 0x0000007a fffff6fc ' 80613920 ffffffff ' c000009c 00000000' 9853e880 fffff900'c27249f0 ntoskrnl.exe ntoskrnl.exe + 71f00 NT kernel & system Microsoft® Windows® operating system Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713 - 1255) x 64 ntoskrnl.exe + 71f00 C:\Windows\Minidump\022912-108171-01.dmp 4 15 7600 279 248 2/29/2012 01:21:05

  My money is on the patch Microsoft held for the same problem on Windows Server 2008 R2 SP1 or the disk hard diagnosis showing an imminent failure. There is a thread on the issue in the Microsoft Windows Server forums. I have gottten this information for you earlier, but I had to download and reload symbols for my degugger of Windows file run the dump file. You have certainly provided enough dump files.

  Te followning image is one of the minidumps showed me. Alternatively, you can consider running on your hard drive.

  

  View your results.

  Best regards
  ERICO

• Blue screen on HP on HP all-in - One PC Vision

  Hello. For the last week or so my PC all-in-One was bat with a blue screen every time that comes out of hibernation. It seems not serious if it went into hibernate on its own, or through start-> sleep action. The blue screen usually indicates a page KERNEL_DATA_INPAGE_ERROR error.

  I restored my system to attempt to repair. He did, for a while, but today it started again.

  A few web searches made me suspect that it is a manifestation of problems with the fix for Microsoft KB2670838. Other users have reported blue screens after installing (usually as a sine qua non for IE 10), although I have not seem to reports of what happens after a sleep, as it is for me.

  Others hit this kind of problem? Suggestions on solving?

  I intend to uninstall this hotfix, see if it helps. I'll report.

  The number of my all-in-one PC product is

  HP Vision 120-1026

  (Sorry, I wanted to include it).

  I ran the diagnostics twice, but no problems were found with the S.M.A.R.T. tests or anything else; all the past. In addition, the hard drive is not that big by today's standards, just 685GB (not 1 TB or more as suggested the fix).

  I have some good news, however. During the uninstall of the KB2670838 bug fix only made no apparent difference, I managed to solve the problem by using the system restore to restore my system to the first point of restoration, this day here. Thus, it seems that it is triggered by a Microsoft Update, but not pain causes one on other systems.

  I configured my system for manual updates now and will see if I can identify the culprit was updated.

• 8530p blue screen after the awakening of the mode standby.

  Hello.

  Windows 7 Enterprise 32-bit. (EDITED)

  A user has a problem as his computer blue screens after he was awakened to "sleep" mode and the other thing is this problem is intermittent.

  The error message I saw said that it was a KERNEL_DATA_INPAGE_ERROR STOP error message is 0x0000007A and the second parameter was 0xC000009D.

  According to http://msdn.microsoft.com/en-us/library/ff559211 (v = vs. 85) .aspx this type of error indicates - "0xC000009D or STATUS_DEVICE_NOT_CONNECTED, indicates defective wiring or in bulk, termination or that the controller does not see the hard drive."

  Hard disk, I ran the tests integrated in the BIOS, online tool check the system of HP for laptop PC (http://h20239.www2.hp.com/techcenter/HP_SystemCheck/hp_syscheck.htm) and same Seagates own Seatool because there is a Seagate drive in the machine. All these tests said nothing about a problem with the hard drive.

  The online tool, said there is no update available on the BIOS drivers.

  I even had the user to remove the hard drive and put it back to make sure he wasn't a wire loose, bad connection or something like that.

  I phoned helpdesk of HP where I live and I told him this and he said that it is most likely a software problem.

  So so I need help to find out what software might be behind this error.

  I can't provide shocks either, given the error and blue screen also says "dump of physical memory failed with status 0xC0000010.".

  So is it a known software that could be the cause of these problems?

  EDIT: As pointed out by erico, I forgot the information about this operating system. That's why I added this information at the top of my first post.

  Sorry I have not responded earlier.

  It seems that the problem is solved since the user had no blue screens for over a week now.

  The solution was quite simple: reinstall on a new hard drive, even if each test drive, I ran on the subject, said the old drive was ok. This includes BIOS integrated HP and test online, chkdsk in Windows 7 and Seagate tool own Seatool.

  Best regards

  Ljungan.

• I get a blue screen with an error 0x0000007A code.

  Original title: BSOD 0x0000007A ataport.sys

  Salvation to the whole community.

  First of all, I want to say sorry for my English, I'll try to answer as welle as I can! =)
  So here's my problem.
  I got a BSOD when using, or not, my computer. It seems at any time, and I don't know why.
  I took a photo of the blue screen, and I can provide it.
  I tried I tried to uninstall the antivirus software and latest software that I installed it, but the problem is the same. I disconnected the 3 HD and still BSOD.
  The BSOD is:
  KERNEL_DATA_INPAGE_ERROR
  STOP: 0X0000007A (0XFFFFFFFFC000000E, 0X00000000B5F7E860, 0XFFFFF6FC400084E8, 0XFFFFF8800109D93C)
  ataport.sys - address FFFFF8800109D93C base at FFFFF8800107F000 DateStamp 4ce79293
  Data collection for the crashdump...
  Initialization of the disk for the crashdump...
  I installed win7 last Sunday, and the BSOD appears in this week.
  Maybe the drivers GeForce?
  What should I do next?
  PS: I forgot to say: operating system is installed on an SSD. I ran chkdsk and no problems were detected. I have a 1 TB samsung drive too and the 3To WD drive.
  I reinstalled Win7 after a crash of one of my Corsair memory. It works very well for a year before that.
  Thanks for help.

  Ok!

  My computer is running for a few hours with no BSOD more.
  My problem is solved. If the problem was with the Firmware of the SDS for the Crucial M4.
  Thanks for all the help and I hope that will solve all the problems for other users ;)
  Best regards
  Judicaël.
  You can close this topic.

• Blue screen and bad RAM memory?

  My MBP 2011 early all just stopped working yesterday, it worked very well without any problem of performance for the last 5 years, and then suddenly a blue screen (of death) and it has problems starting.

  He will ring the Bell to start, display the bar loading and Apple, and then there will be a glitch on the big screen (horizontally) 1 inch above the Apple, after that, the fans speed up and all that I see a gray screen, not user interface.

  I zapped the PRAM/MSC and tried the unique memory sticks, I have no spare RAM on hand, but who will order soon.

  Tips to solve this problem?

  AHT says this - 65/4MEM/4000000000: 0x84f6f918

  Google says it is bad memory

  Here is the BSoD:

  

  I think you have a problem of memory, although if your MacBook Pro 15 or 17 inch, you should consider video issue as well now.

  http://www.Apple.com/support/MacBookPro-videoissues/

• 10 blue screen on iPhone iOS 5

  I have blue screen in 1-2 seconds on my iPhone 5s by force to restart, then my phone starts as it should and works without any problem. Previous versions of iOS didn't have this bug. What is the problem?

  Same here, I had no problem with ios 9.3.5 just updated to ios 10 with itunes I get the same thing on my iphone 5s and I restore factory default and no luck.