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

critical errors


  • Please log in to reply
19 replies to this topic

#1 tricia5

tricia5

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:utah
  • Local time:07:32 AM

Posted 22 June 2010 - 05:49 PM

i am getting a critical error 424 on my computer,it is stopping me from downloading certain progams or to remove programs can someone help please

BC AdBot (Login to Remove)

 


#2 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:32 PM

Posted 22 June 2010 - 05:51 PM

What operating system do you have?
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#3 tricia5

tricia5
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:utah
  • Local time:07:32 AM

Posted 22 June 2010 - 06:39 PM

windows xp with service pack 3

Edited by Budapest, 22 June 2010 - 06:42 PM.
Moved from Introductions ~BP


#4 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:32 PM

Posted 22 June 2010 - 06:44 PM

Please download VEW and save it to your Desktop: http://images.malwareremoval.com/vino/VEW.exe

Double-click VEW.exe then under Select log to query, select:
Application
System


Under Select type to list, select:
Critical (Vista only)
Error


Click the radio button for Number of events
Type 20 in the 1 to 20 box
Then click the Run button.
Notepad will open with the output log.

In Notepad, click Edit > Select all then Edit > Copy
Reply to this post, click in the reply window and press Ctrl+V on your keyboard to paste the log.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#5 tricia5

tricia5
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:utah
  • Local time:07:32 AM

Posted 23 June 2010 - 01:32 PM

Vino's Event Viewer v01c run on Windows XP in English
Report run at 23/06/2010 12:25:37 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 23/06/2010 12:11:33 AM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application , version 0.0.0.0, faulting module unknown, version 0.0.0.0, fault address 0x00000000.

Log: 'Application' Date/Time: 22/06/2010 1:32:45 PM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application BloodOath.exe, version 1.0.0.9, faulting module BloodOath.exe, version 1.0.0.9, fault address 0x00192e1d.

Log: 'Application' Date/Time: 22/06/2010 11:34:13 AM
Type: error Category: 0
Event: 1000 Source: Application Error
Faulting application _iu14d2n.tmp, version 51.49.0.0, faulting module kernel32.dll, version 5.1.2600.5781, fault address 0x00012afb.

Log: 'Application' Date/Time: 22/06/2010 12:52:56 AM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application , version 0.0.0.0, faulting module unknown, version 0.0.0.0, fault address 0x00000000.

Log: 'Application' Date/Time: 22/06/2010 12:20:09 AM
Type: error Category: 0
Event: 1 Source: swg
The event description cannot be found.

Log: 'Application' Date/Time: 21/06/2010 5:05:51 PM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application , version 0.0.0.0, faulting module unknown, version 0.0.0.0, fault address 0x00000000.

Log: 'Application' Date/Time: 21/06/2010 4:59:28 PM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application , version 0.0.0.0, faulting module unknown, version 0.0.0.0, fault address 0x00000000.

Log: 'Application' Date/Time: 21/06/2010 4:59:28 PM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application , version 0.0.0.0, faulting module unknown, version 0.0.0.0, fault address 0x00000000.

Log: 'Application' Date/Time: 21/06/2010 4:32:41 PM
Type: error Category: 0
Event: 1001 Source: Application Hang
Fault bucket 1528051972.

Log: 'Application' Date/Time: 21/06/2010 4:32:38 PM
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application SystemMechanicPro.tmp, version 51.50.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 21/06/2010 4:30:22 PM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application drwtsn32.exe, version 5.1.2600.0, faulting module dbghelp.dll, version 5.1.2600.5512, fault address 0x0001295d.

Log: 'Application' Date/Time: 21/06/2010 4:30:15 PM
Type: error Category: 0
Event: 1000 Source: Application Error
Faulting application systemmechanicpro.tmp, version 51.50.0.0, faulting module kernel32.dll, version 5.1.2600.5781, fault address 0x00012afb.

