BSOD playing Kings Bounty, random errors and hang ups

[The Impaler]

Hi all,

Having this problem for several months, suspected HDD first but bought new M500 and seems there's something else is responsible for this "fun" I'm having with the PC.

Basically, the nature seems to be the same all the time - when I playing video games (currently it is Kings Bounty, used to be the problem with Max Payne 2012 even during the installation), also used to play Flash games and used to watch video online, it was crushing.
Most common BSOD problem was "page fault in non-paged area" and "IRQL is not less or equal". Sometimes it gives me just a black screen and nothing else at all so I have to go "hard reboot". Sometimes, it hangs with the destroyed, "torn in pieces" video and annoying repetitive sound like ding-ding-ding, so I need to reboot it again, sometimes it goes into BSOD with some errors and exceptions.

I have tried numerous times different Windows 7 versions, both x86 and x64 architecture, and tried XP. Same issues.

I have noticed although, that when the W7 has a clean installation and almost no updates installed, it gives me less headache. Recently I have stopped installing the Catalyst suite for the graphics and thought the problem was just with that but after going through all Windows updates it started again.

I think that there is something with the video, but cannot get to the bottom of it.

Please help as this is becoming now a paranoia for me and I cannot sleep properly.

Thanks

 

[The Impaler]

View attachment 298675
Apologies, please find the right attachment now.

Thanks a lot

 

[Arc]

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

[COLOR=Red]Windows 7 Kernel Version 7600 MP[/COLOR] (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack and Update Center - Microsoft Windows

Update your ATI/AMD display driver to teh latest WHQL. It is failing.

fffff880`059e6808  fffff880`048fa350Unable 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+0x4f350

And the driver is too old.

fffff880`04327000 fffff880`0437c000   atikmpag   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
[COLOR=Red]    Image name: atikmpag.sys
    Timestamp:        Thu Nov 10 07:42:44 2011[/COLOR] (4EBB331C)
    CheckSum:         000502CB
    ImageSize:        00055000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You can get it from the link in our forum, http://www.sevenforums.com/graphic-...alyst-video-driver-windows-7-a.html#post17671, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.

During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.

Let us know the results.

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88006cc752c, 0, fffff80002b7c5c0, 1}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+b0 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88006cc752c, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002b7c5c0, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000001, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ac50e0
 fffff88006cc752c 

FAULTING_IP: 
nt!ObReferenceObjectByHandleWithTag+b0
fffff800`02b7c5c0 8b465c          mov     eax,dword ptr [rsi+5Ch]

MM_INTERNAL_CODE:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  kb.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880059e6940 -- (.trap 0xfffff880059e6940)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000003bc rbx=0000000000000000 rcx=00000000000003bc
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b7c5c0 rsp=fffff880059e6ad0 rbp=fffff880059e6c00
 r8=fffffa80036dc570  r9=0000000077dcf801 r10=00000000000003bc
r11=00000000002f42e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!ObReferenceObjectByHandleWithTag+0xb0:
fffff800`02b7c5c0 8b465c          mov     eax,dword ptr [rsi+5Ch] ds:2625:00000000`0000005c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002839795 to fffff8000288d880

STACK_TEXT:  
fffff880`059e67d8 fffff800`02839795 : 00000000`00000050 fffff880`06cc752c 00000000`00000000 fffff880`059e6940 : nt!KeBugCheckEx
fffff880`059e67e0 fffff800`0288b96e : 00000000`00000000 fffff880`059e6c38 fffffa80`04221200 fffff880`048f815f : nt! ?? ::FNODOBFM::`string'+0x41e7f
fffff880`059e6940 fffff800`02b7c5c0 : fffffa80`0685afd8 fffff780`00000008 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x16e
fffff880`059e6ad0 fffff800`02b8283a : 00000000`00000000 fffff800`00000000 fffffa80`036dc570 fffffa80`0685af01 : nt!ObReferenceObjectByHandleWithTag+0xb0
fffff880`059e6ba0 fffff800`0288cad3 : fffffa80`0579bb60 00000000`000003bc 00000000`00000000 00000000`00000000 : nt!NtReleaseMutant+0x5a
fffff880`059e6c20 00000000`75842dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`126ff0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75842dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ObReferenceObjectByHandleWithTag+b0
fffff800`02b7c5c0 8b465c          mov     eax,dword ptr [rsi+5Ch]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!ObReferenceObjectByHandleWithTag+b0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5147dc36

