Blue Screen of Death while on the net

Victor AU · 30 May 2011

hi i was wondering if anyone could help me with my blue screen of death problem.

The BSOD only happens while i am on the net such as when i am on Youtube, playing online games etc. Horizontal lines pop up and then the BSOD comes up.

i have updated most if not all of my driver on my computer since i thought originally it was a driver problem but to no luck

My computer was recently built, within the last two months if that is part of the problem.

Thanks in advance for any help =)

zigzag3143 · 30 May 2011

Victor AU said:

hi i was wondering if anyone could help me with my blue screen of death problem.

The BSOD only happens while i am on the net such as when i am on Youtube, playing online games etc. Horizontal lines pop up and then the BSOD comes up.

i have updated most if not all of my driver on my computer since i thought originally it was a driver problem but to no luck

My computer was recently built, within the last two months if that is part of the problem.

Thanks in advance for any help =)

Two Problems

1-CPU64.sys Likely a component of SystemRequirementsLabs CanYouRunIt remove it

2- e1q62x64.sys Your Intel Ethernet driver.

Update them both

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\New folder\053111-24304-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`0304be50
Debug session time: Mon May 30 10:33:59.666 2011 (GMT-4)
System Uptime: 0 days 0:01:42.946
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000096, fffff880047df912, 0, 0}

Unable to load image \??\C:\Program Files (x86)\SystemRequirementsLab\cpudrv64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cpudrv64.sys
*** ERROR: Module load completed but symbols could not be loaded for cpudrv64.sys
Probably caused by : cpudrv64.sys ( cpudrv64+1912 )

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

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

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: ffffffffc0000096, The exception code that was not handled
Arg2: fffff880047df912, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

FAULTING_IP: 
cpudrv64+1912
fffff880`047df912 0f32            rdmsr

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  inteldriver.ex

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff880142736c8 -- (.exr 0xfffff880142736c8)
ExceptionAddress: fffff880047df912 (cpudrv64+0x0000000000001912)
   ExceptionCode: c0000096
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff88014273770 -- (.trap 0xfffff88014273770)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000134b780 rbx=0000000000000000 rcx=0000000000000017
rdx=fffff880142739b4 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880047df912 rsp=fffff88014273908 rbp=fffff88014273ca0
 r8=fffff880142739b8  r9=000000000000000e r10=fffff8000300d888
r11=fffff88014273a08 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cpudrv64+0x1912:
fffff880`047df912 0f32            rdmsr
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002eb8ab9 to fffff80002e7e700

STACK_TEXT:  
fffff880`14272ef8 fffff800`02eb8ab9 : 00000000`0000001e ffffffff`c0000096 fffff880`047df912 00000000`00000000 : nt!KeBugCheckEx
fffff880`14272f00 fffff800`02e7dd42 : fffff880`142736c8 fffffa80`0cb1c480 fffff880`14273770 fffffa80`0dbd6b30 : nt!KiDispatchException+0x1b9
fffff880`14273590 fffff800`02e7c64a : 00000000`00000000 00000000`a000000c fffffa01`0dbd6b30 fffff800`02e9dd1c : nt!KiExceptionDispatch+0xc2
fffff880`14273770 fffff880`047df912 : fffff880`142739b8 fffff880`142739b4 fffffa80`0dbd6b30 fffffa80`0dbd6b30 : nt!KiGeneralProtectionFault+0x10a
fffff880`14273908 fffff880`142739b8 : fffff880`142739b4 fffffa80`0dbd6b30 fffffa80`0dbd6b30 fffff880`14273ca0 : cpudrv64+0x1912
fffff880`14273910 fffff880`142739b4 : fffffa80`0dbd6b30 fffffa80`0dbd6b30 fffff880`14273ca0 fffffa80`0cb1c480 : 0xfffff880`142739b8
fffff880`14273918 fffffa80`0dbd6b30 : fffffa80`0dbd6b30 fffff880`14273ca0 fffffa80`0cb1c480 fffff880`047e23c3 : 0xfffff880`142739b4
fffff880`14273920 fffffa80`0dbd6b30 : fffff880`14273ca0 fffffa80`0cb1c480 fffff880`047e23c3 fffffa80`0ce69980 : 0xfffffa80`0dbd6b30
fffff880`14273928 fffff880`14273ca0 : fffffa80`0cb1c480 fffff880`047e23c3 fffffa80`0ce69980 00000000`00000000 : 0xfffffa80`0dbd6b30
fffff880`14273930 fffffa80`0cb1c480 : fffff880`047e23c3 fffffa80`0ce69980 00000000`00000000 00000000`00003400 : 0xfffff880`14273ca0
fffff880`14273938 fffff880`047e23c3 : fffffa80`0ce69980 00000000`00000000 00000000`00003400 00000000`00000000 : 0xfffffa80`0cb1c480
fffff880`14273940 fffffa80`0ce69980 : 00000000`00000000 00000000`00003400 00000000`00000000 fffffa80`000000fc : cpudrv64+0x43c3
fffff880`14273948 00000000`00000000 : 00000000`00003400 00000000`00000000 fffffa80`000000fc fffff880`142739a8 : 0xfffffa80`0ce69980


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cpudrv64+1912
fffff880`047df912 0f32            rdmsr

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  cpudrv64+1912

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cpudrv64

IMAGE_NAME:  cpudrv64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a819eb1

FAILURE_BUCKET_ID:  X64_0x1E_cpudrv64+1912

BUCKET_ID:  X64_0x1E_cpudrv64+1912

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

Victor AU · 31 May 2011

thanks i updated the drivers and removed SystemRequirementLab ill see if it still causes any blue screens.

zigzag3143 · 31 May 2011

Victor AU said:

thanks i updated the drivers and removed SystemRequirementLab ill see if it still causes any blue screens.

Let us know if you need help.

Ken