BSOD 0x0000003b when using MS Word and Firefox

JoostK said:

And here's a third minidump file created in a crash while running Verifier.

The system did not crash "by itself", though, only after trying to visit a website in Firefox. I can get the system to crash "at will" just by visiting certain websites in Firefox (e.g. CNN, YouTube movies), but is that the way to test this or should I just let Verifier run and not touch any program I know to be causing a crash?

This one is not verifier enabled and reports Pool_corruption as the cause. Again a driver but since verifier wasnt running we dont know which one.

Again Old drivers

Code:

RTKVHD64.sys    7/24/2008 6:05:39 AM        fffff880`06a48000    000083cc`06bb1f80    0x00008b4c00169f80    0x488853f3                        
Rt64win7.sys    2/26/2009 5:04:13 AM        fffff880`04450000    fffff880`04482000    0x00032000    0x49a65b0d

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

JoostK said:

Good morning,

I updated the two drivers you mentioned.

Here's the latest minidump file. Verifier was running, but I doubt that it could be of any use. The problems seems to be that the computer is stable when I don't touch anything and it only crashes when I start running programs. Or is that what I'm supposed to do to make it crash? I'm a bit confused here.

Thanks for sticking with me. What can I do next? Or should I just let Verifier run for a long time without touching the keyboard?

Joost

Joost the one you just upload was NOT driver verified. After you think you have it set up correctly please go to Start>type verifier /query and tell us what drivers have tick marks next to them.

If you dont get some drivers checked it isnt running.

Hi!

I don't know about any checkmarks - when I type verifier /query, all loaded drivers flash past, and with regard to each driver eight numbers (something about allocation) are specified. Some of them are in the thousands. I can see the same information when I load the Verifier GUI.

I have added three screenshots to this post so you can see what I mean.

Does this mean that verifier is working (this time, at least)?

The computer has not crashed yet - should I just let in run in the background of force a crash by opening Word / Firefox or performing other actions that I know cause the computer to crash?

OK, so here is a new minidump - (the system crashed when browsing in Firefox).

Verifier was running, I assume from the numbers shown in the screenshots in the previous post, which kept rising (as I saw in real time in the verifier GUI).

Is the minidump useful in any way? Or should I just let Verifier run for a long time without actively using the computer?

JoostK said:

OK, so here is a new minidump - (the system crashed when browsing in Firefox).

Verifier was running, I assume from the numbers shown in the screenshots in the previous post, which kept rising (as I saw in real time in the verifier GUI).

Is the minidump useful in any way? Or should I just let Verifier run for a long time without actively using the computer?

Ok do what ever it is that makes your computer crash. If verifier recognizes the driver it will log its name.

It may take as long as 36 consecutive hours to crash. When it crashes it may (should) write the faulting drivers name to the page file.

Hi!

I'm sorry, but I'm still a bit confused about what you mean I should do - I just don't know anything about these things. Verifier is running. When I use my computer normally, it will crash now and again when I use certain programs (esp. Firefox, IE) and do something like watching a youtube video or a photo presentation on a news site or start a download. I've attached the latest minidump for a crash that happened like that. Is that minidump of any use?

If not, then what should I do? Should I actively generate more of these crashes and minidumps (then will there be a chance that one of them will prove useful) or should I just leave the computer running without interfering with it? Or should I do something different, like change the settings of verifier in some way?

Thanks for helping me out!

JoostK said:

Hi!

I'm sorry, but I'm still a bit confused about what you mean I should do - I just don't know anything about these things. Verifier is running. When I use my computer normally, it will crash now and again when I use certain programs (esp. Firefox, IE) and do something like watching a youtube video or a photo presentation on a news site or start a download. I've attached the latest minidump for a crash that happened like that. Is that minidump of any use?

If not, then what should I do? Should I actively generate more of these crashes and minidumps (then will there be a chance that one of them will prove useful) or should I just leave the computer running without interfering with it? Or should I do something different, like change the settings of verifier in some way?

Thanks for helping me out!

Verifier doesnt seem to be running please type cmd in search>verifier /query . What does it return?

This is a screenshot of the start of the output of verifier /query (somehow I cannot get the program to log or dump this output it to a file, so I have to use a screenshot). The numbers in it increase with time. (And other drivers have higher numbers than the ones shown.)

JoostK said:

This is a screenshot of the start of the output of verifier /query (somehow I cannot get the program to log or dump this output it to a file, so I have to use a screenshot). The numbers in it increase with time. (And other drivers have higher numbers than the ones shown.)

Verifier is indeed running and may take 36 hours to crash. Do whatever you think makes it crash