Author Topic: BSOD  (Read 7036 times)

0 Members and 1 Guest are viewing this topic.

cpupro

  • Guest
BSOD
« on: July 01, 2006, 05:42:50 PM »
I am running Vista 5456.5 and was advised to use this AV. It worked fine until I went to access this computer from my home network, XP machine, and when it trys to connect to the Vista computer with Avast Free on it it goes straight to the BS, shutdown and the whole process.

I tried from various machines on the network, same thing. I uninstalled AVAST and everything is working just fine. Problem now is I have no AV on this Vista machine.

Can anyone help with this I need to have AV present on this computer!!!

CharleyO

  • Guest
Re: BSOD
« Reply #1 on: July 03, 2006, 05:55:57 AM »
***

Welcome to the forums, cpupro.    :)

Hopefully, one of the Avast team members will be able to help you with this soon.


***

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11840
    • AVAST Software
Re: BSOD
« Reply #2 on: July 03, 2006, 10:37:24 AM »
How exactly were you accessing the Vista computer? I mean, you just accessed the files thorugh a share, or connected to is using Remote Desktop, or... ?
Are there any (mini)dumps corresponding to the crashes on the Vista computer?

cpupro

  • Guest
Re: BSOD
« Reply #3 on: July 03, 2006, 11:25:40 AM »
Just simple map to drive to transfer or open files on the machine from an XP machine, simple home network. I do have .dmp files on this and here is the error message.
Problem signature
Problem Event Name:   BlueScreen
OS Version:   6.0.5456.2.0.5.768.1
Locale ID:   1033

Files that help describe the problem (some files may no longer be available)
Mini070206-01.dmp
sysdata.xml
Version.txt

 View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem
BCCode:   a
BCP1:   00000060
BCP2:   0000001B
BCP3:   00000001
BCP4:   8146B667
OS Version:   6_0_5456
Service Pack:   0_5
Product:   768_1
Server information:   e6ca9bf4-3f04-4e30-a900-e2f1c2e5a4aa

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11657
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re: BSOD
« Reply #4 on: July 03, 2006, 11:35:36 AM »
Please send the contents of the \windows\minidump folder to my email address.


Thanks
Vlk
If at first you don't succeed, then skydiving's not for you.

cpupro

  • Guest
Re: BSOD
« Reply #5 on: July 13, 2006, 02:03:03 AM »
I sent all the information requested to you by email did you not receive it or are you still working on it? I am still waiting for an AV for Vista and will be rebuilding this beta machine soon. I would like to be able to try Avast but if it continues to BS I will have to try something else???

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11657
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re: BSOD
« Reply #6 on: July 13, 2006, 02:32:05 PM »
This seems to be a peculiar problem, most likely a bug in Vista.
I'm in contact with engineers at Microsoft and they're looking at it.


Thanks
Vlk
If at first you don't succeed, then skydiving's not for you.

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11657
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re: BSOD
« Reply #7 on: July 13, 2006, 09:17:52 PM »
OK, I just talked to a guy at Microsoft, and he told me they'd need a full dump.
Please do the following:

1. Enable Generation of Kernel Dump
Open Control Panel -> System -> Advanced System Settings -> (Advanced Page) ->Startup and Recovery Settings -> Write Debugging Information: set to "Kernel memory dump". Confirm with OK, but don't restart the machine (yet).

2. Set up the driver verifier
Run verifier.exe (part of Windows) -> choose "Create custom settings (for code developers)", click Next -> select "Enabled predefined settings" and check "Standard settings" and "Force pending I/O requests", click Next -> select "Automatically select all drivers installed on this computer", click Finish.

Let the machine reboot, and simulate the problem (note that the machine might actually bluescreen even before you expect it - that's because of the enabled Driver Verifier). Anyway, when the system blue screens, let it generate the dump file. After it restarts, take the dump file (\windows\memory.dmp), ZIP it (call the remaining ZIP file e.g. vistacrash.zip) and finally upload it to our ftp site ftp://ftp.avast.com/incoming (please note that you will have only WRITE access to the ftp site, not read).

After you're done, please let me know.


Thanks for your help
Vlk
If at first you don't succeed, then skydiving's not for you.

cpupro

  • Guest
Re: BSOD
« Reply #8 on: July 14, 2006, 12:48:55 AM »
I did as you asked and sent the file per your instructions to the avast ftp site. If you need anymore information please notify me. I also need to know if this is a "Vista" problem so I can file the correct bug information.

wlfpck

  • Guest
Re: BSOD
« Reply #9 on: July 16, 2006, 04:02:27 AM »
ok... not to be mean or anything but cpupro... shouldn't this be under a different thread?  since.... its a different topic?  again... not trying to be mean or anything but this could confuse people who have the same trouble as I do.

cpupro

  • Guest
Re: BSOD
« Reply #10 on: July 16, 2006, 04:59:16 AM »
Not sure what you mean it is all related to the same BSOD that hasn't been determined if it is a hardware, software or ???. I would put this under another heading if I knew what the cause of the BSOD was from. It is a possibility that this could just be a OS problem, beta that is and maybe a future build will take away the problem. I know that there are lot's of people that are using Avast with no problems so it is somewhat unique.

Offline bob3160

  • Avast √úberevangelist
  • Probably Bot
  • *****
  • Posts: 48321
  • 63 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re: BSOD
« Reply #11 on: July 16, 2006, 02:48:51 PM »
wlfpck
Same person, same problem since it hasn't been resolved. So why would this need to be any where else ???
Besides all this does it take it off topic.

All cpupro wants is a resolution and, those of us following this, are also curious about the outcome and are following this thread.
Free Security Seminar: https://bit.ly/bobg2023  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 11 Pro v22H2 64bit, 16 Gig Ram, 1TB SSD, Avast Free 23.5.6066, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq -- My Online Activity https://bit.ly/BobGInternet

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11657
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re: BSOD
« Reply #12 on: July 25, 2006, 07:57:09 AM »
Hi again cpupro,

sorry for the delay.

I finally got a confirmation from MS that this was indeed a bug in the Vista beta2 build. A fix was checked in to the main Vista source tree in mid June, and the bug should be fixed in the latest public ctp build (5472)


Hope this helps, :)
Vlk
If at first you don't succeed, then skydiving's not for you.

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67198
Re: BSOD
« Reply #13 on: July 25, 2006, 02:26:19 PM »
The bug should be fixed in the latest public ctp build (5472)
Vlk, do you know if this will be a patch (released by Windows Update) or we must download and install all Vista package again?
The best things in life are free.

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11657
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re: BSOD
« Reply #14 on: July 25, 2006, 03:17:06 PM »
They don't fix such bugs via patches. That's why they're releasing new builds all the time.
If at first you don't succeed, then skydiving's not for you.