Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD while doing anything, error 0x0000007a

19 Dec 2013   #1
EliBueno

Windows Home Premium 64bit
 
 
BSOD while doing anything, error 0x0000007a

I have been blue screening on my computer for roughly a month, not seriously messing anything up, but the first time it happened my HDD couldn't be loaded, but after that I thought the worst had passed, but it had kept coming over and over again, just annoying me now, but I don't want it to get worse. Here is the crash data:


On Thu 12/19/2013 11:10:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121913-34382-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FB80000000, 0xFFFFFFFFC000000E, 0xAC265880, 0xFFFFF70000000000)
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 check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 12/19/2013 11:10:34 PM GMT 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: 0x7A (0xFFFFF6FB80000000, 0xFFFFFFFFC000000E, 0xAC265880, 0xFFFFF70000000000)
Error: KERNEL_DATA_INPAGE_ERROR
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 12/13/2013 6:22:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121213-55754-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x148760)
Bugcheck code: 0x7A (0xFFFFF6FC4000AB30, 0xFFFFFFFFC000000E, 0xDE88C860, 0xFFFFF88001566760)
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 check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 12/13/2013 2:57:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121213-35552-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8005BEB360, 0xFFFFFA8005BEB640, 0xFFFFF80002FE07B0)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 12/13/2013 2:44:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121213-34710-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FC400494B8, 0xFFFFFFFFC000000E, 0x5C434BE0, 0xFFFFF88009297000)
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 check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 12/5/2013 11:19:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120513-113880-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FB41FFBF70, 0xFFFFFFFFC000000E, 0x633A8884, 0xFFFFF683FF7EEAE0)
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 check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 11/27/2013 7:42:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112713-96408-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xEED18)
Bugcheck code: 0x7A (0xFFFFF6FC4000A940, 0xFFFFFFFFC000000E, 0x35EC8860, 0xFFFFF88001528D18)
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 check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 11/21/2013 8:06:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112113-39078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FC50007868, 0xFFFFFFFFC000000E, 0x4EDCC880, 0xFFFFF8A000F0D080)
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 check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 11/28/2012 8:55:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112812-52915-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002AE4F74)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 11/13/2012 3:07:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111212-51027-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7A1C)
Bugcheck code: 0x116 (0xFFFFFA8005EAC4E0, 0xFFFFF88004007A1C, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR



Conclusion

10 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


My System SpecsSystem Spec
.
19 Dec 2013   #2
Brink

64-bit Windows 10 Pro
 
 

Hey EliBueno, and welcome to Seven Forums.

Please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions, and post back with the needed information. One of our BSOD experts should be by later when able to further help.
My System SpecsSystem Spec
20 Dec 2013   #3
EliBueno

Windows Home Premium 64bit
 
 

Here are the files
My System SpecsSystem Spec
.

Reply

 BSOD while doing anything, error 0x0000007a




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD while out - Error: 0x0000007a
Hi all and welcome to my first post. Having never received a blue screen (officially known as stop errors) before on my current machine, I came back to my computer after being out and discovered an stop error had occurred. The error/bug check code is 0x0000007a (kernal data inpage error). ...
BSOD Help and Support
BSOD working PC sometime, error 0x0000007a
0x0000007a (0xfffff6fb40000038, 0xffffffffc000000e, 0x0000000052872884, 0xfffff68000007000).
BSOD Help and Support
BSOD error 0X0000007A
Hello, I just got my first BSOD today. And now it happens every hour or so. I'm not sure what to do. I have all the necessary files attached, I believe. Thank you for any help you can give.
BSOD Help and Support
KSOD error before Login Screen then BSOD, error 0x0000007A
Hi 2 days ago I turned my computer on and I was logging in as normal. It finished doing the 'starting windows sequence' and then the screen turned black, with a cursor. I waited then the BSOD came up. ALSO the KSOD comes up in the Safe Mode as well.I spam f8 and I have tried everything.The most...
BSOD Help and Support
Occasional BSOD, last error was 0x0000007A
I have been experiencing BSOD occasionally since I bought my laptop just over a year ago. I have tried a few things (updates, disk check, memory diagnosis) but the problem persists. There doesn't appear to be any obvious reason why it crashes, sometimes it happens when I'm playing a video or music...
BSOD Help and Support
BSOD doing nothing, error 0x0000007A
I was just dozing off since it was late and when i woke up to turn off my rig it gave me this BSOD. I googled the problem and most says its caused by bad sectors. One of my HDD monitoring software says it has 1 bad sector. I've run memtest before for 16 hours+ and it gave me no error so it's...
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 06:06.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App