New PC, random BSOD. Multiple Errors.

[osiato]

Got this pc a week or so ago. BSOD seems to occur whenever I play games. I've played incremental games and used youtube for a few hours and some days it'll occur in an hour and some days it doesn't occur. It always occurs when playing most other games (on steam).

Not much I can say that isn't listed in the dump files except that Driver Verifier causes my audio to become shitty and I'll always end up with a corrupted screen (meaning I need to restart) before BSOD, so I can't seem to use that. I'll try and find a usb to run memtest+ on tonight.

 

[Boozad]

The errors you're receiving are mostly pointing to corruption or some defect in hardware. Before we start looking at drivers could you perform the steps outlined below please.

Download and run MemTest86+ to test your RAM. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Note

Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.

:ar: Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

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

:ar: Open an elevated command prompt, type in or copy and paste sfc /scannow and hit enter.

 

[osiato]

I ran memtest and seatools, I've run the chkdsk but only the system errors one, should I do bad sectors as well? sfc said it detected corrupted files and fixed them or something. Is that good?

 

[Boozad]

They may be fixed, test the system for stability and report back.

 

[osiato]

They may be fixed, test the system for stability and report back.

Seemed to work fine, played a game for an hour with no issue. Swapped to another game and crashed in a few minutes.

Should I upload the new .dmp file?

 

[osiato]

bump (not sure what bump rules are but I figure 1 day is acceptable..)

 

[Boozad]

Sorry this slipped me by, I've been pretty busy lately. Please upload the new dump files.

 

[osiato]

Here you go. Only got the 1, haven't played games since.

 

[Boozad]

We got a driver showing this time round, bonus. It's the ATI driver, download the latest driver from here and save it to your desktop. Download DDU and follow http://www.sevenforums.com/tutorials/367109-display-driver-uninstaller-how-use.html to remove all traces of your current driver. Reboot and install the downloaded driver.

fffff880`0a3fa9c8  fffff880`1115b93eUnable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys[/COLOR]
 atikmdag+0x11d93e

3: kd> lmvm atikmdag
start             end                 module name
fffff880`1103e000 fffff880`11de3000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR=Red]Sun Aug 17 03:15:04 2014[/COLOR] (53F01028)
    CheckSum:         00D5A709
    ImageSize:        00DA5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[osiato]

Alright, I'm downloading the videocard drivers now and will go through those steps and try out gaming again.

 

[osiato]

Well I ran the installer that I suppose was for my hardware.. I couldn't find the drivers directly, but anyway. Was mostly successful, except for AMD Steady Video Plug-In , the installs succeeded. The only error message was 'Application Install: install source package not found'. Time to play games.

 

[Boozad]

Keep us posted.

 

[osiato]

Worked alright for a bit, but suddenly BSOD!

WhoCrashed says it was the same thing as last time, but I just updated the drivers I suppose I gotta go look for specific drivers.. AMD is so hard to use I can get to this page - Desktop - But I can only get Beta drivers or the suite. I'll try out the beta drivers this time.

Got the beta drivers installed and whatnot, was fine for a bit. New BSOD (418), this one wasn't caused by those drivers. Yay \o/. Now apparently it's win32k.sys. What should I do now?

 

[osiato]

bump

 

[Boozad]

Can you run the Log Collector again and post full logs, not just dump files.

 

[osiato]

Here you go.

 

[osiato]

bump

 

[cluberti]

Uh oh - you're not gonna like this. The dumps are all over the place - video driver issues, crashes in kernel and ntfs, etc. However, there are a few that point to a misaligned instruction pointer when doing work in win32k.sys - a misaligned instruction as it references an address that is not aligned (it's not a multiple of 4). It

If you haven't already, start testing your memory and CPU for issues.

3: kd> .trap 0xfffff880072eb190
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff900c0809b40 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960001bde2e rsp=fffff880072eb328 rbp=fffff880072eb4a0
 r8=0000000000000401  r9=0000000000000001 r10=fffffa80090b4520
r11=fffffa800b328b50 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
win32k!SetOrClrWF+0xe:
fffff960`001bde2e 20488b          and     byte ptr [rax-75h],cl ds:ffffffff`ffffff8b=??
3: kd> u .
win32k!SetOrClrWF+0xe:
fffff960`001bde2e 20488b          and     byte ptr [rax-75h],cl
fffff960`001bde31 fa              cli
fffff960`001bde32 4585c9          test    r9d,r9d
fffff960`001bde35 7410            je      win32k!SetOrClrWF+0x27 (fffff960`001bde47)
fffff960`001bde37 448b5234        mov     r10d,dword ptr [rdx+34h]
fffff960`001bde3b 448b5a30        mov     r11d,dword ptr [rdx+30h]
fffff960`001bde3f 8b9220010000    mov     edx,dword ptr [rdx+120h]
fffff960`001bde45 eb0e            jmp     win32k!SetOrClrWF+0x35 (fffff960`001bde55)

3: kd> ub .
          ^ Unable to find valid previous instruction for 'ub .'

3: kd> u @rip-8
win32k!SetOrClrWF+0x6:
fffff960`001bde26 89742418        mov     dword ptr [rsp+18h],esi
fffff960`001bde2a 57              push    rdi
fffff960`001bde2b 4883ec20        sub     rsp,20h
fffff960`001bde2f 488bfa          mov     rdi,rdx
fffff960`001bde32 4585c9          test    r9d,r9d
fffff960`001bde35 7410            je      win32k!SetOrClrWF+0x27 (fffff960`001bde47)
fffff960`001bde37 448b5234        mov     r10d,dword ptr [rdx+34h]
fffff960`001bde3b 448b5a30        mov     r11d,dword ptr [rdx+30h]

The instruction pointer on this thread is misaligned, which causes Windows to bugcheck. It's *possible* that a driver could be causing the behavior, but... not likely.

 

[osiato]

I've run memtest. How do I do CPU?

 

[cluberti]

Prime95 would be the way I would recommend a CPU be stress-tested.