rampant BSOD during games and idle

[phyguy]

I don't have long, I'll probably BSOD soon. I don't know what to do, I'm at my wit's end. I was playing GW2 when I started getting rampant BSODS, even when I just idled on the desktop. its happened for about 3 hours now. I tried uninstalling my GPU drivers. I cant even install new GPU drivers, because it just BSODs whenever I try to install anything. I recently installed a new processor, but it has been running perfectly for 3 weeks now, so I doubt it is an issue. I tried swapping out ram, removing 1 stick then the other, nothing changes.

W7 64 bit professional
GPU: Nvidia GTX 580
PSU: AMD Phenom II X4 965
8GB of G-skill ram.

I've checked the event viewer, all I'm seeing are kernel 41 (63) errors. Dunno if that helps at all.

If anything else is needed please tell me, I'll be checking this thread on my phone. a speedy reply is appreciated, I just started online classes this week and I need to be up and running.

I followed the instructions to attach the dump file.

 

[Maguscreed]

What I'm seeing is a cascade of random errors followed by a cascade of memory errors, wash rinse repeat.

While this could be caused by a driver issue. I don't think it would be quiet so bad on you if it was only a driver, you are getting bad pfn lists, and even the microsoft management console has crashed. I'm going to suggest taking memtest to it, and letting it run for a bit.
The bright side is, it's very possible that only one of your two ram sticks is bad, if you can isolate that you can at least run for awhile on 4 gigs while you wait for new ram.

Anyhow memtest instructions / download etc.. are all here
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

I suggest allowing a few passes if your memory is as bad off as I think it is, you'll likely see errors popping up fairly quickly though. If you do get errors try pulling one stick of ram and running on the other.

Like I said at the start, there is the possibility this is caused by a driver or messed up security suite. Testing ram is easy if a tad time consuming though.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa800171a0e0
Arg3: 000000000000ffff
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003b05b50 to fffff80003a99fc0

STACK_TEXT:  
fffff880`0df2a538 fffff800`03b05b50 : 00000000`0000001a 00000000`00041790 fffffa80`0171a0e0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0df2a540 fffff800`03accb69 : 00000000`00000000 00000000`06bfefff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35054
fffff880`0df2a700 fffff800`03dace21 : fffffa80`06fef570 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`0df2a820 fffff800`03dad223 : 00000000`00000000 00000000`06740000 fffffa80`00000001 00000000`00000000 : nt!MiUnmapViewOfSection+0x1b1
fffff880`0df2a8e0 fffff800`03a99253 : 00000000`06918000 00000000`00000000 fffffa80`06ef3060 fffff880`0df2ab50 : nt!NtUnmapViewOfSection+0x5f
fffff880`0df2a930 fffff800`03a95810 : fffff960`0012694c fffff880`0df2aca0 fffffa80`06f25060 00000000`0020dd08 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0df2aac8 fffff960`0012694c : fffff880`0df2aca0 fffffa80`06f25060 00000000`0020dd08 00000000`000f0007 : nt!KiServiceLinkage
fffff880`0df2aad0 fffff800`03a99253 : 00000000`00000000 00000000`0000011c fffff880`00000000 00000000`00000000 : win32k!NtGdiCreateDIBSection+0x3e4
fffff880`0df2abb0 00000000`7465077a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0020dce8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7465077a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!NtGdiCreateDIBSection+3e4
fffff960`0012694c 488bcf          mov     rcx,rdi

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  win32k!NtGdiCreateDIBSection+3e4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50ad9b54

FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!NtGdiCreateDIBSection+3e4

BUCKET_ID:  X64_0x1a_41790_win32k!NtGdiCreateDIBSection+3e4

Followup: MachineOwner

 

[phyguy]

I ran it, and as you predicted I instantly received notification that I had memory hardware problems. I checked each ram stick individually, with stick A I got an immediate BSOD after logging in. I switched to stick B and it is stable!

I decided to do a bit of a makeshift stress test, by I trying to install my new GPU driver (that was a surefire way among other things to make it Bsod) I was able to install my new GPU driver successfully. no crashing like it usually did at around 10%. I am going to let it idle for a few hours, then if all is well ill try out some games, iTunes etc. and report back.

Thanks for the amazingly quick response, I am very pleased.

 

[Maguscreed]

No problem I'm glad it was a relatively easy fix, and on the bright side RAM is super cheap these days so replacing the bad stick shouldn't be a big problem.