InDesign CC crash with blue screen at startup to the top
HY Forum!
I just bought the full version of Adobe CC a few weeks ago. Adobe Audition/first/Media encode/Photoshop works very well. But if I want to run Adobe InDesign CC I instantly get a screen blue, followed by a restart of the automatic system. It happens every time after about one minute after the launch of the program, even when I do absolutely anything in InDesign and leave the portion of the mouse. It is a time-related system crash. According to me, InDesign tries to load something in the background, after commissioning and crashes more. But that's just a guess... I have attached a picture of the error massage and a screenshot of my system specs.
Maybe someone can help here. As I said, the work of other programms all well.
Greetings from Germany, Maik
System specs
Hallo Maik,
It seems that you have and with a ci.dll error that appears in you Blue error screen.
When you google for it, you have found the number of entries. Some entries show that this ci.dll is a problem with a rootkit or virus.
[SOLVED] C:/ci.dll boot critical file is damaged - Tech Support Forum
Start the file review corrupt c:\\ci.dll - HELP! Resolved - Windows 7 Help Forums
Its is not clear why indesign causes the blue screen, but your blue screen display this file.
Alternatively, you can check this with a blue screen reader.
I'm sorry.
Tags: InDesign
Similar Questions
-
When I use internet through Wi - Fi some message crash put in time with blue screen (driver_irql_not_less_or_equal (rtwlane.sys), my adapter Wi - Fi is Realtek RTL8723BE 802.11bgn (new version) how can I solve this problem? please help me...)
Wireless 802.11b/g/n Realtek RTL8723BE/RTL8188EE LAN drivers
By downloading, you accept the terms and conditions of the license agreement for the HP software.
Note: Some software requires a valid warranty, current support contract HP or a fee.Type: Driver - network Version: 2023.9.401.2015 Rev.A (21 may 2015) System: Microsoft Windows 8.1 (64-bit) | See all Name of the file: sp71432.exe (35 MB) -
VAIO will not boot xp. Crashes with blue screen error.
VAIO will not boot xp.
Sony Vaio PCG - 691L
XP, installed at the factory has SP3 update..5gig ram
I worked on the machine to get to start XP. Sometimes it will boot in Safe Mode, but most of the time (and when it does not start in 'normal' mode), it crashes with a blue screen. The blue screen flashes fast to read, and then the machine tries to restart.
Once I do start safe mode and got WIndows update but can't update due to the update that needs to be in normal mode.
I was able to install Malwarebytes and a full scan. Also installed Spybot S & D and performed a full scan.When it does not start in normal mode it is slow, very slow. I tried rkill and it causes the machine down.
It starts in normal mode today, but it crashed before I can get open IE and go to the windows update.
Help...
Thank you
Rick
Tired of playing with this. Re-install xp.
Thank you...
-
Windows Vista crashes with blue screen
My computer dell laptop crashed with the blue screen.
I tried to restart and log in on my windows account. As you move the cursor to enter my password, it crashes every time.
That's why I tried to reinstall windows Vista by using the dell windows vista installation disc provided with the laptop. Everything went well, but in the end, it came with the message "Windows could not update registry data in the installation."
Hello
Check with Dell Support, their drivers and documentation online and ask in the Dell forums for known issues.
Dell support
http://support.Dell.com/Dell support drivers - product manual & warranty Info (left side) - and much more
http://support.Dell.com/support/index.aspx?c=us&l=en&s=DHSDell forums
http://en.community.Dell.com/forums/
==========Check this thread for more information using BlueScreenView, MyEventViewer and other methods
to troubleshoot the BlueScreens - top 3 responses (+ 1 other).We can analyze the minidumps if make you it available to the SkyDrive or another file
sharing sites.ZIP or download the content of the C:\Windows\minidump
Use SkyDrive to upload collected files
http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65-------------------------------------------------------------------------
Also this, so you can see the probable bluescreens.
Windows Vista restarts automatically if your computer encounters an error that requires him to plant.
(also Windows 7)
http://www.winvistatips.com/disable-automatic-restart-T84.html===========================================================
Check out these utilities to see if information may be collected:
It is an excellent tool for displaying the blue screen error information
-Free - BlueScreenView scans all your minidump files created during "blue screen of death," collisions
and displays information about all accidents of a table.
http://www.NirSoft.NET/utils/blue_screen_view.html-------------
MyEventViewer can be verified at the time of the blue screen (BSOD) within a second or so of the
time of the BSOD to provide more information about the possible cause - see TIP.MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
TIP - Options - Advanced filter allows you to see a period of time instead of the whole of the record-
Set it for a bit before and after the time of the BSOD.
http://www.NirSoft.NET/utils/my_event_viewer.html------------
AppCrashView - free - a small utility for Windows Vista and Windows 7 that displays the details of all the
application goes down has occurred in your system. The information breaks down is extracted from the .wer
the files created by the Windows Error Reporting (WER) of the operating system component of each
time that an accident has occurred. AppCrashView also allows you to easily record the list of accidents to
text/html/csv/xml file.
http://www.NirSoft.NET/utils/app_crash_view.htmlI hope this helps.
-
Vista sp2 crash with blue screen
I loaded on my hp Pavilion dv6000 vista sp2 and it works very well for a few minutes, but then it crashes with showed a blue screen with something written on it and its too fast to be read
In the control panel choose reports on problems and Solutions ( problem in the START search box type), go to historical problem, right click on your error and choose check for the Solution. You can also examine the details.
In administrative tools choose reliability and performance monitor and click on MonitoringTools then the reliability monitor (type reliability in research on Start). This list is a chart of the software installs, uninstalls, updated Windows and crashes by date. See if your plant has started to happen after you installed or uninstalled something.
It may be useful to eliminate equipment defects
Type of memory in the search box of start and choose Memory diagnosis
In a command prompt (type command in the start search box then right click and choose Run as administrator) type
CHKDSK c: /r
If you have more than one drive replace C: with the other drive letters.
Search for corrupted files by typing at the command prompt
sfc/scannow
You can perform a clean boot to determine if background programs interfere with your game or program
http://support.Microsoft.com/kb/331796 >
How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
http://support.Microsoft.com/kb/929135>
06/12 / 1110:21: 43 am
-
Qosimio G30-116 with blue screen at startup
I have a bunch of dule Qosmio-Qosmio G30-116 of the start-up in windows generates a blue screen of death, which is quickly erased before I can read what is displayed.
It starts in windows safe mode results in a long list of files displayed the last being Mup.sysBoot Linux and execution of everything I can think off generate no error.
Connecting the edge dignostics Toshiba BIOS does not generate an error.
Runs the check memory linux does not generate an error.
Display of the file system does not generate an error.
So I don't think I have a hardware problem, I think that something comes with windows
Does anyone have an idea how to stop my erasing of the screen so I could real know what the problem is?
There are a lot of valuable software on this machine, I didn't want to trash the entire disk to try to repair what seems to be a specific windows problem.
Hello
I think that the BSOD screen information would be very useful for you. The BSOD shows above all a memory dump that is not obvious to a common user.
Another user has already proposed the question could be linked to the installed windows OS.
I think he do not since then to study for a long time, who knows what unique application or which parts of Windows cause this problemYou can try to use the freeware application called CCleaner which may help you clean up the operating system and the registry. This tool helped me in different cases
But if the BSODS persist then a new install of Windows can help.
-
Windows Vista keeps crashing with blue screen errors when I play
My windows is crashing for some reason and I can't understand what it is, I have everything updated, the error is as follows:
Problem event name: BlueScreen
Versão SO: 6.0.6002.2.2.0.768.3
Region ID: 2070Peruano problem details:
BCCode: 116
BCP1: 87CDC250
BCP2: 8FE2EAFA
BCP3: 00000000
BCP4: 00000002
OS version: 6_0_6002
Service Pack: 2_0
Product: 768_1Records strategies help the problem:
C:\Windows\Minidump\Mini081312-01.dmp
C:\Users\Badnature\AppData\Local\Temp\WER-108623-0.SysData.XML
C:\Users\Badnature\AppData\Local\Temp\WERB588.tmp.version.txtLeia a nossa privacidade declaracao:
http://go.Microsoft.com/fwlink/?LinkId=50163&clcid=0x0816I'd really aprecciate help, thank you for your time
Hello
The basic definition of a bugcheck 0 x 116 is:
There may be a bug in the video driver or video material.
So I would now explain what means VIDEO_TDR_ERROR. Firstly, TDR is an acronym for Timeout detection and recovery. Detection time and recovery was introduced in Vista and carried over to Windows 7. Rather than exactly what detection time and recovery did exactly, I'll just quote the MSDN article!
Timeout detection:
Planner of the GPU, which is part of the DirectX Graphics kernel subsystem (Dxgkrnl.sys), detects that the GPU takes more than the amount of time to perform a particular task. The GPU scheduler then attempts to anticipate on this particular task. Preempt is a timeout 'wait', which is the actual time of TDR. This step is the detection of delay of the process phase. The period of default timeout in Windows Vista and later versions is 2 seconds. If the GPU cannot complete or anticipate the current task period TDR, the diagnostic operating system that the GPU is frozen.
To avoid detection of timeout to occur, hardware vendors should ensure that graphics operations (i.e. buffer DMA completion) will not take more than 2 seconds in scenarios such as productivity and the game to the end user.Preparation for recovery:
The operating system GPU Scheduler calls the function DxgkDdiResetFromTimeout of the miniport driver of the display to inform the driver that the operating system detected a timeout. The pilot must then resets and reset the GPU. In addition, the driver must stop access to memory and go not material. The operating system and the driver collect material and other State information that might be useful for post-mortem diagnosis.
Recovery of funds:
The operating system resets the State appropriate graphics stack. The video memory manager, which is also part of Dxgkrnl.sys, serving all allocations of video memory. The miniport display driver resets the State of the GPU hardware. The graphics stack takes the final steps and restores the receptive office. As mentioned previously, some older DirectX applications could make only in black at the end of this recovery, which requires the user to restart these applications. Well-written 9Ex, DirectX and DirectX 10 and subsequent applications which manage peripheral technology delete continue to function correctly. An application must release and then recreate the Direct3D device and all the objects in the device. For more information on how get the DirectX applications, see the Windows SDK.
That being said, if the detection time and recovery fails to retrieve the display driver, it will then pull the bugcheck 0 x 116. There are many different things that can cause a 0 x 116, which I'll explain below:
The following hardware problems may cause a TDR event:
1 unstable overclock (CPU, GPU, etc.). Return any overclocks to stock settings.
2 bad sector in memory, resulting in corrupted data is communicated between the GPU and system (memory video, otherwise known as VRAM or physical memory, also called RAM).
GPU tests: Furmark
RAM test: Memtest86 +.
3 corrupt hard drive or install Windows / OS install resulting in corruption in the registry or the page file.
HARD drive Diagnostics: http://www.carrona.org/hddiag.html
To reset your swap file, follow these steps:
(a) go to start... Run... and type "sysdm.cpl" (without the quotes) and press ENTER.
-Then click on the Advanced tab.
- then the Performance Settings button.
- then on the tab advanced following.
-and then click the virtual memory button.(b) in this window, note the current settings of your swap file (so you can restore them later).
-Then click on the option button "No paging file", and
- Press the Set"" button. Don't forget, if you have several hard drives, make sure that the paging file is set to 0 on all of them.
-Click OK to exit the dialog boxes.(c) restarted (this will remove the file from your system)
((d) then go back following the directions in step one) and re-enter the settings that you noted in step
(b) follow the steps along the (and including) the reset.
(e) once you have restarted this second time, go back and make sure the settings are as they are supposed to be.
Run the System File Checker:
SFC. EXE/SCANNOW
Click on start and type "cmd.exe" (without the quotes)
At the top of the search box, right-click on the cmd.exe and select "Run as Administrator"
In the black window that opens, type "SFC. EXE/scannow"(without the quotes) and press ENTER.
Let the program run and after return what he says when it's done.
-Overheating of the CPU or GPU and or other elements can cause 0 x 116 bugs. Monitor your temperature and ensure that the system is sufficiently cooled.
-GPU failure. Whether the heat, power (PSU) issue, lack of VRAM, etc..
The following software issues can cause a TDR event:
-Incompatible drivers of any kind (two GPU, sound, etc)
-Messy registry / corrupted
-DirectX bad files (uninstall and reinstall DirectX)
-bad system files (System File Checker - has been run on it)
-Bad driver (some drivers will cause an event due to internal bugs, but they are not nearly as common as many think because of all the previous things, causing the same symptom) - (remove all 3rd party programs and make sure that are not load drivers. Then install only what you need 3rd party stuff and make sure it is the latest version).
Kind regards
Patrick
-
HP Envy: a blue screen at startup, then the system shuts down its own
When I turn on my computer, a blue screen appears and remains. The boot sequence does not turn on and the computer shuts off after a minute or two.
Hit the ESC key after that market puts me at the page 'option '. 'Advanced options', I tried "System Restore" and "Startup Repair" or solved the problem. Failed to start in safe mode or change the boot settings because the sequence of starting (reboot) the system is broken.
A hard system reset did not work and pushing the F2 key does not bring to the top of the page of diag sys.
At this point, it seems that the only option on the left are trying to boot from a USB device or do a Reset from the PC (keep my files)?
Any suggestion would be appreciated.
Thank you
It looks like you can have a hard/failed drive. If PC Reset is an option try it. If this does not work I would like to replace the hard drive and booting with recovery media to install Windows.
-
my display settings keep returning on 2 screens at startup to the top
I have attached a second monitor to my Sony laptop. The 2d display monitor used to iterate through a docking station Kensington DisplayLink. For some reason, the docking station picks up is no longer display for the #2--si monitor I recently started to connect the monitor directly #2 on my laptop. Now every time I disconnect the monitor #2 to try to use the laptop with the Moose #1 display attached - after startup, it comes in white. I discovered the Dungeon of display settings back to the #2 monitor, as the main display with the office displays only on the monitor #2 - it's why my laptop screen is blank - unless I'm reconnect the 2d display whenever I start. But it is not practical and the net effect is that until this has been resolved I can't use my laptop away from my office. I keep resettingt the display settings in the control panel to a single monitor, but it keeps going back to 2. What is the solution?
Hi, Msnsurf101,
Check your settings in the Bios
Procedures vary depending on the manufacturer of the BIOS. Usually, you must press a key (for example, F2, F12, DEL, ESC) or a key combination whenever you turn on your computer but before Windows starts. For more information, see the documentation provided with your computer or go to the website of the manufacturer of the computer.
WarningBe careful when you change the BIOS settings. The BIOS interface is designed for advanced users, and it is possible to change a setting that can prevent your computer from starting properly.
How to switch monitors primary & secondary
http://www.ehow.com/how_5919616_switch-primary-secondary-monitors.html
Uninstall of display adapters
Start > right click on computer
Select manage
Click on continue for UAC window (Vista or 7)
Select Device Manager
Click on the + sign next to display adapters
Right-click on the adapter and select uninstall
Restart the computer
Windows will reinstall the adapters
See the updated chipset manufacturer site
-
Windows will not be stopped. Laptop crashes with blue screen and a mouse pointer. This laptop has XP Professional SP3.
Look in the event log to see if any errors are recorded. Install the Service Profile Hive Cleanup (UPHClean) Microsoft and see if things improve. See here for more information:
You experience disconnection problems on a computer based on Windows XP, Windows Server 2003 - based, Windows 2000 or Windows NT 4.0-based:
http://support.Microsoft.com/kb/837115
John
-
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,
SRSKoutput 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
there when you start the debugger argument. *. * using the .sympath and .sympath + *.
*********************************************************************
Could not load the ntoskrnl.exe, 0n2 error Win32 image
WARNING: Unable to verify timestamp for ntoskrnl.exe
ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) PUTS free x 86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Computer name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
The debugging session: 23:57:36.015 Tue Oct 20, 2009 (GMT-4)
System Uptime: 0 days 9:05:10.605
*********************************************************************
* 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
there when you start the debugger argument. *. * using the .sympath and .sympath + *.
*********************************************************************
Could not load the ntoskrnl.exe, 0n2 error Win32 image
WARNING: Unable to verify timestamp for ntoskrnl.exe
ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
Loading the kernel symbols
...............................................................
................................................................
.......
Loading user symbols
Loading unloaded module list
..................
*******************************************************************************
* *
* Bugcheck analysis *.
* *
*******************************************************************************
Use! analyze - v to obtain detailed debugging information.
Bugcheck 1000007E, {c0000005, 8736d01a, f78d9ec4, f78d9bc0}
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
there when you start the debugger argument. *. * using the .sympath and .sympath + *.
*********************************************************************
*********************************************************************
* 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
there when you start the debugger argument. *. * using the .sympath and .sympath + *.
*********************************************************************
Probably caused by: PxHelp20.sys (PxHelp20 + 59b 7)
Follow-up: MachineOwner
---------
KD > .symfix
KD > .reload
Could not load the ntoskrnl.exe, 0n2 error Win32 image
WARNING: Unable to verify timestamp for ntoskrnl.exe
ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
Loading the kernel symbols
...............................................................
................................................................
.......
Loading user symbols
Loading unloaded module list
..................
KD > kb
ChildEBP RetAddr Args to child
WARNING: Frame IP not in any known module. Sequence of images may be wrong.
68772073 20657265 20657261 3f756f79 0x8736d01a f78da54c
20657265 20657261 3f756f79 6d6f4820 f78da550 0 x 68772073
f78da554 20657261 3f756f79 6d6f4820 63207265 0 x 20657265
f78da558 3f756f79 6d6f4820 63207265 736c6c61 0 x 20657261
f78da55c 6d6f4820 63207265 736c6c61 62654 has 20 0x3f756f79
f78da560 63207265 62654a 20 00217375 0x6d6f4820 736c6c61
f78da564 736c6c61 62654a 20 00217375 666e6f63 0 x 63207265
62654a 20 00217375 666e6f63 692e6769 0x736c6c61 f78da568
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=enalso 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/928228Run 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)
I hope this helps.
Rob - bicycle - Mark Twain said it is good.
-
Crash blue screen when I use the internet? Urgent need help, thesis at the end!
my laptop was pretty rubbish for a while, but now whenever I connect to the internet I get about 30 seconds before the thing of crash dump blue screen appears.
The error report details are
-System
-Supplier
[Name] Service Control Manager
[Guid] {555908D1-A6D7-4695-8E1E-26931D2012F4}
[EventSourceName] Service Control Manager
-EventID 7026[Qualification] 49152
Version 0
Level 2
Task 0
Opcode 0
Keywords 0 x 80000000000000
-TimeCreated[SystemTime] 2010-12 - 12T 09: 50:42.000Z
EventRecordID 283429
Correlation
-Execution[ProcessID] 0
[ThreadID] 0
Channel system
Jo computer PC
Security-EventData
param1 aswSP aswTdi spldr Wanarpv6
I can use internet in safe mode. I do a virus check. Device Manager it says the 4to6 adapter #7 and the ISATAP #15 card do not work properly, but there seems to be no updates for them. I tried unchecking IpV6 on my network card. This did nothing.I tried to restore to an earlier point, and it does not help.
Hello
Check this thread for more information using BlueScreenView, MyEventViewer and other methods
to troubleshoot the BlueScreens - top 3 responses (+ 1 other).-------------------------------------------------------------------------
Also this, so you can see the probable bluescreens.
Windows Vista restarts automatically if your computer encounters an error that requires him to plant.
(also Windows 7)
http://www.winvistatips.com/disable-automatic-restart-T84.html===========================================================
Check out these utilities to see if information may be collected:
It is an excellent tool for displaying the blue screen error information
-Free - BlueScreenView scans all your minidump files created during "blue screen of death," collisions
and displays information about all accidents of a table.
http://www.NirSoft.NET/utils/blue_screen_view.html-------------
MyEventViewer can be verified at the time of the blue screen (BSOD) within a second or so of the
time of the BSOD to provide more information about the possible cause - see TIP.MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
TIP - Options - Advanced filter allows you to see a period of time instead of the whole of the record-
Set it for a bit before and after the time of the BSOD.
http://www.NirSoft.NET/utils/my_event_viewer.html------------
AppCrashView - free - a small utility for Windows Vista and Windows 7 that displays the details of all the
application goes down has occurred in your system. The information breaks down is extracted from the .wer
the files created by the Windows Error Reporting (WER) of the operating system component of each
time that an accident has occurred. AppCrashView also allows you to easily record the list of accidents to
text/html/csv/xml file.
http://www.NirSoft.NET/utils/app_crash_view.htmlI hope this helps and happy holidays!
Rob Brown - MS MVP - Windows Desktop Experience: Bike - Mark Twain said it right.
-
Blue screen when you unplug the power of the computer dell laptop XP
I have a dell latitude E6500... problems with blue screen when I unplug the laptop. his past about 5 out of 10 times now. Ive updated all recommended microsoft updates and it is still the case? is there a driver for xp needed to solve this problem? It only happens when I unplug the power cord and it happens as soon as I unplug
Hello suncoastsrq,
Usually, when we see problems during shutdown, the cause is something that loads at startup.
To this end, I would recommend mode startup minimum troubleshooting as seen in the following articles:
http://support.Microsoft.com/kb/310353
http://support.Microsoft.com/kb/316434
Please note that after refine us the cause, it is important that we return to a normal startup and manually delete the startup program.
In addition, if we can get downloaded discharge, the community has access to them and will probably be able to determine the cause.
You can download the dump Auggy's previous suggestion?
Let us know.
Best regards
Matthew_Ha
-
The dreaded blue screen on startup with Windows XP
Get the dreaded blue screen at startup. Use Windows XP and my PC of becomes as much as the screen connection, but when I select my login name, that the blue screen appears. If I choose one of the other names the process gets a little further, but the blue screen then appears. I can login in safe mode and that you ran some diagnostic tests, but the problem persists.
As the forums MS Answers does not prompt for any information system when a new question is asked, we know absolutely nothing about your system.
Not knowing the basic information a problem prolongs the frustration and the agony of these issues.
If would know more about your system and that the Blue Screen of Death (BSOD said):
Please provide additional information on your system:What is your system brand and model?What is your Version of XP and the Service Pack?Describe your current antivirus and software anti malware situation: McAfee, Symantec, Norton, Spybot, AVG, Avira!, MSE, Panda, Trend Micro, CA, Defender, ZoneAlarm, PC Tools, Comodo, etc..The question was preceded by a loss of power, aborted reboot or abnormal termination? (this includes the plug pulling, buttons power, remove the battery, etc.)The afflicted system has a CD/DVD drive work?You have a true bootable XP installation CD (it is not the same as any recovery CD provided with your system)?Do you see that you think not you should see and when you see it?What do not you think that you should see?Your system seems to start OK and then crash or didn't he start not at all?If your system works fine, what do you think might have changed since the last time it worked correctly?The next time your system crashes, provide more information on what you see.
Here's a BSOD example showing information you provide:Send for the nose and the Red arrows (3 to 4 lines total).Send all * line STOP message since there are clues in the 4 parameters.If there is a name of the file listed in the STOP message, don't forget to include this information too. -
My Vista system was crushed, tried everything, but finally resorted to a recovery of the original factory image off the coast of the hard drive Partition. Everything seemed to go smooth but now I get a blue screen at startup: irql_not_less_or_equal STOP: 0x0000000A (0 x 0, 00000002 00000001, 0x81AE8590)
Odd part is the system has two RAM slots, we have a 2 GB key and another has a 1 GB. Could not get the machine to start with two sticks in. Will start with a stick in each thin slot. Will not start no matter how they are installed if you are using the two RAM slots. Ran SFC/scannow. He found errors, that it cannot correct. How can I fix these errors?
CBS log is large enough: what details should I post it to help you troubleshoot?
Note: Were able to update the system, including the installation of updates Windows 128 and seems to be updated throughout the SP-2. I really don't want to run another recovery if possible.
Thank you!
Hello
Perhaps you have different brands of RAM in your computer, and so it would not start with the two inserted Rams. Do a check for your specific PC memory that tells you what products work with your system.
Follow the information in this article.
Know what type of RAM you needIn addition, updated BIOS.
Warning of the BIOS:
BIOS change / semiconductor (CMOS) to complementary metal oxide settings can cause serious problems that may prevent your computer from starting properly. Microsoft cannot guarantee that problems resulting from the configuration of the BIOS/CMOS settings can be solved. Changes to settings are at your own risk.If scan SFC did not fix the issue, I would say that you follow the steps in this article to fix it.
http://support.Microsoft.com/kb/929833
Regarding blue screen errors, follow the steps in this article that applies also for Vista.
Maybe you are looking for
-
Tecra A2: How to get a CC3 network
I'll try to get a Tecra A2 laptop on a network of CC3, but cannot find drivers (back and Protocol.ini files) to allow the laptop to get the info he has to go in the back. Someone at - it a solution or know what should be please?
-
Satellite A100-906 - black screen with a cursor
Hi all There is a problem with my Satellite A100-906: After having lit - Toshiba page appears - that the loading Windows XP page - more than a black screen with a cursor (the touchpad moveable)... and nothing more. That's what I tried without success
-
my computer always shutdown really slow and I don't know how to fix it. I have it says takes too long to close Windows media player. (300 seconds)also for my documents when I click the key in the window, and then click Properties, the location is by
-
Classic Blackberry blackBerry software
After you install the update to Windows 10 (August 11). My blackberry is inot sinking to my laptop. FRIM the file Explorer, I can see my blackberry is connebted. one faced this problem recently? Thank you Siva
-
I couldn't activate microphone surveillance.
Hello I couldn't hear anything from the microphone. I've read the FAQ and I found the description how can I solve this problem. I did everything according to the description, but I have not found in the volume control panel the monitor input box. I h