Random BSOD 3B (usually unattended) - Windows 7 x64

[CarolHaynes]

Been getting random reboots with bugcheck 3B listed on an almost daily basis.

On every occasion it has happened when I have been away from the computer.

I ran verifier.exe and that flagged up a bigcheck c9 for stream.sys but that file doesn't seem to be damaged and is identical to the stored copy.

SFC /Scannow generates no errors in file integrity.

Driving me mad - anyone any ideas?

I have attached a zip of an original 3B minidum and also a dump created by verifier.

(By the way I tried to download windbg from Microsoft but the only version I can find for Windows 7 x64 is on MSDN and requires a user account!)

 

[JMH]

These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

If you have Raid > update its Driver.


Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

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

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

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



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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).

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 "Special Pool", "Force Pending I/O Requests" and "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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[zigzag3143]

In addition please update these drivers from as far back as 2004. I also note the many Audio/Video drivers that may be contributing to the issue.

If there are no updated drivers these need to be re-installed in compatibility mode.


Old drivers needing updating

lirsgt.sys    3/6/2004 2:53:01 PM    fffff880`08f32000    fffff880`08f3f000    0x0000d000    0x404a2c1d                            
GVTDrv64.sys    9/5/2006 2:10:02 AM    fffff880`08f6e000    0074f8ec`08f78000    0x0075006c0000a000    0x44fd22ca                            
wacommousefilter.sys    2/16/2007 1:12:17 PM    fffff880`0755a000    fffff880`07562000    0x00008000    0x45d5f401                            
ezplay.sys    4/30/2007 5:08:55 AM    fffff880`04fb3000    fffff300`04fcfe80    0xfffffa800001ce80    0x4635c037                            
atksgt.sys    10/20/2008 2:50:38 AM    fffff880`08ee1000    fffff880`08f30000    0x0004f000    0x48fc384e                            
MtiCtwl.sys    11/4/2008 2:40:50 AM    fffff880`01800000    c4834080`01809000    0xc483480000009000    0x490ffc82                            
RimSerial_AMD64.sys    11/24/2008 12:01:01 PM    fffff880`05884000    fffff880`0588bc00    0x00007c00    0x492addcd                            
gdrv.sys    3/12/2009 10:22:29 PM    fffff880`0aa81000    fffff300`0aa8a000    0xfffffa8000009000    0x49b9d175                                                   
GEARAspiWDM.sys    5/18/2009 7:17:04 AM    fffff880`04f82000    fffff300`04f8f000    0xfffffa800000d000    0x4a1151c0                            
cdrbsdrv.SYS    6/16/2009 10:37:33 PM    fffff880`01bdd000    fffff880`01beb000    0x0000e000    0x4a3864fd

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

 

[CarolHaynes]

Thanks for the feedback.

To JMH:

I have already run MEMTEST+ for over 24 hours and no errors. Been running fine for the last 12 months until the last couple of weeks.

Don't use RAID (but if I were to I have already installed the latest mobo and GPU Catalyst drivers).

Not overclocking.

I'll have another stab at verifier with the setting you suggested.

To zigzag3143:

I have checked the drivers you suggested and installed the latest versions I could find. Some of them have been updated but the file version is the same, some are newer. I'll see if it makes any difference.

Cheers - I will post back when I have some results to share (probably tomorrow).