Freeze, crash and BSOD in Vista

Hi all.

Just recently I bought an Acer Aspire 5930G from a retailer here in Norway. It worked splendidly for quite a while, with no problems worth mentioning. Unfortunately, this was not to be.

It all started out when gaming. The machine would then get very warm (but I've seen other 5930G owners complaining about this as well), and when I was done, it went ahead and froze. Neither the keyboard nor the mouse responded (only the in and unplugging of the power cable would trigger the charging light), but it did turn off when I held the power button. I didn't think too much about this at the time though, thinking it probably had something to do with the heat.

Then one day, it froze in Word even though the computer was cool and under little strain. After this the computer started freezing more regulary, in addition to simply crashing and restarting and displaying BSODs.

So I performed a recovery with Acer eRecovery, and was back to the factory settings. However, not before I had deleted all the bloatware, done some tweaks in Vista and started installing programs again, the problems reoccured.

Since I did the recovery I've had a lot of freezes and crashes, and three BSODs. I've also installed the Windows Debugger Tool, and the minidumps from these BSODs suggest as far as I can see, three different error sources. I'm no pro at these though, so I was really hoping someone in here could take a look at them. They are as follows:


March 22nd:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: b7b40000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: a50290b4, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from 81d89868
Unable to read MiSystemVaType memory at 81d69420
b7b40000

FAULTING_IP:
WSVD+70b4
a50290b4 ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: 8a933c2c -- (.trap 0xffffffff8a933c2c)
ErrCode = 00000000
eax=b7b40000 ebx=00000000 ecx=b7b40000 edx=b7b62000 esi=00000000 edi=00000000
eip=a50290b4 esp=8a933ca0 ebp=8a933ca0 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
WSVD+0x70b4:
a50290b4 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from 81cacbb4 to 81cf7155

STACK_TEXT:
8a933c14 81cacbb4 00000000 b7b40000 00000000 nt!MmAccessFault+0x10a
8a933c14 a50290b4 00000000 b7b40000 00000000 nt!KiTrap0E+0xdc
WARNING: Stack unwind information not available. Following frames may be wrong.
8a933c9c 8a933cac a50290ff b7b40000 8a933cc4 WSVD+0x70b4
8a933ca0 a50290ff b7b40000 8a933cc4 a50293e7 0x8a933cac
8a933cac a50293e7 b7b62000 b7b62000 855db0e0 WSVD+0x70ff
8a933cc4 a5023598 b7b62000 b50c4030 81d86d40 WSVD+0x73e7
8a933ce0 81d0e053 855db028 8597c008 84dca0e0 WSVD+0x1598
8a933cf8 81f22213 81d54100 84188580 00000000 nt!IofCallDriver+0x63
8a933d2c 81f27cc8 855db028 84188580 81d5fbd0 nt!IoShutdownSystem+0x80
8a933d44 81c8a41d 00000000 00000000 84188580 nt!PopGracefulShutdown+0x14c
8a933d7c 81e27b18 00000000 74e5d5e0 00000000 nt!ExpWorkerThread+0xfd
8a933dc0 81c80a3e 81c8a320 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
WSVD+70b4
a50290b4 ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: WSVD+70b4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: WSVD

IMAGE_NAME: WSVD.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4764f67f

FAILURE_BUCKET_ID: 0x50_WSVD+70b4

BUCKET_ID: 0x50_WSVD+70b4

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


March 25th:



*******************************************************************************
* *
* 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: ff833503, 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: 81e70c44, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 81f54868
Unable to read MiSystemVaType memory at 81f34420
ff833503

CURRENT_IRQL: 2

FAULTING_IP:
nt!RtlCompareMemory+14
81e70c44 f3a7 repe cmps dword ptr [esi],dword ptr es:[edi]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: 81f12a60 -- (.trap 0xffffffff81f12a60)
ErrCode = 00000000
eax=ff833503 ebx=8eecbb99 ecx=224062c5 edx=00000200 esi=81f12b2c edi=ff833503
eip=81e70c44 esp=81f12ad4 ebp=81f12af4 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!RtlCompareMemory+0x14:
81e70c44 f3a7 repe cmps dword ptr [esi],dword ptr es:[edi]
Resetting default scope

LAST_CONTROL_TRANSFER: from 81e70c44 to 81e77d24

STACK_TEXT:
81f12a60 81e70c44 badb0d00 00000200 ffd070f0 nt!KiTrap0E+0x2ac
81f12ad8 89da8b47 81f12b2c ff833503 89018b14 nt!RtlCompareMemory+0x14
81f12af4 89da8d82 81f12b2c ff833503 89018b14 NETIO!PtpCompareFullKeys+0x21
81f12b14 8eecfd09 8eecbb99 81f12b2c 81f12b0c NETIO!PtGetLongestMatch+0x22
81f12b50 8eecc296 8ef29188 81f12c50 81f12c88 tcpip!IppFindNextHopAtDpc+0x6af
81f12b60 8eecb9e3 8ef29188 81ed3c40 8ef36780 tcpip!IppProtocolTimeout+0xf
81f12b68 81ed3c40 8ef36780 00000000 f3337bcb tcpip!IppTimeout+0x4f
81f12c88 81ed3876 81f12cd0 af005a02 81f12cd8 nt!KiTimerListExpire+0x367
81f12ce8 81ed33c3 00000000 00000000 00004983 nt!KiTimerExpiration+0x2a0
81f12d50 81ed1edd 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
81f12d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49


STACK_COMMAND: kb

FOLLOWUP_IP:
NETIO!PtpCompareFullKeys+21
89da8b47 8bc8 mov ecx,eax

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: NETIO!PtpCompareFullKeys+21

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME: NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 47919103

FAILURE_BUCKET_ID: 0xA_NETIO!PtpCompareFullKeys+21

BUCKET_ID: 0xA_NETIO!PtpCompareFullKeys+21

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


March 27th:

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 81f75868
Unable to read MiSystemVaType memory at 81f55420
00000000

CURRENT_IRQL: 2

FAULTING_IP:
NETw5v32+ff74
91216f74 ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: 803eca08 -- (.trap 0xffffffff803eca08)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=859a3402 edx=00000000 esi=88d95000 edi=00000000
eip=91216f74 esp=803eca7c ebp=803ecb08 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
NETw5v32+0xff74:
91216f74 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from 91216f74 to 81e98d24

STACK_TEXT:
803eca08 91216f74 badb0d00 00000000 91216fd5 nt!KiTrap0E+0x2ac
WARNING: Stack unwind information not available. Following frames may be wrong.
803eca78 869e9240 88d95000 862a808c 81e125b0 NETw5v32+0xff74
803ecb08 91248dd6 859e6d10 00000000 00000001 0x869e9240
803ecb4c 91211d6e 846d5fc8 860e0560 88d95058 NETw5v32+0x41dd6
803ecb78 912120b3 846d5fa8 846d5ff8 860e0560 NETw5v32+0xad6e
803ecb90 91211515 860e0560 846d5fd8 860d0db8 NETw5v32+0xb0b3
803ecbac 912268e6 860d0df4 00000086 00000000 NETw5v32+0xa515
803ecbd4 91223828 803ecbf0 803ecbf0 86125438 NETw5v32+0x1f8e6
803ecc0c 91223a73 86125438 86100d50 862a8100 NETw5v32+0x1c828
803ecc48 9121cd84 00000001 86100d50 000000ff NETw5v32+0x1ca73
803ecc80 91219dac 80000000 86100d01 803ecc9c NETw5v32+0x15d84
803ecc90 91208755 86100d50 803eccc4 89d40115 NETw5v32+0x12dac
803ecc9c 89d40115 859b2ed0 00000000 00000000 NETw5v32+0x1755
803eccc4 89c81468 88d37e18 91208740 00000000 ndis!ndisMiniportDpc+0x7a
803ecce8 81ef4450 88d37e18 854df0e8 00000000 ndis!ndisInterruptDpc+0xc4
803ecd50 81ef2edd 00000000 0000000e 562eb7ce nt!KiRetireDpcList+0x147
803ecd54 00000000 0000000e 562eb7ce 58b9f6a0 nt!KiIdleLoop+0x49


STACK_COMMAND: kb

FOLLOWUP_IP:
NETw5v32+ff74
91216f74 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: NETw5v32+ff74

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETw5v32

IMAGE_NAME: NETw5v32.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4815d132

FAILURE_BUCKET_ID: 0xD1_NETw5v32+ff74

BUCKET_ID: 0xD1_NETw5v32+ff74

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

I might also add that I haven't updated any of the drivers except the Nvidia driver, and this I only did before the recovery. OS is Windows Vista Home Permium 32-bit, and hardware specs should be in my signature.

My only guess here is that it has something to do with being on the internet. Most of the problems occur while surfing pages, and even though it has happend in Word as well, I've always been connected I think.

I'm really considering to just send this back to the retailer, but as I'm sure that will take quite a lot of time I want to make sure there's nothing I can do to fix this. So if there's any other information that might be relevant, just let me know I will do my best to get them on here.

Thanks in advance.

- Eirik

 

If you updated the NVIDIA driver from the NVIDIA site, uninstall it and download / install the driver from your system manufacturer's site - the OEM driver's aren't quite the same as they are on your system support site.

2 other things to try as you're obviously having memory errors:

Perform a Hard Reset of your system:

1. Remove AC Adapter and then the battery from the unit.
2. Hold down the Power button for at least 20 - 30 seconds. This will clear
any residual commands in you memory.
3. Reinstall the Battery and Adapter and reboot.

The other thing you need to do is to check you Event logs to see if there's a Hardware Event logged. Click on Start, then type Event, then click on Event Viewer at the top. When it opens, check the following logs:

Custom: Administrative Events
Windows: System Events
Applications and Services: Hardware Events
Microsoft/Windows: Diagnostics-Performance, Memory Diagnostics

Look for Error (Red) and Warning (Yellow) flags that will give you further information on what the problem is.

 

Thanks for replying

I would think this happened when I did the recovery and went back to factory settings?

Tried this, but couldn't see any changes when rebooting. So I have no idea if it worked or not.

Whoa! I found quite a lot.

Custom - Administrative Events: 10 830 events, all either warnings or errors. Mostly warnings with source: Servicing, but it appears to be a little bit of everything. Especially at the beginning and end there's lots of errors and warnings that state its' source as something other than servicing.

(The computer then crashed, and when I rebooted it was 10 839 events.)

Windows - System Events: 37 679 event, but mostly information. Still, lots of warnings, many of which have source: servicing, and some errors. All errors seems to be from reasonably recent times, upper 10th of the list perhaps.

Applications and Services - Hardware Events: 0 events

Microsoft/Windows - Diagnostics-Performance: 185 events. Appears to be a nice mix of warnings, erros and some red ones with a cross that says somethins like "Critical". (Vista in norwegian, so bear with my translations.) Earliest a critical from 06.02.08, which is long before I got the computer.

Microsoft/Windows - Memory Diagnostics: 0 events.


Is there anything in particular I'm looking for?

 

So I take this lack of response means no one really has a clue (except that it's hardware) and I'm best off just returning it?

 

I suppose the exact events would be interesting, but if you get hardware errors returnig is generally the easiest option.

 

It certainly seems to be hardware related, so I guess you're right.

I might have a listen some other places just to be sure though. Like I said, I would rather try to avoid the time consuming process of returning it.

Anyways, thanks for helping