BSOD with Call of Duty MW3, Kernal Data In page Error

[code90]

I have had problems with getting BSOD while playing new games. First had loaded Battlefield 3 onto my C: drive (using two 1 TB drives in RAID 1 as C. It would play for short while, then crash to BSOD. Noticed RAID had gone critical. Eventually replaced one of the HD and repaired the RAID. It still crashed. I figured maybe it was the game, or playing in RAID that caused problem. Then I put in a new 320 GB HD and loaded Call of Duty MW3 onto that drive. Played Call of Duty for while, then started getting BSOD. Have just noticed that the RAID has again gone critical and appears to have split one of the two 1 TB drives from the RAID array (it is now shown as a <single drive> instead of <LD 1 of 2>). The BSOD has listed "Kernal data in page error". I have tried to attach the dump file. Any thoughts?

 

[zigzag3143]

These crashes were caused by memory corruption/exception (probably a drivr)
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.

 

[code90]

I ran Verifier and it crashed before windows finished booting. Was able to boot to safe mode and turned off Verifier. I attached the dump file from the crash. Will start memtest now. Thanks for any help.

 

[code90]

Memtest went through 8 times with no errors. Any thoughts?

 

[zigzag3143]

I ran Verifier and it crashed before windows finished booting. Was able to boot to safe mode and turned off Verifier. I attached the dump file from the crash. Will start memtest now. Thanks for any help.

Related to timntr.sys Backup Archive Explorer from Acronis/. I would remove or update it.

 

[code90]

Found out timntr.sys was in Seagate Diskwizard. I uninstalled Diskwizard, but still had to go into Windows Drivers and actually delete the timntr.sys file to get it out of there. I removed the three other drivers that were associated with Acronis too. After this, game on! All playing well together now. Thanks so much for the help.