BSOD since playing SWTOR and more frequently since moving PC

[holloa]

Hi, I've been playing STWOR and started getting BSOD over the past few weeks but I also moved the PC to a different room 3 weeks ago and cleaned it all out (thought overheating might be the cause - it wasn't) and am stuck now looking at the dmp files, actually I can't find anything that lets me look at them, wordpad makes no sense and notepad is denied even as Admin.

So, I followed the guide and created info on last 7 dumps.

I'm an Ex. software engineer but rarely touched windows so whilst I'm very much into self help and geeky enough to follow the info, I must admit to not understanding this!

PC details,
- x86
- Was OEM with Vista, upgraded to Windows 7 retail about 9 months ago
- PC about 3 years old

Antony.


Edit - Since posting I found the tool BlueScreenView and found 3 BSOD's were caused by the wireless dongle WPN111, I do remember having a problem with this last year but am using the latest drivers for this and have tried both dongles I have. Looks like I'll have to run an ethernet cable to the PC.

The other drivers, halmacpi.dll, avgmfx86.sys (I'll remove AGV AV to check this one) and tcpip.sys are more interesting that I'l like any advice on please.

 

[Maguscreed]

You need windows debugger to view dump files, and even then they are pretty useless unless you know what you are looking at.

At any rate. In this particular case the debugger was actually quite clear for once.
The offending component seems to be related to a Netgear device you have. (probably router)
I would swing by the netgear website and try to locate updated drivers/software for it.

http://support.netgear.com/app/products/list

Probably caused by : WPN111.sys ( WPN111+35bb3 )

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: ea03ffc4, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: d35d5bb3, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from e2fa0848
Unable to read MiSystemVaType memory at e2f7fe20
 ea03ffc4 

CURRENT_IRQL:  2

FAULTING_IP: 
WPN111+35bb3
d35d5bb3 8b0c82          mov     ecx,dword ptr [edx+eax*4]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  e2f5ead8 -- (.trap 0xffffffffe2f5ead8)
ErrCode = 00000000
eax=00000000 ebx=00000800 ecx=00000001 edx=ea03ffc4 esi=0000000f edi=c4bc6ce0
eip=d35d5bb3 esp=e2f5eb4c ebp=e2eae4c5 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
WPN111+0x35bb3:
d35d5bb3 8b0c82          mov     ecx,dword ptr [edx+eax*4] ds:0023:ea03ffc4=a2000000
Resetting default scope

LAST_CONTROL_TRANSFER:  from d35d5bb3 to e2e785fb

STACK_TEXT:  
e2f5ead8 d35d5bb3 badb0d00 ea03ffc4 0000884e nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
e2f5eb50 d35d5e6c ea03ffc4 0000003c d35d5161 WPN111+0x35bb3
e2f5eb5c d35d5161 ea03ffc4 c4c9e000 d35d7ad7 WPN111+0x35e6c
e2f5eb8c e2eaf913 00000000 c3f5ce28 00000000 WPN111+0x35161
00000000 00000000 00000000 00000000 00000000 nt!IopfCompleteRequest+0x128


STACK_COMMAND:  kb

FOLLOWUP_IP: 
WPN111+35bb3
d35d5bb3 8b0c82          mov     ecx,dword ptr [edx+eax*4]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  WPN111+35bb3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: WPN111

IMAGE_NAME:  WPN111.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  41ddeeeb

FAILURE_BUCKET_ID:  0xD1_WPN111+35bb3

BUCKET_ID:  0xD1_WPN111+35bb3

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

 

[holloa]

Thanks for clarifying that Maguscreed, I found some drivers for the wireless adpator that work have been updated with Win 7 - Really should look more often for these things, they are dated April 11!

running 'verifier' and selecting drivers caused all sorts of BSOD on boot errors and I couldn't get into safe mode either, had to use install disc and go back 3 days of restore points to get a boot!

Anyway, that is highlighting 'halmacpi.dll' as the problem, can I discard this one now?

Thanks for you assistance, Antony.

 

[Maguscreed]

yes I leave driver verifier off for general use.
It can get picky and cause bsod's when there should be none.

 

[holloa]

I'll leave it now then and see what happens,

Many thanks, Antony.

 

[holloa]

Well for anyone else having problems with Win 7 and Netgear WPN111 dongle, I can say that the new driver installer V3.0 for Win 7 has faulty drivers in it. You get a Code 10 error on the device and it doesn't start.

My solution after a days frustration was to revert back to the v1.0.0.1 driver which has worked fine all evening (was BCOD every few hours on V2 drivers)

I'm waiting to see if Netgear will send standalone drivers as Im aware their installer software causes problems anyway.

 

[writhziden]

Thanks for posting back your solution for others having the same problem. We always appreciate post backs and people who do their own troubleshooting. I have given you rep for the steps.