BSOD 0x0000003b when using MS Word and Firefox

[JoostK]

Hi,

My computer keeps crashing with BSOD's, alternating between "Page Fault in Paged Area" and "System Service Exception", soon after I start MS Word or Firefox, and at other times as well. I have no idea why.

I have attached the required diagnostics files and the Perfmon test output (both as zips).

UPDATE: I have also uploaded the most recent minidump file (as zip).

Running MemTest86+ for 3 passes did not show RAM problems.
Windows, Flash and graphic drivers are fully up-to-date.

Here's the problem description of the latest crash as reported by Windows 7:

Problem: BlueScreen
OS Version:6.1.7601.2.1.0.256.48
Country-id: 1043

BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80002FC8B05
BCP3: FFFFF88008423EE0
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Can anyone help me to find (and solve) the problem?

Thanks so much in advance!

Joost

 

[zigzag3143]

Hi,

My computer keeps crashing with BSOD's, alternating between "Page Fault in Paged Area" and "System Service Exception", soon after I start MS Word or Firefox, and at other times as well. I have no idea why.

I have attached the required diagnostics files and the Perfmon test output (both as zips).

Running MemTest86+ for 3 passes did not show RAM problems.
Windows, Flash and graphic drivers are fully up-to-date.

Here's the problem description of the latest crash as reported by Windows 7:

Problem: BlueScreen
OS Version:6.1.7601.2.1.0.256.48
Country-id: 1043

BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80002FC8B05
BCP3: FFFFF88008423EE0
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Can anyone help me to find (and solve) the problem?

Thanks so much in advance!

Joost

No DMP files included in upload. Please try this method.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.


To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

 

[JoostK]

Minidump added

Thank you for your reply. I have attached the minidump file (zipped) to the original post.

(Afterwards I checked the sysdm.cpl and the setting was (the Dutch translation of)) "Kernel memory dump", by the way, not Small memory dump, so I've changed that to Small memory dump. Or should I leave it at Kernel memory dump?)

(The Jcgriff2.zip file was created just before the latest crash by the way, whereas the minidump file was created during the latest crash. Is that ok?)

Thanks in advance for your trouble.

Joost

 

[zigzag3143]

Thank you for your reply. I have attached the minidump file (zipped) to the original post.

(Afterwards I checked the sysdm.cpl and the setting was (the Dutch translation of)) "Kernel memory dump", by the way, not Small memory dump, so I've changed that to Small memory dump. Or should I leave it at Kernel memory dump?)

(The Jcgriff2.zip file was created just before the latest crash by the way, whereas the minidump file was created during the latest crash. Is that ok?)

Thanks in advance for your trouble.

Joost

Hi Jooost

The single crash reported memory corruption, probably caused by a driver. Please run the following testsm



1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[JoostK]

Thank you for you suggestions. I will run the tests and probably come back here with a new dump file if it's a faulty driver and Driver verifier manages to crash the system.

 

[JoostK]

- update: no RAM failure, two more minidump files -

Well, MemTest86+ does not show errors after 9 passes, so I guess it's not the RAM.

I have uploaded two more minidump files with this post of the most recent crashes. (Firefox crashes every time I start to play a YouTube video.) BlueScreenView identifies the culprits in these dumps as HIDPARSE.SYS (the Firefox/YouTube crash) and volmgr.sys. The driver from the first dump was ntoskrnl.exe. I guess that's to general to arrive at any conclusions?

I should try Driver Verifier next then.

 

[zigzag3143]

Well, MemTest86+ does not show errors after 9 passes, so I guess it's not the RAM.

I have uploaded two more minidump files with this post of the most recent crashes. (Firefox crashes every time I start to play a YouTube video.) BlueScreenView identifies the culprits in these dumps as HIDPARSE.SYS (the Firefox/YouTube crash) and volmgr.sys. The driver from the first dump was ntoskrnl.exe. I guess that's to general to arrive at any conclusions?

I should try Driver Verifier next then.

You should try verifier to identify the driver causing this. These point to "pool_corruption" (usually a driver). I am starting to think it may be your AVG.

 

[JoostK]

OK, I'll try verifier. (Here's the latest minidump (this time ksthunk.sys is flagged), for a crash that again happened after trying to watch a youtube video.)

 

[JoostK]

Minidump after enabling verifier

OK, so I ran Verifier and after a couple of minutes (while browsing in Firefox) a BSOD crash occurred. I have included the minidump (25303) with this post.

Can you get any information out of it or should I have the computer crash some more couple of times?

* UPDATE: I have added another minidump, the one with 15522 in the file name, which was generated when the system crashed shortly after I had disabled verifier, but I had not rebooted yet at that point. *

Cheers,

Joost

 

[JoostK]

Another minidump while running Verifier

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?

 

[zigzag3143]

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

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]

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

 

[zigzag3143]

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.

 

[JoostK]

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?

 

[JoostK]

new minidump

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?

 

[zigzag3143]

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.

 

[JoostK]

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!

 

[zigzag3143]

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?

 

[JoostK]

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.)

 

[zigzag3143]

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