Unsolved
This post is more than 5 years old
61 Posts
0
45732
Alienware 18 Power supply
I have the new 18 with following specs
4900mq
780m sli
300w power supply
16gb ram (stock)
Problem is when moving from one page to the next, either between internet pages, metro to desktop or vice versa, or different apps or programs there is a significant drop in brightness for a few moments. The workstation is always plugged in, on U3 cooling pad, and free of any obstruction. Its less than a month old since I received it but I still checked and no dust problems. I have verified that all drivers are up to date. I went to power supply and have all settings set to max performance and brightness all the way up. I've reinstalled the operating system and still issues persist. I've also had problems while gamming where the system stutters in game or starts slowing up during the game. I've monitored the temps while this is going on and its hitting 85-90c and it does not appear the fans are spinning on the CPU side. The GPU temps are a bit better usually around 75-80c under load but on occasion hitting 85-90c as well. I'm not sure if the high temps are causing the behavior and this also does not appear to be internet related as its happening when not playing multiplayer games as well as multiplayer games. Another note is I've been steady hitting about 3-4 BSOD everyday since I've had the machine. Most are from page fault in non page area, irql_not_less_or_equal as well as others. I try to check them and resolve the issue on my own but I have not found working resolutions. I gotta get the BSOD's to stop and the stuttering or lagging in game issues are a big worry. The upper left corner of the keyboard (CPU) is too hot to touch when gaming. The decrease in brightness when changing apps or pages is a concern and the decreased performance in offline as well as online gaming is also an issue. Any suggestions?
BJFox
763 Posts
0
January 27th, 2014 13:00
The stop errors are not pointing to a specific hardware device driver as far as I can see.
By chance do you still have the pre-installed McAfee junk? Is so, this could be the culprit. If you removed the McAfee without using a "cleaner" to thoroughly rid your system of their horrible files, that could be causing some problems. Download the MCPR tool from McAfee web site [DIRECT DOWNLOAD LINK] and run it after removing any McAfee product.
If not McAfee, what antivirus are you using?I have seen some examples of McAfee, AVG and Avast causing this STOP error. If you are running Windows 8, you do not need a third-party antivirus. The native antivirus and malware support is adequate. If you have Windows 7, Microsoft Security Essentials is a good free option you can try as an alternative to the above. If none of these resolves the issue, you can always go back to using your preferred protection solution once the issue is resolved.
Another thing you might want to try is disabling your Windows page file. Reboot, then go back in and set a static size of 8192MB for both minimum and maximum.
BJFox
763 Posts
0
January 27th, 2014 13:00
ian dalm
61 Posts
0
January 27th, 2014 20:00
I did the adaptive display brightness previously but maybe it was just I picked the wrong settings. I think I went back in and set it to zero this may have cleared up the issue. Thanks for the heads up on this one. Easy fix for an annoying issue. Also I didn't have Macafee installed out of the box. I did, however, follow your instructions and ran the uninstall tool. This was just moments ago btw and no stop errors yet.
I'm running MSE only. I never use anything else. The current config is all stock and has win 7. I had to download mse and install it but win 8 is nice as it comes with it.
ian dalm
61 Posts
0
February 2nd, 2014 06:00
Still crashing...
I've run all diagnostic tests and tested all memory short of pulling the palmrest off to get at the memory under keyboard. I was familar with taking apart and putting reassembling previous models of the 17xr3,r4 but hesitate with this 18 until I decide to put 3rd part RAM in myself. Since its still stock parts and under warranty I would like to see what Dell advises before I take it apart. Still getting 1-2 everyday I use the machine. Most of the errors still appear to reference memory but hey, I'm no expert on this. Here are the errors. Any help is appreciated! Thanks!!
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 2/2/2014 8:11:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020214-15693-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF80002ED2E61)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 2/2/2014 8:11:49 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF80002ED2E61)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 2/1/2014 7:23:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020114-19827-01.dmp
This was probably caused by the following module: hal.dll (hal+0x7AE7)
Bugcheck code: 0x50 (0xFFFFF80003E9DC17, 0x8, 0xFFFFF80003E9DC17, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 1/31/2014 12:29:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\013014-19687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3D (0xFFFFF80000B9BFA0, 0x0, 0x0, 0xFFFFF80002E853F8)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 1/30/2014 7:57:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\013014-28314-01.dmp
This was probably caused by the following module: bcmwl664.sys (0xFFFFF8800588F6DC)
Bugcheck code: 0x50 (0xFFFFFA8033AF5A13, 0x0, 0xFFFFF8800588F6DC, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\bcmwl664.sys
product: Broadcom 802.11 Network Adapter wireless driver
company: Broadcom Corporation
description: Broadcom 802.11 Network Adapter wireless driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
Google query: Broadcom Corporation PAGE_FAULT_IN_NONPAGED_AREA
On Sun 1/26/2014 7:18:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012614-30856-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0xFFFFEA00388EC54F, 0xF, 0x1, 0xFFFFF80002EB6F7C)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
BJFox
763 Posts
0
February 2nd, 2014 08:00
Brother Ian, at least one of your STOP error is pointing to your WiFi adapter driver. Not sure if it will help, but here are a couple of suggestions.
If you haven't already tried it, go into the BIOS and reset defaults on the Exit menu. This will undo any changes you have implemented to make your CPU run better, but see if the BSOD continues to occur over a day or two. If the problem is resolved, you will need to try some alternative CPU power settings to get the CPU to perform correctly.
If it does continue to happen with BIOS defaults, grab either one of these options:
Edimax EW-7811Un 150 Mbps Wireless 11n Nano Size USB Adapter - $9.99
TP-LINK TL-WN725N Wireless N Nano USB Adapter - $8.99
...and disable your internal Broadcom WiFi adapter in Device Manager. If using one of these cheap USB adapters makes the STOP errors go away you will know the WiFi driver and/or WiFi adapter is the culprit. If you have the ability to use the wired network adapter for a couple of days instead of paying $9-10 for testing, disable the WiFi adapter and use wired access for a couple of days to see if the problem goes away. If it does, you'll have some meaningful information to share with Alienware Tech Support. If the WiFi adapter is causing the problem, ask them to replace it with another Broadcom AC or Killer 1202 N adapter.
Vincent Routhie
2 Posts
0
February 2nd, 2014 15:00
I am having same couple bsod with my alienware 17. I do not have all my dump file because i did a fresh install of windows 7 yesterday and I did not save them but i still get a IRQL_NOT_LESS_OR_EQUAL bsod today. I hope we find a solution to that!
ian dalm
61 Posts
0
February 2nd, 2014 18:00
Brother Fox,
I did previously see the Broadcom error and also noticed Dell drivers have new driver listed for the Broadcom WiFi adapter literaly the same day. I updated it and have not run into that STOP error again. If I do run into that one again I could probably plug in for a few days or I think I have and intel 6series WiFi card here somewhere I could swap.
Just read your response about A04 though and really these STOP errors have had me down the potential of effective solutions to fan table issues in A04 make the STOP errors hurt that much less
Vincent Routhie
2 Posts
0
February 3rd, 2014 17:00
Here is my CrashDump Analyze
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\020214-10920-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02e12000 PsLoadedModuleList = 0xfffff800`030556d0
Debug session time: Sun Feb 2 14:01:40.757 2014 (UTC - 5:00)
System Uptime: 0 days 0:06:17.600
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {ffffd80003a10f84, 2, 1, fffff80002e93c83}
Unable to load image \SystemRoot\system32\DRIVERS\bflwfx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bflwfx64.sys
*** ERROR: Module load completed but symbols could not be loaded for bflwfx64.sys
Probably caused by : hardware ( bflwfx64+123f )
Followup: MachineOwner
---------
0: 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: ffffd80003a10f84, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002e93c83, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bf100
ffffd80003a10f84
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeExpandKernelStackAndCalloutEx+4e7
fffff800`02e93c83 004c8984 add byte ptr [rcx+rcx*4-7Ch],cl
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff80000b9c270 -- (.trap 0xfffff80000b9c270)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80000b97000 rbx=0000000000000000 rcx=fffff80000b9d000
rdx=fffff80000b90070 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e93c83 rsp=fffff80000b9c400 rbp=0000000000000000
r8=fffff80000b9d000 r9=0000000000000000 r10=0000000000000002
r11=fffff80000b9c400 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KeExpandKernelStackAndCalloutEx+0x4e7:
fffff800`02e93c83 004c8984 add byte ptr [rcx+rcx*4-7Ch],cl ds:ffffd800`03a10f84=??
Resetting default scope
MISALIGNED_IP:
nt!KeExpandKernelStackAndCalloutEx+4e7
fffff800`02e93c83 004c8984 add byte ptr [rcx+rcx*4-7Ch],cl
LAST_CONTROL_TRANSFER: from fffff80002e87169 to fffff80002e87bc0
STACK_TEXT:
fffff800`00b9c128 fffff800`02e87169 : 00000000`0000000a ffffd800`03a10f84 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9c130 fffff800`02e85de0 : 00000000`04b00000 00000000`00000000 00000000`00000000 fffff800`03010cc0 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c270 fffff800`02e93c83 : fffffa80`0d81b520 00000000`00004800 fffff800`03010cc0 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9c400 fffff880`01a57e22 : fffff880`01a57650 fffffa80`175619b0 00000000`00000002 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x4e7
fffff800`00b9c4e0 fffff880`019310eb : fffffa80`18bec010 00000000`00000000 fffffa80`179c51a0 fffffa80`179c51a0 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff800`00b9c550 fffff880`018faad6 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff800`00b9c5c0 fffff880`0187d5d4 : fffffa80`179c51a0 00000000`00000002 00000000`00000001 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffff800`00b9ca40 fffff880`0187d549 : 00000000`0000b901 fffff880`04663b1d fffffa80`17767288 00000000`00000000 : ndis!ndisMTopReceiveNetBufferLists+0x24
fffff800`00b9ca80 fffff880`0187d4e0 : fffffa80`17764008 00000000`0000b900 fffffa80`0d78e520 fffffa80`0d78e520 : ndis!ndisFilterIndicateReceiveNetBufferLists+0x29
fffff800`00b9cac0 fffff880`0465c23f : 00000000`00000001 fffffa80`0d78e520 00000000`00000002 00000000`00000024 : ndis!NdisFIndicateReceiveNetBufferLists+0x50
fffff800`00b9cb00 00000000`00000001 : fffffa80`0d78e520 00000000`00000002 00000000`00000024 00000000`00000000 : bflwfx64+0x123f
fffff800`00b9cb08 fffffa80`0d78e520 : 00000000`00000002 00000000`00000024 00000000`00000000 00000000`00000000 : 0x1
fffff800`00b9cb10 00000000`00000002 : 00000000`00000024 00000000`00000000 00000000`00000000 00000000`00000001 : 0xfffffa80`0d78e520
fffff800`00b9cb18 00000000`00000024 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff880`04660231 : 0x2
fffff800`00b9cb20 00000000`00000000 : 00000000`00000000 00000000`00000001 fffff880`04660231 0000077d`00000701 : 0x24
STACK_COMMAND: kb
FOLLOWUP_IP:
bflwfx64+123f
fffff880`0465c23f ?? ???
SYMBOL_STACK_INDEX: a
SYMBOL_NAME: bflwfx64+123f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------