Phil Adamson said:
First one I came to is:-
Faulting application DrvInst.exe, version 6.0.6000.16386, time stamp
0x4549ad51, faulting module ntdll.dll, version 6.0.6000.16386, time stamp
0x4549bdc9, exception code 0xc0000374, fault offset 0x000af1c9, process id
0x158c, application start time 0x01c7cc85828a1e8a.
That's a plausible candidate. A "0xC0000374" exception means
STATUS_HEAP_CORRUPTION. A "heap" is a structure which exists temporarily in
memory while a program runs. Every program has one or more heaps. If a heap
gets damaged while the program is running, the program will often crash.
Heap corruption can be caused either by an internal programming error, or by
some external factor like bad data which is input to the program.
DrvInst.exe is a Microsoft-supplied component of Windows; as the name
suggests, it installs device drivers. Likewise, ntdll.dll is part of the
very heart of Windows, which provied an access point for processes out there
in user-space (like DrvInst) to communicate with the Windows kernel. These
are both extremely heavily exercised bits of code; if there was a
programming error which could cause heap corruption, we should be seeing
hundreds, thousands or millions of reports of it every day. But so far,
0xC0000374 in DrvInst seems to be pretty rare (although not unique). So
axiomatically, it's being caused by some faulty data somehwere - maybe a bad
driver *.INF file or the like.
I guess teh main question is: does this event No. 15354 occur every time you
boot the machine? Or was it a once-off event? If it was a one-off, we ca
probably ignore it. If it happens every time you boot, it's probably related
to the error message you see - the "The instruction at 0x00366f9d referenced
memory at 0x00000f18. The memory could not be read."
O'course going to the next step, and identifying the data data which is
upsetting DrvInst could be tricky ... but, we'll cross that when we come to
it.