I get some BSODs when I play games like World of Tanks, League of Legends, Skyrim, etc. IRQL_Not_Less_or_Equal, Driver_IRQL_Not_Less_or_Equal, System_Service_Exception, Bad_Pool_Header.
Things I've tried:
Replaced RAM, Put more fans to prevent overheating, reinstalled windows 7, checked connections inside computer.
Any help would be appreciated. :)
Hi jsnarch,
Welcome to the 7forums :)
The only problem I see is an improper seating of the memory
Make sure the memory is seated in the same colored slots.
Attachment 386259
So I change the RAM to the two black sockets and got the memory management bsod, I going to switch the RAM to the two grey sockets and see if they work there.
I am also am including another attachment of the dmp files.
If the other colored slots don't help either, I suggest that you try a memory test per below instructions.
Diagnostic Test
RAM TEST
Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums
Note
MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.
Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.
So I switched the RAM sticks to the grey slots and I was able to play a game. A few minutes after I quit the game, I got a different BSOD.
It said, "An attempt was made to write to read-only memory." 0x000000BE (0xFFFFF8A00E855412, 0x5A400001F37A8121, 0xFFFFF88006D124B0, 0x000000000000000B)
For some reason, I can't find the crash on BlueScreenView.
If you know anything about the BSOD I just described, let me know. I am hoping this RAM is not bad because I just bought it a week ago. I thought my other RAM was bad.
Upload the dump from either %systemroot% or %systemroot%\minidump for analysis, it has 2 possibilities
1. driver writes to an improper memory address
2. a part of the memory is basically bad
Most recent dumps. Got some ntfs.sys BSODs
I don't see a 0xBE coming back in the dumps, in the logs there is also nothing present about a 0xBE crash.
Anyway, seeing the NTFS + 0x1A it may be time to check in with the hard drive.
Diagnostics Test
HDD TEST
Run following tests
- Short Drive Self Test
- Short generic
- Long generic
If the short generic fails, no need for the long generic.
NoteDo not run SeaTools on an SSD as the results will be invalid.
Disk Check - Windows 7 Help Forums
- scan for errors, no quick scan but full scan
- check the health,
- benchmark.
It may take some time, but please take the time you need to perform it properly.
Let me know what the results are
- of the error scan,
- make a screenshot of the health of every hard drive and post the screenshots,
- post screenshots with the benchmark of the
- transfer rate,
- access time,
- burst rate,
- cpu usage.
Alright, thank you very much for so far. I really appreciate it.
By the way, I found another .dmp file in C\Windows. It is called MEMORY.dmp, it's too big to upload. 180MB
There is no need to upload it anymore :)
I wanted to have a look at it for the 0xBE crash if there wasn't a minidump, but with the normal settings it is already overwritten.
Quote