Anybody know what this error could be?

zaoka

Member
Reaction score
2
Log Name: Application
Source: Application Error
Date: 07/09/2014 11:32:22 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ROKO-PC
Description:
Faulting application rundll32.exe, version 6.0.6000.16386, time stamp 0x4549b0e1, faulting module kernel32.dll, version 6.0.6002.18449, time stamp 0x4da47a32, exception code 0x0eedfade, fault offset 0x0001c83b, process id 0x1930, application start time 0x01cfcab0e910c940.
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="2014-09-07T15:32:22.000Z" />
<EventRecordID>84664</EventRecordID>
<Channel>Application</Channel>
<Computer>ROKO-PC</Computer>
<Security />
</System>
<EventData>
<Data>rundll32.exe</Data>
<Data>6.0.6000.16386</Data>
<Data>4549b0e1</Data>
<Data>kernel32.dll</Data>
<Data>6.0.6002.18449</Data>
<Data>4da47a32</Data>
<Data>0eedfade</Data>
<Data>0001c83b</Data>
<Data>1930</Data>
<Data>01cfcab0e910c940</Data>
</EventData>
</Event>


I did sfc /scannow and disk error check, it did not fix it.

Machine appears to be virus free, at least Norton, MBAM and OTL does not show infection...

Its Vista 64bit


???
 
this is the code for a Delphi exception. probably some thread synchronization issue. basically an application is crashing due to a null pointer, memory being accessed after a cleanup or object destruction. pity the error message doesn't mention the application. it could be a service. look for applications installed around the time the error started appearing.
 
How about upgrading them to win7 pro? With the information provided I would think its going to be a PITA to find the offending software thats causing this problem.

Might be a better way to go instead of wasting alot of time/resources figuring this out.

If not then I normally go into msconfig and setup minimal bootup and see if problem can be reproduced after adding back services / startup programs.

Never really did enjoy MS error messages. :)

coffee
 
hi

Sorry guys my mistake. It was malware.

Norton 360 did intercept it, however, not properly and did not remove infection completely so it was crashing system.

I was checking Norton log files and found the same time and date for malware detection.

Used OTL to remove traces and userinit.exe load points...

Symptom was rundll32.exe error all the time.
 
Back
Top