Log: 'Application' Date/Time: 21/06/2010 4:27:11 PM
Type: error Category: 0
Event: 1001 Source: Application Error
Fault bucket 1234638564.

Log: 'Application' Date/Time: 21/06/2010 4:27:09 PM
Type: error Category: 0
Event: 1000 Source: Application Error
Faulting application _iu14d2n.tmp, version 51.49.0.0, faulting module kernel32.dll, version 5.1.2600.5781, fault address 0x00012afb.

Log: 'Application' Date/Time: 21/06/2010 4:19:08 PM
Type: error Category: 0
Event: 1000 Source: Application Error
Faulting application systemmechanicpro.tmp, version 51.49.0.0, faulting module kernel32.dll, version 5.1.2600.5781, fault address 0x00012afb.

Log: 'Application' Date/Time: 21/06/2010 3:56:25 PM
Type: error Category: 0
Event: 1000 Source: Application Error
Faulting application _iu14d2n.tmp, version 51.49.0.0, faulting module kernel32.dll, version 5.1.2600.5781, fault address 0x00012afb.

Log: 'Application' Date/Time: 21/06/2010 3:55:29 PM
Type: error Category: 0
Event: 1000 Source: Application Error
Faulting application _iu14d2n.tmp, version 51.49.0.0, faulting module kernel32.dll, version 5.1.2600.5781, fault address 0x00012afb.

Log: 'Application' Date/Time: 21/06/2010 3:50:37 PM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application , version 0.0.0.0, faulting module unknown, version 0.0.0.0, fault address 0x00000000.

Log: 'Application' Date/Time: 21/06/2010 3:50:36 PM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application , version 0.0.0.0, faulting module unknown, version 0.0.0.0, fault address 0x00000000.

Log: 'Application' Date/Time: 21/06/2010 3:45:00 PM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application , version 0.0.0.0, faulting module unknown, version 0.0.0.0, fault address 0x00000000.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 23/06/2010 11:30:34 AM
Type: error Category: 0
Event: 49 Source: Ftdisk
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.

Log: 'System' Date/Time: 23/06/2010 11:30:34 AM
Type: error Category: 0
Event: 45 Source: Ftdisk
The system could not sucessfully load the crash dump driver.

Log: 'System' Date/Time: 22/06/2010 5:28:59 PM
Type: error Category: 0
Event: 49 Source: Ftdisk
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.

Log: 'System' Date/Time: 22/06/2010 5:28:59 PM
Type: error Category: 0
Event: 45 Source: Ftdisk
The system could not sucessfully load the crash dump driver.

Log: 'System' Date/Time: 22/06/2010 2:00:00 PM
Type: error Category: 0
Event: 7901 Source: Schedule
The At2.job command failed to start due to the following error: %%2147942402

Log: 'System' Date/Time: 22/06/2010 2:00:00 PM
Type: error Category: 0
Event: 7901 Source: Schedule
The At1.job command failed to start due to the following error: %%2147942402

Log: 'System' Date/Time: 22/06/2010 11:35:39 AM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

Log: 'System' Date/Time: 22/06/2010 11:35:38 AM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

Log: 'System' Date/Time: 22/06/2010 11:35:38 AM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

Log: 'System' Date/Time: 22/06/2010 11:35:38 AM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

Log: 'System' Date/Time: 22/06/2010 11:35:38 AM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

Log: 'System' Date/Time: 22/06/2010 11:35:38 AM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

Log: 'System' Date/Time: 22/06/2010 11:35:37 AM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

Log: 'System' Date/Time: 22/06/2010 11:35:37 AM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

Log: 'System' Date/Time: 22/06/2010 11:35:37 AM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

Log: 'System' Date/Time: 22/06/2010 11:35:37 AM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

Log: 'System' Date/Time: 22/06/2010 11:35:37 AM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

Log: 'System' Date/Time: 22/06/2010 11:35:37 AM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

Log: 'System' Date/Time: 22/06/2010 11:35:37 AM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

