BSOD playing any type of game, kernal driver?

[hernar62]

I have been getting BSOD's on my computer since June of 2011. I have pretty much added all new hardware to my PC other than my hardrive.
I have taken my computer to Best Buy for a diagnostics test in which they claim that they have checked my RAM, stressed test my hardrive, and even replaced my RAM with new sticks.
I am still getting BSOD"s after all the changes and still can't figure out why. The majority of the time I get it is from playing computer games from BF3, League of Legends, or Skyrim. After the initial BSOD my comp will freeze within 5 minutes of startup.
I don't know what to do anymore. Any information will help.

- x86 (32-bit) or x64 ?
Windows 7 x64bit
- the original installed OS on the system?
No
- an OEM or full retail version?
Full Retail


- What is the age of system (hardware)?
All the hardware stems from within the last 5 months. Video Card was bought in October 2011, and everything else from November 2011.

- What is the age of OS installation (have you re-installed the OS?)
I have re-installed the OS in December of 2011.

 

[JMH]

These crashes were probably 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!!!


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

 

[hernar62]

Ok, I did the Memtest and it was 100% cleared, no errors but did get 3 BSOD's when doing the verifier. I let Verifier go on for about 24 hours.

Gotten these BSOD's

IRQL_NOT_LESS_OR_EQUAL (0x0000000a)
fffffb80`097e5f90
00000000`00000002
00000000`00000000
fffff800`030f8da4

MEMORY_MANAGEMENT (0x0000001a)
00000000`00000411
fffff6fc`50000e80
81100001`e9d55882
fefff6fc`50000e81

SYSTEM_SERVICE_EXCEPTION (0x0000003b)
00000000`c0000005
fffff800`030d3ceb
fffff880`034a5b30
00000000`00000000

I have attached the last known dump files that I had in the last 24 hours.

 

[JMH]

* Of interest is CI.DLL which MAY indicate Malware..

Please download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.

Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!

* Also I suggest you run SFC.{ Option 2}
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

 

[hernar62]

Ok, I did both. Nothing came from the scan, but the sfc /scannow came with "Windows Resource Protection found corrupt files and successfully repaired them.". It is just weird because I have done this scan for the last couple of days and nothing has come up on it until now.

This is what I got from scan.

Malwarebytes Anti-Malware (Trial) 1.60.1.1000
Malwarebytes : Free anti-malware, anti-virus and spyware removal download

Database version: v2012.02.09.03

Windows 7 Service Pack 1 x64 NTFS
Internet Explorer 9.0.8112.16421
hernar :: HERNAR-PC [administrator]

Protection: Enabled

2/8/2012 10:28:29 PM
mbam-log-2012-02-08 (22-28-29).txt

Scan type: Full scan
Scan options enabled: Memory | Startup | Registry | File System | Heuristics/Extra | Heuristics/Shuriken | PUP | PUM
Scan options disabled: P2P
Objects scanned: 372528
Time elapsed: 42 minute(s), 11 second(s)

Memory Processes Detected: 0
(No malicious items detected)

Memory Modules Detected: 0
(No malicious items detected)

Registry Keys Detected: 0
(No malicious items detected)

Registry Values Detected: 0
(No malicious items detected)

Registry Data Items Detected: 0
(No malicious items detected)

Folders Detected: 0
(No malicious items detected)

Files Detected: 0
(No malicious items detected)

(end)

 

[JMH]

Good reports from both.
Well done!

 

[zigzag3143]

Go0d news on both. let us know if your issue has been resolved

 

[hernar62]

I received two BSOD's but they did not go into the dump folder. It froze at 90%.

It gave me

Stop x24
NTFS.SYS
Address: FFFFF8800122414
Base at FFFFF88001214000
Date Stamp4d79997b

 

[JMH]

* We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

* I suggest you run Disk Check.{ Option 8}
This may take a long time.

http://www.sevenforums.com/tutorials/433-disk-check.html

 

[hernar62]

Got done with Disk Check, I let it run overnight while I was sleeping and woke up to my login screen. How do I find out what it scanned?

 

[JMH]

This should help you...

http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html

 

[hernar62]

Here is what I got from it. I know it is hard to figure out the problem without some BSOD logs. So I will wait until I get at least 2 more to help you guys out some more. I appreciate all the help that has been given to me in the last couple of days.

Checking file system on C:
The type of the file system is NTFS.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
199936 file records processed. File verification completed.
849 large file records processed. 0 bad file records processed. 2 EA records processed. 76 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
267752 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
199936 file SDs/SIDs processed. Cleaning up 203 unused index entries from index $SII of file 0x9.
Cleaning up 203 unused index entries from index $SDH of file 0x9.
Cleaning up 203 unused security descriptors.
Security descriptor verification completed.
33909 data files processed. CHKDSK is verifying Usn Journal...
36732632 USN bytes processed. Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

976657407 KB total disk space.
236924008 KB in 164966 files.
95276 KB in 33910 indexes.
0 KB in bad sectors.
332331 KB in use by the system.
65536 KB occupied by the log file.
739305792 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
184826448 allocation units available on disk.

Internal Info:
00 0d 03 00 e7 08 03 00 8f bb 05 00 00 00 00 00 ................
8a 1a 00 00 4c 00 00 00 00 00 00 00 00 00 00 00 ....L...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.


Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.


----------------------------------------------------------------------------------


CHKDSK is verifying files (stage 1 of 5)...
202240 file records processed. File verification completed.
851 large file records processed. 0 bad file records processed. 2 EA records processed. 76 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
270138 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
202240 file SDs/SIDs processed. Cleaning up 10 unused index entries from index $SII of file 0x9.
Cleaning up 10 unused index entries from index $SDH of file 0x9.
Cleaning up 10 unused security descriptors.
Security descriptor verification completed.
33950 data files processed. CHKDSK is verifying Usn Journal...
34007672 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
202224 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
184747219 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

976657407 KB total disk space.
237240372 KB in 166496 files.
96076 KB in 33951 indexes.
0 KB in bad sectors.
332079 KB in use by the system.
65536 KB occupied by the log file.

 

[JMH]

Thanks for reporting back.
Now we wait to see if you crash as you go about your normal routine....

 

[hernar62]

Ok, it seems like I don't get BSOD's anymore from playing games, other than league of legends after everything I have did. Seems like what you guys told me fixed that, is there anything that can help me playing LoL without getting bug errors for both my explorers (gives me a memory error for chrome and firefox) and LoL?

 

[JMH]

You know where to find us should you require more help / DMP analysis.

Any browser issues/ questions are best addressed to this part of our Forum.

http://www.sevenforums.com/browsers-mail/

 

[hernar62]

Ok, I thought I had it fixed, but it seemed like it BSOD'ed when I was playing Skyrim. I posted the file on the post.

 

[zigzag3143]

Ok, I thought I had it fixed, but it seemed like it BSOD'ed when I was playing Skyrim. I posted the file on the post.

First Skyrim has huge problems. I must do more than a dozen crashes a day with it. If it is the only game still crashing I would go to the developers site to see if there are any updates or patches available.

 

[JMH]

Still caused by a memory exception..

Generic Resolution.

You should use some basic troubleshooting techniques.

Make sure you have enough disk space.

If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.

Try changing video adapters.

Check with your hardware vendor for any BIOS updates.

Disable BIOS memory options such as caching or shadowing.


BTW...
Refer this link...
Stop error message in Windows 7 or Windows Server 2008 R2: "Stop error code 0x0000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)" or "Stop error code 0x00000050 (PAGE_FAULT_IN_NONPAGED_AREA)"