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

IE 9 Appcrash with Windows 7 Pro


  • Please log in to reply
54 replies to this topic

#16 LucheLibre

LucheLibre

  • Members
  • 608 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Tennessee
  • Local time:06:26 PM

Posted 01 March 2012 - 09:54 AM

Click the start orb, type in cmd. When it appears in the start menu, right-click it and select Run as administrator. Then type in the commands.

If it looks like I know what I'm doing, there's a pretty good chance the only reason for that is because
I once asked someone to run chkdsk /r and a BC Advisor smacked me in the back of the head.

~ LL ~


BC AdBot (Login to Remove)

 


#17 valerie586

valerie586
  • Topic Starter

  • Members
  • 78 posts
  • OFFLINE
  •  
  • Local time:04:26 PM

Posted 01 March 2012 - 02:28 PM

I typed in cmd and the black dos window comes up....not sure what I'm supposed to do after that. I don't see anything new in the start menu to right click.

#18 LucheLibre

LucheLibre

  • Members
  • 608 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Tennessee
  • Local time:06:26 PM

Posted 01 March 2012 - 02:32 PM

Try this instead:

Click the Start Orb and type cmd. Then hold down both Ctrl and Shift and press Enter. At the prompt, type in the two commands I gave you earlier in the thread.

If it looks like I know what I'm doing, there's a pretty good chance the only reason for that is because
I once asked someone to run chkdsk /r and a BC Advisor smacked me in the back of the head.

~ LL ~


#19 valerie586

valerie586
  • Topic Starter

  • Members
  • 78 posts
  • OFFLINE
  •  
  • Local time:04:26 PM

Posted 01 March 2012 - 07:34 PM

Notepad opened after the commands, but it is blank/empty.

#20 valerie586

valerie586
  • Topic Starter

  • Members
  • 78 posts
  • OFFLINE
  •  
  • Local time:04:26 PM

Posted 01 March 2012 - 07:48 PM

I was able to do the original request - cmd and right-click, run as administrator....still access is denied to the CBS text file.

#21 valerie586

valerie586
  • Topic Starter

  • Members
  • 78 posts
  • OFFLINE
  •  
  • Local time:04:26 PM

Posted 01 March 2012 - 08:21 PM

Not sure if this is related, but since I ran the cmd, right-click, run as administrator.....now the computer freezes whenever I right-click on anything in explorer...tried it 7 times, had to re-boot each time....still freezes.

#22 LucheLibre

LucheLibre

  • Members
  • 608 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Tennessee
  • Local time:06:26 PM

Posted 02 March 2012 - 01:06 PM

Thanks to some excellent help from AustrAlien, the next step is to test your hard drive.

  • Backup all important files first!
  • "Safely Remove" and disconnect any external drives.
  • Shut the computer down, open the case, and reseat the data and power cables to the hard drive.

Use SeaTools for DOS to perform diagnostics on your hard drive.

  • You will need:
    • A new blank CD (CD-R) or a re-writable CD (CD-RW).
    • A User Guide is available for more information.
  • If you haven't already, include your computer's manufacturer and model number in your next reply.
  • Using a working computer, download SeaTools for DOS.
  • Burn the .ISO image file to a CD.
    Follow these instructions if you are not familiar with burning an .ISO image file to disc.
  • Boot the affected computer from the CD.
    You may need to configure the BIOS or use the Boot Menu to boot first from the CD.
  • Write down the Model ID of your hard drive as reported by SeaTools.
  • From the Basic menu, run the Short Test. If it passes, run the Long Test.
    Be patient as the Long Test can take over an hour.
    • If SeaTools offers you the option to attempt repairs and your backups are current, accept it. If SeaTools cannot repair the damage, it will show an error code.
  • Include in your next reply:
    • Test results (PASS or FAIL)
    • Error codes
    • Model ID

=====================================================

If it looks like I know what I'm doing, there's a pretty good chance the only reason for that is because
I once asked someone to run chkdsk /r and a BC Advisor smacked me in the back of the head.

~ LL ~


#23 valerie586

valerie586
  • Topic Starter

  • Members
  • 78 posts
  • OFFLINE
  •  
  • Local time:04:26 PM

Posted 02 March 2012 - 07:32 PM

Ok, I don't know how to "create an ISO image" to burn to a disc. Where is the ISO image?

#24 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:08:26 AM

Posted 02 March 2012 - 07:35 PM

The download link in LL's above post is a direct download link to the SeaTools .ISO file. When you click on the link, the download window should open for you to click on ...

