G
Guest
I've only posted this in the vain hope that someone out there is familiar
with this stinker, god, the no of times I've helped folks out with this BSOD,
I'm embarrased!
Blue screen error IRQL_NOT_LESS_OR_EQUAL, yes it points to h/ware & a
misbehaved driver but:
But Here's what it says in Event viewer:
Log Name: Application
Source: Windows Error Reporting
Date: 17/07/2007 19:40:17
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Heather-PC
Description:
Fault bucket 0xA_W_nt!KiInsertTimerTable+4e, type 0
Event Name: BlueScreen
Response: None
Cab Id: 0
Its the 0xA_W_nt!KiInsertTimerTable+4e, type 0 that's puzzling The thing
that really gets me is that Prob Reports & Solutions actually classes it as a
Windows error, & nothing more! I gather something tries to interfere with
Sys32 & gets blocked, but instead of being able to ID the offending item (as
is the norm) it only seems to clock the "Windows" reaction, which is to throw
up the blue screen.
Before & after the event in EV (apps) there are various entries referring to
WLO corrupt database & then another to say its been repaired, but I gather
that's an after effect caused by the original mystery prob - hope somebody's
familiar with this, any help would be great. If sys specs are needed - will
post separately
with this stinker, god, the no of times I've helped folks out with this BSOD,
I'm embarrased!
Blue screen error IRQL_NOT_LESS_OR_EQUAL, yes it points to h/ware & a
misbehaved driver but:
But Here's what it says in Event viewer:
Log Name: Application
Source: Windows Error Reporting
Date: 17/07/2007 19:40:17
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Heather-PC
Description:
Fault bucket 0xA_W_nt!KiInsertTimerTable+4e, type 0
Event Name: BlueScreen
Response: None
Cab Id: 0
Its the 0xA_W_nt!KiInsertTimerTable+4e, type 0 that's puzzling The thing
that really gets me is that Prob Reports & Solutions actually classes it as a
Windows error, & nothing more! I gather something tries to interfere with
Sys32 & gets blocked, but instead of being able to ID the offending item (as
is the norm) it only seems to clock the "Windows" reaction, which is to throw
up the blue screen.
Before & after the event in EV (apps) there are various entries referring to
WLO corrupt database & then another to say its been repaired, but I gather
that's an after effect caused by the original mystery prob - hope somebody's
familiar with this, any help would be great. If sys specs are needed - will
post separately