System Recovered From a Serious Error

Anonymous
2013-02-08T02:49:55+00:00

I had the a similar problem about a month ago

http://answers.microsoft.com/en-us/windows/forum/windows\_xp-system/the-system-has-recovered-from-a-serious-error/da1629fc-32e0-4737-a5ff-63bf6003ddb2?page=1&tab=AllReplies

Thought it was fixed with all the great help I got here, but a day or so ago I rebooted and chkdsc came on without me scheduling it, then this morning I found my computer had crashed during the night ..

here's some Info-

Win XP Home 2002 SP III

Computer is getting old, Inter (R) Pentium 4CPU 240 GHz, 1.5 GB Ram

I Mainly use FFox

No idea about IDE drives or SATA drives

I have Avast free and Win Firewall

I have a CD and DVD but hardly ever use them

I don't know if I have a genuine bootable XP installation CD

Computer boots fairly well and fast

here's my System Summary-

OS Name    Microsoft Windows XP Home Edition

Version    5.1.2600 Service Pack 3 Build 2600

OS Manufacturer    Microsoft Corporation

System Name   

System Manufacturer    Dell Computer Corporation

System Model    Dimension 4600

System Type    X86-based PC

Processor    x86 Family 15 Model 2 Stepping 7 GenuineIntel ~2394 Mhz

BIOS Version/Date    Dell Computer Corporation A07, 11/6/2003

SMBIOS Version    2.3

Windows Directory    C:\windows

System Directory    C:\windows\system32

Boot Device    \Device\HarddiskVolume1

Locale    United States

Hardware Abstraction Layer    Version = "5.1.2600.5512 (xpsp.080413-2111)"

User Name   

Time Zone    Pacific Standard Time

Total Physical Memory    1,536.00 MB

Available Physical Memory    653.13 MB

Total Virtual Memory    2.00 GB

Available Virtual Memory    1.96 GB

Page File Space    3.35 GB

Page File    C:\pagefile.sys

My Display Info-

Name    NVIDIA GeForce FX 5200

PNP Device ID    PCI\VEN_10DE&DEV_0322&SUBSYS_80DF1043&REV_A1\4&1246FE7B&0&0008

Adapter Type    GeForce FX 5200, NVIDIA compatible

Adapter Description    NVIDIA GeForce FX 5200

Adapter RAM    128.00 MB (134,217,728 bytes)

Installed Drivers    nv4_disp.dll

Driver Version    6.14.11.7519

INF File    oem36.inf (nv4_NV3x section)

Color Planes    1

Color Table Entries    4294967296

Resolution    1024 x 768 x 60 hertz

Bits/Pixel    32

Memory Address    0xFD000000-0xFEAFFFFF

Memory Address    0xF0000000-0xF7FFFFFF

IRQ Channel    IRQ 16

I/O Port    0x000003B0-0x000003BB

I/O Port    0x000003C0-0x000003DF

Memory Address    0xA0000-0xBFFFF

Driver    c:\windows\system32\drivers\nv4_mini.sys (6.14.11.7519, 6.25 MB (6,557,408 bytes), 8/3/2004 10:29 PM)

I've been doing MalwareByte and SASpyware scans,

here's my Dump File https://skydrive.live.com/redir?resid=5E9161E0412D6528!164&authkey=!AJ38-Yq\_Q0SoGyY

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

43 answers

