Jump to content

How can I turn off the update to Pro/trial balloon?


Recommended Posts

Hi,

I clicked "End Trial" and my laptop crashed with a 0xC4 error code: "A device driver attempting to corrupt the system has been caught..."

 

I thought it might be a coincidence so re-started my laptop and again clicked on End Trial and again my laptop crashed immediately with the same error.

 

What can I do about this?!

 

I'm running Windows Professional XP on a Dell Latitude D620.

 

Thank you

Link to post
Share on other sites

A clean install will correct the issue you are having, let’s try that and see if that helps.

Please go the following pinned topic located ==> HERE <== and let us know if this corrects the issue for you or not.

You will need to follow the instructions for the Free Version...

Basically you will run a tool called mbam-clean.exe and the will un-install Malwarebytes and all associated registry keys.

Then after that you can download and re-install the free version making sure you uncheck the Trial option at the end of the install as shown in the picture below....

DkgJ7Zr.png

Link to post
Share on other sites

Hi,

I followed these instructions and with all applications closed and my anti-virus software turned off I clicked Run on the mbam removal tool, but my laptop immediately crashed again, with a 0xC4 error.

 

WhoCrashed cam up with this:

On Fri 12/6/2013 9:13:45 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini120613-02.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
 

Link to post
Share on other sites

Strange, these tools should not be causing this sort of issues, perhaps you may try doing a memory test on your system to make sure you don't have a faulty memory stick. Also see if you can run dds and get some logs for us to review.....

Please run the following scanner and send back the logs.

Download DDS from one of the locations below and save to your Desktop

dds.scr

dds.com

Temporarily disable any script blocker if your Anti-Virus/Anti-Malware has it.

How To Temporarily Disable Your Anti-virus, Firewall And Anti-malware Programs

Once downloaded you can disconnect from the Internet and disable your Ant-Virus temporarily if needed.

Then double click dds.scr or dds.com to run the tool.

Click the Run button if prompted with an Open File - Security Warning dialog box.

A black DOS console should open and run for a moment.

  • When done, DDS will open two (2) logs:
  • DDS.txt
  • Attach.txt
  • Save both reports to your desktop
  • Please include the following logs in your next reply "as an attachment": DDS.txt and Attach.txt

    You can ignore the note about zipping the Attach.txt file

Link to post
Share on other sites

This is the WhoCrashed report of my crashes

 

System Information (local)

computer name: LATITUDE-D620
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
Hardware: Latitude D620 , Dell Inc.,
CPU: GenuineIntel Intel® Core2 CPU T5600 @ 1.83GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2145435648 total
VM: 2147352576, free: 2048118784


 

Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 12/6/2013 9:13:45 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini120613-02.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Thu 12/5/2013 10:23:03 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini120613-03.dmp
This was probably caused by the following module: mbr.sys (mbr+0xA28)
Bugcheck code: 0x100000D1 (0xFFFFFFFFE361A000, 0xFF, 0x0, 0xFFFFFFFFB8370A28)
Error: CUSTOM_ERROR
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: mbr.sys .
Google query: mbr.sys CUSTOM_ERROR



On Thu 12/5/2013 5:00:39 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini120613-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x66016)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF866016, 0xFFFFFFFFAC537AE4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Wed 12/4/2013 10:22:29 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini120513-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22FA3)
Bugcheck code: 0xC4 (0x60, 0x0, 0x98, 0x1)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver is unloading without first freeing its pool allocations. A bug check with this parameter occurs only when the Pool Tracking option of Driver Verifier is active. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 12/4/2013 10:11:58 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini120513-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22FA3)
Bugcheck code: 0xC4 (0x1006, 0xFFFFFFFF89D23810, 0xFFFFFFFF8A8A5550, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
Thread holds resources: A thread is deleted before the thread can release its resources. A bug check with this parameter occurs only when the Deadlock Detection option of Driver Verifier is active. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 12/4/2013 8:50:03 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini120513-02.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0xBC59)
Bugcheck code: 0xC4 (0x60, 0x0, 0xA0, 0x1)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus
company: AVAST Software
description: avast! self protection module
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver is unloading without first freeing its pool allocations. A bug check with this parameter occurs only when the Pool Tracking option of Driver Verifier is active. 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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: AVAST Software DRIVER_VERIFIER_DETECTED_VIOLATION



