Windows 7 REPEATED BSOD - sandy bridge b3 revision, z68 chipset, very little hair left!

cardyology

New Member
Joined
Jun 28, 2011
Hey guys, I'm in need of help with a HTPC I built based on sandybridge (Z68) which suffers from BSOD approx 2-3 times per day under Windows 7 Ultimate x64. It'll run fine for days sometimes but then it'll randomly BSOD three times in 2 hours. The BSOD usually occurs when using windows media centre, mainly live tv but also when playing xvid etc. The BSOD seem to nearly all refer to ntoskrnl?

I've stressed it with intel burn test without fault, prime95x64 for in excess of the recommended 15 hours & completed all tests. I've ran memtest86 on the RAM for 24hours without fail, scanned the HDD's (all three) with windows chkdsk, seagate seatools, maxtor powermax, all show no errors.
I've also run sfc /scannow in an elevated cmd prompt & found no problems.

My system is up to date with SP1. All drivers are up to date from the gigabyte website as of 6 days ago, the AHCI & VGA drivers are newer than the ones listed on Intels site!?

I've never posted here before but I am pretty techie when it comes to hardware, my limits lie at any development/debugging stuff so I'm reaching out to you wise ones :)

I'm not sure if i'm just supposed to post one .dmp or all of them, I have them from the past 8 days (15 files, sorry) I'm hoping someone can point me to a specific device/driver causing the majority of issues so I can replace or remove it.

My specs are as foillows:

-Gigabyte GA-Z68MA-D2H-B3 mobo - latest F4 BIOS
-Intel Core i3 2100 sandy bridge CPU
-Corsair XMS3 1333 4GB RAM - One 4GB stick in DIMM_0
-1x Hitachi 160GB 2.5" HDD
-2x Western Digital 1TiB HDD's - one WD green, one blue
-NVIDIA 9600GSO 512MB GFX card

I'm also using one or two peripherals which could be responsible.

-An official (but old) MCE eHome IR reciever/remote
-A sony play TV dual USB tuner (designed for PS3, used driver found here Link Removed due to 404 Error )- has worked flawlessly with various other HTPC's for the past 18 months however I know it could be the cause of the problem. If I remove it, I still get BSOD.

Really really sorry for the wordy, horrible post & loads of crash dumps.... I'm just at a brick wall with this system & its winding me up. i;ve used a Pentum DC, intel G41 P.O.S. for the past year as a HTPC & its worked flawlessly!

Thanks.
 

Attachments

  • Minidump copy.rar
    368 KB · Views: 267
Last edited:
Hello there,

Since you have already ran the basic Hardware Diagnostic I would recommend to enable Driver Verifier Using Driver Verifier to identify issues with Drivers - Windows 7 Forums to find out which driver is causing the problem.

Update the following driver:

UsbFltr.sys Mon Apr 09 15:39:44 2007 - Ortek USB Keypad Driver

Code:
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff96000172f61, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000020, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
win32k!ClearWakeBit+d
fffff960`00172f61 83791000        cmp     dword ptr [rcx+10h],0

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000020

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b5100
 0000000000000020 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x1E

PROCESS_NAME:  conhost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800a6447d0 -- (.trap 0xfffff8800a6447d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000010 rbx=0000000000000000 rcx=0000000000000010
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000172f61 rsp=fffff8800a644960 rbp=fffff900c1c04cd0
 r8=fffff900c1b29c30  r9=0000000000000000 r10=fffff960001743c0
r11=fffff900c1c04cd0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
win32k!ClearWakeBit+0xd:
fffff960`00172f61 83791000        cmp     dword ptr [rcx+10h],0 ds:0060:00000000`00000020=????????
Resetting default scope

MISALIGNED_IP: 
win32k!ClearWakeBit+d
fffff960`00172f61 83791000        cmp     dword ptr [rcx+10h],0

LAST_CONTROL_TRANSFER:  from fffff80002ed15d8 to fffff80002e85d00

