Pciidex.sys vista error

pciidex.sys vista error

www.800error.com › windows-bluescreen-bsod-stopcode-pciidex. But Im still getting those BSoDs I already ran memtest86 (from Ubuntu) for 9 hours and NO MEM ERRORS! I also tried to read and understand the. Abstract—Windows Vista introduces several additional barriers that aim to prevent malicious code from gaining access to the operating system kernel.

Pciidex.sys vista error - special case

Why did I get error BSOD bluescreen pciidex.sys?

When your computer has a heavy poblem it will show you a bluescreen of death BSOD with some additional information. To solve your bluescreen we need to detect the root cause of this problem. You can detect the root cause by look at the Stop Code on the bluescreen. Here are some popular stopcodes:

> SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
> VIDEO_TDR_FAILURE
> SYSTEM_SERVICE_EXCEPTION
> PAGE_FAULT_IN_NONPAGED_AREA
> CRITICAL_PROCESS_DIED
> IRQL_NOT_LESS_OR_EQUAL
> VIDEO_TDR_TIMEOUT_DETECTED
> DPC_WATCHDOG_VIOLATION

How to fix BSOD bluescreen stopcode pciidex.sys?

You can follow this tutorial:


1. Check your computer for malware and virus with this program
Download
2. Update your Windows by installing all updates.
3. Update all your drivers. You can download all your drivers on the manufacturer website.


Now we will check your computer for corrupt files:

1. Search for CMDand open the Command Promt (Admin)
2. Type the following text in the black window to repair the core components of Windows.

DISM /online /cleanup-image /restorehealth

3. Wait until this process is finished. Based on your computer this process can take a couple minutes.
4. Type the following text in the black window to scan for corrupt files.

If the problem still persists, you can run the System File Checker (SFC) utility. This handy in-built tool will check your filesystem.

1. Click Start and start typing on your keyboard for "cmd".
2. In your search results cmd should show up with an black icon.
3. Right-click it and select Run as administrator.
4. If you are prompted for the admin password, enter the password and click OK.
5. A new completely black windwos will open. You can type commands directly into this window.
6. Type sfc/scannow and press Enter.
7. This process will take a long time. You can minimize this black windows and work on.

Come back to the black window after a time and check if the process finished.
As soon as the SFC process finished, restart your computer. After the restart you search for Updates again.

You are still facing the same issue?

1. Restart your computer.


You are still facing this issue? I think this is not an usual problem and your computer should be checked by professional.
Try to look for a solution here or search further in the search box below.


Advanced information

The following Windows verisons are affected by this error:

> Windows Vista
> Windows 7
> Windows 8
> Windows 8.1
> Windows 10
> Windows 10 Redstone 2
> Windows 10 Creators Update
> Windows 10 2004
> Windows 10 1903
> Windows 10 1908
> Windows Server 2008 R2
> Windows Server 2012
> Windows Server 2016
> Windows Server 2019

Windows Boot Failed

So yesterday I was on my Dell computer (Vista SP2). Everything was fine, there were no problems or changes, nothing. I tried turning on my computer today and it stops at the "Windows Boot Manager." This is the message it came up with:

Windows failed to start. A recent hardware or software change might be the case. To fix the problem:
1. Insert your Windows Installation disc and restart your computer.
2. Choose your language settings, and then click "Next."
3. Click "Repair your computer."

File: PCIIDEX.sys
Status: 0x00000e9
Info: Windows failed to load because a required file is missing, or corrupt.


