G-hot

Emergency kit scanner and Get the blue screen ?

Recommended Posts

I try to use scanner, but after seconds from now, Get the blue screen of death.

Is this a problem with the program?

Help me I can not use this program.......

Share this post


Link to post
Share on other sites

Dear Sir,

sorry for the late reply.

Please open the Emsisoft Emergency Kit and go to section Scan PC. Now please select Custom Scan and press SCAN. Please disable the option Scan for active Rootkits and start the scan. Windows crashes again with the blue screen?

What windows version and servicepack do you use?

Share this post


Link to post
Share on other sites

hi there

This problem occurs with version 2 and 3 (quick scan)

And I use Windows XP Service Pack 2

Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 10/28/2012 1:34:31 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102812-02.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xE051)
Bugcheck code: 0x24 (0x1902FE, 0xFFFFFFFFA97B2648, 0xFFFFFFFFA97B2344, 0xFFFFFFFF804EDDF5)
Error: NTFS_FILE_SYSTEM
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sun 10/28/2012 6:26:57 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102812-01.dmp
This was probably caused by the following module: a2ddax86.sys (a2ddax86+0xCFE)
Bugcheck code: 0x35 (0xFFFFFFFF823189D0, 0x0, 0x0, 0x0)
Error: NO_MORE_IRP_STACK_LOCATIONS
file path: C:\Documents and Settings\mr\Desktop\EmsisoftEmergencyKit\Run\a2ddax86.sys
product: Emsisoft Anti-Malware
company: Emsi Software GmbH
description: Emsisoft Direct Disk Access Support Driver
Bug check description: This bug check occurs when the IoCallDriver packet has no more stack locations remaining.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: a2ddax86.sys (Emsisoft Direct Disk Access Support Driver, Emsi Software GmbH).
Google query: Emsi Software GmbH NO_MORE_IRP_STACK_LOCATIONS
On Wed 10/24/2012 4:15:06 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102412-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21925)
Bugcheck code: 0xC000021A (0xFFFFFFFFE2AB1B38, 0xFFFFFFFFC0000005, 0x7C9106C3, 0x11AF36C)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This means that an error has occurred in a crucial user-mode subsystem.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
a2ddax86.sys (Emsisoft Direct Disk Access Support Driver, Emsi Software GmbH)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.