New
#51
Updated the BIOs and @TEWs Im not giving up :P
Updated the BIOs and @TEWs Im not giving up :P
Graphics Driver Download successful, everything looks prettier and resolution has been increased to 1024x768 (Finally!No more 800x600)So far so good, the real test will be if I get a blue screen while running Maple Story......I'll post what happens in a couple of hours when I download it, also where can I get directx 9 which will work fir windows 7 if anyone has a link that would be much appreciated and also thanks for your help guys, I hope this works! Anyways can someone give me a link to directx 9 that will work with windows 7?
JNC
Microsoft for directX if your card supports it. run dxdiag in search to find out
Crap BSOD already!!!!!!! I was just on google and all of sudden BSOD....... what should I do? :/
jnc
You can try to install direct x 9 in compatibility mode or try installing directx 10. Im not sure
Attachment 28790
BSOD....What should I do?^^^^^
JNC
ok that one was caused by
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\092009-20062-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8183f000 PsLoadedModuleList = 0x8197e570
Debug session time: Sun Sep 20 16:05:02.586 2009 (GMT-4)
System Uptime: 0 days 0:17:53.211
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {20, 2, 0, 8ca0cb54}
Unable to load image \SystemRoot\system32\DRIVERS\netr61.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netr61.sys
*** ERROR: Module load completed but symbols could not be loaded for netr61.sys
Probably caused by : netr61.sys ( netr61+bb54 )
Followup: MachineOwner
---------
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: 00000020, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8ca0cb54, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 8199e700
Unable to read MiSystemVaType memory at 8197e0c0
00000020
CURRENT_IRQL: 2
FAULTING_IP:
netr61+bb54
8ca0cb54 837c812000 cmp dword ptr [ecx+eax*4+20h],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: iexplore.exe
TRAP_FRAME: 8818ade4 -- (.trap 0xffffffff8818ade4)
ErrCode = 00000000
eax=00000000 ebx=84b3da80 ecx=00000000 edx=00000000 esi=848630e0 edi=00000000
eip=8ca0cb54 esp=8818ae58 ebp=8818ae5c iopl=0 nv up ei pl nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010217
netr61+0xbb54:
8ca0cb54 837c812000 cmp dword ptr [ecx+eax*4+20h],0 ds:0023:00000020=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 8ca0cb54 to 81877b5b
STACK_TEXT:
8818ade4 8ca0cb54 badb0d00 00000000 848630e0 nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
8818ae5c 8ca0c54f 00000000 849a84e8 84b2e000 netr61+0xbb54
8818aed4 8ca02262 849ad268 849ad268 8818af20 netr61+0xb54f
8818aee4 88a48309 849ad268 00000000 8818af10 netr61+0x1262
8818af20 889f39f4 84b3da94 00b3da80 00000000 ndis!ndisMiniportDpc+0xe2
8818af48 81894815 84b3da94 84b3da80 00000000 ndis!ndisInterruptDpc+0xaf
8818afa4 81894678 81960d20 83ac1758 00000000 nt!KiExecuteAllDpcs+0xf9
8818aff4 81893e3c 9bbe2838 00000000 00000000 nt!KiRetireDpcList+0xd5
8818aff8 9bbe2838 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
81893e3c 00000000 0000001a 00d6850f bb830000 0x9bbe2838
STACK_COMMAND: kb
FOLLOWUP_IP:
netr61+bb54
8ca0cb54 837c812000 cmp dword ptr [ecx+eax*4+20h],0
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: netr61+bb54
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: netr61
IMAGE_NAME: netr61.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 44ee74a9
FAILURE_BUCKET_ID: 0xD1_netr61+bb54
BUCKET_ID: 0xD1_netr61+bb54
Followup: MachineOwner
Seems that IE c aused the ralink driver to puke and die. what does the wifi/nic driver look like in device manager?
kEN
Linksys Wireless-G PCI Adapter (What I'm using)
And Intel(R) Pro/1000 MT Network Connection (Dunno what this is)
This is all there is under Network Adapters
Nothing about Ralink...=/
Intel is the wired driver
let me go double check brb
My mistake the same file is used byt both rallink, and linksys. so IE caused the wifi driver to bsod. Im begining to wonder if there isn't an underlying memory problem causing all the other problems.
Can you type msinfo32 in search, save the resulting file and upload it to us?
Last edited by zigzag3143; 20 Sep 2009 at 15:32. Reason: for addition and correction