[*Note I can't get into safemode] I tried everything I know to fix it with the original disc. I tried a System Restore, but unfortunately that was disable (I thought I had enabled), a Startup Repair (which found a problem but couldn't fix it), Windows Complete PC Restore (Which couldn't find a backup image). I also tried booting from the operating system on the CD itself and I got this message when trying to fix it:

C:\PCIIDEX.SYS is corrupt.

c:\windows\system32\drivers\pciide.sys is corrupt.

Error code:0x2


I even did a Dell Diagnosis which is installed by default on the hardrive and it came up with this error, but I don't even think it has anything to do with my real problem:

** Hard Drive - DST Short Test **
Test Results: Fail
Error Code 2000-0142
Msg: Hard Drive 0 - self test unsuccessful. Status: 79


If there is anything I can do or any step I can take please let me know. I tried searching all over for solutions but obviously I did not succeed with that. My only option left is to completely format my hardrive and reinstall Windows Vista, which I do not want to do at all. Thanks!

+ HID Keyboard Device
Driver: i8042prt.sys, 1/19/2008 01:49:18, 54784 bytes

alexoiu :

So, you installed XP on a SATA HDD on your machine, without SATA driver needed?
Can you check in BIOS the SATA setting? Is it IDE or AHCI?



Hi,

These are the current BIOS Settings:

InChip SATA Controller ( AMD SB950 South Bridge, SATA3_0-SATA3_5 connectors )
Enables or Disables integrated SATA Controller
( ( Default: Enabled ))

OnChip SATA Type ( AMD SB950 South Bridge, SATA3_0-SATA_3 connectors
Configures opening mode of the integrated SATA2_0-SATA2_3 Controller
( ( Default: Native IDE ) Allows SATA Controller to operate in Native IDE mode )
Other options are RAID and AHCI

OnChip SATA Port4/5 Type (AMD SB950 South Bridge, SATA3_4/SATA3_5 Connectors
Configurable only if OnChip SATA Type is set to RAID or ACHI. Configures operating mode of
SATA2_4/SATA2_5 Connectors
( IDE ( Default )) Disables RAID for the SATA Controller and configures the SATA Controller to PATA mode.

OnChip SATA RAID5 Support (AMD SB950 South Bridge, SATA3_0-SATA3_5 Connectors
Enables or Disables RAID5 Support for SATA Controller integrated in the AMD SB950 South Bridge
Default: Enabled

OnChip SATA3.0 Support
Enables or Disables SATA 6Gbs function integrated in the AMD SB950 South Bridge.
When Disabled the Controller will operate in SATA 3Gbs mode.
( Default: Enabled)

Port0 as ESP/Port1 as ESP/Port2 as ESP/Port3 as ESP
Available if OnChip SATA Type is set to AHCI. Enabled it will speed up hot plug detection of SATA Device. ( Default: Disabled )

Port4 as ESP/Port5 as ESP
Available only when OnChip SATA Type is set to ACHI, and OnChip SATA Type Port4/5 is set to As SATA Type. Enabled it will speed up hot plug connection of SATA Device.
( Default: Disabled)


Thanks,
Moonraven

 

Driver: kbdclass.sys, 1/19/2008 03:41:52, 35384 bytes

Error on blue screen on Windows 7.

Get the IRQL_NOT_LESS_OR_EQUAL Error with blue screen

Hello

I get the IRQL_NOT_LESS_OR_EQUAL Error with blue screen when I start the machine.
STOP: 0X0000000A (0X00000000, 0X804DC11D, 0X00000001, 0 X 000000002)

I can't connect in Debug Mode. I tried winDBG, but cannot interpret the output (output is attached below). There was no new HW SW or recently installed or when this error occurred.

I also tried to run Verifier.exe with the option "Select all drivers installed automatically on this computer" and as soon as I chose this option, another mistake (and cannot change this option), DRIVER_IRQL_NOT_LESS_OR_EQUAL
STOP: 0x000000D1(0x8068329C,0x00000002,0x00000000,0x89E4460A)

Thanks in advance,
SRSK

output in winDbg:

Debug version of Microsoft Windows (R) 6.11.0001.404 X 86

Copyright (c) Microsoft Corporation. All rights reserved.

Loading dump file [C:\WINDOWS\Minidump\Mini102109-01.dmp]

The mini kernel dump file: only registers and the trace of the stack are available

Symbol search path is: * invalid *.

****************************************************************************

* Loading of the symbol may be unreliable without a symbol search path.           *

* Use .symfix to get the debugger to choose a symbol path.                   *

* After adjusting your path to symbols, use .reload to refresh the locations of symbols. *

****************************************************************************

Executable search path is:

*********************************************************************

* Symbols cannot be loaded because the path is not initialized. *

*                                                                   *

* The symbol path can be defined: *.

* using the _NT_SYMBOL_PATH environment variable.                 *

* with the help of the

The kernel symbols are FALSE. Correct symbols to do the analysis.

*************************************************************************

***                                                                   ***

***                                                                   ***

Your debugger is not using the appropriate symbols *.

***                                                                   ***

In order for this command works correctly, your symbol path *.

should point to .pdb files have the type information complete.      ***

***                                                                   ***

Some (such as the public OS symbols) .pdb files are not *.

contain the required information.  The contact group that *.

you provided with these symbols, if you need this command for *.

work.                                                          ***

***                                                                   ***

Type referenced: nt! _KPRCB *.

*

Type referenced: nt! KPRCB                                      ***

Type referenced: nt! _KPRCB *.

*

Type referenced: nt! _KPRCB *.

*************************************************************************

WARNING: Unable to verify timestamp for Ntfs.sys

ERROR: Module load completed but symbols can be loaded for Ntfs.sys

Could not load the PxHelp20.sys, 0n2 error Win32 image

WARNING: Unable to verify timestamp for PxHelp20.sys

ERROR: Module load completed but symbols can be loaded for PxHelp20.sys

Type referenced: nt! _KPRCB *.

*                                                                  ***

Type referenced: nt! _KPRCB *.

* Symbols cannot be loaded because the path is not initialized. *

*                                                                   *

* The symbol path can be defined: *.

* using the _NT_SYMBOL_PATH environment variable.                 *

* with the help of the

f78da56c 00217375 666e6f63 692e6769 0000696e 0x62654a20

f78da570 666e6f63 692e6769 0000696e 73726576 0 x 217375

f78da574 0000696e 692e6769 73726576 006e6f69 0x666e6f63

00000000 73726576 006e6f69 746f7571 0x692e6769 f78da578

KD > lmv

start end module name

804 d 7000 806ed700 nt T (no symbol)

Loaded symbol image file: ntoskrnl.exe

Image path: ntoskrnl.exe

Image name: ntoskrnl.exe

Timestamp: Fri Feb 06 06:08:08 2009 (498C1A18)

CheckSum: 002197F5

ImageSize: 00216700

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

806ee000 8070e300 hal (postponed)

Image path: hal.dll

Image name: hal.dll

Timestamp: Sun Apr 13 14:31:27 2008 (4802517F)

CheckSum: 00024F17

ImageSize: 00020300

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

951ba180 95190000 kmixer (postponed)

Image path: c:\windows\system32\drivers\kmixer.sys

Image name: c:\windows\system32\drivers\kmixer.sys

Timestamp: Sun Apr 13 14:45:07 2008 (480254B 3)

CheckSum: 0002F580

ImageSize: 0002A 180

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

953c 6000 953d 2000 1 (postponed)

Image path: 1C.tmp

Image name: 1C.tmp

Timestamp: Sat Oct 17 23:21:43 2009 (4ADA89C7)

CheckSum: 00007E35

ImageSize: 0000-000 C

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

98528000 98579880 srv (postponed)

Image path: srv.sys

Image name: srv.sys

Timestamp: Thu Dec 11 05:57:07 2008 (4940F203)

CheckSum: 0005EF30

ImageSize: 00051880

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

985f5000 98609480 wdmaud (postponed)

Image path: wdmaud.sys

Image name: wdmaud.sys

Timestamp: Sun Apr 13 15:17:18 2008 (48025C3E)

CheckSum: 00018CBD

ImageSize: 00014480

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9865 to 000 9869aa80 HTTP (postponed)

Image path: HTTP.sys

Image name: HTTP.sys

Timestamp: Sun Apr 13 14:53:48 2008 (480256BC)

Checksum: 00046D 31

ImageSize: 00040A 80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9870e000 9873 has 180 mrxdav (postponed)

Image path: c:\windows\system32\drivers\mrxdav.sys

Image name: c:\windows\system32\drivers\mrxdav.sys

Timestamp: Sun Apr 13 14:32:42 2008 (480251CA)

Sum: 0002C 564

ImageSize: 0002C 180

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9a7b3000 9a 825100 dump_iastor (postponed)

Image path: dump_iastor.sys

Image name: dump_iastor.sys

Timestamp: Tue Mar 23 15:13:55 2004 (40608 C 73)

CheckSum: 00072C3C

ImageSize: 00072100

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9a 826000 9 has 876380 avgldx86 (postponed)

Image path: avgldx86.sys

Image name: avgldx86.sys

Timestamp: Thu Jul 09 20:17:49 2009 (4A5688AD)

Sum: 0005C 506

ImageSize: 00050380

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9a 877000 9a89c500 ipnat (postponed)

Image path: ipnat.sys

Image name: ipnat.sys

Timestamp: Sun Apr 13 14:57:10 2008 (48025786)

CheckSum: 0002AF4A

ImageSize: 00025500

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9a89d000 9a90c280 mrxsmb (postponed)

Image path: mrxsmb.sys

Image name: mrxsmb.sys

Timestamp: Fri Oct 24 07:21:07 2008 (4901AFA3)

CheckSum: 0007CB15

ImageSize: 0006F280

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9a90d000 9a937e80 rdbss (postponed)

Image path: rdbss.sys

Image name: rdbss.sys

Timestamp: Sun Apr 13 15:28:38 2008 (48025EE6)

CheckSum: 0002F906

ImageSize: 0002AE80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9a 938000 9a959d00 afd (postponed)

Image path: afd.sys

Image name: afd.sys

Timestamp: Thu Aug 14 06:04:35 2008 (48A 40333)

CheckSum: 000292E0

ImageSize: 00021D 00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9a95a000 9a981c00 netbt (postponed)

Image path: netbt.sys

Image name: netbt.sys

Timestamp: Sun Apr 13 15:20:59 2008 (48025D1B)

CheckSum: 0002FE7A

ImageSize: 00027C 00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9a 982000 9a99ae00 avgtdix (postponed)

Image path: c:\windows\system32\drivers\avgtdix.sys Device

Image name: c:\windows\system32\drivers\avgtdix.sys Device

Timestamp: My Apr 06 09:42:27 2009 (49DA06C3)

CheckSum: 00029806

ImageSize: 00018E00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9a99b000 9a9f3480 tcpip (postponed)

Image path: tcpip.sys

Image name: tcpip.sys

Timestamp: Fri Jun 20 07:51:09 2008 (485B99AD)

CheckSum: 0005ED6B

ImageSize: 00058480

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9a9f4000 9aa06600 ipsec (postponed)

Image path: ipsec.sys

Image name: ipsec.sys

Timestamp: Sun Apr 13 15:19:42 2008 (48025CCE)

CheckSum: 00016389

ImageSize: 00012600

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9aa27000 9aac3000 ctac32k (postponed)

Image path: ctac32k.sys

Image name: ctac32k.sys

Timestamp: Fri Aug 11 02:45:14 2006 (44DC277A)

CheckSum: 00081570

ImageSize: 0009C 000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9aac3000 9aaea000 ctsfm2k (postponed)

Image path: ctsfm2k.sys

Image name: ctsfm2k.sys

Timestamp: Fri Aug 11 02:45:18 2006 (44DC277E)

Checksum: 000275C 8

ImageSize: 00027000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9aaea000 9ab17000 emupia2k (postponed)

Image path: emupia2k.sys

Image name: emupia2k.sys

Timestamp: Fri Aug 11 02:45:17 2006 (44DC277D)

CheckSum: 00013B 96

ImageSize: 0002D 000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9ab17000 9ac1b000 ha10kx2k (postponed)

Image path: ha10kx2k.sys

Image name: ha10kx2k.sys

Timestamp: Fri Aug 11 02:45:24 2006 (44DC2784)

CheckSum: 000BD2C0

ImageSize: 00104000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9ac1b000 9ac45000 hap16v2k (postponed)

Image path: hap16v2k.sys

Image name: hap16v2k.sys

Timestamp: Fri Aug 11 02:45:26 2006 (44DC2786)

Checksum: 0002D 547

ImageSize: 0002A, 000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9b20b000 9b219a80 usbaudio (postponed)

Image path: usbaudio.sys

Image name: usbaudio.sys

Timestamp: Sun Apr 13 14:45:11 2008 (480254B 7)

CheckSum: 0001D8AC

ImageSize: 0000EA80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9b2bb000 9b2be900 o ndisuio (postponed)

Image path: ndisuio.sys

Image name: ndisuio.sys

Timestamp: Sun Apr 13 14:55:57 2008 (4802573D)

CheckSum: 00008481

ImageSize: 00003900

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9b2dc000 9b2dcb80 Null (postponed)

Image path: Null.SYS

Image name: Null.SYS

Timestamp: Fri Aug 17 16:47:39 2001 (3B7D82EB)

CheckSum: 00008483

ImageSize: 00000B 80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9b 964000 9b972d80 arp1394 (postponed)

Image path: arp1394.sys

Image name: arp1394.sys

Timestamp: Sun Apr 13 14:51:22 2008 (4802562A)

CheckSum: 0000EE1E

ImageSize: 0000ED80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9b 974000 9b97c700 wanarp (postponed)

Image path: wanarp.sys

Image name: wanarp.sys

Timestamp: Sun Apr 13 14:57:20 2008 (48025790)

CheckSum: 00009785

ImageSize: 00008700

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9b 994000 9b99ee00 Fips (postponed)

Image path: Fips.SYS

Image name: Fips.SYS

Timestamp: Sun Apr 13 14:33:27 2008 (480251F7)

CheckSum: 0001559A

ImageSize: 0000AE00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9b9b4000 9b9bc780 netbios (postponed)

Image path: netbios.sys

Image name: netbios.sys

Timestamp: Sun Apr 13 14:56:01 2008 (48025741)

CheckSum: 00010B5E

ImageSize: 00008780

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9bd09000 9bd0c240 OMCI (postponed)

Image path: OMCI. SYS

Image name: OMCI. SYS

Timestamp: Sea Aug 22 12:42:57 2001 (3B83E111)

CheckSum: 0000FDD9

ImageSize: 00003240

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

9ca 75000 9 ca 77280 Rdbss (postponed)

Image path: rasacd.sys

Image name: rasacd.sys

Timestamp: Fri Aug 17 16:55:39 2001 (3B7D84CB)

CheckSum: 0000B2E7

ImageSize: 00002280

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

a6782000 dog guard a6786500 (postponed)

Image path: watchdog.sys

Image name: watchdog.sys

Timestamp: Sun Apr 13 14:44:59 2008 (480254AB)

CheckSum: 000078B 2

ImageSize: 00004500

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

a6870000 a687f900 Cdfs (postponed)

Image path: Cdfs.SYS

Image name: Cdfs.SYS

Timestamp: Sun Apr 13 15:14:21 2008 (48025B8D)

CheckSum: 000127A 4

ImageSize: 0000F900

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

a7027000 a7029900 Dxapi (postponed)

Image path: Dxapi.sys

Image name: Dxapi.sys

Timestamp: Fri Aug 17 16:53:19 2001 (3B7D843F)

CheckSum: 0000ACC2

ImageSize: 00002900

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

aa431000 aa437700 USBSTOR (postponed)

Image path: USBSTOR. SYS

Image name: USBSTOR. SYS

Timestamp: Sun Apr 13 14:45:37 (1 480254) 2008

CheckSum: 00011541

ImageSize: 00006700

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

ad66c000 ad673d80 usbccgp (postponed)

Image path: usbccgp.sys

Image name: usbccgp.sys

Timestamp: Sun Apr 13 14:45:38 2008 (480254 2)

CheckSum: 000100CC

ImageSize: 00007D 80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

ad684000 ad689280 avgmfx86 (postponed)

Image path: avgmfx86.sys

Image name: avgmfx86.sys

Timestamp: Wed Jul 01 16:37:21 2009 (4A4BC901)

CheckSum: 0000B17B

ImageSize: 00005280

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

ad68c000 ad693880 NPH (postponed)

Image path: Npfs.SYS

Image name: Npfs.SYS

Timestamp: Sun Apr 13 14:32:38 2008 (6 480251)

CheckSum: 0000C3AB

ImageSize: 00007880

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

ad694000 ad698a80 Msfs (postponed)

Image path: Msfs.SYS

Image name: Msfs.SYS

Timestamp: Sun Apr 13 14:32:38 2008 (6 480251)

CheckSum: 00005BB8

ImageSize: 00004A 80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

ad69c000 ad6a1200 vga (postponed)

Image path: vga.sys

Image name: vga.sys

Timestamp: Sun Apr 13 14:44:40 2008 (48025498)

Checksum: 0001170C

ImageSize: 00005200

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

ad6a4000 ad6aa180 HIDPARSE (postponed)

Image path: HIDPARSE. SYS

Image name: HIDPARSE. SYS

Timestamp: Sun Apr 13 14:45:22 2008 (480254 2)

CheckSum: 00008E19

ImageSize: 00006180

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

b03d8000 b03d8d00 dxgthk (postponed)

Image path: dxgthk.sys

Image name: dxgthk.sys

Timestamp: Fri Aug 17 16:53:12 2001 (3B7D8438)

CheckSum: 000035E7

ImageSize: 00000D 00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

b9722000 b977ff00 update (postponed)

Image path: update.sys

Image name: update.sys

Timestamp: Sun Apr 13 14:39:46 2008 (48025372)

CheckSum: 0006CBBF

ImageSize: 0005DF00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

b9780000 b97afe80 rdpdr (postponed)

Image path: rdpdr.sys

Image name: rdpdr.sys

Timestamp: Sun Apr 13 14:32:50 (480251 2) 2008

CheckSum: 00039B0C

ImageSize: 0002FE80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

b97b0000 b97c0e00 psched (postponed)

Image path: psched.sys

Image name: psched.sys

Timestamp: Sun Apr 13 14:56:36 2008 (48025764)

CheckSum: 0001E655

ImageSize: 00010E00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

b97c1000 b97d7580 ndiswan (postponed)

Image path: ndiswan.sys

Image name: ndiswan.sys

Timestamp: Sun Apr 13 15:20:41 2008 (48025-09)

CheckSum: 00018B 10

ImageSize: 00016580

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

b97d8000 b9826500 luipsec (postponed)

Image path: luipsec.sys

Image name: luipsec.sys

Timestamp: Fri Feb 20 14:55:19 2008 (47BC85A7)

CheckSum: 0005082D

ImageSize: 0004E500

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

b9827000 b9860000 arkzlin6 (postponed)

Image path: arkzlin6. SYS

Image name: arkzlin6. SYS

Timestamp: Sun Jul 13 18:54 2008 (487A 8788)

CheckSum: 00042E1D

ImageSize: 00039000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

b9860000 b9873900 parport (postponed)

Image path: parport.sys

Image name: parport.sys

Timestamp: Sun Apr 13 14:40:09 2008 (48025389)

CheckSum: 00018D4E

ImageSize: 00013900

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

b9874000 b98a7000 ctoss2k (postponed)

Image path: ctoss2k.sys

Image name: ctoss2k.sys

Timestamp: Fri Aug 11 02:45:23 2006 (44DC2783)

CheckSum: 000299B 7

ImageSize: 00033000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

b98a7000 b98caa80 portcls (postponed)

Image path: portcls.sys

Image name: portcls.sys

Timestamp: Sun Apr 13 15:19:40 2008 (48025CCC)

CheckSum: 00030B 59

ImageSize: 00023A 80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

b98cb000 b9944f80 ctaud2k (postponed)

Image path: ctaud2k.sys don't

Image name: ctaud2k.sys don't

Timestamp: Fri Aug 11 02:45:37 2006 (44DC2791)

CheckSum: 00084619

ImageSize: 00079F80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

b9945000 b9967700 ks (deferred)

Image path: ks.sys

Image name: ks.sys

Timestamp: Sun Apr 13 15:16:34 (48025 12) 2008

CheckSum: 000326F0

ImageSize: 00022700

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

b9968000 b99dea00 atinewp2 (postponed)

Image path: atinewp2.sys

Image name: atinewp2.sys

Timestamp: Kills Jul 27 21:43:40 2004 (410704CC)

CheckSum: 00083DD5

ImageSize: 00076A 00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

b99df000 b9a02200 USBPORT (postponed)

Image path: USBPORT. SYS

Image name: USBPORT. SYS

Timestamp: Sun Apr 13 14:45:34 2008 (480254CE)

CheckSum: 0002AAEC

ImageSize: 00023200

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

b9a03000 b9a20a80 b57xp32 (postponed)

Image path: b57xp32.sys

Image name: b57xp32.sys

Timestamp: Mon August 23 at 17:49:29 2004 (412A 6669)

CheckSum: 00028D3C

ImageSize: 0001DA80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

b9a21000 b9a34f00 VIDEOPRT (postponed)

Image path: VIDEOPRT. SYS

Image name: VIDEOPRT. SYS

Timestamp: Sun Apr 13 14:44:39 2008 (48025497)

CheckSum: 000142CF

ImageSize: 00013F00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

b9a35000 b9bb2000 ati2mtag (postponed)

Image path: ati2mtag.sys

Image name: ati2mtag.sys

Timestamp: Thu Feb 09 21:57:44 2006 (43EC0128)

CheckSum: 00179501

ImageSize: 0017D 000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

b9cd6000 b9cda580 ptilink (postponed)

Image path: ptilink.sys

Image name: ptilink.sys

Timestamp: Fri Aug 17 16:49:53 2001 (3B7D8371)

Sum: 0000648C

ImageSize: 00004580

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

b9cde000 b9ce2a80 TDI (postponed)

Image path: TDI. SYS

Image name: TDI. SYS

Timestamp: Sun Apr 13 15:00:04 2008 (48025834)

CheckSum: 0000649E

ImageSize: 00004A 80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

ba0a0000 ba0a9f00 termdd (postponed)

Image path: termdd.sys

Image name: termdd.sys

Timestamp: Sun Apr 13 14:38:36 2008 (4802532 C)

CheckSum: 0000DEB5

ImageSize: 00009F00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

ba0b0000 ba0b8900 msgpc (postponed)

Image path: msgpc.sys

Image name: msgpc.sys

Timestamp: Sun Apr 13 14:56:32 2008 (48025760)

CheckSum: 0000DE60

ImageSize: 00008900

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

ba0c0000 ba0cbd00 raspptp (postponed)

Image path: raspptp.sys

Image name: raspptp.sys

Timestamp: Sun Apr 13 15:19:47 2008 (48025 CD 3)

CheckSum: 000188A 6

ImageSize: 0000BD00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

ba0d0000 ba0da200 raspppoe (postponed)

Image path: raspppoe.sys

Image name: raspppoe.sys

Timestamp: Sun Apr 13 14:57:31 2008 (4802579B)

Sum: 0000D 695

ImageSize: 0000A 200

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

ba0e0000 ba0ec880 rasl2tp (postponed)

Image path: rasl2tp.sys

Image name: rasl2tp.sys

Timestamp: Sun Apr 13 15:19:43 2008 (48025CCF)

CheckSum: 0000FAE5

ImageSize: 0000C 880

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

ba0f0000 ba0fa480 imapi (postponed)

Image path: imapi.sys

Image name: imapi.sys

Timestamp: Sun Apr 13 14:40:57 2008 (B 480253, 9)

CheckSum: 00014A 61

ImageSize: 0000A 480

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

ba100000 ba10e100 redbook (postponed)

Image path: redbook.sys

Image name: redbook.sys

Timestamp: Sun Apr 13 14:40:27 2008 (4802539B)

CheckSum: 0001462F

ImageSize: 0000E100

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

ba63d000 ba64c600 cdrom (postponed)

Image path: cdrom.sys

Image name: cdrom.sys

Timestamp: Sun Apr 13 14:40:45 2008 (480253AD)

CheckSum: 00018524

ImageSize: 0000F600

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

ba64d000 ba65cc00 series (postponed)

Image path: serial.sys

Image name: serial.sys

Timestamp: Sun Apr 13 15:15:44 2008 (48025BE0)

CheckSum: 00014865

ImageSize: 0000 00 FC

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

ba65d000 ba669d00 i8042prt (postponed)

Image path: i8042prt.sys

Image name: i8042prt.sys

Timestamp: Sun Apr 13 15:17:59 2008 (48025 C 67)

Checksum: 0001918C

ImageSize: 0000CD 00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

ba66d000 ba67bb00 drmk (postponed)

Image path: drmk.sys

Image name: drmk.sys

Timestamp: Sun Apr 13 14:45:12 2008 (480254B 8)

CheckSum: 0001 B 540

ImageSize: 0000EB00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

ba67d000 ba689100 STREAM (postponed)

Image path: streams. SYS

Image name: streams. SYS

Timestamp: Sun Apr 13 14:45:14 2008 (480254BA)

CheckSum: 0001B4AB

ImageSize: 0000C 100

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

ba68d000 ba695e00 intelppm (postponed)

Image path: intelppm.sys

Image name: intelppm.sys

Timestamp: Sun Apr 13 14:31:31 2008 (48025183)

Sum: 0000C 894

ImageSize: 00008E00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

badd2000 badd5c80 mssmbios (postponed)

Image path: mssmbios.sys

Image name: mssmbios.sys

Timestamp: Sun Apr 13 14:36:45 2008 (480252BD)

CheckSum: 0000FC8F

ImageSize: 00003C 80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

badfb000 badfd780 ndistapi (postponed)

Image path: ndistapi.sys

Image name: ndistapi.sys

Timestamp: Sun Apr 13 14:57:27 2008 (48025797)

CheckSum: 0000A1B3

ImageSize: 00002780

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

bae17000 bae1ad80 serenum (postponed)

Image path: serenum.sys

Image name: serenum.sys

Timestamp: Sun Apr 13 14:40:12 2008 (4802538 C)

CheckSum: 0001290A

ImageSize: 00003D 80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

bae43000 bae5cb80 Mup (postponed)

Image path: Mup.sys

Image name: Mup.sys

Timestamp: Sun Apr 13 15:17:05 (48025 31) 2008

CheckSum: 0001AB3E

ImageSize: 00019B 80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

bae5d000 bae89980 NDIS (postponed)

Image path: NDIS.sys

Image name: NDIS.sys

Timestamp: Sun Apr 13 15:20:35 (48025 03) 2008

CheckSum: 0002E181

ImageSize: 0002C 980

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

bae8a000 baf16600 Ntfs (postponed)

Image path: Ntfs.sys

Image name: Ntfs.sys

Timestamp: Sun Apr 13 15:15:49 2008 (48025BE5)

CheckSum: 0009586B

ImageSize: 0008C 600

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

baf17000 baf2d880 KSecDD (postponed)

Image path: KSecDD.sys

Image name: KSecDD.sys

Timestamp: Sun Apr 13 14:31:40 2008 (4802518 C)

CheckSum: 00025D4C

ImageSize: 00016880

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

baf3e000 baf47e80 NDProxy (postponed)

Image path: NDProxy.SYS

Image name: NDProxy.SYS

Timestamp: Sun Apr 13 14:57:28 2008 (48025798)

CheckSum: 00011DE5

ImageSize: 00009E80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

bafce000 bafdff00 sr (postponed)

Image path: sr.sys

Image name: sr.sys

Timestamp: Sun Apr 13 14:36:50 2008 (480252 2)

CheckSum: 00012604

ImageSize: 00011F00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

bafe0000 bafffb00 fltmgr (postponed)

Image path: fltmgr.sys

Image name: fltmgr.sys

Timestamp: Sun Apr 13 14:32:58 2008 (480251DA)

CheckSum: 000251BB

ImageSize: 0001FB00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

BF800000 bf9c2f80 win32k (postponed)

Image path: win32k.sys

Image name: win32k.sys

Timestamp: Fri Apr 17 08:26:26 2009 (49E87572)

CheckSum: 001C50F1

ImageSize: 001C2F80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

bf9c3000 bf9d4600 dxg (postponed)

Image path: dxg.sys

Image name: dxg.sys

Timestamp: Sun Apr 13 14:38:27 2008 (48025323)

Sum: 0001313C

ImageSize: 00011600

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

BF9D5000 bfa17000 ati2dvag (postponed)

Image path: ati2dvag.dll

Image name: ati2dvag.dll

Timestamp: Thu Feb 09 21:58:02 2006 (43EC013A)

CheckSum: 000493AB

ImageSize: 00042000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

bfa17000 bfa56000 ati2cqag (postponed)

Image path: ati2cqag.dll

Image name: ati2cqag.dll

Timestamp: Thu Feb 09 21:22:39 2006 (43EBF8EF)

CheckSum: 00044F2F

ImageSize: 0003F000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

bfa56000 bfa8c000 atikvmag (postponed)

Image path: c:\windows\system32\atikvmag.dll

Image name: c:\windows\system32\atikvmag.dll

Timestamp: Thu Feb 09 21:27:47 2006 (43EBFA23)

Checksum: 000317C 3

ImageSize: 00036000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

bfa8c000 bfd0f940 ati3duag (postponed)

Image path: ati3duag.dll

Image name: ati3duag.dll

Timestamp: Thu Feb 09 21:44:39 2006 (43EBFE17)

CheckSum: 0028EAA1

ImageSize: 00283940

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

bfd10000 bfde20c0 ativvaxx (postponed)

Image path: ativvaxx.dll

Image name: ativvaxx.dll

Timestamp: Thu Feb 09 21:39:23 2006 (43EBFCDB)

CheckSum: 000D58AB

ImageSize: 000D20C0

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

bff50000 bff52f00 TSDDD (postponed)

Image path: TSDDD.dll

Image name: TSDDD.dll

Timestamp: Sun Apr 13 20:11:25 2008 (4802A12D)

CheckSum: 0000E39C

ImageSize: 00002F00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

bffa0000 bffe5c00 ATMFD (postponed)

Image path: ATMFD. DLL

Image name: ATMFD. DLL

Timestamp: Sun Apr 13 20:09:55 2008 (4802A0D3)

CheckSum: 0004BE90

ImageSize: 00045C 00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f747f000 f748fa80 pci (postponed)

Image path: pci.sys

Image name: pci.sys

Timestamp: Sun Apr 13 14:36:43 2008 (480252BB)

CheckSum: 00015F46

ImageSize: 00010A 80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f7490000 f74bdd80 ACPI (postponed)

Image path: ACPI.sys

Image name: ACPI.sys

Timestamp: Sun Apr 13 14:36:33 2008 (480252B 1)

CheckSum: 00038955

ImageSize: 0002DD80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f74be000 f74d5880 SCSIPORT (postponed)

Image path: SCSIPORT. SYS

Image name: SCSIPORT. SYS

Timestamp: Sun Apr 13 14:40:29 2008 (4802539 D)

CheckSum: 00021101

ImageSize: 00017880

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f74d6000 f75d6000 DTAS (postponed)

Image path: c:\windows\system32\drivers\sptd.sys

Image name: c:\windows\system32\drivers\sptd.sys

Timestamp: Wed Mar 05 19:32:57 2008 (47CF3BB9)

CheckSum: 000 B 4211

ImageSize: 00100000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f75f7000 f7606100 ohci1394 (postponed)

Image path: ohci1394.sys

Image name: ohci1394.sys

Timestamp: Sun Apr 13 14:46:18 2008 (480254FA)

CheckSum: 000151B 2

ImageSize: 0000F100

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f7607000 f7614080 1394BUS (postponed)

Image path: 1394BUS. SYS

Image name: 1394BUS. SYS

Timestamp: Sun Apr 13 14:46:18 2008 (480254FA)

CheckSum: 0000F247

ImageSize: 0000D 080

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f7617000 f7620180 isapnp (postponed)

Image path: isapnp.sys

Image name: isapnp.sys

Timestamp: Sun Apr 13 14:36:40 2008 (480252B 8)

Sum: 0000D 074

ImageSize: 00009180

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f7627000 f7631580 MountMgr (postponed)

Image path: MountMgr.sys

Image name: MountMgr.sys

Timestamp: Sun Apr 13 14:39:45 2008 (48025371)

CheckSum: 0000E3AA

ImageSize: 0000A 580

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f7637000 f7643c80 VolSnap (postponed)

Image path: VolSnap.sys

Image name: VolSnap.sys

Timestamp: Sun Apr 13 14:41 2008 (480253BC)

CheckSum: 00019063

ImageSize: 0000CC80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f7647000 f764fe00 drive (postponed)

Image path: disk.sys

Image name: disk.sys

Timestamp: Sun Apr 13 14:40:46 2008 (480253AE)

Checksum: 00014C 02

ImageSize: 00008E00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f7657000 f7663180 CLASSPNP (postponed)

Image path: CLASSPNP. SYS

Image name: CLASSPNP. SYS

Timestamp: Sun Apr 13 15:16:21 2008 (48025-05)

CheckSum: 0000CA8C

ImageSize: 0000C 180

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f7667000 f766fde0 PxHelp20 (postponed)

Image path: PxHelp20.sys

Image name: PxHelp20.sys

Timestamp: Wed Jun 20 18:26 2007 (4679A 978)

CheckSum: 00015660

ImageSize: 00008DE0

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f7687000 f7696180 nic1394 (postponed)

Image path: nic1394.sys

Image name: nic1394.sys

Timestamp: Sun Apr 13 14:51:22 2008 (4802562A)

CheckSum: 0000F8AC

ImageSize: 0000F180

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f76b7000 f76c5880 usbhub (postponed)

Image path: usbhub.sys

Image name: usbhub.sys

Timestamp: Sun Apr 13 14:45:36 2008 (480254 D 0)

CheckSum: 0000FBBC

ImageSize: 0000E880

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f7707000 f770d180 PCIIDEX (postponed)

Image path: PCIIDEX. SYS

Image name: PCIIDEX. SYS

Timestamp: Sun Apr 13 14:40:29 2008 (4802539 D)

CheckSum: 00009319

ImageSize: 00006180

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f770f000 f7713d00 PartMgr (postponed)

Image path: PartMgr.sys

Image name: PartMgr.sys

Timestamp: Sun Apr 13 14:40:48 2008 (B 480253, 0)

CheckSum: 0000C1F3

ImageSize: 00004D 00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f77b7000 f77bc080 usbuhci (postponed)

Image path: usbuhci.sys

Image name: usbuhci.sys

Timestamp: Sun Apr 13 14:45:34 2008 (480254CE)

CheckSum: 0000DB34

ImageSize: 00005080

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f77bf000 f77c6600 usbehci (postponed)

Image path: usbehci.sys

Image name: usbehci.sys

Timestamp: Sun Apr 13 14:45:34 2008 (480254CE)

Checksum: 000099D 5

ImageSize: 00007600

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f77c7000 f77cf000 ctprxy2k (postponed)

Image path: ctprxy2k.sys

Image name: ctprxy2k.sys

Timestamp: Fri Aug 11 02:45:39 2006 (44DC2793)

CheckSum: 00005746

ImageSize: 00008000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f77cf000 f77d5000 kbdclass (postponed)

Image path: kbdclass.sys

Image name: kbdclass.sys

Timestamp: Sun Apr 13 14:39:46 2008 (48025372)

CheckSum: 00011FF4

ImageSize: 00006000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f77d7000 f77dca00 mouclass (postponed)

Image path: mouclass.sys

Image name: mouclass.sys

Timestamp: Sun Apr 13 14:39:47 2008 (48025373)

CheckSum: 00014EAB

ImageSize: 00005A 00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f77ff000 f7803080 raspti (postponed)

Image path: raspti.sys

Image name: raspti.sys

Timestamp: Fri Aug 17 16:55:32 2001 (3B7D84C4)

CheckSum: 000114B 1

ImageSize: 00004080

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f7832000 f7857700 dmio (postponed)

Image path: dmio.sys

Image name: dmio.sys

Timestamp: Sun Apr 13 14:44:45 2008 (4802549 D)

CheckSum: 00034FCE

ImageSize: 00025700

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f7858000 f7876880 ftdisk (postponed)

Image path: ftdisk.sys

Image name: ftdisk.sys

Timestamp: Fri August 17 16:52:41 2001 (3B7D8419)

CheckSum: 00021032

ImageSize: 0001E880

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f7877000 f7885d80 sysaudio (postponed)

Image path: sysaudio.sys

Image name: sysaudio.sys

Timestamp: Sun Apr 13 15:15:55 2008 (48025BEB)

CheckSum: 0001C7CE

ImageSize: 0000ED80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f7897000 f789a000 BOOTVID (postponed)

Image path: BOOTVID.dll

Image name: BOOTVID.dll

Timestamp: Fri Aug 17 16:49:09 2001 (3B7D8345)

CheckSum: 0000A36C

ImageSize: 00003000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f796f000 f7986900 atapi (postponed)

Image path: atapi.sys

Image name: atapi.sys

Timestamp: Sun Apr 13 14:40:29 2008 (4802539 D)

Sum: 0001CD 25

ImageSize: 00017900

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f7987000 f7988b80 kdcom (postponed)

Image path: kdcom.dll

Image name: kdcom.dll

Timestamp: Fri Aug 17 16:49:10 2001 (3B7D8346)

CheckSum: 00008311

ImageSize: 00001 B 80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f7989000 f798a100 WMILIB (postponed)

Image path: WMILIB. SYS

Image name: WMILIB. SYS

Timestamp: Fri 17 August 17:07:23 2001 (3B7D878B)

Sum: 0000D 600

ImageSize: 00001100

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f798b000 f798c580 intelide (postponed)

Image path: intelide.sys

Image name: intelide.sys

Timestamp: Sun Apr 13 14:40:29 2008 (4802539 D)

CheckSum: 0000E81D

ImageSize: 00001580

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f798d000 f798e700 dmload (postponed)

Image path: system32\drivers\dmload.sys

Image name: system32\drivers\dmload.sys

Timestamp: Fri Aug 17 16:58:15 2001 (3B7D8567)

CheckSum: 0000DC8A

ImageSize: 00001700

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f79b7000 f79b8a80 ParVdm (postponed)

Image path: ParVdm.SYS

Image name: ParVdm.SYS

Timestamp: Fri Aug 17 16:49:49 2001 (3B7D836D)

CheckSum: 0000A 855

ImageSize: 00001 has 80

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f79c1000 f79c2f00 Fs_Rec (postponed)

Image path: Fs_Rec.SYS

Image name: Fs_Rec.SYS

Timestamp: Fri Aug 17 16:49:37 2001 (3B7D8361)

CheckSum: 000079A 7

ImageSize: 00001F00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f79c3000 f79c4080 beep (postponed)

Image path: c:\windows\system32\drivers\beep.sys

Image name: c:\windows\system32\drivers\beep.sys

Timestamp: Fri Aug 17 16:47:33 2001 (3B7D82E5)

CheckSum: 0000C82C

ImageSize: 00001080

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f79c5000 f79c6080 mnmdd (postponed)

Image path: mnmdd. SYS

Image name: mnmdd. SYS

Timestamp: Fri Aug 17 16:57:28 2001 (3B7D8538)

CheckSum: 0000F3F7

ImageSize: 00001080

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f79c7000 f79c8080 RDPCDD (postponed)

Image path: system32\drivers\rdpcdd.sys

Image name: system32\drivers\rdpcdd.sys

Timestamp: Fri Aug 17 16:46:56 2001 (3B7D82C0)

CheckSum: 0000E2B7

ImageSize: 00001080

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f79d3000 f79d4100 swenum (postponed)

Image path: swenum.sys

Image name: swenum.sys

Timestamp: Sun Apr 13 14:39:52 2008 (48025378)

CheckSum: 0000383A

ImageSize: 00001100

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f79d9000 f79da380 MSPQM (postponed)

Image path: MSPQM.sys

Image name: MSPQM.sys

Timestamp: Sun Apr 13 14:39:51 2008 (48025377)

Checksum: 00006D 54

ImageSize: 00001380

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f79df000 f79e0280 USBD (postponed)

Image path: USBD. SYS

Image name: USBD. SYS

Timestamp: Fri Aug 17 17:02:58 2001 (3B7D8682)

CheckSum: 000040AF

ImageSize: 00001280

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f7a4f000 f7a4fd00 pciide (postponed)

Image path: system32\drivers\pciide.sys

Image name: system32\drivers\pciide.sys

Timestamp: Fri Aug 17 16:51:49 2001 (3B7D83E5)

CheckSum: 0000213E

ImageSize: 00000D 00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f7a73000 f7a73c00 audstub (postponed)

Image path: audstub.sys

Image name: audstub.sys

Timestamp: Fri Aug 17 16:59:40 2001 (3B7D85BC)

CheckSum: 000105B 1

ImageSize: 00000C 00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

f7b6c000 f7bde100 iaStor (postponed)

Image path: iaStor.sys

Image name: iaStor.sys

Timestamp: Tue Mar 23 15:13:55 2004 (40608 C 73)

CheckSum: 00072C3C

ImageSize: 00072100

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Unloaded modules:

9525b 000 95286000 c:\windows\system32\drivers\kmixer.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

955e4000 9560f000 c:\windows\system32\drivers\kmixer.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

975e4000 9760f000 c:\windows\system32\drivers\kmixer.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

975e4000 9760f000 c:\windows\system32\drivers\kmixer.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

975e4000 9760f000 c:\windows\system32\drivers\kmixer.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

975e0000 b 9760, 000 c:\windows\system32\drivers\kmixer.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

979c 6000 979f1000 c:\windows\system32\drivers\kmixer.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ca 985 000 985f5000 c:\windows\system32\drivers\kmixer.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

b03da000 b03db000 drmkaud.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

b0ffe000 b100b000 DMusic.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ba6bd000 ba6cb000 c:\windows\system32\drivers\swmidi.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ad4ab000 ad4ad000 splitter.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

9869b 000 986be000 aec.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ca 9, 79000 kbdhid.sys 9ca7d000

Timestamp: unavailable (00000000)

Checksum: 00000000

ad6ac000 ad6b1000 Cdaudio.SYS

Timestamp: unavailable (00000000)

Checksum: 00000000

9ca7d000 ca 9, 80000 Sfloppy.SYS

Timestamp: unavailable (00000000)

Checksum: 00000000

ad6b4000 ad6b9000 Flpydisk.SYS

Timestamp: unavailable (00000000)

Checksum: 00000000

ae12a000 ae131000 Fdc.SYS

Timestamp: unavailable (00000000)

Checksum: 00000000

Hello

Bluescreens can certainly be triggered by malware.

Download malwarebytes and scan with it, run MRT and add Prevx to be sure that he is gone. (If Rootkits run UnHackMe)

Download - SAVE - go to where you put it-right on - click RUN AS ADMIN

Malwarebytes - free
http://www.Malwarebytes.org/

Run the malware removal tool from Microsoft

Start - type in the search box-> find MRT top - right on - click RUN AS ADMIN.

You should get this tool and its updates via Windows updates - if necessary, you can download it here.

Download - SAVE - go to where you put it-right on - click RUN AS ADMIN
(Then run MRT as shown above.)

Malicious removal tool from Microsoft
http://www.Microsoft.com/downloads/details.aspx?FamilyId=AD724AE0-E72D-4F54-9AB3-75B8EB148356&displaylang=en

also install Prevx to be sure that it is all gone.

Download - SAVE - go to where you put it-right on - click RUN AS ADMIN

Prevx - Home - free - small, fast, exceptional CLOUD protection, working with other security programs. It comes
a scan only, VERY EFFICIENT, if it finds something to come back here or use Google to see how to remove.
http://www.prevx.com/

Choice of PCmag editor - Prevx-
http://www.PCMag.com/Article2/0, 2817,2346862,00.asp

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

If necessary here are some free online scanners to help the

http://www.eset.com/onlinescan/

http://www.Kaspersky.com/virusscanner

Other tests free online
http://www.Google.com/search?hl=en&source=HP&q=antivirus+free+online+scan&AQ=f&OQ=&AQI=G1

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

Also do to the General corruption of cleaning.

Run DiskCleanup - start - all programs - Accessories - System Tools - Disk Cleanup

Start - type this in the search box-> find COMMAND at the top and RIGHT CLICK – RUN AS ADMIN

Enter this at the command prompt - sfc/scannow

How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program
generates in Windows Vista cbs.log
http://support.Microsoft.com/kb/928228

Run checkdisk - schedule it to run at the next startup, then apply OK then restart your way.

How to run the check disk at startup in Vista
http://www.Vistax64.com/tutorials/67612-check-disk-Chkdsk.html

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

If we find Rootkits use this thread and other suggestions. (Run UnHackMe)

http://social.answers.Microsoft.com/forums/en-us/InternetExplorer/thread/a8f665f0-C793-441A-a5b9-54b7e1e7a5a4/

I hope this helps.

Rob - bicycle - Mark Twain said it is good.

Service: mouhid
Vendor/Product ID: 0x1532, 0x000C

pciidex.sys vista error alexoiu :

So, you installed XP on a SATA HDD on your machine, without SATA driver needed?
Can you check in BIOS the SATA setting? Is it IDE or AHCI?



Hi,

These are the current BIOS Settings:

InChip SATA Controller ( Pciidex.sys vista error SB950 South Bridge, SATA3_0-SATA3_5 connectors )
Enables or Disables integrated SATA Controller
( ( Default: Enabled ))

OnChip SATA Type ( AMD SB950 South Bridge, SATA3_0-SATA_3 connectors
Configures opening mode of the integrated SATA2_0-SATA2_3 Controller
( ( Default: Native IDE ) Allows SATA Controller to operate in Native IDE mode )
Other options are RAID and AHCI

OnChip SATA Port4/5 Type (AMD SB950 South Bridge, SATA3_4/SATA3_5 Connectors
Configurable only if OnChip SATA Type is set to RAID or ACHI. Configures operating mode of
SATA2_4/SATA2_5 Connectors
( IDE ( Default )) Disables RAID for the SATA Controller and configures the SATA Controller to PATA mode.

OnChip SATA RAID5 Support (AMD SB950 South Bridge, SATA3_0-SATA3_5 Connectors
Enables or Flexparser i/o error 1784 RAID5 Support for SATA Controller integrated in the AMD SB950 South Bridge
Default: Enabled

OnChip SATA3.0 Support
Enables or Disables SATA 6Gbs function integrated in the AMD SB950 South Bridge.
When Disabled the Controller will operate in SATA 3Gbs mode.
( Default: Enabled)

Port0 as ESP/Port1 as ESP/Port2 as ESP/Port3 as ESP
Available if OnChip SATA Type is set to AHCI. Enabled it will speed up hot plug detection of SATA Device. ( Default: Disabled )

Port4 as ESP/Port5 as ESP
Available only when OnChip SATA Type is set to ACHI, and OnChip SATA Type Port4/5 is set to As SATA Type. Enabled it will speed up hot plug connection of SATA Device.
( Default: Disabled)


Thanks,
Moonraven

 

Driver: i8042prt.sys, 1/19/2008 01:49:18, 54784 bytes

Boot critical file is corrupt: Fix for Windows Vista, 7, 8, 8.1

Get the fix for the “Boot critical file is corrupt” error for Windows Vista, Windows 7, Windows 8 and Windows 8.1

Contents

About “Boot critical file is corrupt”

The following information on this error has been compiled by NeoSmart Technologies, based on the information gathered and reported by our global network of engineers, developers, and technicians or partner organizations.

Description and Symptoms

The error messages, alerts, pciidex.sys vista error, warnings, and symptoms below are tied to this error.

Symptom 1: Startup repair fails with message “Boot critical file $file is corrupt”

The error “Boot critical file is corrupt” is displayed when Startup Repair fails to correct problems with a non-booting PC.

In particular, pciidex.sys vista error, this message indicates that Startup Repair identified that the file in question was determined to be damaged, corrupted, or infected. If you are using Startup Repair from a recovery-only CD (typically 120 – 160 MiB), it will not have the file repair option needed.

Windows uses digital signatures to identify if system files have been damaged or modified by anyone since the date Microsoft digitally “signed” the files, pciidex.sys vista error. Discrepancies in the file signature indicate that a file has been modified, pciidex.sys vista error, infected, or tampered with by unauthorized persons or software.

When attempting to use the automated repair feature of Startup Repair, it attempts to repair your PC but fails. Clicking to view the contents of Startup Repair’s “Diagnosis and repair details” reveals the error to be “Boot critical file $file is corrupt” with one or more failed repair attempts, where $file is the name of a critical system file needed for Windows to start up. Depending on the file and the exact origins of the repair CD, you may then see pciidex.sys vista error or more messages pertaining to recovery methods attempted.

Example message:

Boot critical file C:\Windows\system32\drivers\fileinfo.sys is corrupt Repair action: File repair Result: Failed. Error code = 0xa Time taken = <i>pciidex.sys vista error</i> ms Repair action: System Restore. Result: Failed. Error Code = 0x1f

Test Performed: --------------------------- Name: System boot log diagnosis Result: Completed successfully. Error code =  0x0 Time taken = 0 ms Root cause found: --------------------------- Boot critical file C:\Windows\system32\drivers\fileinfo.sys is corrupt Repair action: File repair Result: Failed. Error code = 0xa Time taken = 1529 ms Repair action: System Restore. Result: Failed. Error Code = 0x1f Repair action: System files integrity check and repair. Result: Failed. Error Code = 0x490

Known files affected

As mentioned above, the error “Boot critical file is corrupt” is not limited to a single system file. Pciidex.sys vista error field technicians have identified that this error could present itself with any of the following files, pciidex.sys vista error, amongst others:

  • C:\CI.dll
  • C:\Windows\system32\ntoskrnl.exe
  • C:\Windows\system32\ntkrnlpa.exe
  • C:\Windows\system32\kdcom.dll
  • C:\Windows\system32\drivers\fileinfo.sys
  • C:\Windows\system32\drivers\vmbus.sys
  • C:\Windows\system32\drivers\megasr.sys
  • C:\Windows\system32\drivers\iastor.sys
  • C:\Windows\system32\drivers\sshrmd.sys
  • C:\Windows\system32\drivers\atapi.sys
  • C:\Windows\system32\drivers\compbatt.sys
  • C:\Windows\system32\drivers\ecache.sys
  • C:\Windows\system32\drivers\hal.dll
  • C:\Windows\system32\drivers\intelide.sys
  • C:\Windows\system32\drivers\aswvmm.sys
  • C:\Windows\system32\drivers\acpi.sys
  • C:\Windows\system32\drivers\tpm.sys
  • C:\Windows\system32\drivers\tcpip.sys

The list above is not exhaustive and this error may appear with files other than those mentioned above.

Causes of this Error

This error has been known to occur as a result of one or more of the following:

Cause 1: Corrupt Windows volume

Corruption of the system partition on a Windows PC can cause this error to present.

If the drive Windows is installed to suffers filesystem corruption for any reason (e.g. unsafe shutdown, sudden power loss, etc.) the data on the drive may no longer be read correctly and will trigger the above integrity alert.

Corruption of the boot partition is known to occur on both NTFS and FAT32 partitions.

Cause 2: Corruption of system files

The files named above (and other files in the \Windows\system32\ directory) are critical components of Windows. If the files are inadvertently replaced or overwritten by other data due to bugs in recently installed computer software or due to user error (for example, during system backup), the “boot critical file is error” may present.

Cause 3: Virus infection

If a Windows computer has become infected by a virus, it may attempt to inject itself or other malicious code into one or more critical system files. Corruption of any of the digitally signed drivers or libraries (files with extensions .sys or .dll) can cause your PC to fail to boot and this error to be shown by Startup Repair. Of particular note is that viruses may infect/inject a file that is not a critical Windows system/boot file and then set up your PC to load this file on boot. For example, any “boot critical file is corrupt” errors indicating a corrupt C:\CI.dll are guaranteed to be the result of system infection pciidex.sys vista error this file is not normally part of the Windows startup process.

Cause 4: Rootkits

Viruses, spyware, or other malware on your PC as well as DRM software attempting to prevent copyright infringement and IP violation may patch or modify core system files in an attempt to cloak their existence from antivirus or encryption circumvention software on your PC. Changes to core system files for this or any other reason will trigger the “Critical boot file is corrupt” error.

Fixing “Boot critical file is corrupt” on Windows

Windows Setup CD/DVD Required!
Some of the solutions below require the use of the Microsoft Windows setup CD or DVD. If your PC did not come with a Windows installation disc or if you no longer have your Windows setup media, you can use Easy Recovery Essentials for Windows instead. EasyRE will automatically find and fix many problems, and can also be used orcad 15.7 crack error solve this problem with the directions below.

Fix #1: Scan the Windows drive for corruption

The command line tool ships with Windows and can be used to check (and sometimes repair) your drives for filesystem corruption. More information about how chkdsk operates and how it works can be found in our knowledgebase. The following steps will launch the command line option from Startup Repair on the Windows setup disc and use the chkdsk utility.

Unable to boot into the Windows setup CD?
See our guide on setting up a PC to boot from the CD or DVD for c# process error and more detailed instructions.

  1. Insert your Windows installation DVD into your PC’s CD-ROM drive,
  2. Fully power down your PC, and make sure it has fully shut off,
  3. Power up your PC,
  4. Press any key when you see “Press any key to boot from CD or DVD.”
  5. Click the link titled “Repair pciidex.sys vista error computer” in the bottom-lefthand corner, after first selecting your language and keyboard options.
    Windows 7 setup Install Now dialog, with repair your computer link
  6. Wait for Startup Repair to scan your PC for Windows installations, then select your install from the list it pciidex.sys vista error alt="Startup repair lists available operating systems to repair." src="https://i0.wp.com/neosmart.net/wiki/wp-content/uploads/sites/5/2013/10/Select-Windows-OS-to-repair.png?resize=300%2C227&is-pending-load=1#038;ssl=1" width="300" height="227">
  7. Choose “Command Prompt” from the list of available recovery options to begin:
    Startup Repair lists all available recovery options, choose a recovery tool

Once the command prompt is launched, enter the following to use the System File Checker to check your installation for corrupted, invalid, or deleted system files. If the previous page showed that your Windows installation has a drive letter other than C:\, make sure to use that below!

chkdsk C: /f

chkdsk will begin scanning your drive for problems, fixing them if it is able to, and reporting its progress when done.

Checking file system on C: The type of the file system is NTFS. Volume label is Windows 7, pciidex.sys vista error. CHKDSK is verifying files (stage 1 of 5). 259072 file records processed.  . Windows has finished checking your disk.

Fix #2: Scan for viruses with Easy Recovery Essentials

The Professional Edition of Easy Recovery Essentials for Windows features a powerful antivirus and rootkit scanner that can normally resolve this and similar errors caused by viruses, rootkits, trojans, or spyware. EasyRE is currently available for Windows XP, Vista, 7 and 8 and can be downloaded and created on any PC.

  1. Download Easy Recovery Essentials, pciidex.sys vista error. Make sure to note your Windows version (XP, Vista, 7 or 8) before you download EasyRE. This guide can help you identify what version of Windows you have installed. For the purposes of this guide, you will need to obtain the Professional Edition of EasyRE.
  2. Burn the pciidex.sys vista error. Follow these instructions on how to burn the bootable ISO image very carefully, as making a bootable CD can be tricky! Alternatively, pciidex.sys vista error, these instructions explain how pciidex.sys vista error create a bootable EasyRE recovery USB pciidex.sys vista error up your PC from the Easy Recovery Essentials CD or USB you created.
  3. Once EasyRE is running, choose the “Virus Cod2 directx unrecoverable error fix option and click .
    EasyRE Home

    Choose “Virus Scanner” in Easy Recovery Essentials

  4. After EasyRE scans your computer’s drives, identify and select the drive letter for your Windows installation from the list, and then click on the  button to begin.
    EasyRE listing available drives for antivirus scan

    Choose the drive associated with the Windows 3d studio max out memory error you’re trying to repair.

  5. EasyRE will begin scanning the drive for viruses, rootkits, trojans, spyware, and other unwanted malware on your machine. No intervention is required, pciidex.sys vista error, and EasyRE will repair viruses as it finds them, reporting its progress as it goes along:
    EasyRE: Automated Repair

    Easy Recovery Essentials searches for viruses and cleans infections on the selected Windows installation.

  6. Once the process is complete, EasyRE will report its findings. Click on the  button to reboot your PC and test the changes.

You can download Easy Recovery Essentials from here.

Fix #3: Scan for corrupted files

Windows ships with a tool called sfc, which stands for the System File Checker, pciidex.sys vista error. More information about how sfc operates and when to use it can be found in our knowledgebase. The following steps will launch the command line option from Startup Repair on the Windows setup disc and use the system file checker to attempt a repair of your PC.

  1. Insert your Windows installation DVD into your PC’s CD-ROM drive,
  2. Fully power down your PC, pciidex.sys vista error make sure it has fully shut off,
  3. Power up your PC,
  4. Press any key when you see “Press any key to boot from CD or DVD.”
  5. Click the link titled “Repair your computer” in the bottom-lefthand corner, after first selecting your language and keyboard options.
    Windows 7 setup Install Now dialog, with repair your computer link
  6. Wait for Startup Repair to scan your PC for Windows installations, then select your install from the list it shows:
    Startup repair lists available operating systems to repair.
  7. Choose “Command Prompt” from the list of available recovery options to begin:
    Startup Repair lists all available recovery options, choose a recovery tool

Once the command prompt is launched, enter the following to use the System File Checker to check your installation for corrupted, invalid, or deleted system files. If the previous page showed that your Windows installation has a drive letter other than C:\, make sure to use that below!

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Once sfc has completed its scan, it will report its results like below:

Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% completed. Windows Resource Searchprotocolhost.exe windows 7 application error found corrupt files and successfully repaired them. OR Windows Resource Protection found corrupt files but was unable to asus cpu ucode loading error rus some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log

More Information

Linked Entries

Support Links

Applicable Systems

This Windows-related knowledgebase article applies to the following operating systems:

  • Windows Vista (all editions)
  • Windows 7 (all editions)
  • Windows 8 (all editions)
  • Windows 8.1 (all editions)
  • Windows Server 2008 (all editions)
  • Windows Server 2012 (all editions)

Propose an edit

Windows Boot Failed

So yesterday I was on my Dell computer (Vista SP2). Everything was fine, there were no problems or changes, nothing. I tried turning on my computer today and it stops at the "Windows Boot Manager." This is the message it came up with:

Windows failed to start. A recent hardware or software change might be the case. To fix the problem:
1. Insert your Windows Installation disc and restart your computer.
2. Choose your language settings, and then click "Next."
3. Click "Repair your computer."

File: PCIIDEX.sys
Status: 0x00000e9
Info: Windows failed to load because a required file is missing, or corrupt.


[*Note I can't get into safemode] I tried everything I know to fix it with the original disc. I tried a System Restore, but unfortunately that was disable (I thought I had enabled), a Startup Repair (which found a problem but couldn't fix it), Windows Complete PC Restore (Which couldn't find a backup image), pciidex.sys vista error. I also tried booting from the operating system on the CD itself and I got this message when trying to fix it:

C:\PCIIDEX.SYS is corrupt.

c:\windows\system32\drivers\pciide.sys is corrupt.

Error code:0x2


I even did a Dell Diagnosis which is installed by default on the hardrive and it came up with this error, but I don't even think it has anything to do with my real problem:

** Hard Drive - DST Short Test **
Test Results: Fail
Error Code 2000-0142
Msg: Hard Drive 0 - self test unsuccessful. Status: 79


If there is anything I can do or any step I can take please let me know. I tried searching all over for solutions but obviously I did not succeed with that. My only option left is to completely format my hardrive and reinstall Windows Vista, which I do not want to do at all, pciidex.sys vista error. Thanks! networkerror 500 internal server error - http

Pciidex.sys vista error - agree

Driver: kbdclass.sys, 1/19/2008 03:41:52, 35384 bytes
Service: TermDD
Driver: kbdhid.sys, 4/11/2009 00:38:40, 17408 bytes

Boot critical file is corrupt: Fix for Windows Vista, 7, 8, 8.1

Get the fix for the “Boot critical file is corrupt” error for Windows Vista, Windows 7, Windows 8 and Windows 8.1

Contents

About “Boot critical file is corrupt”

The following information on this error has been compiled by NeoSmart Technologies, based on the information gathered and reported by our global network of engineers, developers, and technicians or partner organizations.

Description and Symptoms

The error messages, alerts, warnings, and symptoms below are tied to this error.

Symptom 1: Startup repair fails with message “Boot critical file $file is corrupt”

The error “Boot critical file is corrupt” is displayed when Startup Repair fails to correct problems with a non-booting PC.

In particular, this message indicates that Startup Repair identified that the file in question was determined to be damaged, corrupted, or infected. If you are using Startup Repair from a recovery-only CD (typically 120 – 160 MiB), it will not have the file repair option needed.

Windows uses digital signatures to identify if system files have been damaged or modified by anyone since the date Microsoft digitally “signed” the files. Discrepancies in the file signature indicate that a file has been modified, infected, or tampered with by unauthorized persons or software.

When attempting to use the automated repair feature of Startup Repair, it attempts to repair your PC but fails. Clicking to view the contents of Startup Repair’s “Diagnosis and repair details” reveals the error to be “Boot critical file $file is corrupt” with one or more failed repair attempts, where $file is the name of a critical system file needed for Windows to start up. Depending on the file and the exact origins of the repair CD, you may then see one or more messages pertaining to recovery methods attempted.

Example message:

Boot critical file C:\Windows\system32\drivers\fileinfo.sys is corrupt Repair action: File repair Result: Failed. Error code = 0xa Time taken = 1529 ms Repair action: System Restore. Result: Failed. Error Code = 0x1f

Test Performed: --------------------------- Name: System boot log diagnosis Result: Completed successfully. Error code =  0x0 Time taken = 0 ms Root cause found: --------------------------- Boot critical file C:\Windows\system32\drivers\fileinfo.sys is corrupt Repair action: File repair Result: Failed. Error code = 0xa Time taken = 1529 ms Repair action: System Restore. Result: Failed. Error Code = 0x1f Repair action: System files integrity check and repair. Result: Failed. Error Code = 0x490

Known files affected

As mentioned above, the error “Boot critical file is corrupt” is not limited to a single system file. Our field technicians have identified that this error could present itself with any of the following files, amongst others:

  • C:\CI.dll
  • C:\Windows\system32\ntoskrnl.exe
  • C:\Windows\system32\ntkrnlpa.exe
  • C:\Windows\system32\kdcom.dll
  • C:\Windows\system32\drivers\fileinfo.sys
  • C:\Windows\system32\drivers\vmbus.sys
  • C:\Windows\system32\drivers\megasr.sys
  • C:\Windows\system32\drivers\iastor.sys
  • C:\Windows\system32\drivers\sshrmd.sys
  • C:\Windows\system32\drivers\atapi.sys
  • C:\Windows\system32\drivers\compbatt.sys
  • C:\Windows\system32\drivers\ecache.sys
  • C:\Windows\system32\drivers\hal.dll
  • C:\Windows\system32\drivers\intelide.sys
  • C:\Windows\system32\drivers\aswvmm.sys
  • C:\Windows\system32\drivers\acpi.sys
  • C:\Windows\system32\drivers\tpm.sys
  • C:\Windows\system32\drivers\tcpip.sys

The list above is not exhaustive and this error may appear with files other than those mentioned above.

Causes of this Error

This error has been known to occur as a result of one or more of the following:

Cause 1: Corrupt Windows volume

Corruption of the system partition on a Windows PC can cause this error to present.

If the drive Windows is installed to suffers filesystem corruption for any reason (e.g. unsafe shutdown, sudden power loss, etc.) the data on the drive may no longer be read correctly and will trigger the above integrity alert.

Corruption of the boot partition is known to occur on both NTFS and FAT32 partitions.

Cause 2: Corruption of system files

The files named above (and other files in the \Windows\system32\ directory) are critical components of Windows. If the files are inadvertently replaced or overwritten by other data due to bugs in recently installed computer software or due to user error (for example, during system backup), the “boot critical file is error” may present.

Cause 3: Virus infection

If a Windows computer has become infected by a virus, it may attempt to inject itself or other malicious code into one or more critical system files. Corruption of any of the digitally signed drivers or libraries (files with extensions .sys or .dll) can cause your PC to fail to boot and this error to be shown by Startup Repair. Of particular note is that viruses may infect/inject a file that is not a critical Windows system/boot file and then set up your PC to load this file on boot. For example, any “boot critical file is corrupt” errors indicating a corrupt C:\CI.dll are guaranteed to be the result of system infection as this file is not normally part of the Windows startup process.

Cause 4: Rootkits

Viruses, spyware, or other malware on your PC as well as DRM software attempting to prevent copyright infringement and IP violation may patch or modify core system files in an attempt to cloak their existence from antivirus or encryption circumvention software on your PC. Changes to core system files for this or any other reason will trigger the “Critical boot file is corrupt” error.

Fixing “Boot critical file is corrupt” on Windows

Windows Setup CD/DVD Required!
Some of the solutions below require the use of the Microsoft Windows setup CD or DVD. If your PC did not come with a Windows installation disc or if you no longer have your Windows setup media, you can use Easy Recovery Essentials for Windows instead. EasyRE will automatically find and fix many problems, and can also be used to solve this problem with the directions below.

Fix #1: Scan the Windows drive for corruption

The command line tool ships with Windows and can be used to check (and sometimes repair) your drives for filesystem corruption. More information about how chkdsk operates and how it works can be found in our knowledgebase. The following steps will launch the command line option from Startup Repair on the Windows setup disc and use the chkdsk utility.

Unable to boot into the Windows setup CD?
See our guide on setting up a PC to boot from the CD or DVD for troubleshooting and more detailed instructions.

  1. Insert your Windows installation DVD into your PC’s CD-ROM drive,
  2. Fully power down your PC, and make sure it has fully shut off,
  3. Power up your PC,
  4. Press any key when you see “Press any key to boot from CD or DVD..”
  5. Click the link titled “Repair your computer” in the bottom-lefthand corner, after first selecting your language and keyboard options.
    Windows 7 setup Install Now dialog, with repair your computer link
  6. Wait for Startup Repair to scan your PC for Windows installations, then select your install from the list it shows:
    Startup repair lists available operating systems to repair.
  7. Choose “Command Prompt” from the list of available recovery options to begin:
    Startup Repair lists all available recovery options, choose a recovery tool

Once the command prompt is launched, enter the following to use the System File Checker to check your installation for corrupted, invalid, or deleted system files. If the previous page showed that your Windows installation has a drive letter other than C:\, make sure to use that below!

chkdsk C: /f

chkdsk will begin scanning your drive for problems, fixing them if it is able to, and reporting its progress when done.

Checking file system on C: The type of the file system is NTFS. Volume label is Windows 7. CHKDSK is verifying files (stage 1 of 5)... 259072 file records processed.  .... Windows has finished checking your disk.

Fix #2: Scan for viruses with Easy Recovery Essentials

The Professional Edition of Easy Recovery Essentials for Windows features a powerful antivirus and rootkit scanner that can normally resolve this and similar errors caused by viruses, rootkits, trojans, or spyware. EasyRE is currently available for Windows XP, Vista, 7 and 8 and can be downloaded and created on any PC.

  1. Download Easy Recovery Essentials. Make sure to note your Windows version (XP, Vista, 7 or 8) before you download EasyRE. This guide can help you identify what version of Windows you have installed. For the purposes of this guide, you will need to obtain the Professional Edition of EasyRE.
  2. Burn the image. Follow these instructions on how to burn the bootable ISO image very carefully, as making a bootable CD can be tricky! Alternatively, these instructions explain how to create a bootable EasyRE recovery USB stick/drive.
  3. Boot up your PC from the Easy Recovery Essentials CD or USB you created.
  4. Once EasyRE is running, choose the “Virus Scanner” option and click .
    EasyRE Home

    Choose “Virus Scanner” in Easy Recovery Essentials

  5. After EasyRE scans your computer’s drives, identify and select the drive letter for your Windows installation from the list, and then click on the  button to begin.
    EasyRE listing available drives for antivirus scan

    Choose the drive associated with the Windows installation you’re trying to repair.

  6. EasyRE will begin scanning the drive for viruses, rootkits, trojans, spyware, and other unwanted malware on your machine. No intervention is required, and EasyRE will repair viruses as it finds them, reporting its progress as it goes along:
    EasyRE: Automated Repair

    Easy Recovery Essentials searches for viruses and cleans infections on the selected Windows installation.

  7. Once the process is complete, EasyRE will report its findings. Click on the  button to reboot your PC and test the changes.

You can download Easy Recovery Essentials from here.

Fix #3: Scan for corrupted files

Windows ships with a tool called sfc, which stands for the System File Checker. More information about how sfc operates and when to use it can be found in our knowledgebase. The following steps will launch the command line option from Startup Repair on the Windows setup disc and use the system file checker to attempt a repair of your PC.

  1. Insert your Windows installation DVD into your PC’s CD-ROM drive,
  2. Fully power down your PC, and make sure it has fully shut off,
  3. Power up your PC,
  4. Press any key when you see “Press any key to boot from CD or DVD..”
  5. Click the link titled “Repair your computer” in the bottom-lefthand corner, after first selecting your language and keyboard options.
    Windows 7 setup Install Now dialog, with repair your computer link
  6. Wait for Startup Repair to scan your PC for Windows installations, then select your install from the list it shows:
    Startup repair lists available operating systems to repair.
  7. Choose “Command Prompt” from the list of available recovery options to begin:
    Startup Repair lists all available recovery options, choose a recovery tool

Once the command prompt is launched, enter the following to use the System File Checker to check your installation for corrupted, invalid, or deleted system files. If the previous page showed that your Windows installation has a drive letter other than C:\, make sure to use that below!

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Once sfc has completed its scan, it will report its results like below:

Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% completed. Windows Resource Protection found corrupt files and successfully repaired them. OR Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log

More Information

Linked Entries

Support Links

Applicable Systems

This Windows-related knowledgebase article applies to the following operating systems:

  • Windows Vista (all editions)
  • Windows 7 (all editions)
  • Windows 8 (all editions)
  • Windows 8.1 (all editions)
  • Windows Server 2008 (all editions)
  • Windows Server 2012 (all editions)

Propose an edit

Service: TermDD

alexoiu :

So, you installed XP on a SATA HDD on your machine, without SATA driver needed?
Can you check in BIOS the SATA setting? Is it IDE or AHCI?



Hi,

These are the current BIOS Settings:

InChip SATA Controller ( AMD SB950 South Bridge, SATA3_0-SATA3_5 connectors )
Enables or Disables integrated SATA Controller
( ( Default: Enabled ))

OnChip SATA Type ( AMD SB950 South Bridge, SATA3_0-SATA_3 connectors
Configures opening mode of the integrated SATA2_0-SATA2_3 Controller
( ( Default: Native IDE ) Allows SATA Controller to operate in Native IDE mode )
Other options are RAID and AHCI

OnChip SATA Port4/5 Type (AMD SB950 South Bridge, SATA3_4/SATA3_5 Connectors
Configurable only if OnChip SATA Type is set to RAID or ACHI. Configures operating mode of
SATA2_4/SATA2_5 Connectors
( IDE ( Default )) Disables RAID for the SATA Controller and configures the SATA Controller to PATA mode.

OnChip SATA RAID5 Support (AMD SB950 South Bridge, SATA3_0-SATA3_5 Connectors
Enables or Disables RAID5 Support for SATA Controller integrated in the AMD SB950 South Bridge
Default: Enabled

OnChip SATA3.0 Support
Enables or Disables SATA 6Gbs function integrated in the AMD SB950 South Bridge.
When Disabled the Controller will operate in SATA 3Gbs mode.
( Default: Enabled)

Port0 as ESP/Port1 as ESP/Port2 as ESP/Port3 as ESP
Available if OnChip SATA Type is set to AHCI. Enabled it will speed up hot plug detection of SATA Device. ( Default: Disabled )

Port4 as ESP/Port5 as ESP
Available only when OnChip SATA Type is set to ACHI, and OnChip SATA Type Port4/5 is set to As SATA Type. Enabled it will speed up hot plug connection of SATA Device.
( Default: Disabled)


Thanks,
Moonraven

 


+ HID-compliant mouse
pciidex.sys vista error

Related Videos

This serious issue was a simple fix... Here's how!

1 Comments

Leave a Comment