I have been having Some Problems With my Laptop Havin BSOD.
It Got Windows 7 Ultimate 64 bit , With the bluescreen view It says That the files causing the BSOD are : netw5v64.sys And : ntoskrnl.exe
I Include the .dmp file Here For you all to check:
https://rapidshare.com/files/26072065/042612-40560-01.dmp
Waiting For you help....![]()
-
StormJumper Notebook Virtuoso
Do you have Sp1 updated to that version? Just a reminder you can also do a search on the internet can sometimes locate others whom had problems related to those files you listed. Also you need to tell us your computer make and model and if laptop or desktop for others to get a better feel of what problem is happening. Identifying the hardware goes along way incase others had similar problems and what solutions they used. Since all those seems to related to NT which are core operating files windows needs would seem to suggested you got a malware or virus that changed those core files causing the BSOD or that your windows core system files during your usage was corrupted and that would suggest a reinstall of the O/S or using the O/S to do a file recovery to over write those bad files to fix the problem but if the latter doesn't work a total wipe and reinstall of the O/S is the only way to fix your problem and then update to SP1 as well.
-
Here is the information of the laptop...
------------------
System Information
------------------
Time of this report: 4/26/2012, 17:55:17
Machine name: --------
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7600) (7600.win7_rtm.090713-1255)
Language: Finnish (Regional Setting: Finnish)
System Manufacturer: Acer
System Model: Aspire 7738
BIOS: Ver 1.00PARTTBL
Processor: Intel(R) Core(TM)2 Duo CPU T6400 @ 2.00GHz (2 CPUs), ~2.0GHz
Memory: 4096MB RAM
Available OS Memory: 4090MB RAM
Page File: 2652MB used, 5527MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7600.16385 32bit Unicode -
download who crashed (in my sig below) which gives a much better dump file.
-
I did Donwload the service pack 1 , and for now it seems to be better.
If there any problems i will contact here again... -
Here's the dump file you uploaded:
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {1b, 2, 0, fffff88004a9ac30} Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys Probably caused by : hardware ( atikmdag+27dc30 ) Followup: MachineOwner --------- 0: 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: 000000000000001b, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff88004a9ac30, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec40e0 000000000000001b CURRENT_IRQL: 2 FAULTING_IP: atikmdag+27dc30 fffff880`04a9ac30 02751a add dh,byte ptr [rbp+1Ah] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff80000b9c390 -- (.trap 0xfffff80000b9c390) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800a09f590 rdx=fffffa800a09f580 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88004a9ac30 rsp=fffff80000b9c528 rbp=0000000000000001 r8=0000000010b6b783 r9=0000000001cd2194 r10=fffff80002c1c000 r11=fffff80000b9c570 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc atikmdag+0x27dc30: fffff880`04a9ac30 02751a add dh,byte ptr [rbp+1Ah] ss:0018:00000000`0000001b=?? Resetting default scope MISALIGNED_IP: atikmdag+27dc30 fffff880`04a9ac30 02751a add dh,byte ptr [rbp+1Ah] LAST_CONTROL_TRANSFER: from fffff80002c8bb29 to fffff80002c8c5c0 STACK_TEXT: fffff800`00b9c248 fffff800`02c8bb29 : 00000000`0000000a 00000000`0000001b 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff800`00b9c250 fffff800`02c8a7a0 : 00000000`0000000a fffff800`00b9c5c0 fffff800`02e06e80 fffff800`02c98c60 : nt!KiBugCheckDispatch+0x69 fffff800`00b9c390 fffff880`04a9ac30 : fffff800`02c9812e fffff800`00b9c5c0 00000000`00018510 00000000`00000000 : nt!KiPageFault+0x260 fffff800`00b9c528 fffff800`02c9812e : fffff800`00b9c5c0 00000000`00018510 00000000`00000000 00000000`00000055 : atikmdag+0x27dc30 fffff800`00b9c530 fffff800`02c97c76 : fffffa80`0e197c68 fffffa80`0e197c68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff800`00b9c5a0 fffff800`02c9834e : 00000003`ee55fdcc fffff800`00b9cc18 00000000`0001a6c2 fffff800`02e0aac8 : nt!KiProcessExpiredTimerList+0xc6 fffff800`00b9cbf0 fffff800`02c97b57 : 00000000`d79df0c2 00000000`0001a6c2 00000000`d79df077 00000000`000000c2 : nt!KiTimerExpiration+0x1be fffff800`00b9cc90 fffff800`02c94d8a : fffff800`02e06e80 fffff800`02e14c40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277 fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: atikmdag+27dc30 fffff880`04a9ac30 02751a add dh,byte ptr [rbp+1Ah] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: atikmdag+27dc30 FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_IP_MISALIGNED_atikmdag.sys BUCKET_ID: X64_IP_MISALIGNED_atikmdag.sys Followup: MachineOwner ---------
If the problem persists, it may be your video card (hardware problem).
If you get more BSODs please upload the dump file(s).
Windows 7 64 bit BSOD Problem!
Discussion in 'Windows OS and Software' started by tuk12, Apr 26, 2012.