Does Anyone know how to read a crash report

[UMG]

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/268556-30-post-boot-normal-shutdowns-gigabyte-ds3l
All my problems are the identical. Could it be just with Win 7 in general? Please help!!

 

[Jonathan_King]

Welcome!

Please follow these directions: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[UMG]

Hey Jonathan,
sorry for such a long delay ( 8 Months ) but I been busy with work and troubleshooting a LOT since I posted this problem. I went ahead and followed your directions and attached are the files you requested. Please advise

 

[UMG]

attached another file

 

[Jonathan_King]

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

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: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-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: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

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:

[font=lucida console]
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.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[UMG]

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!

 

[Jonathan_King]

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.

 

[UMG]

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

 

[Jonathan_King]

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.

 

[UMG]

I was referring to my cpu cores that hit 80s and low 90s. As for the hardware the reason I had suggested my motherboard is because if in fact my dimms are good (all 6 sticks) and my cpu overall temp only hit 53 celcius and I have a new graphics card, reinstalled os, board drivers from the cd that came with it and if it is still indicating hardware then I would think it is safe to assume the board is faulty. But again atm, I am still running memtest86: walltime 7:32:50 1 pass 0 errors since I lefted for work but I think the test will come back with 0 errors. It would be up to p95 at that point to see if my system is stable. Again, I have set clocks back to default.

 

[Dave76]

Jonathan has given you excellent advice and suggestions, as usual.

You are having issues that can come from several causes, the best way to find them is to systematically rule out causes.
1. Software, drivers and SP1 - done

2. Hardware testing-
MS memtest is not the best memory test, as mentioned, memtest86+ is much better.

You should run memtest86+ as per the tutorial.

Also run Memtest86: RAM - Test with Memtest86+

6x2GB RAM cards brings up several possible causes, as well as several difficulties in finding the causes.
Welcome to the world of lots of RAM for not so much money.
The above tutorial describes the best way to test RAM, with six RAM cards this will take several days to complete.
​

Jonathan has given you the best approach to testing this much RAM, due to the time envolved, first run memtest86+ with all six cards installed.
Minimum 7 passes, 8 passes are better.
This will be best done overnight or start in the morning if you are gone all day.
If there are any errors, one errors is too many, you can stop the test.

The next step is:

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.

This will take a long time, but is necessary, refer to the tutorial for the procedure.

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

80-90C is very high for a water cooled CPU at stock settings.

This needs to be addressed, again I agree with Jonathan, download and run CoreTemp to get a clear confirmation on your CPU temps.
Core temps are taken from each CPU core, CPU temp is taken from the CPU case.
You should see no more than a 10C temp difference between the two.
It is possible that if your CPU cores are reaching 90+C your CPU could be throttling down to reduce those temps.
The mention of the perfmon report indicates that this needs further attention.

Check your GPU temps, at idle and at full load.



Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.

For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Go to your BIOS and tell us what the CPU, RAM and memory controller (QPI voltage in your BIOS) voltages are.



EDIT:
Just saw your last post.

Check your motherboard website for updated drivers.
The drivers on the CD are generally older, even on the day you buy the motherboard.

Let memtest86+ run for minimum 7 passes, each pass uses different tests, so it is important to let it run.
This may take a while with 12GB RAM.

Memtest86+ is one of the best RAM testing software but, no software can 100% confirm that there are no errors/faults on RAM.
It is the first important step, if it finds errors then you know there is a problem. If it doesn't find an error you can't completely rule out the RAM as causing the issue.

I am still running memtest86: walltime 7:32:50 1 pass 0 errors

Finished 1st pass and 0 errors in 7 1/2 hours, this will take a long time to complete 7 passes.

What is your mobo BIOS version?
The MSI site lists this on the last three BIOS updates:

- Update CPU micro code.
- Improved memory compatibility.

Don't recommend updating BIOS unless absolutely necessary, might have to come back to this.

 

[UMG]

Hi Dave, I agree that Jonathan has given me some very good advice and approaches. Just as I posted my last walltime about 5-10 mins after it complete 2 passes with no errors. I stopped it around 8:30 yea that is a long time if I was going to complete 7 passes. I also have a friend atm helping me find a solution and before this post we started gaming and he mentioned that someone had disabled Catalyst Control Center task manager end process tree and have had no crashes, hmmm? Of course I'm still in the process of testing/troubleshooting hardware. Regarding my CPU cores to be exact real temp indicated during prime with my cpu oc 4.187
core 0: 78
core 1: 81
core 2: 76
core 3: 79
and these readings were at the time of running p95 so I don not have a screenshot. However, moving forward, when I do test with p95 again I will per your request take a snip shot of my cpuz, and all tabs. Now regarding voltages:
cpu vcore: 1.46
cpu pll: 1.96
qpi: 1.59
dram: 1.66
ioh: 1.15-1.31
pci e: 1.51-1.6
memory speed: 1600 @ 1450
bios version: 1.2

 

[Dave76]

OC Genie?

Re: i950 Overclock Help (OC Genie Help)

HU16E


Re: i950 Overclock Help (OC Genie Help)
« Reply #12 on: 10 March 11, 06:01:37 »
Quote
[email protected]

You for sure don't want to allow this high a voltage. 1.35v's is the recommended maximum. For around a 1600 RAM speed, would estimate 1.22v's or 1.24v's should be plenty.

The above post is discussing the same CPU and Motherboard that you have.

A QPI voltage at 1.59v can damage your CPU.
This could be the source of your crashes and will be causing high core temps.

All automatic OverClocking utilities set the voltages way too high and this will cause damage to the CPU and RAM.
Manual OC'ing and testing is the preferred method, will take longer but is much safer for your components.
One button OC'ing is very flawed at this stage.

You have previously mentioned that you have set your clocks back to stock settings.
How did you do this?
Reset BIOS to optimized defaults?

At stock clocks and cpu vcore: 1.46v, it's not suprising that the core temps are so high.
Your CPU VID voltage range is 0.800v - 1.375v.

What water cooling are you using?

Can you post the CPUZ tabs now?
The system doesn't need to be stressed for these readings, at idle is fine.