FAILURE_BUCKET_ID:  X64_0x50_nt!ObReferenceObjectByHandleWithTag+b0

BUCKET_ID:  X64_0x50_nt!ObReferenceObjectByHandleWithTag+b0

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

 

[The Impaler]

Hi Arc,

Thank you very much for your advice and efforts in helping me.

I have tried the 1st part of your suggestion - even though I have previously had clean installation and updated W7 to Service Pack 1 and done all other updates, it still was crushing, this time all (touch the wood) seems to run nice and sound. Within few days of using the PC it crashed once or twice.

So far it is suitable for me so I am going to keep it as it is. If I have any problems later, I will get in touch but right now I consider this matter as resolved.

Thank you very much,
Merry Christmas and Happy New Year.
Best regards,
Vlad The Impaler

P.S. I will keep your notes safe in case I need to do the further updates to my display drivers.

 

[Arc]

Good news mate.

Definitely, let us know for any further issue.

 

[The Impaler]

Hi all,

Had issues becoming more often, so decided to install the display drivers as advised above.
Please see the dump of required infoView attachment 301250.
Still it just has crashed, so I thought to seek for your help.

Thanking you,
Best regards,
Vlad

 

[Arc]

The latest BSOD is of 5th of this month, and that was caused by avast.

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88002591630, 0, fffff80002d03a12, 0}

Unable to load image aswSP.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS

Could not read faulting driver name
[COLOR=Red]Probably caused by : aswSP.SYS [/COLOR]( aswSP+1f0f6 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88002591630, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002d03a12, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b0b100
 fffff88002591630 

FAULTING_IP: 
nt!CmCallbackGetKeyObjectID+22
fffff800`02d03a12 813a3230796b    cmp     dword ptr [rdx],6B793032h

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88007a370e0 -- (.trap 0xfffff88007a370e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88007a37478 rbx=0000000000000000 rcx=fffff880040813c8
rdx=fffff88002591630 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d03a12 rsp=fffff88007a37270 rbp=0000000000000000
 r8=0000000000000000  r9=fffff88007a372e8 r10=fffff880009ea720
r11=fffff8a0025beac0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!CmCallbackGetKeyObjectID+0x22:
fffff800`02d03a12 813a3230796b    cmp     dword ptr [rdx],6B793032h ds:7288:fffff880`02591630=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002951bf0 to fffff800028d3bc0

STACK_TEXT:  
fffff880`07a36f78 fffff800`02951bf0 : 00000000`00000050 fffff880`02591630 00000000`00000000 fffff880`07a370e0 : nt!KeBugCheckEx
fffff880`07a36f80 fffff800`028d1cee : 00000000`00000000 fffff880`02591630 00000000`c0000000 00000000`0000001d : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`07a370e0 fffff800`02d03a12 : fffff8a0`120d7da4 fffff880`07a374d8 fffff8a0`027262f0 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`07a37270 fffff880`0404e0f6 : 00000000`0000001d 00000000`0000001d 00000000`00000000 ffffd040`20c61c2b : nt!CmCallbackGetKeyObjectID+0x22
fffff880`07a372a0 00000000`0000001d : 00000000`0000001d 00000000`00000000 ffffd040`20c61c2b 00000001`12010101 : aswSP+0x1f0f6
fffff880`07a372a8 00000000`0000001d : 00000000`00000000 ffffd040`20c61c2b 00000001`12010101 00000000`00000001 : 0x1d
fffff880`07a372b0 00000000`00000000 : ffffd040`20c61c2b 00000001`12010101 00000000`00000001 00000000`00000001 : 0x1d


STACK_COMMAND:  kb

FOLLOWUP_IP: 
aswSP+1f0f6
fffff880`0404e0f6 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  aswSP+1f0f6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSP

IMAGE_NAME:  aswSP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  52204be5

FAILURE_BUCKET_ID:  X64_0x50_aswSP+1f0f6

BUCKET_ID:  X64_0x50_aswSP+1f0f6

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

If it continues, better to uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

 

[The Impaler]

Hi Arc,

Fabulous, thank you very much, already uninstalled the Avast and installed MS Security Essentials with Firewall on.
Going to install MBAM and trial the functionality.
I'll update the thread in a few days.

Best regards,
Vlad

 

[The Impaler]

Good time of the day/night, dear specialists!

It was a while, now I'm facing similar troubles, not already just playing a game, but no matter what I do, BSOD at random times doing random things, and reasons for BSOD always different....

Please help.

 

[The Impaler]

Anyone is available to help with the Issue please?