Crashing: Repost

[usasma]

Your drivers looked in good shape when I scanned them (it's actually a part of the program that generates the summary - I just didn't include it).

Search your computer for the file "kl1.sys" I find it easiest to do a complete search of the C:\Windows directory. If you find it, rename it to kl1.BAK Then reboot and see if it comes back on you.

 

[TheMyst]

So you're saying that kl1.sys was brought up even in the later reports?

EDIT: Doubt it. Search of my C:\ drive came up dry. I'll search without the extension and see.

EDIT AGAIN: Nope.

 

[TheMyst]

I was doing it wrong. I ran KAVRemover from the command line with the correct settings, and it found KAV artifacts. Restarting now.

 

[usasma]

No, I'm saying that it was in one of the reports (Debug session time: Fri Jun 19 21:27:03.889 2009 (GMT-4)). I searched for it in the remaining reports, and it doesn't show in the first couple of reports, then shows in the middle reports, then doesn't show in the last reports. But that doesn't mean that it's gone - just that it's not listed as being loaded when that particular process crashed.

The remaining errors tend towards networking type of issues, but we'll need a new memory dump to see what's happening.

If the kl1.sys issue is fixed (and you can find this out by seeing if it's still on your system), then we can proceed with checking the networking stuff.

As the drivers appear current, our possibilities will most likely be that either the driver is corrupted or the device is malfunctioning. There are other possibilities (such as Win7 compatibility, firmware updates, Windows OS issues, malware, etc). But I need to do more research on the networking component (not just the drivers) - and that's why I'd like to see another memory dump.

 

[usasma]

Great! Things are starting to come together!
Wait for the next BSOD and we'll go from there.

I've gotta take a shower, eat breakfast and go to the dump with the trash.
I'll be back in a couple of hours to see what's happened.

Good luck!

 

[TheMyst]

Great! Things are starting to come together!
Wait for the next BSOD and we'll go from there.

I've gotta take a shower, eat breakfast and go to the dump with the trash.
I'll be back in a couple of hours to see what's happened.

Good luck!

And I will leave the Source engine running since that has been the cause of the most errors and see if it bluescreens.

 

[TheMyst]

Well... my computer didn't crash, but TF2 sure as hell did!

BUT: Knock on wood, my computer is running stable.

 

[TheMyst]

Something else I did was I went into my BIOS and set the voltage for my RAM to auto from 2.1V. I only had the voltage that high since that was what my RAm was rated at. 5-5-5-15 @ 2.1

 

[Dzomlija]

Something else I did was I went into my BIOS and set the voltage for my RAM to auto from 2.1V. I only had the voltage that high since that was what my RAm was rated at. 5-5-5-15 @ 2.1

And if you set it back to Auto?

 

[TheMyst]

I think auto is 1.8v. The timings I set manually.

 

[Dzomlija]

I think auto is 1.8v. The timings I set manually.

You really should get into the habit of reporting ALL pertinent information, which includes altering the voltages and timings of the memory. If you changed ANYTHING in the BIOS, let us know, and not one item at a time in new posts. It makes it extremely difficult to provide adequate assistance.

Right, then let's try this: Go back into your BIOS, and reset to FAIL SAFE DEFAULTS. If you still have a problem, try resetting to OPTIMAL DEFAULTS.

If you have done anything else, and I mean ANYTHING that might be related, now is the time to tell us...

 

[TheMyst]

I locked the multiplier of my CPU to 7, as it should be by default.

 

[Dzomlija]

I locked the multiplier of my CPU to 7, as it should be by default.

Have you, or have not, attempted to reset the BIOS to FAILSAFE or OPTIMAL defaults? And what was the result of the defaults reset?

 

[TheMyst]

I ghave not set any defaults recently and it would appear that I have not crashed since restarting after running Kapersky's removal tool.

Knock on wood.

 

[usasma]

Please stop changing things around while we're trying to fix this issue. Each attempt/change will change the system state - which will affect the results of what we're getting.

A memory dump is a picture of the system state at the moment in time when the crash occurred. So, if program A writes to memory owned by program B - nothing will happen until program B tries to access that memory. When program B does access the memory, that's when it'll crash. If program A has exited by this point, then there's no evidence that it caused the crash. This is why the system state is a delicate balance - and we should, at a minimum, be able to observe the same drivers being loaded throughout the parade of dump files.

Thanks!

FWIW - you can generate a crash dump of a user-mode process by locating the process in Task Manager - Processes tab. Then right click on the process and select "Create Dump File".

As with BSOD's, this is a snapshot of a point in time (of this process). Unless the process has crashed (and hasn't exited yet) there's no sense in doing it. If you're able to catch the process before it exits, use the above steps to generate the dump file. Then upload it and give us the link so we can analyze it.

 

[TheMyst]

Everything is fine now. I will come back if I crash again. Thank you all for your help.

 

[Dzomlija]

Everything is fine now. I will come back if I crash again. Thank you all for your help.

Glad to hear it.