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

Help with diagnosis!


  • Please log in to reply
20 replies to this topic

#1 Del64

Del64

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:09:54 PM

Posted 21 July 2012 - 03:44 PM

Hello,

My home pc is not taken care of very well since I go to school, and every time I return something is broken. There were a few BSoDs my family complained about but then I realized they blew the video card and I am forced to use the integrated inputs on the motherboard.

It seemed to work for a while, however after a bit of use I received a BSoD stating 0x00000024. I restarted and then I received the BSoD 0x00000050. I read around about memory errors however, I am pretty sure I checked the ram and it stated to be healthy still. I ran multiple check disks, re-installed windows. I am at a loss with this pc.

Is there anything I should do to help determine if its hardware or software?

BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:10:54 PM

Posted 21 July 2012 - 03:46 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 Del64

Del64
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:09:54 PM

Posted 21 July 2012 - 03:53 PM

==================================================
Dump File : 072112-19328-01.dmp
Crash Time : 7/21/2012 4:49:40 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff100`0135094c
Parameter 2 : 00000000`00000001
Parameter 3 : fffff880`03a6f5dd
Parameter 4 : 00000000`00000007
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+5af3
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\072112-19328-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 266,688
==================================================

==================================================
Dump File : 062612-59186-01.dmp
Crash Time : 6/26/2012 3:31:39 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`02bdff92
Parameter 3 : fffff880`0461ad60
Parameter 4 : 00000000`00000000
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+97e65
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\062612-59186-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 280,992
==================================================

==================================================
Dump File : 062212-33415-01.dmp
Crash Time : 6/22/2012 11:35:52 AM
Bug Check String : APC_INDEX_MISMATCH
Bug Check Code : 0x00000001
Parameter 1 : 00000000`76ec14aa
Parameter 2 : 00000000`00000008
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`054f9ca0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\062212-33415-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 279,640
==================================================

==================================================
Dump File : 062112-86206-01.dmp
Crash Time : 6/21/2012 10:47:00 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000096
Parameter 2 : fffff800`028e4414
Parameter 3 : fffff880`02a21f90
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\062112-86206-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 279,696
==================================================

==================================================
Dump File : 053112-40263-01.dmp
Crash Time : 5/31/2012 4:35:31 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00005003
Parameter 2 : fffff700`01080000
Parameter 3 : 00000000`000107b0
Parameter 4 : 00010846`00020f68
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\053112-40263-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 281,232
==================================================

#4 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:10:54 PM

Posted 21 July 2012 - 04:00 PM

Let's run a diagnostic on your installed memory. 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.

#5 Del64

Del64
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:09:54 PM

Posted 21 July 2012 - 04:09 PM

Will an ubuntu cd and or UBCD suffice for this test?

#6 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:10:54 PM

Posted 21 July 2012 - 04:12 PM

Please follow the instructions in my post. Thanks.

#7 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:12:54 PM

Posted 21 July 2012 - 04:43 PM

Will an ubuntu cd ... suffice for this test?

Yes, in a word.

memtest86+ is included on the Ubuntu bootable CD, and can be run from there no differently than it would be if burning a separate bootable CD.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#8 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:10:54 PM

Posted 21 July 2012 - 04:46 PM


Will an ubuntu cd ... suffice for this test?

Yes, in a word.

memtest86+ is included on the Ubuntu bootable CD


Wasn't aware of that - thanks for the assist.

#9 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:12:54 PM

Posted 21 July 2012 - 04:51 PM

My pleasure, Allan

... I received a BSoD stating 0x00000024.

That reported error message (along with the fact that it is not showing in the BSV report) concerns me:
  • It indicates that the hard drive may be having a problem of some sort.

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

Posted Image

#10 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:10:54 PM

Posted 21 July 2012 - 05:00 PM

Yes, but the errors are all over the place and can be anything from ram to hd to malware to a failing mobo or cpu. I'm actually guessing the ram will pass - just want to rule it out. But I'll tell you what AustrAlien, you're better at hardware than I am so if you're comfortable jumping in that's absolutely fine with me.

#11 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:12:54 PM

Posted 21 July 2012 - 05:10 PM

Testing the RAM firstly is appropriate, I think; as you say, "the errors are all over the place".

I thought it might help if I pointed out something that might easily be overlooked ... especially since a STOP 0x24 error was not showing in the BSV report.

Good luck ... and thanks, but I'll just watch ... unless I can be of any assistance.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#12 Del64

Del64
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:09:54 PM

Posted 22 July 2012 - 12:49 AM

I let the test go on for a few hours since I had to go somewhere. Test came back clean with no errors.

#13 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:12:54 PM

Posted 22 July 2012 - 12:55 AM

Test came back clean with no errors.

That's a good start: However, for the result to be at all reliable when no errors are being found, it needs to run for at least 24 hours. Please test the hard drive now.

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

#14 Del64

Del64
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:09:54 PM

Posted 22 July 2012 - 01:17 AM

I unfortunately do not have the time to try this since I am only here on the weekend, however I did run a vivard scan which checked the sectors of the hard drive. The test also came back clean. I will try what you suggested come next weekend.

#15 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:12:54 PM

Posted 22 July 2012 - 01:20 AM

That could be good: However without knowing the details (for example of whether or not you ran a long/extended test) I cannot say. Nevertheless, it is a good start. Perhaps the problem does not lie with either RAM or HDD?

If you wish we can post some more instructions that will enable us to learn more ... for next time you can get "at it". Let me know if you would like me to do that.
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