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: Bluescreen since today


11 Nov 2010   #1

Windows 7 Home Premium 64bit
 
 
Bluescreen since today

Hello

Today my windows crashed 3 times, 2x in 5 minutes and 1x after ~30 minutes.

Im using Windows 7 Home Premium 64 bit (Installed for just 3 days).

Hardware changes (3 days ago): new harddrive, HDD => SSD (OCZ Vertex II).
Software changes (3 days ago): Win 7 Pro 64bit => Win 7 Home Premium 64bit (fresh install because of the new harddrive).

What could be the problem?

Thanks,

Tim


Edit: forgot to mention, the first crash came after starting a youtube video, second after loading an URL in winamp (mp3 stream), and third after playing a youtube video (like after 30 secs playing).

My System SpecsSystem Spec
.

11 Nov 2010   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by crimpson View Post
Hello

Today my windows crashed 3 times, 2x in 5 minutes and 1x after ~30 minutes.

Im using Windows 7 Home Premium 64 bit (Installed for just 3 days).

Hardware changes (3 days ago): new harddrive, HDD => SSD (OCZ Vertex II).
Software changes (3 days ago): Win 7 Pro 64bit => Win 7 Home Premium 64bit (fresh install because of the new harddrive).

What could be the problem?

Thanks,

Tim


Edit: forgot to mention, the first crash came after starting a youtube video, second after loading an URL in winamp (mp3 stream), and third after playing a youtube video (like after 30 secs playing).
These were caused by your Atheros wifi drivers which is of course two years old and in need of updating and nwifi.sys.

After updating the wifi driver I would also run a system file check to verify and repair the system file

SFC /SCANNOW Command - System File Checker


Ken


analysis
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\111110-17004-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`0281d000 PsLoadedModuleList = 0xfffff800`02a5ae50
Debug session time: Thu Nov 11 10:55:03.034 2010 (GMT-5)
System Uptime: 0 days 0:46:54.845
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

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

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

0: 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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, 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: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+5dea952f0404da6c
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000b9c2f8 -- (.exr 0xfffff80000b9c2f8)
ExceptionAddress: fffff88003af4767 (nwifi!Pt6RepackRecvNBL+0x0000000000000103)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000b9c3a0 -- (.trap 0xfffff80000b9c3a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8005eb9f50 rbx=0000000000000000 rcx=fffff88003b2c6e0
rdx=fffffa8005f0df40 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003af4767 rsp=fffff80000b9c530 rbp=0000000000000000
 r8=0000000000000000  r9=fc64fea45aeddbda r10=fffff88003b2a110
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nwifi!Pt6RepackRecvNBL+0x103:
fffff880`03af4767 450fb701        movzx   r8d,word ptr [r9] ds:fc64fea4`5aeddbda=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000288546e to fffff8000288d710

STACK_TEXT:  
fffff800`00b9b3e8 fffff800`0288546e : fffffa80`047b9c58 fffffa80`05e95010 fffff800`00b9bb60 fffff800`028ba668 : nt!KeBugCheck
fffff800`00b9b3f0 fffff800`028b340d : fffff800`02a9bb7c fffff800`029d5e84 fffff800`0281d000 fffff800`00b9c2f8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b420 fffff800`028baa90 : fffff800`029dcb14 fffff800`00b9b498 fffff800`00b9c2f8 fffff800`0281d000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b450 fffff800`028c79ef : fffff800`00b9c2f8 fffff800`00b9bb60 fffff800`00000000 fffffa80`05ec0b10 : nt!RtlDispatchException+0x410
fffff800`00b9bb30 fffff800`0288cd82 : fffff800`00b9c2f8 00000000`00000000 fffff800`00b9c3a0 fffffa80`0609b010 : nt!KiDispatchException+0x16f
fffff800`00b9c1c0 fffff800`0288b68a : fffffa80`05c6c048 fffffa80`00000001 fffff800`00b9c400 fffff800`028e495f : nt!KiExceptionDispatch+0xc2
fffff800`00b9c3a0 fffff880`03af4767 : 00000000`00000000 00000000`00000000 fffffa80`0609b010 fffff880`03e3d783 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c530 fffff880`03af56c8 : fffffa80`05cc5030 fffffa80`05ee3e14 fffffa80`00001e14 fffffa80`0609b010 : nwifi!Pt6RepackRecvNBL+0x103
fffff800`00b9c630 fffff880`014d92b7 : fffffa80`05c331a0 fffffa80`05ec0b10 00000000`00000001 fffffa80`05ee6200 : nwifi!Pt6Receive+0x170
fffff800`00b9c690 fffff880`024e7202 : 00000000`00000000 fffff880`00dd2130 fffffa80`05b0e9f0 00000000`00000000 : ndis! ?? ::FNODOBFM::`string'+0xccef
fffff800`00b9c6e0 00000000`00000000 : fffff880`00dd2130 fffffa80`05b0e9f0 00000000`00000000 fffffa80`00000001 : athrxusb+0x11202


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nwifi!Pt6RepackRecvNBL+103
fffff880`03af4767 450fb701        movzx   r8d,word ptr [r9]

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  nwifi!Pt6RepackRecvNBL+103

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nwifi

IMAGE_NAME:  nwifi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc3b

FAILURE_BUCKET_ID:  X64_0x1E_nwifi!Pt6RepackRecvNBL+103

BUCKET_ID:  X64_0x1E_nwifi!Pt6RepackRecvNBL+103

Followup: MachineOwner
---------
old drivers
Code:
athrxusb.sys        fffff880`02595000    0x0010d000    7/29/2008 07:47:13            0x488f1151    fffff880`02488000                
nvm62x64.sys        fffff880`04174d80    0x00063d80    10/17/2008 16:01:06            0x48f8fd12    fffff880`04111000
My System SpecsSystem Spec
Reply

 Bluescreen since today




Thread Tools



Similar help and support threads for2: Bluescreen since today
Thread Forum
Today [12] Chillout Room
When a bluescreen isnt a bluescreen Performance & Maintenance
Today [7] Chillout Room
Bluescreen 3 times today... BSOD Help and Support
Today [4] Chillout Room
Today [2] Chillout Room
Today Chillout Room

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 04:20 AM.
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