BSOD streaming online video Hulu Plus win32.sys

pineappleraptor · 07 Mar 2012

Hi all.

I get a BSOD/STOP error when streaming Hulu. The BSOD will appear after streaming roughly 10 minutes of video, then the system is set to restart so it will restart. After prompting safe mode etc. it will start as normal and we will be able to watch a video on Hulu plus all the way through with no errors

Lenovo Essential Series B570 laptop
OS: Win7 Home Premium 64 bit
System: OEM (Best buy may have updated it to 7 before sale. I believe this model orig. had XP )
Purchased at Best Buy 2 months ago
Have not reinstalled the OS.
Have performed recovery via OEM One Key Recovery wizard. BSOD still appeared

I moved files from an XP machine to this system using an external hard drive and Windows easy move (inbuilt Win7 wizard). I have used Lenovo's One Key recovery to recover the system but the BSOD still appears after a successful run. I do not remember if the BSOD occurred after the file move or right out of the box but I suspect that it was due to the file move. My IT guy at work has recommended a full system restore. I suppose I can search for a thread that explains such a procedure but wanted to know if a more knowledgeable person could come up with a different fix.

In addition , and maybe related I cannot complete an update using Windows Update. I can download the updates just fine. But when it comes to applying them, the system will begin applying the updates with the progress bar, but after 2 minutes, I will receive a fail message everytime. Any guidance is much appreciated!

Please see ATTACHMENT for dump file and Performance Analysis HTML file.

panais · 07 Mar 2012

Hi and welcome to SF :)

Remove Mcafee from your system.

Download and install Microsoft Security Essentials with windows firewall enable.

Run RAM - Test with Memtest86+
Let it run until at least 9 passes are completed, or errors are found (whichever comes first). The longer you run it, the better.

Finish with the above steps and post back with results\news.

pineappleraptor · 09 Mar 2012

Wow!

I appreciate the warm welcome and fast response. Over the last 2 days I have performed the steps you have suggested.

I first uninstalled McAfee, restarted, downloaded Microsoft Security Suite, updated the definitions, ran a scan. No bad items were found. Then attempted Windows update. Then I did the memtest for about 20 hours (22 passes) It's currently running and there are no errors to be found.

A side note: between the download of Security Suite and running Memtest I attempted to download and install via Windows Update. I am not sure b/c I was away from the computer but there may have been another blue screen. I returned to the computer to see:
1. failed updates 2. "your system has shut down unexpectedly" (this appears everytime after the blue screen from streaming hulu)

So my question is, no errors found, how do I find the blue screen minidump information that pertains specifically to the second alleged blue screen, not the one streaming from Hulu but the one that may have occurred during the update attempt?

panais · 09 Mar 2012

Go to C:\Windows\Minidump" folder.

Copy the most recent minidumps to another (temporary) location somewhere on your computer.

Zip up the copy.

Attach the ZIP archive to your post using the "paperclip" (file attachments) button.

pineappleraptor · 09 Mar 2012

Thank you again for your reply!

I have attached the latest minidump file (wow there are a lot of them in there!)

This one is from about 10:30AM yesterday, when I did the update attempt. I am sure it is a completely different BSOD/STOP error.

I really appreciate it.

EDIT: I have since deleted the one file and instead included it with an entire week's worth of minidump files to make it easier to see more of the problem.

writhziden · 09 Mar 2012

Code:


