Anybody plz help me!!!!

[lak121727]

Does it point out specific hardware as the cause? How about the real reason for those crashing is the bad hardware inside
By saying let it run for 36hrs, I just let the computer run and crash and log on? or just let it run itself to the log on screen? Bcuz I just cant sitting all day logging on the computer?
Thanks

 

[CarlTR6]

Leave it on for a two more days and lets see what happens. Yes, I think there there is a hardware problem based on what your posted:

I turn on my computer this morning and there's a new problem with it. Whenever i plug the charger in, it suddenly restart when reach the log on screen. as long as i use the battery, it's ok, rite now everything seems to be alrite but i think due to its crashing alot of time like this, system cause the sudden death like that.

 

[CarlTR6]

No, it does not point to specific hardware. Just use your computer normally while Driver Verifier. If it BSOD"S while you are using the computer, upload the dump file. If it BSOD's while you are a way from it; don't worry about it. Just upload the dump file when you can get back to your computer.

 

[lak121727]

Thank you!
Is it crash even if it's still in the log on screen ? The driver verifier works that way? All I need is just run the computer

 

[CarlTR6]

If you are in the welcome screen, the computer has already stopped and rebooted. There should be a dump file. Nothing much will happen while the computer is at the welcome screen.

 

[lak121727]

I've run my computer til last night and shut it down for a while. Here the minidump files that i've found

 

[Jonathan_King]

It appears that your Intel wireless adapter drivers are the cause. Dated January 2010, they could possibly use an update, but if you can't find one, uninstall your current drivers and install a fresh copy.

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


Loading Dump File [C:\Documents and Settings\JK\Desktop\minidump\072610-9391-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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x8283b000 PsLoadedModuleList = 0x82983810
Debug session time: Tue Jul 27 00:58:34.176 2010 (GMT-4)
System Uptime: 0 days 0:06:45.893
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {85f04140, 2, 0, 828c0993}

*** WARNING: Unable to verify timestamp for NETw5s32.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s32.sys
Probably caused by : NETw5s32.sys ( NETw5s32+2386 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 85f04140, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 828c0993, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 829a3718
Unable to read MiSystemVaType memory at 82983160
 85f04140 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MmAccessFault+195
828c0993 f7401800000008  test    dword ptr [eax+18h],8000000h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  807e0964 -- (.trap 0xffffffff807e0964)
ErrCode = 00000009
eax=a97999d4 ebx=a97999c0 ecx=8be99558 edx=8ec84a29 esi=8be99548 edi=00000000
eip=82b7ade1 esp=807e09d8 ebp=807e0a48 iopl=0         nv up ei pl nz ac po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010212
nt!VfDeadlockAcquireResource+0x300:
82b7ade1 833b00          cmp     dword ptr [ebx],0    ds:0023:a97999c0=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 828c0993 to 8288182b

STACK_TEXT:  
807e086c 828c0993 badb0d00 00000080 000afe7c nt!KiTrap0E+0x2cf
807e094c 82881638 00000000 a97999c0 00000000 nt!MmAccessFault+0x195
807e094c 82b7ade1 00000000 a97999c0 00000000 nt!KiTrap0E+0xdc
807e0a48 82b753a8 8ec84a28 00000005 807c9800 nt!VfDeadlockAcquireResource+0x300
807e0a74 8e638386 854265c0 807e0ac8 00002000 nt!VerifierKfAcquireSpinLock+0x8d
WARNING: Stack unwind information not available. Following frames may be wrong.
807e0a88 8e63865a 8ec849d0 afe26fec 807e0acc NETw5s32+0x2386
807e0a98 8e6497ef 807e0ac8 0000000c 00000001 NETw5s32+0x265a
807e0acc 8e645cdc afe26fec 00002000 94790e18 NETw5s32+0x137ef
807e0ae4 8e644279 94790e18 00000087 9470ae68 NETw5s32+0xfcdc
807e0af8 8e671f59 94790e18 00000087 00000000 NETw5s32+0xe279
807e0b1c 8e668660 94790e18 807e0b38 9470ae68 NETw5s32+0x3bf59
807e0b54 8e66893e 9470ae68 946f2e10 933e0080 NETw5s32+0x32660
807e0bb8 8e662897 000000f0 946f2e10 000000ff NETw5s32+0x3293e
807e0bf4 8e66062c 006f8e78 80000000 807e0c10 NETw5s32+0x2c897
807e0c04 8e8c0bb5 946f2e10 807e0c50 8546e301 NETw5s32+0x2a62c
807e0c10 8546e301 935aceb0 00000000 00000000 NETw5s32+0x28abb5
807e0c50 854199f4 947d0f84 007d0e70 00000000 ndis!ndisMiniportDpc+0xda
807e0c78 828a33b5 947d0f84 947d0e70 00000000 ndis!ndisInterruptDpc+0xaf
807e0cd4 828a3218 807c4120 807c9800 00000000 nt!KiExecuteAllDpcs+0xf9
807e0d20 828a3038 00000000 0000000e ffffffff nt!KiRetireDpcList+0xd5
807e0d24 00000000 0000000e ffffffff ffffffff nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETw5s32+2386
8e638386 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  NETw5s32+2386

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETw5s32

IMAGE_NAME:  NETw5s32.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b4df694

FAILURE_BUCKET_ID:  0xA_VRF_NETw5s32+2386

BUCKET_ID:  0xA_VRF_NETw5s32+2386

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

1: kd> lmvm NETw5s32
start    end        module name
8e636000 8ecb2000   NETw5s32 T (no symbols)           
    Loaded symbol image file: NETw5s32.sys
    Image path: \SystemRoot\system32\DRIVERS\NETw5s32.sys
    Image name: NETw5s32.sys
    Timestamp:        Wed Jan 13 11:36:36 2010 (4B4DF694)
    CheckSum:         0067CCFF
    ImageSize:        0067C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4