STACK_TEXT:  
fffff880`0a643f48 fffff800`02ed15d8 : 00000000`0000001e ffffffff`c0000005 fffff960`00172f61 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a643f50 fffff800`02e85382 : fffff880`0a644728 00000000`000300d2 fffff880`0a6447d0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`0a6445f0 fffff800`02e83efa : 00000000`00000000 00000000`00000020 fffffa01`c0000000 00000000`000300d2 : nt!KiExceptionDispatch+0xc2
fffff880`0a6447d0 fffff960`00172f61 : fffff8a0`0f1afa01 fffff880`0a644968 fffff880`00020019 fffff880`0a6449d0 : nt!KiPageFault+0x23a
fffff880`0a644960 fffff8a0`0f1afa01 : fffff880`0a644968 fffff880`00020019 fffff880`0a6449d0 fffff880`0a6449a8 : win32k!ClearWakeBit+0xd
fffff880`0a644968 fffff880`0a644968 : fffff880`00020019 fffff880`0a6449d0 fffff880`0a6449a8 00000000`00000000 : 0xfffff8a0`0f1afa01
fffff880`0a644970 fffff880`00020019 : fffff880`0a6449d0 fffff880`0a6449a8 00000000`00000000 00000000`00000100 : 0xfffff880`0a644968
fffff880`0a644978 fffff880`0a6449d0 : fffff880`0a6449a8 00000000`00000000 00000000`00000100 00000000`00620060 : 0xfffff880`00020019
fffff880`0a644980 fffff880`0a6449a8 : 00000000`00000000 00000000`00000100 00000000`00620060 00000000`0022f650 : 0xfffff880`0a6449d0
fffff880`0a644988 00000000`00000000 : 00000000`00000100 00000000`00620060 00000000`0022f650 00000000`00000000 : 0xfffff880`0a6449a8


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
15 errors : !win32k (fffff960001720be-fffff96000172ff6)
fffff960001720b0  00  00  8b  74  24  50  81  fe  00  01  00  00  0f  85 *16  04 ...t$P..........
...
fffff96000172230  08  00  00  00  41  3b  c5  77  70  48  8b  86  50  01 *08  00 ....A;.wpH..P...
fffff96000172240  48  89  84  24  88  02  00  00  48  8d  84  24  88  02 *40  00 H..$....H..$..@.
...
fffff96000172270  01  18  89  7c  24  20  4c  8d  8c  24  50  01  00  00 *55  33 ...|$ L..$P...U3
...
fffff96000172510  00  00  00  4d  8b  c1  49  c1  e8  18  44  22  c3  41 *90  c8 ...M..I...D".A..
fffff96000172520  a0  45  8a  d0  44  32  d3  39  bc  24  bc  00  00  00 *7d  66 .E..D2.9.$....}f
...
fffff960001726e0  00  4c  3b  fa  75  0f  45  0f  b7  8e  c2  02  00  00 *51  c1 .L;.u.E.......Q.
...
fffff960001727b0  01  00  00  8b  50  18  41  0b  96  28  02  00  00  f6 *ca  40 ....P.A..(.....@
...
fffff960001727f0  b4  24  68  03  00  00 *f9  80  00  00  00  44  8b  6c  24  50 .$h........D.l$P
...
fffff96000172940  24  50  45  33  c0  41 *9b  d5  41  8b  cd  e8  c0  06  03  00 $PE3.A..A.......
...
fffff96000172a70  03  fe  7f  48  0f  af  c8  48  c1  e9  18  49  8b  86 *68  01 ...H...H...I..h.
...
fffff96000172e30  00  66  41  21  43  06  4c  3b  e7  74  1b  ba  40  20 *08  00 .fA!C.L;.t..@ ..
...
fffff96000172e50  41  21  5b  06  eb  46  48  8b  05  93  f6  24  00  48 *9b  88 A![..FH....$.H..
...
fffff96000172fd0  0f  66  89  74  24  32 *76  89  74  24  30  48  89  44  24  38 .f.t$2v.t$0H.D$8
...
fffff96000172ff0  3b  c6  0f  84  2c  01 *18  00  48  8b  0d  f1  f4  24  00  48 ;...,...H....$.H

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------
 
Back
Top Bottom