Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Help Please:Problem Event Name BlueScreen


23 Oct 2010   #1

Windows 7 Home Premium 64bit
 
 
Help Please:Problem Event Name BlueScreen

My Windows 7 . . .
- Home Premium x64
- Original installed OS on the system
- An OEM version
- I don't know where to find the age of system (hardware) but I just bought my hp dm4 around two weeks ago so I guess the system is quite new?
- I have re-installed the OS once because I tried to installed the Professional version but it won't work so I reinstalled the OS to its factory mode.


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 3076

Additional information about the problem:
BCCode: d1
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF88007439A45
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\102310-31777-01.dmp
C:\Users\HP\AppData\Local\Temp\WER-43945-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


My System SpecsSystem Spec
.

23 Oct 2010   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium SP1, clean install, upgrade disc
 
 

It appears that the problem is caused by your Intel driver
Productname: Intel® Wireless WiFi Link Adapter
Description: Intel® Wireless WiFi Link Driver
Company: Intel Corporation

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_System%20Health%20Report[1].zip\Windows_NT6_BSOD_jcgriff2\102210-30716-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c52000 PsLoadedModuleList = 0xfffff800`02e8fe50
Debug session time: Fri Oct 22 06:52:14.994 2010 (GMT-4)
System Uptime: 1 days 17:24:29.571
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 0, fffff8800748aa45}
Unable to load image \SystemRoot\system32\DRIVERS\NETw5s64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+13a45 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800748aa45, address which referenced memory
Debugging Details:
------------------
 
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efa0e0
 0000000000000000 
CURRENT_IRQL:  2
FAULTING_IP: 
NETw5s64+13a45
fffff880`0748aa45 48833b00        cmp     qword ptr [rbx],0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  wcg_hfcc_autod
TRAP_FRAME:  fffff880009b0340 -- (.trap 0xfffff880009b0340)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa800788a290
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800748aa45 rsp=fffff880009b04d0 rbp=fffffa800456af20
 r8=0000000000000000  r9=0000000000000000 r10=fffff880031d3a60
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
NETw5s64+0x13a45:
fffff880`0748aa45 48833b00        cmp     qword ptr [rbx],0 ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002cc1ca9 to fffff80002cc2740
STACK_TEXT:  
fffff880`009b01f8 fffff800`02cc1ca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`009b0200 fffff800`02cc0920 : fffffa80`04185148 00000000`00000000 00000000`00000000 fffff800`02cca1aa : nt!KiBugCheckDispatch+0x69
fffff880`009b0340 fffff880`0748aa45 : 00000000`00000004 00000000`00000000 fffffa80`00000002 00000000`00000115 : nt!KiPageFault+0x260
fffff880`009b04d0 00000000`00000004 : 00000000`00000000 fffffa80`00000002 00000000`00000115 00000000`000000f9 : NETw5s64+0x13a45
fffff880`009b04d8 00000000`00000000 : fffffa80`00000002 00000000`00000115 00000000`000000f9 fffffa80`07210fb0 : 0x4
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
NETw5s64+13a45
fffff880`0748aa45 48833b00        cmp     qword ptr [rbx],0
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  NETw5s64+13a45
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: NETw5s64
IMAGE_NAME:  NETw5s64.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4b4df6b9
FAILURE_BUCKET_ID:  X64_0xD1_NETw5s64+13a45
BUCKET_ID:  X64_0xD1_NETw5s64+13a45
Followup: MachineOwner
---------
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done:
www.duplexsecure.com/en/downloads
My System SpecsSystem Spec
23 Oct 2010   #3

Windows 7 Home Premium 64bit
 
 

Is there any possible way to fix it? Thanks!
My System SpecsSystem Spec
.


23 Oct 2010   #4

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium SP1, clean install, upgrade disc
 
 

Two choices, buy a new computer or replace the driver, which is very easy

Just go to the Intel site. If you need help just ask

How to Find Drivers
search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone - will help you search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
To remove any left over driver remnants, especially from graphics cards, use driver sweeper
www.guru3d.com/category/driversweeper/
My System SpecsSystem Spec
23 Oct 2010   #5

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium SP1, clean install, upgrade disc
 
 

Second box, second row, Intel will pick the correct driver for your needs
http://downloadcenter.intel.com/default.aspx?lang=eng
My System SpecsSystem Spec
23 Oct 2010   #6

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Veinslala View Post
My Windows 7 . . .
- Home Premium x64
- Original installed OS on the system
- An OEM version
- I don't know where to find the age of system (hardware) but I just bought my hp dm4 around two weeks ago so I guess the system is quite new?
- I have re-installed the OS once because I tried to installed the Professional version but it won't work so I reinstalled the OS to its factory mode.


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 3076

Additional information about the problem:
BCCode: d1
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF88007439A45
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\102310-31777-01.dmp
C:\Users\HP\AppData\Local\Temp\WER-43945-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

This one is easy your NETw5s64.sys Intel wifi driver. Re-install with the newest verison available from Intel.

Second SPTD.sys known to cause BSOD's and used in daemon tools/alcohol. remove it.

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
[/quote]
You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview



Let us know if you need further assistance.



