Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

STOP error 7A


  • Please log in to reply
12 replies to this topic

#1 Train2104

Train2104

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:12:06 AM

Posted 03 July 2011 - 04:34 PM

Running multiple applications at once, especially Firefox + Explorer + Outlook + Acrobat, or using Outlook immediately after the computer resumes from hibernation without waiting a few minutes, usually leads to this error.

First, all the applications stop responding one by one. Then the taskbar no longer responds to mouseovers. Then the mouse stops moving, and the STOP error occurs after a couple of seconds.

KERNEL_DATA_INPAGE_ERROR, 0x7A, Windows 7 x64 Home Premium SP1, Dell Inspiron 1564, Core i3, 4GB RAM.

It's only started happening recently, perhaps caused by the Acrobat 10.1 update. Does anyone know what's going on?

BlueScreenView provides the following report (this is one, several more have happened before but CCleaner removed the dumps):

==================================================
Dump File : 070311-34023-01.dmp
Crash Time : 7/3/2011 5:00:28 PM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : fffff6fc`5002cda0
Parameter 2 : ffffffff`c0000185
Parameter 3 : 00000000`173f4880
Parameter 4 : fffff8a0`059b4000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7fd00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17592 (win7sp1_gdr.110408-1631)
Processor : x64
Crash Address : ntoskrnl.exe+7fd00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070311-34023-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 283,080
==================================================

Edited by Train2104, 03 July 2011 - 04:37 PM.


BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,562 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:06 AM

Posted 03 July 2011 - 04:36 PM

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

#3 Train2104

Train2104
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:12:06 AM

Posted 03 July 2011 - 04:38 PM

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply


Did that before I saw your post.

#4 Allan

Allan

  • BC Advisor
  • 8,562 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:06 AM

Posted 03 July 2011 - 04:43 PM

1) Let's start with checkdisk. To run checkdisk, right-click on a command prompt icon and open as administrator. In the command prompt window type: chkdsk /r (then press ENTER). You'll be told the disk is in use and asked if you want to run checkdisk on the next boot. Say yes, exit the command prompt window, and reboot.

2) Also, I suggest you do the following in order

* Disable the pagefile
* Reboot
* Run a disc defrag
* Reset the pagefile to system managed
* Reboot

Edited by Allan, 03 July 2011 - 04:44 PM.


#5 Train2104

Train2104
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:12:06 AM

Posted 03 July 2011 - 06:23 PM

1) Let's start with checkdisk. To run checkdisk, right-click on a command prompt icon and open as administrator. In the command prompt window type: chkdsk /r (then press ENTER). You'll be told the disk is in use and asked if you want to run checkdisk on the next boot. Say yes, exit the command prompt window, and reboot.

2) Also, I suggest you do the following in order

* Disable the pagefile
* Reboot
* Run a disc defrag
* Reset the pagefile to system managed
* Reboot


First part is done.

As for the second part:

-I am using Diskeeper, which replaces Microsoft's defrag, should I use it?
-How do you disable the pagefile?

#6 Allan

Allan

  • BC Advisor
  • 8,562 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:06 AM

Posted 04 July 2011 - 06:16 AM

Sure, diskkeeper is fine.

Go to System Properties - Advanced Tab - Performance Button - Advanced Tab (again) - Change button (under Virtual Memory) - click on the drive where the pagefile is and put a tick in "no pagefile". Apply - OK your way out - reboot. Afterward the defrag, go back and reset it to "system managed".

#7 Train2104

Train2104
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:12:06 AM

Posted 04 July 2011 - 09:41 AM

Sure, diskkeeper is fine.

Go to System Properties - Advanced Tab - Performance Button - Advanced Tab (again) - Change button (under Virtual Memory) - click on the drive where the pagefile is and put a tick in "no pagefile". Apply - OK your way out - reboot. Afterward the defrag, go back and reset it to "system managed".


Done. Diskeeper apparently couldn't defrag the USN Journal (\$Extend\$UsnJrnl), with 34 fragments and a size of 5,664 MB.

#8 Train2104

Train2104
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:12:06 AM

Posted 05 July 2011 - 07:33 AM

It happened again. This is the sequence of events:

-Resume
-Outlook (already open) downloads emails
-I read one and click on a link
-I launch Windows Explorer
-Firefox opens with the link
-I open a new tab+open my homepage
-Firefox becomes unresponsive
-The Windows Explorer that I launched finally opens, locked up.
-System crashes.

==================================================
Dump File : 070511-21902-01.dmp
Crash Time : 7/5/2011 8:27:23 AM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : fffff6fc`40009a10
Parameter 2 : ffffffff`c0000185
Parameter 3 : 00000000`8a21c860
Parameter 4 : fffff880`01342d40
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+eed40
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7fd00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070511-21902-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 283,080
==================================================

Edited by Train2104, 05 July 2011 - 07:33 AM.


#9 Allan

Allan

  • BC Advisor
  • 8,562 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:06 AM

Posted 05 July 2011 - 08:00 AM

Okay. Next step is to test ram. To check the ram, download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

#10 Train2104

Train2104
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:12:06 AM

Posted 05 July 2011 - 08:48 PM

Okay. Next step is to test ram. To check the ram, download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.


I let the test run once (about 30 minutes), then I pressed ESC when it began its second (seemingly repeat) test. I'll reply again if another crash occurs. It seems to have something to do with hibernation, as it never crashes if I open Outlook immediately after a full boot.

Maybe reset the hibernation file?

Edited by Train2104, 05 July 2011 - 08:48 PM.


#11 Allan

Allan

  • BC Advisor
  • 8,562 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:06 AM

Posted 06 July 2011 - 05:40 AM

Just stop using hibernation - it causes problems on some systems. Instead, set the display and hd to power down after a defined period of inactivity in Power Options.

#12 Train2104

Train2104
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:12:06 AM

Posted 06 July 2011 - 03:01 PM

Just stop using hibernation - it causes problems on some systems. Instead, set the display and hd to power down after a defined period of inactivity in Power Options.


That unfortunately is the last, last resort. The computer must physically be off when I'm not using it, rather than dumping heat into the room. So if I must not use hibernation, it would mean full restarts all the time. That may be better for the system, but pretty time consuming.

Plus, this is a laptop, which usually supports hibernation. I've done it for a year with no problems.

#13 Train2104

Train2104
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:12:06 AM

Posted 14 July 2011 - 11:26 AM

Haven't had a crash since after disabling and re-enabling hibernation. I guess the file was corrupt.

Some lockups, but they resolve themselves in a few minutes.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users