Edit: You don't create the .ISO ... you download it, and then burn it to a CD on the proper manner, as per the instructions in the link provided by LL.

Edited by AustrAlien, 02 March 2012 - 07:38 PM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#25 valerie586

valerie586
  • Topic Starter

  • Members
  • 78 posts
  • OFFLINE
  •  
  • Local time:04:26 PM

Posted 02 March 2012 - 07:44 PM

I have a program called Acronis, does that create the ISO image?

#26 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:08:26 AM

Posted 02 March 2012 - 07:48 PM

No ... as I posted in my edit above, you don't create the .ISO file, you download it.

Click on the following link to download SeaToolsDOS223ALL.ISO <<< this is the name of the file you will download

Edit to add: BSOD BUGCHECK SUMMARY
................................................................
Loading Dump File [C:\CactusIsland\valerie586_BC\Windows7_Vista_jcgriff2\022812-31543-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Feb 29 13:46:05.145 2012 (UTC + 11:00)
System Uptime: 0 days 2:27:32.002
Probably caused by : Ntfs.sys ( Ntfs!NtfsTeardownStructures+77 )
NTFS_FILE_SYSTEM (24)
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
BUGCHECK_STR: 0x24
FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsTeardownStructures+77
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`06f0c548 fffff880`06f0bda0 fffff880`012925e7
BiosVersion = A03
BiosReleaseDate = 07/23/2007
SystemProductName = Latitude D630
CPUID: "Intel® Core™2 Duo CPU T7300 @ 2.00GHz"
MaxSpeed: 2000
CurrentSpeed: 1995
................................................................
Loading Dump File [C:\CactusIsland\valerie586_BC\Windows7_Vista_jcgriff2\022812-24835-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Feb 29 17:42:34.274 2012 (UTC + 11:00)
System Uptime: 0 days 3:51:46.006
Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+86 )
IRQL_NOT_LESS_OR_EQUAL (a)
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86
Bugcheck code 0000000A
Arguments fffffa80`23d280c0 00000000`00000002 00000000`00000001 fffff800`02b97fe6
................................................................
Loading Dump File [C:\CactusIsland\valerie586_BC\Windows7_Vista_jcgriff2\022712-24133-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Feb 28 15:54:50.967 2012 (UTC + 11:00)
System Uptime: 0 days 2:41:45.825
Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+86 )
IRQL_NOT_LESS_OR_EQUAL (a)
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86
Bugcheck code 0000000A
Arguments fffffa80`23a01040 00000000`00000002 00000000`00000001 fffff800`02b39fe6
................................................................
Loading Dump File [C:\CactusIsland\valerie586_BC\Windows7_Vista_jcgriff2\022612-23244-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Feb 27 10:59:58.106 2012 (UTC + 11:00)
System Uptime: 0 days 0:01:01.963
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2a80f )
MEMORY_MANAGEMENT (1a)
BUGCHECK_STR: 0x1a_5003
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2a80f
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff781`c0000000 00000000`0000783e 00007837`00000000
................................................................
Loading Dump File [C:\CactusIsland\valerie586_BC\Windows7_Vista_jcgriff2\022212-89981-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Feb 23 13:09:51.117 2012 (UTC + 11:00)
System Uptime: 0 days 0:00:15.974
Probably caused by : win32k.sys ( win32k!GreExtTextOutWLocked+1d0d )
SYSTEM_SERVICE_EXCEPTION (3b)
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: winlogon.exe
FAILURE_BUCKET_ID: X64_0x3B_win32k!GreExtTextOutWLocked+1d0d
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`00033ffd fffff880`05210d70 00000000`00000000
................................................................
Loading Dump File [C:\CactusIsland\valerie586_BC\Windows7_Vista_jcgriff2\022112-23150-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Feb 22 03:37:27.123 2012 (UTC + 11:00)
System Uptime: 0 days 0:00:21.964
Probably caused by : win32k.sys ( win32k!DrvProbeAndCaptureDevmode+f7a )
SYSTEM_SERVICE_EXCEPTION (3b)
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: csrss.exe
FAILURE_BUCKET_ID: X64_0x3B_win32k!DrvProbeAndCaptureDevmode+f7a
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`0005effe fffff880`05de87e0 00000000`00000000
................................................................
Loading Dump File [C:\CactusIsland\valerie586_BC\Windows7_Vista_jcgriff2\022012-25942-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Feb 21 01:53:15.308 2012 (UTC + 11:00)
System Uptime: 0 days 0:00:23.166
Probably caused by : memory_corruption
SYSTEM_SERVICE_EXCEPTION (3b)
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x3B
PROCESS_NAME: csrss.exe
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`0012c000 fffff880`05adcd30 00000000`00000000
................................................................
Loading Dump File [C:\CactusIsland\valerie586_BC\Windows7_Vista_jcgriff2\022012-25162-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Feb 21 01:54:56.638 2012 (UTC + 11:00)
System Uptime: 0 days 0:00:41.496
Probably caused by : memory_corruption
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: csrss.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
BUGCHECK_STR: 0x7E
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff960`001a4001 fffff880`031c7868 fffff880`031c70c0
................................................................
Loading Dump File [C:\CactusIsland\valerie586_BC\Windows7_Vista_jcgriff2\021812-45552-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Feb 19 07:57:04.666 2012 (UTC + 11:00)
System Uptime: 0 days 0:00:43.524
Probably caused by : memory_corruption
SYSTEM_SERVICE_EXCEPTION (3b)
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x3B
PROCESS_NAME: csrss.exe
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`000a6001 fffff880`03a24e40 00000000`00000000
................................................................
Loading Dump File [C:\CactusIsland\valerie586_BC\Windows7_Vista_jcgriff2\020212-21481-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Feb 2 14:44:48.934 2012 (UTC + 11:00)
System Uptime: 0 days 0:21:58.165
Unable to load image \SystemRoot\system32\DRIVERS\tdrpm251.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tdrpm251.sys
*** ERROR: Module load completed but symbols could not be loaded for tdrpm251.sys
Probably caused by : tdrpm251.sys ( tdrpm251+4c72e )
IRQL_NOT_LESS_OR_EQUAL (a)
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xA_tdrpm251+4c72e
Bugcheck code 0000000A
Arguments fffffa80`23409030 00000000`00000002 00000000`00000001 fffff800`02b36fe6
BiosVersion = A03
BiosReleaseDate = 07/23/2007
SystemManufacturer = Dell Inc.
SystemProductName = Latitude D630
CPUID: "Intel® Core™2 Duo CPU T7300 @ 2.00GHz"
MaxSpeed: 2000
CurrentSpeed: 1995
................................................................

Edited by AustrAlien, 02 March 2012 - 08:49 PM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#27 valerie586

valerie586
  • Topic Starter

  • Members
  • 78 posts
  • OFFLINE
  •  
  • Local time:04:26 PM

Posted 02 March 2012 - 11:17 PM

Passed both the Short Test and Long Test.

Model ID: ST980811AS

Am I supposed to do anything with the BSOD Summary posted above?

#28 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:08:26 AM

Posted 02 March 2012 - 11:31 PM

Am I supposed to do anything with the BSOD Summary posted above?

No, that is simply a record of the analysis of your minidump files for reference.

Very good result on the hard drive. Well done!

How did you go with the task of disconnecting and then reconnecting firmly, the internal hard drive of the laptop? The System event log was showing an indication of a possible problem with the connection in the form of numerous "The driver detected a controller error on \Device\Harddisk1\DR1." errors. We are trying to eliminate this as a possible source of the file corruption on the laptop's hard drive.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#29 valerie586

valerie586
  • Topic Starter

  • Members
  • 78 posts
  • OFFLINE
  •  
  • Local time:04:26 PM

Posted 03 March 2012 - 12:19 AM

I haven't done anything with the hard drive. I know I can take out the hard drive and put it back in very easily, however, I'm a little leary about removing the bottom cover off the computer. Last time I did that with a D620, I couldn't reseat it completely, now the screen doesn't work.

Do I need to do more than take the hard drive out and put it back in?

#30 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:08:26 AM

Posted 03 March 2012 - 12:32 AM

We need to confirm that the connection to the hard drive is good ... because the repeated error in the log "The driver detected a controller error on \Device\Harddisk1\DR1." indicates that it may not be good. The only realistic way we can do that is to unplug the hard drive, and re-plug it back in, ensuring the connection is fully and firmly seated. There is little else that we can do to confirm the connection is good.

Therefore, all you need to is to carefully unplug the hard drive, and then plug it back in carefully, ensuring that the connection is good.

If you are at all concerned that you may not be able to do that (and remove/replace the cover), without causing a problem, perhaps we had better consult DELL's documentation for the instructions on how to do it ... because I am not familiar with that particular machine.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users