Sort by: Newest
  1. Anonymous
    2013-02-08T23:51:19+00:00

    From the crash dump, is says this might somehow be involved:

    PROCESS_NAME:  wmpnetwk.exe

    Can you tell me where you are seeing the above? I use WhoCrashed and BlueScreenView and neither of them indicated anything about Windows Media Player. Am I missing something?

    WhoCrashed

    On Thu 2/7/2013 2:50:07 PM GMT your computer crashed

    crash dump file: C:\Windows\Minidump\Mini020713-01.dmp

    This was probably caused by the following module: ntoskrnl.exe (nt+0x5C8BE)

    Bugcheck code: 0x1A (0x4128B, 0x6D1201, 0xFFFFFFFF80000818, 0xFFFFFFFFC0503000)

    Error: MEMORY_MANAGEMENT

    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 severe memory management error occurred.

    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.

    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-02-08T21:37:51+00:00

    From the crash dump, is says this might somehow be involved:

    PROCESS_NAME:  wmpnetwk.exe

    That belongs to Windows Media Player and that may not be the cause, but send a few more recent crash dumps (5 or so) and we can look for a pattern.

    You can also check to see if you WMP is up to date.  I am not a WMP user especially, but my version is  11.0.5721.5280 and asking it to check for update says I am running the latest version.

    It also looks like you have Acronis and the UPH Cleanup Service installed, but that is not implicated (just curious as to why UPH Cleanup).

    Can you say that there is anything in particular that you are doing when you have this BSOD - watching videos, playing games, listening to music in the wood shop, etc. or is it just out of the blue (screen of death).  What are you doing most often when it happens?

    If you can narrow it down to something like "Every time I do this ________________ the system crashes" that will help.  Or maybe "I know I can make the system crash anytime I want if I do this _____________________________".

    You have to fill in the blanks.

    Send some more recent crash dumps to your SkyDrive and post back the link.  Sometimes there is not enough info in just one to narrow things down and you have to look at a few to spot a pattern.

    Then somebody will suggest running a test of your RAM and that will not hurt - here's how:

    Run a test of your RAM with memtest86+ (I know it is boring and will cost you a CD).

    Memtest86+ is a more up to date version of the old memtest86 program and they are not the same.

    The memtest86+ will not run under Windows, so you will need to download the ISO file and create a bootable CD, boot on that and then run the memtest86+ program.

    If even a single error is reported that is a failure and should make you suspicious of your RAM.

    If you have multiple sticks of RAM you may need to run the test on them one at a time and change them out to isolate the failure to a particular single stick.

    Always keep at least the first bank of RAM occupied so the test will find something to do and there is enough to boot your system.

    Sometimes, reseating the RAM in the slots will relieve the error but a failure is still cause for suspicion.

    The file and complete instructions for using a USB or CD drive are here:

    http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

    or here:

    http://www.memtest.org/

    Here is a link that shows you have to create and use the memtest86+ CD:

    http://www.geekstogo.com/forum/Guide-to-using-Memtest86-t246994.html

    If someone says to run memtest86, you can tell them to go pound sand and that you know memtest86+ supersedes  memtest86 and here's why:

    http://en.wikipedia.org/wiki/Memtest86

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-02-08T20:29:07+00:00

    Yep I have an older Dell Daavee, and yes chkdsc came on by itself.

    sorry, don't understand 'run Recovery Console and run the command chkdsk /r.'

    do you mean just run chkdsk /r ? With a space after chkdsc? That will get the Recovery Console?

    Here are instructions:

    http://forums.whatthetech.com/index.php?showtopic=95574

    Assuming you have the Dell-branded XP CD, scroll down to where it says (ignore the part about ARCDC):

    Steps to perform on the problem machine

    Actually, I will see if I can paste the instructions:

    Steps to perform on the problem machine:

    1. Place your Windows XP Installation CD or the new Recovery Console disk you just created into your CD or DVD ROM drive, and reboot. 

    You should see this:

    If you don't see the above, try pressing the F10 or F12 keys during boot and selecting the CDRom device from the list. 

    If that doesn't work, enter BIOS Setup by pressing the F1, F2, F10 or Del key during boot and modifying the

    Boot Order or Boot Priority to make the CD/DVD first boot device. 

    If your machine won't boot to the CD, make a post in the Microsoft Windows™ forum asking for assistance with this task. 

    Please include the exact make and model of your computer so we can provide more exact instructions. 2. Press any key to start Windows Setup (Don't worry.. we're not actually using setup at this point) 3. Wait a while for setup to start, until you see the following screen, then press the R key.

     Reduced: 94% of original size [ 720 x 396 ] - Click to view full image

    4. Wait until you see this screen, and enter the number of your main installation. (Typically 1 for C:\Windows)

    5. Press Enter. 6. If prompted to do so, enter your Administrator password. If you don't have one, leave it blank and press enter. 7. From the command prompt, enter: chkdsk /r (note the space between chkdsk and /r)

    Allow it to complete undisturbed. 8. Remove the CD/DVD then reboot. Windows should now begin loading.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-02-08T20:24:27+00:00

    If you have a Dell-branded XP installation CD, you will boot off that and enter the Recovery Console (instructions to follow).

    Yes that is the command to run once in Recovery Console. And yes, there is a space before the slash.

    Do you remember me mentioning that sometimes one needs to use the Dell-branded driver instead of othre more up-to-date ones? That's what I was driving at.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2013-02-08T18:55:47+00:00

    Yep I have an older Dell Daavee, and yes chkdsc came on by itself.

    sorry, don't understand 'run Recovery Console and run the command chkdsk /r.'

    do you mean just run chkdsk /r ? With a space after chkdsc? That will get the Recovery Console?

    Yes I had the bsod rarely, performance if fine otherwise.

    still not getting notifications.

    Was this answer helpful?

    0 comments No comments