Log: 'System' Date/Time: 22/06/2010 11:35:37 AM
Type: error Category: 0
Event: 7023 Source: Service Control Manager
The Application Management service terminated with the following error: The specified module could not be found.

#6 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:32 PM

Posted 23 June 2010 - 04:22 PM

Right click on the C drive in Explorer and go Properties > Tools > Check Now (under Error Checking). Check both boxes then click "Start Now". A message will pop up saying that Error Checking will run after you restart the computer. Restart the computer and Error Checking will run automatically after the restart. After itís finished it will restart into Windows automatically.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#7 tricia5

tricia5
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:utah
  • Local time:07:32 AM

Posted 23 June 2010 - 06:09 PM

ok i did that and it still came up on my screen after restart critical error error 424 so what do i need to do now

#8 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:32 PM

Posted 23 June 2010 - 06:15 PM

Go Start > Run and type "eventvwr.msc" (without the quotes). Click on Application and select the most recent winlogon entry. It should give the chkdsk log. Post the log back here.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#9 tricia5

tricia5
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:utah
  • Local time:07:32 AM

Posted 23 June 2010 - 09:08 PM

when i do that it gives me 824 events and will not let me select all to post

#10 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:32 PM

Posted 23 June 2010 - 10:08 PM

Try increasing the size of the Pagefile.sys File to see if that makes any difference:

1. Right-click My Computer, and then click Properties.
2. Click the Advanced tab, and then click Performance Options.
3. Under Virtual Memory, click Change.
4. Set the initial size of the page file that exists on the same partition as the operating system to be one and a half times the size of the amount of RAM installed in the computer.
5. Reboot.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#11 tricia5

tricia5
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:utah
  • Local time:07:32 AM

Posted 23 June 2010 - 11:44 PM

Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 6/23/2010
Time: 5:04:49 PM
User: N/A
Computer: EMACHINE-7AF6B9
Description:
Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 819 unused index entries from index $SII of file 0x9.
Cleaning up 819 unused index entries from index $SDH of file 0x9.
Cleaning up 819 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Windows has made corrections to the file system.

72774449 KB total disk space.
10603308 KB in 49994 files.
17824 KB in 4923 indexes.
0 KB in bad sectors.
138181 KB in use by the system.
65536 KB occupied by the log file.
62015136 KB available on disk.

4096 bytes in each allocation unit.
18193612 total allocation units on disk.
15503784 allocation units available on disk.

Internal Info:
00 0a 01 00 90 d6 00 00 00 2e 01 00 00 00 00 00 ................
a1 00 00 00 02 00 00 00 be 04 00 00 00 00 00 00 ................
4c 68 2c 01 00 00 00 00 4a e2 dc 19 00 00 00 00 Lh,.....J.......
46 a4 19 06 00 00 00 00 3a 41 a3 12 01 00 00 00 F.......:A......
de 78 0d ea 01 00 00 00 c2 92 b5 24 03 00 00 00 .x.........$....
10 85 ce 5f 00 00 00 00 a0 39 07 00 4a c3 00 00 ..._.....9..J...
00 00 00 00 00 b0 2c 87 02 00 00 00 3b 13 00 00 ......,.....;...

Windows has finished checking your disk.
Please wait while your computer restarts.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

#12 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:32 PM

Posted 23 June 2010 - 11:46 PM

Did you change the pagefile settings? Has this helped with the errors?
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#13 tricia5

tricia5
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:utah
  • Local time:07:32 AM

Posted 23 June 2010 - 11:54 PM

the original pagefile settings was double the amount changed it to one and half times the amount and no it did not help at all still get critical error[error 424]

#14 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:32 PM

Posted 24 June 2010 - 12:15 AM

What is the exact wording of this error message?
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#15 tricia5

tricia5
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:utah
  • Local time:07:32 AM

Posted 24 June 2010 - 12:36 AM

critical error[error424]




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users