BSOD whilst gaming, error 0x0000001a

[zachdb]

Hello,

Recently while running games such as Team Fortress 2 (resulting in the first dump file, 7/3/2012 5:03 PM - 070312-15366-01.dmp) and Civilization V (the second dump file, just 2 hours ago - 070412-19125-01.dmp) the game has froze and consequently a BSOD popped up immediately after.

I have not witnessed this error prior to yesterday albeit I have came back to my computer telling me it had just recovered from a BSOD (in the same way it did when I rebooted after the more recent ones. There have been no .dmp files for these, however.)

I have peered into the dump files and the errors seem to point to two files:
- ntoskrnl.exe
- wind32k.sys
Both labeled under Bug Check String as "MEMORY_MANAGEMENT".
Both are error 0x0000001a.

System Specifications:
Everything has been bought/installed as of March 2012. (Bought 21st, built ~27th)

OS: Windows 7 Home Premium x64
- Installed myself, as this is a custom-built computer (OEM)
- Original installed OS (have not reformatted)
RAM: CORSAIR Vengeance 8GB (2 x 4GB) DDR3 SDRAM DDR3 1600 (PC3 12800)
MB: ASrock Z68 Extreme3 Gen3
CPU: Intel i5-2500k (was overclocked to 4.5Ghz during crashes, although heat is not a problem. Have down-clocked since the previous BSOD to 4.2Ghz)
GPU: MSi Nvidia GTX560Ti 2GB

As for memtest86, I will run that when I have time. I have a CD made to boot up and run the test while I sleep (7+ hours for 7-8 cycles). I am posting here now to make sure my suspicions are in the right place (memory problem, I am guessing)

The files pertaining to this error have been attached below.
Will look forward to a reply and a whole-hearted thank you in advance!

If there is any bit of information you need, I will try my best to provide.

In relation to the report saying that I have no antivirus, I have Windows Security Essentials on and fully updated.

 

[Jonathan_King]

Hello,

I'd suspect a problem with the RAM or video card, but we can try a driver update first. Run the Intel Driver Update Utility and make sure to install updates it shows, especially the graphics driver: Intel® Driver Update Utility

igdkmd64.sys     Tue Feb 14 13:47:30 2012 (4F3AAC42)

One thing I notice, the nVidia drivers are not even showing as being loaded. Is this a setup such that the motherboard switches to the nVidia card when you put a load on it? I'm not flagging a problem, I'm just curious is all.

Definitely run Memtest86 when you get the chance, and also Prime95: http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

Daemon Tools is also known to cause issues sometimes. I don't think it would be responsible for the stress-related crashes, but it could be involved with the spontaneous BSOD. I'd recommend removing it for now, at least until the BSODs are resolved.

...Summary of the dumps:

[font=lucida console]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Jul  4 18:50:45.624 2012 (UTC - 4:00)
System Uptime: 0 days 1:15:46.857
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+355e4 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355e4
BiosReleaseDate = 11/22/2011
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Tue Jul  3 17:02:35.992 2012 (UTC - 4:00)
System Uptime: 0 days 22:42:35.225
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+19c )
BUGCHECK_STR:  0x1a_8886
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  Steam.exe
FAILURE_BUCKET_ID:  X64_0x1a_8886_nt!MiUnlinkPageFromLockedList+19c
BiosReleaseDate = 11/22/2011
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[zachdb]

hello,

1: i'd suspect a problem with the ram or video card, but we can try a driver update first. Run the intel driver update utility and make sure to install updates it shows, especially the graphics driver: intel® driver update utility

2: one thing i notice, the nvidia drivers are not even showing as being loaded. Is this a setup such that the motherboard switches to the nvidia card when you put a load on it? I'm not flagging a problem, i'm just curious is all.

3: definitely run memtest86 when you get the chance, and also prime95: http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

4: daemon tools is also known to cause issues sometimes. I don't think it would be responsible for the stress-related crashes, but it could be involved with the spontaneous bsod. I'd recommend removing it for now, at least until the bsods are resolved.

1: I have successfully installed the Intel drivers I was missing (graphics & chipset)

2: I have never heard of this, and it surprises me. No, I had never set it up to be like that. Do you know of a way to fix that? The primary card should be the 560 and nothing else. I do not know why the drivers do not show as loaded. Perhaps a reinstallation of them would fix that?

3: I have Prime95 handy, and I will do some further tests with that. The previous tests I did with the 4.5 overclock came out very positive, with temps barely rising above 60 (I'd say the avg would be 60, albeit it went to 61 a few times) and a steady voltage of 1.288v. No hiccups or BSODs. These were done about a month ago.

4: Uninstalled.

As for the memtest86, I will reply tomorrow with the results and let you know of any errors.

Hopefully it was just a driver issue! Although I still have to fix that nVidia driver problem.. I'll go ahead and try to reinstall the driver via the driver suite.

 

[Jonathan_King]

There's probably a setting in the BIOS you can change to set your nVidia card as primary. Also, I'd suggest you back off your overclock a bit for now. Even with torture testing, it's difficult to prove 100% stability, and seeing as you're having problems now, we can't be sure about anything.

 

[zachdb]

There's probably a setting in the BIOS you can change to set your nVidia card as primary. Also, I'd suggest you back off your overclock a bit for now. Even with torture testing, it's difficult to prove 100% stability, and seeing as you're having problems now, we can't be sure about anything.

Well, it's been overclocked since around late March without any problems until yesterday.

But, if it helps, I will reset the BIOS settings / OC and look if the primary card is set up right.

 

[Jonathan_King]

That sounds like a good plan. Bear in mind, computers slowly lose stability when overclocked. The additional heat and voltage definitely shortens the life of the chip, albeit in most cases of reasonable overclocks the CPU still is not the first part to go. Still, many people find they have to keep bumping up voltage or decreasing the clock speed as time goes on.

 

[zachdb]

That sounds like a good plan. Bear in mind, computers slowly lose stability when overclocked. The additional heat and voltage definitely shortens the life of the chip, albeit in most cases of reasonable overclocks the CPU still is not the first part to go. Still, many people find they have to keep bumping up voltage or decreasing the clock speed as time goes on.

Everything has been reset in the BIOS.
I checked the GPU setting and it is (and has been) set to PCI Express.

No idea why it shows up that the driver is not loaded. All system-stat readers confirm that I am using the 560Ti..

 

[zachdb]

It seems it may not be stress-related, as I just played 3+ hours of TF2 with no hiccups. I don't know what else may be causing it, however. The other non-recorded BSODs (the ones where I would come back to Windows telling me it recovered from a crash) happened when the system was idle.

Again, can't really be sure without a memtest. I will now be running it and will report the results in the morning.

 

[zachdb]

When I conducted the memtest, it was clear that the second stick of RAM was the issue. I took the stick out and the memtest showed up clear. I will contact my RAM provider and see if I can get new sticks. I think this may have solved it! Although I can't be sure until I get the new sticks. If the problem persists I will be sure to come back here.

(Once I took out the faulty RAM stick, those errors did not show up.)

 

[Jonathan_King]

That seems like a good lead, nice work! If the RAM replacement doesn't solve the problem we'll be happy to continue.