Ken J

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\Windows_NT6_BSOD_jcgriff2\102310-31777-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c1b000 PsLoadedModuleList = 0xfffff800`02e58e50
Debug session time: Sat Oct 23 07:55:25.565 2010 (GMT-4)
System Uptime: 1 days 1:02:04.752
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, fffff88007439a45}

Unable to load image \SystemRoot\system32\DRIVERS\NETw5s64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+13a45 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88007439a45, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec30e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
NETw5s64+13a45
fffff880`07439a45 48833b00        cmp     qword ptr [rbx],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800318b110 -- (.trap 0xfffff8800318b110)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8007828290
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88007439a45 rsp=fffff8800318b2a0 rbp=fffffa80049cc1c0
 r8=fffffa80096ee100  r9=0000000000000000 r10=fffff88003163a60
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
NETw5s64+0x13a45:
fffff880`07439a45 48833b00        cmp     qword ptr [rbx],0 ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c8aca9 to fffff80002c8b740

STACK_TEXT:  
fffff880`0318afc8 fffff800`02c8aca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0318afd0 fffff800`02c89920 : fffffa80`0417ac68 00000000`00000000 00000000`00000000 fffff800`02c931aa : nt!KiBugCheckDispatch+0x69
fffff880`0318b110 fffff880`07439a45 : 00000000`00000004 00000000`00000000 fffffa80`00000002 00000000`00000115 : nt!KiPageFault+0x260
fffff880`0318b2a0 00000000`00000004 : 00000000`00000000 fffffa80`00000002 00000000`00000115 00000000`000000f9 : NETw5s64+0x13a45
fffff880`0318b2a8 00000000`00000000 : fffffa80`00000002 00000000`00000115 00000000`000000f9 fffffa80`0ad16fb0 : 0x4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETw5s64+13a45
fffff880`07439a45 48833b00        cmp     qword ptr [rbx],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  NETw5s64+13a45

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETw5s64

IMAGE_NAME:  NETw5s64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b4df6b9

FAILURE_BUCKET_ID:  X64_0xD1_NETw5s64+13a45

BUCKET_ID:  X64_0xD1_NETw5s64+13a45

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88007439a45, address which referenced memory

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


READ_ADDRESS:  0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
NETw5s64+13a45
fffff880`07439a45 48833b00        cmp     qword ptr [rbx],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800318b110 -- (.trap 0xfffff8800318b110)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8007828290
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88007439a45 rsp=fffff8800318b2a0 rbp=fffffa80049cc1c0
 r8=fffffa80096ee100  r9=0000000000000000 r10=fffff88003163a60
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
NETw5s64+0x13a45:
fffff880`07439a45 48833b00        cmp     qword ptr [rbx],0 ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c8aca9 to fffff80002c8b740

STACK_TEXT:  
fffff880`0318afc8 fffff800`02c8aca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0318afd0 fffff800`02c89920 : fffffa80`0417ac68 00000000`00000000 00000000`00000000 fffff800`02c931aa : nt!KiBugCheckDispatch+0x69
fffff880`0318b110 fffff880`07439a45 : 00000000`00000004 00000000`00000000 fffffa80`00000002 00000000`00000115 : nt!KiPageFault+0x260
fffff880`0318b2a0 00000000`00000004 : 00000000`00000000 fffffa80`00000002 00000000`00000115 00000000`000000f9 : NETw5s64+0x13a45
fffff880`0318b2a8 00000000`00000000 : fffffa80`00000002 00000000`00000115 00000000`000000f9 fffffa80`0ad16fb0 : 0x4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETw5s64+13a45
fffff880`07439a45 48833b00        cmp     qword ptr [rbx],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  NETw5s64+13a45

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETw5s64

IMAGE_NAME:  NETw5s64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b4df6b9

FAILURE_BUCKET_ID:  X64_0xD1_NETw5s64+13a45

BUCKET_ID:  X64_0xD1_NETw5s64+13a45

Followup: MachineOwner
---------
My System SpecsSystem Spec
23 Oct 2010   #7

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium SP1, clean install, upgrade disc
 
 

You have a choice of two answers take your pick.
My System SpecsSystem Spec
23 Oct 2010   #8

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium SP1, clean install, upgrade disc
 
 

Thank you for the rep. I would, also take care of that Deameon, sptd, as suggested by me and Ken. That is trouble, potentially, just waiting to happen
My System SpecsSystem Spec
29 Oct 2010   #9

Windows 7 Home Premium 64bit
 
 
BSOD again...

I don't know why but I am having the BSOD again. I have removed the daemon tool and sptd and I think I have the driver upgraded. I really don't know what went wrong

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 3076

Additional information about the problem:
BCCode: d1
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF88007435431
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\102910-31278-01.dmp
C:\Users\HP\AppData\Local\Temp\WER-188106-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
My System SpecsSystem Spec
Reply

 Help Please:Problem Event Name BlueScreen




Thread Tools



Similar help and support threads for2: Help Please:Problem Event Name BlueScreen
Thread Forum
Problem Event Name: BlueScreen BSOD Help and Support
HELP! Problem Event Name: BlueScreen BSOD Help and Support
Problem event name: BlueScreen BSOD Help and Support
Problem event name: BlueScreen BSOD Help and Support
Problem Event Name: BlueScreen BSOD Help and Support
problem event name bluescreen BSOD Help and Support
Problem Event Name: BlueScreen BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 12:08 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33