Loading Dump File [D:\Kingston\BSODDmpFiles\pineappleraptor\030812-17082-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03256000 PsLoadedModuleList = 0xfffff800`0349b670
Debug session time: Thu Mar  8 08:41:36.316 2012 (UTC - 7:00)
System Uptime: 0 days 0:12:01.362
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff960082d6470, 0, fffff960000b739f, 2}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: 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: fffff960082d6470, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960000b739f, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003505100
 fffff960082d6470 

FAULTING_IP: 
win32k!NtUserCallTwoParam+1f
fffff960`000b739f ff15cbf02108    call    qword ptr [fffff960`082d6470]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  AýÌ

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88008eff920 -- (.trap 0xfffff88008eff920)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80083c9790
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960000b739f rsp=fffff88008effab0 rbp=fffff88008effb60
 r8=0000000000000069  r9=0000000000000006 r10=fffff960000b7380
r11=000000007efdb000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
win32k!NtUserCallTwoParam+0x1f:
fffff960`000b739f ff15cbf02108    call    qword ptr [fffff960`082d6470] ds:be00:fffff960`082d6470=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000327d3f0 to fffff800032d2c40

STACK_TEXT:  
fffff880`08eff7b8 fffff800`0327d3f0 : 00000000`00000050 fffff960`082d6470 00000000`00000000 fffff880`08eff920 : nt!KeBugCheckEx
fffff880`08eff7c0 fffff800`032d0d6e : 00000000`00000000 fffff960`082d6470 fffff880`08effa00 00000000`00000069 : nt! ?? ::FNODOBFM::`string'+0x447c6
fffff880`08eff920 fffff960`000b739f : 00000000`00000000 00000000`7efdb000 00000000`7efdb000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`08effab0 fffffa80`04138b60 : fffffa80`04138b60 00000000`7efdb000 00000000`00000000 fffffa80`0442cae0 : win32k!NtUserCallTwoParam+0x1f
fffff880`08effae0 fffffa80`04138b60 : 00000000`7efdb000 00000000`00000000 fffffa80`0442cae0 00000000`00000000 : 0xfffffa80`04138b60
fffff880`08effae8 00000000`7efdb000 : 00000000`00000000 fffffa80`0442cae0 00000000`00000000 00001fa0`02010000 : 0xfffffa80`04138b60
fffff880`08effaf0 00000000`00000000 : fffffa80`0442cae0 00000000`00000000 00001fa0`02010000 00000000`7efdd000 : 0x7efdb000


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
7 errors : !win32k (fffff960000b7384-fffff960000b7bb4)
fffff960000b7380  48  89  5c  24 *00  48  89  74  24  10  57  48  83  ec  20  48 H.\$.H.t$.WH.. H
...
fffff960000b73a0  15  cb  f0  21 *08  c6  05  fc  bb  25  00  01  48  89  05  3d ...!.....%..H..=
fffff960000b73b0  e1  25  00  8d  43  98  83  f8  0f  77  16  4c *85  05  3e  59 .%..C....w.L..>Y
...
fffff960000b7b80  08  bf  a0  00  00  00  44  89  59  0c  8b  4b *0c  41  be  01 ......D.Y..K.A..
fffff960000b7b90  00  00  00  41 *81  4a  08  44  8b  0b  45  89  4a  04  8b  42 ...A.J.D..E.J..B
fffff960000b7ba0  1c  41  89  02 *31  7a  50  77  2a  44  3b  4a  58  7c  24  3b .A..1zPw*D;JX|$;
fffff960000b7bb0  4a  5c  7c  1f *4c  3b  5a  60  7f  19  44  3b  42  64  7f  13 J\|.L;Z`..D;Bd..

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
---------

Loading Dump File [D:\Kingston\BSODDmpFiles\pineappleraptor\030712-15834-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03249000 PsLoadedModuleList = 0xfffff800`0348e670
Debug session time: Wed Mar  7 08:40:02.162 2012 (UTC - 7:00)
System Uptime: 0 days 0:23:50.208
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff96000180bd7, fffff8800753b070, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff96000180bd7, Address of the instruction which caused the bugcheck
Arg3: fffff8800753b070, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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!CleanupRemoteHandles+f
fffff960`00180bd7 48897908        mov     qword ptr [rcx+8],rdi

CONTEXT:  fffff8800753b070 -- (.cxr 0xfffff8800753b070)
rax=fffff800032cf848 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=000000000003037a rdi=0000000000000000
rip=fffff96000180bd7 rsp=fffff8800753ba50 rbp=0000000022f823f8
 r8=0000000000000000  r9=000000000000000b r10=fffff80003249000
r11=fffff8800753ba50 r12=0000000000000001 r13=000000002343fd20
r14=000000002343ee30 r15=0000000074482450
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
win32k!CleanupRemoteHandles+0xf:
fffff960`00180bd7 48897908        mov     qword ptr [rcx+8],rdi ds:002b:00000000`00000008=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  wüÌ

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff96000161c4a to fffff96000180bd7

STACK_TEXT:  
fffff880`0753ba50 fffff960`00161c4a : 00000000`00000001 00000000`22f823f8 00000000`0003037a fffff880`0753baf8 : win32k!CleanupRemoteHandles+0xf
fffff880`0753ba80 fffff800`032c4ed3 : fffffa80`04699130 fffff880`0753bb60 00000000`00000001 00000000`00000020 : win32k!NtUserPostMessage+0xfe
fffff880`0753bae0 00000000`744cfeca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`2343e438 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x744cfeca


CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
7 errors : !win32k (fffff9600018039c-fffff96000180bbc)
fffff96000180390  2b  d0  74  36  48  8b  c2  49  2b  c2  48  2b *d1  4e  8d  94 +.t6H..I+.H+.N..
fffff960001803a0  00  ff  ff  ff *77  4c  3b  d7  74  1b  0f  b7 *0c  0b  66  3b ....wL;.t.....f;
...
fffff96000180b80  25  1f  00  45  85  c0  74  19  48  8b  0d  91 *2d  1f  00  45 %..E..t.H...-..E
fffff96000180b90  33  c9  33  d2  ff  15  16  59  1b  00  83  25 *7f  25  1f  00 3.3....Y...%.%..
fffff96000180ba0  00  48  8b  0d *78  2d  1f  00  48  83  25  40  49  1f  00  00 .H..x-..H.%@I...
fffff96000180bb0  c6  05  f1  23  1f  00  00  48  83  c4  28  48 *f7  25  ce  58 ...#...H..(H.%.X

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xfffff8800753b070 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...
Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Graphics Driver... Drivers...

Proceed with the following hardware checks:

If you are overclocking any hardware, please stop.
Monitor temperatures during the following tests.

Use the following programs to monitor the temperatures.
- Real Temp is a good CPU temperature monitor.
- Speccy - System Information - Free Download will monitor all hardware temperatures.
- HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
- Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
- Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.

Please follow the https://www.sevenforums.com/crashes-d...tructions.html to provide us with more information about your crashes so we can give specific troubleshooting steps.

BSOD streaming online video Hulu Plus win32.sys

BSOD streaming online video Hulu Plus win32.sys

New Dump File ATTACHMENT