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

BSODs, Nonworking Malware Tools, and Other Fun Things


  • Please log in to reply
3 replies to this topic

#1 Alphonse509

Alphonse509

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:07:47 PM

Posted 14 July 2012 - 11:01 PM

A few days ago, I had expanded my Windows 7 partition after removing an old Linux installation on my laptop. Then after all was settled, ran a disk defrag using Auslogic's tool. Everything seemed swell. Skip forward a few days of me not being home, my computer is very sluggish, freezes and locks up constantly, and often results in the need to do a force shut down. Thinking it might be malware, I boot into Safe Mode and try to run MBAM. This ends up locking up and never making it past the first stages of the scan after multiple attempts. I also notice in Safe Mode and it Normal boot that Microsoft Security Essentials is having an issue starting its process, thus rendering it useless. Red flag. Throughout some of these attempts, I also got a few BSODs. (have file from BlueScreen View) At this point I'm completely uncertain what to do. I ran the Windows Memory Diagnostic and after many failures, finally got Disk Check to run and do it's thing. Any further suggestions?

==================================================
Dump File         : 071412-20560-01.dmp
Crash Time        : 7/14/2012 9:25:33 PM
Bug Check String  : KERNEL_DATA_INPAGE_ERROR
Bug Check Code    : 0x0000007a
Parameter 1       : fffff6fc`00017260
Parameter 2       : ffffffff`c0000185
Parameter 3       : 00000000`3d238860
Parameter 4       : fffff800`02e4c000
Caused By Driver  : hal.dll
Caused By Address : hal.dll+33000
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+70700
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\071412-20560-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 282,384
==================================================

==================================================
Dump File         : 071412-17846-01.dmp
Crash Time        : 7/14/2012 8:53:23 PM
Bug Check String  : KERNEL_DATA_INPAGE_ERROR
Bug Check Code    : 0x0000007a
Parameter 1       : fffff6fc`80611f80
Parameter 2       : ffffffff`c0000185
Parameter 3       : 00000000`46063880
Parameter 4       : fffff900`c23f0d8c
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70700
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16792 (win7_gdr.110408-1633)
Processor         : x64
Crash Address     : ntoskrnl.exe+70700
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\071412-17846-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 282,384
==================================================

==================================================
Dump File         : 071412-24445-01.dmp
Crash Time        : 7/14/2012 12:47:24 PM
Bug Check String  : KERNEL_DATA_INPAGE_ERROR
Bug Check Code    : 0x0000007a
Parameter 1       : fffff6fb`800083f8
Parameter 2       : ffffffff`c0000185
Parameter 3       : 00000000`59c3b880
Parameter 4       : fffff700`0107fff8
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70700
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16792 (win7_gdr.110408-1633)
Processor         : x64
Crash Address     : ntoskrnl.exe+70700
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\071412-24445-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 282,384
==================================================

Edited by Alphonse509, 14 July 2012 - 11:07 PM.


BC AdBot (Login to Remove)

 


#2 AustrAlien

AustrAlien

    Inquisitor


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

Posted 15 July 2012 - 01:54 AM

You are likely to be facing a hard drive issue.

Test the hard drive.

It is best to use the hard drive manufacturer's own diagnostic utility, but Seagate's tool will work OK on most brands. The diagnostic tool is run from a bootable CD (Windows does not need to be working. The first two steps are done on a working computer, while the third step is to boot the ailing computer with the CD that you create in the first two steps.)

:step1: Please download SeaTools for DOS (CD) from Seagate's SeaTools for DOS web page

or use the following direct download link to download the latest version of SeaTools for DOS:
Download SeaTools for DOS ISO Image

The downloaded file name is SeaToolsDOS223ALL.ISO
[/list]
:step2: Burn the downloaded .ISO image to a CD using the appropriate burning software.
  • If you do not already have a suitable burning program for writing .ISO images to disc ...
    • Download and install ImgBurn.
      Ensure that you UN-check the box agreeing to install the Ask toolbar during the installation.
    • Place a new (blank) CD disc in the drive tray.
    • Choose Write image file to disc.
    • Under Source, click on the Browse button: Navigate to and select the .ISO file that you wish to burn.
    • Place a check-mark in the box beside Verify.
  • Click Posted Image

    When the CD has been burned and verified as successful, it will be bootable.

:step3: Boot from the CD.
  • (You may need to access the BIOS Setup Menu or the Boot Menu and change the boot order to enable booting from CD before hard drive.)
  • From Basic tests on the Main Menu, run the Short test and then the Long test.

    (The long test will take some considerable time to complete.)
    The results will be shown as either a PASS or FAIL.
    There is a chance that during the Long test, you may be offered the opportunity to attempt repairs on the hard drive:
  • If so, go ahead and attempt to do so, but ONLY after backing up all important personal files.
[/list]Note: You may wish to view the following ...
Please let us know the results of the tests.

When you can, include the make and model number of the problematic hard drive. If you do choose to use SeaTools, you will see the model number (and maybe the make) when SeaTools first detects the hard drive.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#3 Alphonse509

Alphonse509
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:07:47 PM

Posted 15 July 2012 - 07:55 PM

I ran SeaTools and the drive failed both tests. However, when I run the long test, the test stops at around 7% or when it reaches 99 errors and then a window appears informing me of the possibility to send in the hard drive, then it runs a Short Test and offers to fix the errors it found. It fixes the errors it find in that scan, but it finds more and more each time I run it. Obviously, if my drive is this badly screwed, this will not be an efficient way to fix it. I still don't know what initially caused this, and what I can do to fix it. Will I just need a new drive?

EDIT: The second link you have for the SeaTools documentation is not broken, but redirects to the new Seagate Knowledgebase, thus not showing the documentation.

Edited by Alphonse509, 15 July 2012 - 07:57 PM.


#4 AustrAlien

AustrAlien

    Inquisitor


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

Posted 16 July 2012 - 12:24 AM

Will I just need a new drive?

Yes, you will need to replace the hard drive, almost certainly. However, I suggest that before doing that, we investigate a little further (see below)

:exclame: Backup your important personal files to a physically separate device now! :exclame:

If you wish, we could have a look at the S.M.A.R.T data to get a better idea of what might be going on.
Please Publish a Snapshot using Speccy, and post a link to it in this thread.

This is a convenient and accurate way of providing us with details of your computer specifications, including the S.M.A.R.T data values.
We could also have a look at the chkdsk (Check Disk/Disk Check) log(s).
A log of the disk check is recorded only if the scheduled re-start is used, and only for drives on the same HDD as the Operating System.
To open Event Viewer and view the log:
  • Go to Start > and type eventvwr and press the <ENTER> key.
    The Event Viewer window will open.
  • In the left pane, expand "Windows Logs" and then click on Application.
  • In the right pane, at the top, click on the column heading Source to sort the list alphabetically.
  • Look in the Source column for "Wininit", with an entry corresponding to the date and time of the disk check.
  • Click on that Wininit entry to select it.
  • On the top main menu, click Action > Copy > Copy Details as Text.
  • Paste the text of all recent logs into your next reply.
=========================
Edit to add: Thank you for pointing out an issue with one of the links used.

Comment on BSOD info included in your first post:

Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 2 : ffffffff`c0000185

This is reporting the issue quite specifically:

Frequently, you can determine the cause of the KERNEL_DATA_INPAGE_ERROR bug check from the error status (Parameter 2).
Some common status codes include the following:
0xC0000185, or STATUS_IO_DEVICE_ERROR

Reference: STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR

Edited by AustrAlien, 16 July 2012 - 04:43 AM.

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