BSoD After CTD From MW2 or Battlefield Bad Company 2

[Mitas]

Hi Guys,

I built my machine a couple of years ago and it has been pretty solid ever since (minus one or two crash due to new hardware). However,over the last few weeks I have been getting a blue screen shortly after a game crashes to desktop (mainly MW2 & BFBC2).

At first I thought it might be heat due to the hot weather here, but I've given it a clean out and temps are well within the normal ranges. Before I go through everything to try and pin this down, I wonder if you could take a look at my minidump file (attached) and point me in the right direction.

The following is what the Reliability Monitor picked up:

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 2057

Extra information about the problem
BCCode: 1a
BCP1: 0000000000041790
BCP2: FFFFFA8000D3F0B0
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Bucket ID: X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+3c8
Server information: 1e5366d1-aa54-4f79-8a0c-77a58f2aefe6

If you need any more information, please let me know.

Any helps greatly appreciated.

Cheers.

 

[usasma]

It's hard to figure out a problem with just one dump file - especially when it's one that could be hardware or software. Please provide all of the dump files that you have.

Please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those 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 manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: Driver Reference ).
Please pay particular attention to any dated 2008 or earlier:

ASACPI.sys   Sun Mar 27 22:30:36 2005 - [B][U][COLOR=Red]a KNOWN BSOD Cause[/COLOR][/U][/B] - Asus ATK0110 ACPI Utility driver - http://www.carrona.org/dvrref.html#ASACPI.sys
habu.sys     Thu Oct 26 04:33:31 2006 - Razer Diamondback USB Optical Mouse Driver                                                              - http://www.carrona.org/dvrref.html#habu.sys
RecFltr.sys  Wed Jan 17 20:23:09 2007 - Reclusa Keyboard - http://www.carrona.org/dvrref.html#RecFltr.sys

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul  5 17:28:38.912 2010 (UTC - 4:00)
System Uptime: 0 days 2:48:25.176
BugCheck 1A, {41790, fffffa8000d3f0b0, ffff, 0}
Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  Steam.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/FONT]

 

[Mitas]

Hi Usasma,

Thanks for the help!

Unfortunately I don't seem to have any other dump files in the folder - I have a feeling I cleared them out after I (stupidly) thought I'd solved the issue initially. I'm not sure if it helps at all, but I can give you the information listed in the reliability history for the crashes I've had previously?

I've taken your advice on the drivers and updated those you listed. If I get any further BSoD's I'll post the dumps here and hopefully that will shed some more light on the issue.

Additionally, I noticed that at the same time as the BSoD's, Windows Defender also crashes. Would this be the cause or just a symptom of the problem?

Again thanks for your help.

 

[Mitas]

Ok,

Just recovered from another BSoD. This time round BFBC2 crashed and I had to end the program via task manager. Usually I get a blue screen within a few seconds of this happening.

However, on this occasion I didn't and on inspecting the reliabilty history noticed that at the same time as the CTD superfecth had stopped working. This also seemed to mess up the Windows Aero graphics and I decided to restart the machine.

Shortly after the restart I fire up Steam and it begins to update - then I get the latest BSoD.

New dump uploaded.

Cheers.

**Edit**

I've just done a couple of SFC /Scannow. First time it got to 29% and then displayed the following error:

'windows resource protection could not perform the requested operation'

On the second try it got to 44% and found corrupt files, but was unable to repair. The details were saved to the attached CBS log.

Just to add, when I first started getting the BSoD's I ran both SFC /Scannow and CHKDSK, but both were clean at that point.

Thanks.

 

[usasma]

What we'll do is watch a couple of the dump files to see if we think it's hardware or software - and we'll try to fix each one as we go along.

If we figure software, we'll run Driver Verifier (the dumps will have some sort of consistency with the errors and the components that are blamed)
If we figure hardware, we'll run hardware diag's and stress tests (the dumps will appear random and will blame random components)

So far we've got some memory issues being blamed (and they're trending towards randomness) - so let's start with some free diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 15:04:21.287 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:15.550
BugCheck 1E, {ffffffffc0000005, fffff80002da70cc, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiApplyCompressedFixups+40 )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]

 

[Mitas]

Thanks for getting back to me Usasma.

**Edit** Better make that 2 new dump files - again, just using the online scanner and general browsing. Both are included in the attachment. **Edit**

A new dump file is attached - BSoD occured while running the malware scanner (ESET) and just general browsing. This time it looked slightly different and mentioned something about the pagefile.

I'm running the ESET online scanner again and will update you on the results.

I've downloaded Memtest86+ and also Seagate SeaTools - as it seemed like a good match for both my Maxtor and WD Raptor HD's.

Unfotunately I don't have any blank discs to burn the ISO's at the moment, but will get the tests done tomorrow and let you know how it goes.

Thanks again for all your help so far!

 

[usasma]

Looking more and more like a hardware issue:
BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 16:48:40.124 2010 (UTC - 4:00)
System Uptime: 0 days 0:16:58.012
BugCheck 1A, {41790, fffffa8000d3aeb0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  SearchProtocol
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 16:30:50.971 2010 (UTC - 4:00)
System Uptime: 0 days 1:25:41.233
BugCheck 50, {fffffa880520486a, 0, fffff80002bc5c4c, 5}
Probably caused by : memory_corruption ( nt!MiLogPageAccess+dc )
BUGCHECK_STR:  0x50
PROCESS_NAME:  OnlineCmdLineS
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]

Here's the set of stress tests to use IF the memory and HDD tests pass:

Then, if the above tests pass, I'd try these free stress tests:

FurMark download site: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Prime95 download site: http://www.mersenne.org/freesoft/
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.

 

[Mitas]

Quick update.

I ran the HD test and both drives passed fine.

I started off memtest86 on all 4 sticks and it had found a couple of errors around test 3 in pass 0. I left it running while I had some lunch and by the time I got back (1.30 hrs later) we were up to 7500 errors. At this point I was fairly certain that I had a dodgy stick and it was just a case of finding out which one.

The first stick did 22 passes with no errors (left it over night). The second managed 10 seconds before we had a couple of hundred errors and after testing it in every slot, it looked like I'd found the culprit. I've tested the others individually with no problems and I'm running the test again on the remaining good sticks together to make sure.

While it is a pain in the ass, at least I know where the problem lies and I really appreciate your help in pinning it down Usasma! Now it's just a case of RMA'ing the matched pair with the faulty module back to Corsair.

Hopefully that's definately the problem, but if I start getting BSoD's again I'll be sure to resurrect this thread!

Cheers.