Solved BSOD Whilst using computer in various situations

[Jimjag]

Hi guys

I've started getting random BSOD's on my computer and I'm trying to work out what's triggering them.

They normally happen after a few hours, but I'll get the occasional one within half an hour of the previous one happening.

If you need any further information please let me know

Thanks

Blue screened again. Included an MSINFO32 into the ZIP as requested

 

[Arc]

It appears that the ATI display driver is causing the issue there.

1. Download the latest WHQL of the display driver from this link : http://www.sevenforums.com/graphic-cards/1810-latest-amd-catalyst-video-driver-windows-7-a.html and save it on your desktop.
2. Download AMD Catalyst Un-install Utility and save it on desktop, too.
3. Disconnect internet.
4. Run AMD Catalyst Un-install Utility to uninstall the display driver totally.
5. Restart the computer.
6. Install the latest WHQL display driver already downloaded.
7. Restart and connect back to internet.

Let us know the results. If the BSODs continue to occur, next time upload your MSINFO32.nfo file, too.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

____________________________________________________________________________
BSOD ANALYSIS:

BugCheck 50, {fffffffffffffffb, 1, fffff800030d15b0, 0}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!SleepInputIdle+79 )

Followup: MachineOwner
-------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff880048d1eb5, fffff8800a6bb760, 0}

Probably caused by : atikmdag.sys ( atikmdag+aeeb5 )

Followup: MachineOwner
-------------------------------------------------------------------------
BugCheck A, {9000000000, 2, 1, fffff800030dafb2}

Probably caused by : ntkrnlmp.exe ( nt!KeReleaseMutant+292 )

Followup: MachineOwner
-------------------------------------------------------------------------
BugCheck D1, {0, 2, 8, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

Followup: MachineOwner
---------

 

[Jimjag]

Thank you,

I'll let you know how I get on

 

[Jimjag]

It BSOD'd again.

What should I try now?

 

[Arc]

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[Jimjag]

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

I updated the original Zip file with the new one if that's what you mean

 

[Jimjag]

Here's the new .Zip and I've corrected the initial post

 

[Arc]

Dont alter teh original post. Those files are needed for comparison purpose. Upload it at your next post from the next time. Anyway, your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If Memtest comes free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
________________________________________________________________________________
BSOD ANALYSIS:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffffffffffff7, 0, fffff800030d3156, 0}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!zzzWakeInputIdle+c7 )

Followup: MachineOwner
---------

0: kd> !thread
GetPointerFromAddress: unable to read from fffff80003306000
THREAD fffffa8008357060  Cid 0f90.1508  Teb: 000000007efd5000 Win32Thread: fffff900c672c250 RUNNING on processor 0
Not impersonating
GetUlongFromAddress: unable to read from fffff80003245ba4
Owning Process            fffffa8009325060       Image:         SwiftKit-RS.ex
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      148211       
Context Switch Count      37             IdealProcessor: 0                 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x0000000072e0786a
Stack Init fffff8800a4ffdb0 Current fffff8800a4fefc0
Base fffff8800a500000 Limit fffff8800a4f9000 Call 0
Priority 12 BasePriority 8 UnusualBoost 0 ForegroundBoost 2 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0a4ff668 fffff800`0314cbe0 : 00000000`00000050 ffffffff`fffffff7 00000000`00000000 fffff880`0a4ff7d0 : nt!KeBugCheckEx
fffff880`0a4ff670 fffff800`030ccd2e : 00000000`00000000 ffffffff`fffffff7 00000000`00000200 ffffffff`fffffff7 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`0a4ff7d0 fffff800`030d3156 : 00000000`000000ff fffff880`0000000d 00000000`00060980 fffff900`c01cc710 : nt!KiPageFault+0x16e (TrapFrame @ fffff880`0a4ff7d0)
fffff880`0a4ff960 fffff960`000e638f : 00000000`000025ff fffff880`00000001 00000000`00000000 00000000`00000000 : nt!KeSetEvent+0x16
fffff880`0a4ff9d0 fffff960`000dbe60 : fffff900`c672c250 00000000`0000000b 00000000`00000000 fffff900`c4fb1c20 : win32k!zzzWakeInputIdle+0xc7
fffff880`0a4ffa00 fffff960`000dbffd : 00000000`00000000 fffff800`000025ff 00000000`00000000 fffffa80`ffffffff : win32k!xxxRealInternalGetMessage+0x744
fffff880`0a4ffae0 fffff960`000d4a47 : 00000000`02aaf100 fffffa80`08357060 fffff880`009ea180 00000000`00000000 : win32k!xxxInternalGetMessage+0x35
fffff880`0a4ffb20 fffff800`030cde93 : fffffa80`08357060 00000000`02aae7e8 fffff880`0a4ffbc8 00000000`74482450 : win32k!NtUserPeekMessage+0x77
fffff880`0a4ffbb0 00000000`744cfdea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0a4ffc20)
00000000`02aae7c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x744cfdea

 

[Jimjag]

I ran Memtest86 for 10 Passes and it appears there's no problems with the memory.

However after enabling Driver Verifier I've had the system hang on me twice.
The first time was just after it booted it the screen became all teared, and the second time it just went black.
I waited about 20 mins each time for the computer to BSOD but it didn't in either case.

 

[Arc]

Wait, and use the computer (though it will be laggy). Do the most crash prone actions. Try to replicate the BSODs.

 

[Jimjag]

The computer still hasn't BSOD'd but it keeps crashing like the attached photo.

Considering the initial issue was the graphics card do you think it could be a physical fault with the card?

 

[Arc]

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

 

[Jimjag]

Stress tested it with Furmark and OCCT. Neither caused it to crash at all.

Suggestions?

 

[Arc]

As it is a long time with DV and no crashes yet, disable DV. Run the computer normally now.

Memtest, furmark both came free from errors. DV did not caught anything. You can see that the scopes are getting narrowed down. Now, with DV disabled, stress test the CPU.
Hardware - Stress Test With Prime95

Andscan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Let us know the results.

 

[Jimjag]

Ok, so I got sick of stress testing stuff and just bought a brand spanking new ATI 7970 and it would appear to have fixed everything. Don't know what was screwed up in the old video card but I no longer want to put my head through my monitor while using my computer.

Thank you so much for all your troubleshooting help Arc.

 

[Arc]

Good to know that everything works fine now.

Its not good really, but the issues with hardware sometimes left no way but change the hardware

For any further issue, let us know