On Wed 12/4/2013 8:34:17 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini120513-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0xBC59)
Bugcheck code: 0xC4 (0x60, 0x0, 0xA0, 0x1)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus
company: AVAST Software
description: avast! self protection module
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver is unloading without first freeing its pool allocations. A bug check with this parameter occurs only when the Pool Tracking option of Driver Verifier is active. 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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: AVAST Software DRIVER_VERIFIER_DETECTED_VIOLATION



On Sat 11/30/2013 8:17:45 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini120113-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2409C)
Bugcheck code: 0x1000000A (0x680063, 0x1C, 0x1, 0xFFFFFFFF804FB09C)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 11/29/2013 3:27:03 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini112913-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2409C)
Bugcheck code: 0x1000000A (0x680063, 0x1C, 0x1, 0xFFFFFFFF804FB09C)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 11/27/2013 5:00:27 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini112813-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC3588)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF8C3588, 0xFFFFFFFFA8B80AD4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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.


 

Conclusion

10 crash dumps have been found and analyzed. 2 third party drivers have 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:

aswsp.sys (avast! self protection module, AVAST Software)
mbr.sys

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.

~

My laptop did have a major hal.dll error last month and I had to boot from a Win XP Professional CD to get it to work again, so perhaps the memory is damaged, though WhoCrashed doesn't suggest hardware as the problem as far as I can tell. I don't know anything about laptops... I just like it when they go well

 

Link to post
Share on other sites

It is quite possible that this could be a rootkit causing all these issues or a hardware/software problem.

We will have to run other tools that we can not run in this section of the forum so you will have to continue over in the HJT section and get an expert to help you run other tools to see what's going on.

Being that you are probably infected, feel free to follow the instructions below to receive free, one-on-one expert assistance in checking your system and clearing out any infections and correcting any damage done by the malware.

Please see the following pinned topic which has information on how to get help with this: Available Assistance for Possibly Infected Computers

Thank you

ALSO....

To test your RAM do the following.

1) Please download the Memtest86 Pre-Compiled Bootable ISO file.

2) Unzip the downloaded memtest86 file. You will need a program like 7-Zip to unzip this file.

3) Inside, you will find the memtest86 file.

4) Please download and install ImageBurn.

5) Insert blank CD into your CD drive.

6) Open ImgBurn, and click on Write image file to disc.

ImgBurn1_zps715cb1c2.png

7) Click on the Browse for a file... icon:

ImgBurn2_zpsaea72ba9.png

8) Locate the memtest86 file, and click on the Open button.

9) Click on the blue arrow to start burning bootable memtest86 CD.

imageburn11_zpse44f577b.png

10) Once the CD is created, boot from it, and memtest will automatically start to run.

Please note: It may be neccessary to change the boot order in the BIOS so the CD/DVD-ROM is the first device in the boot order and the hdd second.

Each pass consists of 8 tests, it is suggested that you run at least 7 passes, this will take several hours, you may find it simpler to let it run overnight. The longer you run the passes the more comprehensive the results will be.

If you are running multiple modules and have a failure, remove all but one module and test it separately, continue this with each module till you find the one that failed.

When you discern that a module is good, use it to test each slot to be sure there isn't a problem with one of them.

When the test is complete a display similar to the one below will appear. Note the locations of the Pass and Errors, any Error is indicative of a failed module.

memtest1_zps7be717f5.png

Link to post
Share on other sites

Thanks for all this information, it's wonderful to have such clear instructions.

 

I've been downloading everything, but have realised I don't have any blank CDs and it's not easy for me to get one - would it work to delete things off an old USB and use that instead?

Link to post
Share on other sites

I have never tried it using a usb flash drive, but I suppose if you can boot from a usb drive and then run the memory test program it should work.

There are instructions here: http://www.memtest86.com/download.htm on how to do this with a usb, (and you can download a usb boot image file) but I have not tested it that way myself.....

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.