Does Anyone know how to read a crash report

Hey guys,

Any help would be appreciated!! I guess recently I have been having problems when I game specifically Bad Company 2. I am running eyefinity with sapphire 5870. Normally I'll hit tab to check my score or hit Enter to go to the squad menu, sometimes it will just freeze then desktop I go. It happens on occassion could be 1 hr into gaming or 3hrs into gaming. Anyhow, here is a crash report I discovered in the BFBC2 folder:

<?xml version="1.0" encoding="UTF-8"?><report><version>2</version><sessionid>38fb22844c4fb6f7</sessionid><type>crash</type><sku>ea.dice.RomePC.Cl</sku><createtime>2010-07-28 07:37:07</createtime><buildsignature>553292</buildsignature><systemconfig></systemconfig><categoryid> 0x61D866</categoryid><stack> 0x61D866 0xCD3A6B 0xCDA77D 0xCEDE9E 0xCEE518 0x69920E99 0xCD43D0 0xD8C0EF 0xCD8EC0 0x13F3758 0x9089AE 0x62B8E2 0x74C2166B 0x857270 0x16355E0 0xFB4432 0x16356D0 0xA50D2B 0x74C2166B 0x62BEB9 0x595F3B 0x74C21126 0x596149 0x74FA0849 0x591B4E 0x591B4E 0x153BD80 0x5992A6 0x153BDA4 0xAAF058 0x14B6808 0x73D929BB 0x153BD80 0x73D98CED 0x73D92A47 0x74C23677 0x77069D42 0x74C49775 0x74C49775 0x770A03DD 0x77069D15 0x73D929E1 0x73D929E1</stack><threads></threads><screenshot></screenshot><memdump></memdump><contextdata>registers: Edi 50d9dc70, Esi 00000000, Ebx 1bfc1db0, Edx 00000000, Ecx 0d3ab430, Eax 20f604d3 Ebp 0ea8fa50, Eip 0061d866, Esp 0ea8fa40</contextdata></report>

I just ran Mem Test x86 v 3.4 for 8:18 (that's 8 hrs n 18 mins) and passed.......Also recently encountered another problem. Here is a link I guess this guy's thread says it all the only difference between us is his MB is a gigabyte n mine is Asus p6t deluxe v2.
http://www.tomshardware.com/forum/26...-gigabyte-ds3l
All my problems are the identical. Could it be just with Win 7 in general? Please help!!

Welcome!

Please follow these directions: https://www.sevenforums.com/crashes-d...tructions.html

It's always a surprise when old threads are bumped like this, as I just forget about threads until they are posted again. I never expect to see a thread from 8 months ago appear in my subscribed threads again!

In any case, welcome back. :)

I fully expect this is a hardware problem, but let's start with some potential software causes.

Install SP1: Learn how to install Windows 7 Service Pack 1 (SP1)

Install this updated Realtek ethernet driver: ErrPage

Code:

Rt64win7.sys Thu Jul 30 07:58:43 2009 (4A718AF3)

You did a clean install on the 23rd, which should eliminate any software issues. Let's move on to hardware.

Run the three Prime95 tests: https://www.sevenforums.com/tutorials...t-prime95.html

Be sure to monitor the temperatures as recommended there; post them here, and I can let you know if they are acceptable or not.

Also run Memtest86: RAM - Test with Memtest86+

Memtest86 is like a second opinion. Prime95 usually detects bad RAM pretty quickly, often within a couple of minutes. Memtest86 takes hours, and might find errors on the third pass for example. However, I've found Memtest86 can flag RAM speed issues which Prime95 completely misses.

I didn't see anything to indicate a bad hard drive, but it still may be worth it to run a quick diagnostic. Give SeaTools a whirl: SeaTools for Windows | Seagate

Let's go from there!

...Summary of the dumps:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Mar 25 07:02:27.711 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:35.133
Probably caused by : fileinfo.sys ( fileinfo!FIPreCreateCallback+1d2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_fileinfo!FIPreCreateCallback+1d2
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Mar 24 11:29:53.567 2011 (UTC - 4:00)
System Uptime: 0 days 0:22:51.004
Probably caused by : memory_corruption ( nt!MiReleaseSystemCacheView+320 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!MiReleaseSystemCacheView+320
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

Thank you for your super fast reply, just a quick question bout
Memtest86, should I test one stick at a time or would it be ok to
test all 6 (12g) sticks all at the same time? Please advise!

12Gb will take a long time to test; I guess this is up to you, so I'll explain the advantages/disadvantages.

Running the test on all the sticks at once should flag any bad DIMMs, bad motherboard slots, or incompatible speeds. If the test passes with no error, you need no more tests; that's it as far as Memtest86 goes.

Running Memtest86 on one stick at a time will take a lot more effort, as you'll have to change the sticks out every couple of hours (if you want to run the tests back to back). Seven passes on 2GB won't take too long though.

If you get errors on the 12GB, the next step is to test each stick individually, to determine which one(s) or which motherboard slot is causing the problems.

If you have mixed brands/speeds/latencies of memory, each stick may be perfectly healthy, so no errors show in Memtest; running them all together may show errors.

Your choice I guess; if you have the time to run 7 passes on 12GB, that's probably the best option. Just be aware it may take a couple of days, and the computer cannot be used during that time. If time is a constraint for you, but frequent checkups aren't, running the sticks individually might be best.

Tbh, I've run memtest from the 7 cd and 2 passes are ok no errors. Wandering if the memtest from the cd is sufficient enough to determine. I might also add that I've taken the overclock off and ran at default and was still getting hard locks. I also install SP1 with windows update this morning so the only thing I guess is to stress test with p95. Could it be that my cpu could be causing all these problems if I ran p95 and my core temps were hitting 80s n low 90s C*, my cpu temp was only 53C*?? There was also one concern I had when I ran perfmon /report and that was when windows reported my cpu, graphics card, memory, and even hard disk was poor/ really poor?? How could I interpret that information? I'm running i7-950 with 6990 could it also be my motherboard altogether? Please advise

I honestly don't know whether "Core" refers to the motherboard or CPU; try using CoreTemp to hopefully get a more descriptive label.

FYI - the Windows Memory Diagnostic Tool is known to be highly inaccurate. I still have to recommend Memtest86.