Well usually they are just random. I play quite a few games on my rig, such as Call of Duty, World of Warcraft etc. EVERY single time I click the WOW launcher to do updates to the game, within 30 seconds I get the BSOD. As I said before, typically it's just completely random. Sometimes I'm not playing any games at all, it just happens. Let me make it happen again. Once I do, what step exactly do you want me to do to get you the info.
If it crashes again, follow the jcgriff2 directions, so that it will include Event Logs.
https://www.sevenforums.com/crashes-d...tructions.html
I'm not sure why no new minidumps are being written, although a full memory dump seems to have been written. It can be found in C:\Windows, and is named memory.dmp.
If you want, you can zip that up, and upload it to Rapidshare: RapidShare AG, Cham, Switzerland
If that's too much of a hassle, I recommend going ahead with disabling the network adapter.Code:Event[97]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2010-12-07T20:33:47.000 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: PC Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000014, 0x0000000000000002, 0x0000000000000000, 0xfffff8800167c2f8). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 120710-14211-01.
Ok, so I opened the wow launcher like I normally do before a crash and immediately disabled the network adapter. It sat there for quite a while before I decided to re-enable the adapter and within 5 seconds, there was a BSOD again.
It sounds as if the network adapter is bad. I suggest that you purchase a new one.
Here's a good PCI Express x1 Ethernet card: Newegg.com - SIIG Single Port Gigabit Ethernet PCIe adapter Model CN-GP1021-S1
You can also get a cheaper one that's for PCI instead: Newegg.com - Rosewill RC-402 10/100Mbps PCI LAN Card 1 x RJ-45 - Also Supports WINDOWS VISTA READY
I'd get the second one, personally, but if all your PCI slots are full, you may need to go with PCI-e x1 instead.
Hey, I wanted to report back to you and let you know that installing a secondary ethernet adapter solved the issue. I went as far as completely replacing the motherboard with a brand new one (of the exact same make and model) and continued getting the same error. Apparently it's just some driver conflict but it's definitely related to the ethernet adapter on the mobo as you said. Even though I couldn't solve the driver related issue, your help pointed me in the direction for the overall fix! Thanks so much.
Thanks for the update, I'm glad to hear it.
Good luck with your computer, and let us know if you need anything else.
Quote