10 replies to this topic

[DesertJerry]

I just noticed this a couple of days ago - can someone else run a check?

Boot into XP Pro x64 or Win7 32-bit or 64-bit, start IE8 (the 32-bit version in the 64-bit OS) and go to this webpage/forum, click to go anywhere and IE8 dies and I get a message to send info to Microsoft. I had to try it couple of time in each of the OS's to verify what was happening, I have no idea why. I am sending this from IE6 in XP Pro w/SP3.

Would appreciate someone else trying IE8 32-bit in their 64-bit Windows to verify. Thanks

[Cristiano]

ok. i will try this at home

[]s

[dfdff3000]

I tried, using IE8 32-bit version in Windows 7 64-bit and failed to duplicate. I didn't log in via IE8 however, and am posting via Firefox. I don't see that logging in would make a difference though?

[Cristiano]

ok, i've tried at home browse this site/forum with ie8 under seven pro x64, running ie8 x86 version. no problem at all, browsing the forum and going elseware. right now, i'm posting this with ie8

the only one odd behavior that i've noticed since some time ago was apup related. i can't run apup anymore. apup starts, looks as the system is running something, but the system doesn't do anything else and just work as expected again after an reboot. the odd part is that apup was working nicelly in this system until some time ago. well, i will wipe this system as soon the final version of seven sp1 arrives, so i'm not really concerned about that right now, but if someone knows how to fix this...

[]s

[DesertJerry]

Cristiano, on 10 August 2010 - 06:05 PM, said:

ok, i've tried at home browse this site/forum with ie8 under seven pro x64, running ie8 x86 version. no problem at all, browsing the forum and going elseware. right now, i'm posting this with ie8

the only one odd behavior that i've noticed since some time ago was apup related. i can't run apup anymore. apup starts, looks as the system is running something, but the system doesn't do anything else and just work as expected again after an reboot. the odd part is that apup was working nicelly in this system until some time ago. well, i will wipe this system as soon the final version of seven sp1 arrives, so i'm not really concerned about that right now, but if someone knows how to fix this...

[]s

Thanks for checking, I'll continue testing.

Win7 SP1 is not due to go final till first half of 2011 - you might want to continue testing APUP to find the problem before that.

My #2 system has Win7 32-bit with SP1 installed - when it finishes todays updates I'll run APUP and see if it screws up.

[Cristiano]

no problem. i probably will wipe before that. in about 3 months, i have to replace my security software and, as usual, i will test several. after my tests, wipe. but of course, my tests will start at the end of this month. any suggestions? just please, no free software. this task is for paid ones

by the way: the problem happens with seven pro x64 (enu, with an localized interface)

[]s

Edited by Cristiano, 10 August 2010 - 10:31 PM.

[DesertJerry]

Ran APUP on my #2 system with Win7 32-bit SP1 - ran fine, as did AutoPatcher. Because AutoPatcher is not updated for SP1 it did list a lot of Win7 updates as being required - I ignored them as I decided SP1 included the items listed. So, those with SP1 are going to be presented a long list of pre-SP1 updates which they will have to ignore until SP1 final arrives and APUP/AutoPatcher are updated.

[DesertJerry]

Win7 64-bit, IE8 32-bit version, came here and home page opened OK, tried to navigate to another page and got fault, as above. Opened IE8 64-bit, using now, and things OK.

Opened Event Viewer and it confirmed fault - follows:
Log Name: Application
Source: Application Error
Date: 12-Aug-10 22:09:03
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Chief
Description:
Faulting application name: iexplore.exe, version: 8.0.7600.16385, time stamp: 0x4a5bc69e
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0d730068
Faulting process id: 0x10a0
Faulting application start time: 0x01cb3aa58bad9e23
Faulting application path: H:\Program Files (x86)\Internet Explorer\iexplore.exe
Faulting module path: unknown
Report Id: e3936f67-a698-11df-9f15-00183704747d
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-08-13T05:09:03.000000000Z" />
<EventRecordID>15146</EventRecordID>
<Channel>Application</Channel>
<Computer>Chief</Computer>
<Security />
</System>
<EventData>
<Data>iexplore.exe</Data>
<Data>8.0.7600.16385</Data>
<Data>4a5bc69e</Data>
<Data>unknown</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>c0000005</Data>
<Data>0d730068</Data>
<Data>10a0</Data>
<Data>01cb3aa58bad9e23</Data>
<Data>H:\Program Files (x86)\Internet Explorer\iexplore.exe</Data>
<Data>unknown</Data>
<Data>e3936f67-a698-11df-9f15-00183704747d</Data>
</EventData>
</Event>

But, as you can see from the info above, no reason is indicated as best I can determine - anyone else have a clue as to what all this stuff may mean?

[Cristiano]

an flash player issue related, perhaps?

by the way, i did apup work again. i've erased readybost, did an update in my security suite, but now i'm dealing with an read-only issue with apup... oh boy...

[]s

[DesertJerry]

Cristiano, on 13 August 2010 - 10:46 AM, said:

an flash player issue related, perhaps?
[]s

Don't think it's FlashPlayer - the problem occured before the recent FlashPlayer update and it iss till happening. Oh well.

[Cristiano]

well, i've just tried this site with ie a few times. personally, i really don't like ie. i'm running firefox since long ago, with a couple of tools that helps me a lot (like enu and ptb dictionaries, flashblocker, adblocker, etc). but googling Exception code: 0xc0000005:

The error 0xC0000005 is generated by an illegal "memory access violation". This can be caused by anything from faulty RAM, an incorrect/corrupt device driver, poorly written/updated software and more commonly under Windows XP Service pack 2, malware/adware installations

as an guess, memory check...

[]s