Random Blue Screen: Windows 7

[bjhclash]

Hi,

Ive searched every where for an answer to my problem, but with my limited knowledge on computers im finding it increasingly difficult to find the cause of the problem.

Basically my pc is randomly restarting, with little of no pattern. Ive ran memtest for 12 hours and it found nothing.. Ive chekced the S.M.A.R.T with a program called Specy and its OK. I had a failing PSU unit but i replaced it and the problem still exists

Here is a copy of the last Bug Check Analysis

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 67b82bb0, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8281e90f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 829b1700
Unable to read MiSystemVaType memory at 829910c0
67b82bb0

CURRENT_IRQL: 2

FAULTING_IP:
hal!KeReleaseQueuedSpinLock+f
8281e90f 188b480483e1 sbb byte ptr [ebx-1E7CFBB8h],cl

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: dwm.exe

TRAP_FRAME: 9993bb50 -- (.trap 0xffffffff9993bb50)
ErrCode = 00000002
eax=9993bb07 ebx=86352768 ecx=9993bbec edx=00000000 esi=8575b218 edi=82973d20
eip=8281e90f esp=9993bbc4 ebp=9993bbf8 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
hal!KeReleaseQueuedSpinLock+0xf:
8281e90f 188b480483e1 sbb byte ptr [ebx-1E7CFBB8h],cl ds:0023:67b82bb0=??
Resetting default scope

MISALIGNED_IP:
hal!KeReleaseQueuedSpinLock+f
8281e90f 188b480483e1 sbb byte ptr [ebx-1E7CFBB8h],cl

LAST_CONTROL_TRANSFER: from 8281e90f to 8288ab5b

STACK_TEXT:
9993bb50 8281e90f badb0d00 00000000 00000000 nt!KiTrap0E+0x2cf
9993bc04 9323bb4d 9325230e 00000000 00000710 hal!KeReleaseQueuedSpinLock+0xf
9993bc08 9325230e 00000000 00000710 9993bc38 win32k!GreReleaseSemaphoreInternal+0xa
9993bc18 9325248b 00000710 00000004 9993bccc win32k!HmgIncProcessHandleCount+0xa7
9993bc38 931e9084 fd8c45c8 00000000 00000004 win32k!HmgInsertObject+0x30
9993bc64 931e9eab fdb7e970 fd8c45c8 00000000 win32k!GrepSfmGetDirtyRgn+0x167
9993bc90 932098ac 011207db 010507dc 00000000 win32k!GreSfmGetDirtyRgn+0x6b
9993bd1c 8288779a 011207db 00000004 030cf7d4 win32k!NtGdiHLSurfGetInformation+0xff
9993bd1c 77cd64f4 011207db 00000004 030cf7d4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
030cf7f0 00000000 00000000 00000000 00000000 0x77cd64f4


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!GreReleaseSemaphoreInternal+a
9323bb4d ff2578f23693 jmp dword ptr [win32k!_imp__PsLeavePriorityRegion (9336f278)]

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: win32k!GreReleaseSemaphoreInternal+a

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

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


If you need anymore i have several dmp files saved

I much appreciate you time

Brian

 

[Route44]

Post your five most recent minidump files in one Zip file (see Managae Attachments button at the bottom the next time your post). If you only have one or two just attach as is.

 

[bjhclash]

Hi,

I much appreciate you trying to help me. Ive posted the last 3 I had as I deleted the other ones a while back after I replaced the PSU as I assumed this had fixed the problem.

Brian

 

[bjhclash]

Just had another restart so i have another dmp file if needed

 

[Route44]

Post tha6t one. Sorry I can't read the latest at this moment because of schedule but I will asap or someone else will.

meanwhile do you know how to run Memtest? Your first set had errors 0xA which simply cited hardware as the problem and 0x8E which are almost always caused by hardware and is a good indicator of corrupted memory.

There is a guide in the Guide and Tutorial forum that tells you how to run it.

 

[Route44]

Your third memory dump is error 0xF7: DRIVER_OVERRAN_STACK_BUFFER
This indicates that a driver has overrun a stack-based buffer.

Cause
A driver overran a stack-based buffer (or local variable) in a way that would have overwritten the function's return address and jumped back to an arbitrary address when the function returned.

This is the classic "buffer overrun" hacking attack. The system has been brought down to prevent a malicious user from gaining complete control of it.

1. Scan your computer for computer viruses.

2. Check your hard disk for errors. Use the free harddrive diagnostic utility from your HD's manufacturer's website. Run both short and lomg tests as well as SMART.

 

[bjhclash]

Hi,
Again i appreciate your help getting to the problem of this. Ill post the other dump file tomorrow when i can get on that pc.

I already ran a memtest last Wednesday for 12hrs, and error checked the hard drive using both windows and seagate tools and it continues to pass both


Brian

 

[Route44]

Okay, then two important diagnostic steps have taken place. Concerning SeaTools, did your run S.M.A.R.T., the Short Test, and the Long Test?

What security software are you running?

 

[bjhclash]

Sorry ive been really busy. Unfortunatly CCleaner has deleted 2 of the recent dmp files ive had, i do however have a dmp file from yestarday.

Is it alright if i post that one

Brian

 

[Route44]

Yes, post that and please answer the questions from my previous post.

 

[bjhclash]

Thanks for sticking with me here.

I'm currently using no Security Software as last week I reinstalled windows to see if that would solve it. Prior to this I was using AVAST Internet Security.

Anyway here are the 3 most recent logs that have happened

Thanks Brian

 

[Route44]

No problem with the sticking around. Glad to be of help. The dumps simply cited OS drivers and they aren't much help.

All three errors are 0x8E and these are almost always caused by hardware. When do these crashes occur, i.e. what are you doing when they occur?

 

[bjhclash]

A few happened while moving files, but to be honest they seem very random in nature. Ive spent the day going through all my drivers and have installed newer audio drivers and graphics drivers.

Should i redo the memory scan but do the sticks seperatly

Thanks

Brian

 

[Route44]

That would be a good idea. As good as memtest is bad RAM has been known to pass from time to time.

 

[mchldpy]

a possible workaround

TO bjhclash
hello,
i couldn't find anything listing your current system, maybe i just missed it, i am from texas. myself and almost everyone i know that's running 7en x64 professional is having periodic random-like restarts, most do not report a bsod, just the restart, no dump, some like myself usually have something in the event log like, kernel power related or display driver (ati.***) geeking but, all seem to be directly or indirectly related to drm.exe, the desktop manager and aero effects. disabling aero (simply switch from aero theme to windows basic or high contrast theme) seems to quell the problem. on 1 of my identical mobo's i had to back off of my igx over-eagerly overclocked settings just a tad and was still able to use aero (what can i say i'm easily amused by shiney baubles and other worthless trinkets). on an identical mobo (0.1 revision # difference) i either disable aero or nothing else stops the restarts. it did it today, first time in over 2 weeks, the other board still has aero and no restarts... go figure. i noticed a reference to dwm.exe in 1 of your bugchecks that's why i posted this overblown reply which i saw while looking around to see if m/soft had released a fix for this or somebody had figured out another workaround.


hope this helps
michael


"please pull up to the second window"

UPDATE

a patch is likely due out on 6/8/2010 for the "conical display driver" problem according to Micropatch, i mean Microsnot, i mean...

 

[Archean]

By the way it is canonical display driver

 

[mchldpy]

oh yeah!

such are the benefits of life w/out s spell checker, but when you're from south-texas canonical, conical... all the same.

you can't call me a tard anymore, i'm developmentally disabled