blue screen crash

  raggydoll 16:24 30 Dec 04
Locked

at least several times a day my PC suddenly crashes,i get a sudden blue screen with loads of text flashes so fast you cant read a thing,computer reboots then get a message recovered from a serious error,here are the message details,=C:\WINDOWS\minidump\mini122104-03.dmp C:\DOCUME~1\ianwis~1\temp\WER1:tmp.dir00\sysdata.xml,can anyone tell me what kind of error this is,software or hardware or what,as it is driving me mad.thanks

  VoG II 16:31 30 Dec 04

Delete this entire folder

C:\DOCUME~1\ianwis~1\temp\WER1:tmp.dir00

That should stop the messages appearing.

  raggydoll 16:40 30 Dec 04

thanks for reply VOG,but stil dont know what is causing the crashes though any ideas????

  JIM 16:44 30 Dec 04

Restart Windows.

Verify for any unsigned drivers and eliminate it.

1. Click Start, click Run, type, sigverif and then click OK.

2. Click Advanced.

3. Click Look for other files that are not digitally signed.

4. In the Look in this folder box, type x:\Windows\system32\drivers, where x is the

letter of the drive where Windows XP is installed.

5. On the Logging tab, make sure the Save the file signature verification results to a log file

6.check box is selected, and then click OK.

7. Click Start.

NOTE: The log file is named Sigverif.txt, and it is saved in the Windows folder. Third-party drivers that are unsigned are displayed as "Not signed." Use the drivers in this list as your troubleshooting starting point.

Disable Unsigned Device Drivers
A common problem is power management features, and Microsoft requires power management support to certify drivers. Many third-party unsigned drivers lack this support, resulting in power management problems (such as problems going into or coming out of hibernation and standby).

After you find unsigned drivers, you can disable them by using any of the following methods.

a/ Disable the device in Device Manager.

(you may have to click "Show hidden devices on the View menu" and then disable the device under the Non-Plug and Play Drivers branch).

b. Uninstall the software that installed the third-party driver by using the Add/Remove Programs tool in Control Panel.

c. Rename the driver in the Windows\System32\Drivers folder.

click here;en-us;308514

Some others to try ,will post.

  JIM 16:48 30 Dec 04

Try again.

http ----- ://support.microsoft.com/default.aspx?scid=kb;en-us;308514

click here;en-us;308514

  VoG II 16:51 30 Dec 04
  raggydoll 16:58 30 Dec 04

thanks all hope i can sort it now.

  JIM 17:00 30 Dec 04

Thankyou.

Will post other poss idea/ answers from elsewhere.

--------------------------------------------------

First if the error is intermitent, (is there is a moment or action you can identify)
or (You cant see a pattern).

Consider that the numbers you give correspond to
hardware failure,examples could be a CDRW using rewritable disks that are incompatible
with the drive. Another example could be a faulty RAM module. Other example could be
Modems, Sound Cards, Video cards, processors, or even the mother board, (temperature is a great
enemy)

Try to track down any similarity between errors, lets say temperature, task that you are
performing, programs in use, combination of opened programs... everyting.

  JIM 17:09 30 Dec 04

may help you and other in similar situation but check before moving on as it is MS routine.


Although there are several poss methods to resolve this issue, such as updating drivers and/or removing unsigned or corrupt drivers, let's see if the corruption lies elsewhere on the system first. Follow the instructions in the first section. If the problem is not resolved, proceed to the next section.

I. Resize the Swap File
When a serious error occurs, by default the system dumps the system state to
the swap file for later retrieval. However, it is possible that the swap
file is not properly cleaned up and the system thinks that it is rebooting
from a crash. To resolve this, you will need to resize the swap file:

1. Click the Start button.

2. Right click the My Computer menu option, and then click Properties on the
context menu that appears.

3. Click the Advanced tab, and then click the Settings button in the
Performance section.
The Performance Options window appears.

4. Click the Advanced tab, and then click the Change button in the Virtual
Memory section.
The Virtual memory window appears.

5. Click Custom Size, and then record the Initial Size and Maximum Size.

6. Set the Initial Size and Maximum Size to the same value as the amount of
RAM that is installed in the system.

7. Click Set and then click OK. The system will advise you to restart the
computer.

8. Click OK.

9. Click OK at the Performance Options window. The system prompts you to
restart the computer.

10. Click Yes.

After the system has restarted, repeat the above steps to restore the
original Initial Size and Maximum Size values for your swap file.

II. Delete the Minidump Files and the Sysdata.xml File
When a serious error occurs, by default the system writes out a miniature
memory dump along with an XML description of the system status (which notes
the program at fault and other pertinent system data) that can be uploaded
to Microsoft. If this data is not correctly closed out, the system may
present a Serious Error screen upon boot. To resolve this problem, perform
the following steps:

1. Click the Start button.

2. Right click the My Computer icon, and then click Explore on the context
menu that appears.

3. Browse to the c:\Windows\Minidump directory.

4. Delete everything located in this directory.

You will need to be able to view hidden and system files and the
system should not be hiding protected operating system files.

5. Browse to the c:\Documents and Settings folder.

6. Search for the following file: sysdata.xml file.

7. Delete all instances (you may find more than one) of this file.

8. Click the Start button, click Turn off the computer, and then click
Restart.

III. Disable the Automatically Restart setting

This attacks the same class of Serious Errors that resizing the swap file
fixes, but it tries to ensure that the errors do not happen beforehand.
However, this does not help to rid the persistent Serious Error message
after the fact.

1. Click the Start button.

2. Right click the My Computer icon, and then click Properties on the
context menu that appears.

3. Click the Advanced tab and then click the Settings button in the
Start-up and Recovery section.

4. Click to remove the check next to Automatically Restart checkbox and
then click OK.

5. Click OK. The system will no longer automatically restart after a
Serious Error message appears.

IV. Disable Memory Dumps
This option totally disables memory dumps altogether, which may help fix
some persistent Serious Error messages. To disable memory dumps, perform the
following steps:

1. Click the Start button

2. Right click the My Computer icon, and then click Properties on the
context menu that appears.

3. Click the Advanced tab, and then click the Settings button in the
Start-up and Recovery section.

4. In the Write debugging information tab, click to select (none) and then
click OK.

5. Click OK.

The system will no longer perform a memory dump when it encounters a Serious
Error.

This thread is now locked and can not be replied to.

iPhone 7 review: a range of small updates add up to an excellent phone

1995-2015: How technology has changed the world in 20 years

How New York’s Stylin’ Seniors became a golden social media campaign

23 Apple Watch tips & secret features: Master your Apple Watch, Apple Watch Series 1 or Apple…