Windows 8.1 BSOD problem

Hello i have an ASUS S400 CA ultrabook and my BSOD problems have started after automated upgrade from windows 8 to windows 8.1 Here is the latest dump file. BSOD problem says "DRIVER_IRQL_NOT_LESS_OR_EQUAL(athw8x.sys)"
I have downloaded driver from the ASUS website but the problem remains unsolved. Please, give me some advice, thank you in advance
https://dl.dropboxusercontent.com/u/79149617/042314-24390-01.dmp

Hi,
The attached DMP file is of the DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) bug check.
This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high. This bug check is usually caused by drivers that have used improper addresses.
3: kd> k
Child-SP RetAddr Call Site
ffffd000`2161c3d8 fffff803`78f627e9 nt!KeBugCheckEx
ffffd000`2161c3e0 fffff803`78f6103a nt!KiBugCheckDispatch+0x69
ffffd000`2161c520 fffff800`0272571f nt!KiPageFault+0x23a
ffffd000`2161c6b0 ffffc000`00000000 athwbx+0x9671f
ffffd000`2161c6b8 fffff803`7918a223 0xffffc000`00000000
ffffd000`2161c6c0 ffffe000`6666744e nt!FsRtlTeardownPerStreamContexts+0x53
ffffd000`2161c730 ffffc000`03ba6010 0xffffe000`6666744e
ffffd000`2161c738 fffff800`00db4dd2 0xffffc000`03ba6010
ffffd000`2161c740 fffff800`00cdbe24 Ntfs!NtfsDeleteFcb+0x460
ffffd000`2161c7c0 fffff800`00000002 Ntfs!NtfsTeardownFromLcb+0x1f4
ffffd000`2161c850 fffff800`00000001 CI!_guard_check_icall_fptr <PERF> (CI+0x2)
ffffd000`2161c858 fffff800`029692f0 CI!_guard_check_icall_fptr <PERF> (CI+0x1)
ffffd000`2161c860 ffffe000`00000000 athwbx+0x2da2f0
ffffd000`2161c868 fffff800`029685d0 0xffffe000`00000000
ffffd000`2161c870 fffff800`02968550 athwbx+0x2d95d0
ffffd000`2161c878 ffffd000`2161c890 athwbx+0x2d9550
ffffd000`2161c880 ffffd000`2161c951 0xffffd000`2161c890
ffffd000`2161c888 ffffd000`2161c900 0xffffd000`2161c951
ffffd000`2161c890 ffffe000`01581098 0xffffd000`2161c900
ffffd000`2161c898 00000000`00000000 0xffffe000`01581098
^^ athwbx.sys is the Qualcomm Atheros AR9485WB-EG Wireless Network Adapter. In every case I've dealt with this driver, the manufacturer never actually had the latest version, and downloading this driver always helped -
http://www.atheros.cz/atheros-wireless-download.php?chipset=61&system=7
^^ Atheros' website can be kind of confusing to say the very least, so let me know if you need help downloading it.
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama

Similar Messages

MOVED: K9N2 SLI Platinum - Windows 7 x64 BSOD problems

This topic has been moved to Windows 7.
https://forum-en.msi.com/index.php?topic=133545.0

The memorycontroller on that board is an oldie, got one myself and it will probably not run @800MHz with all slots occupied on a x64 OS.
That contoller is only rated for 667MHz when running all channells fully occupied.
The fact that you could run it so under x86 has probably to do with the fact it didnt adress all the memory, but only 3.25GB max and thus it was stable enough.
Now you are running an OS that uses all memory and thus it can become unstable while its running at a too high speed for the controller.
I had the same and could "only" get the memory to work @750MHz tops, before it decided to BSOD or bootloop on me.
This is inherent to its design (from NVidia, they made the chipset) and cannot be overcome, but dont worrie yourself, the speeddifference between 667MHz and 800MHz is negligible and will only show up if you run benches, in normal day to day use, you will hardly, if ever, notice it.
But, do you really need 8GB???
If you do gaming, internet, office and other "light" work, i.e. normal homeusage, 4GB is already more then enough.
8GB is nice if you use cad/cam, photoshop and other memory intensive stuff.

Windows 8.1 BSOD - ntoskrnl.exe

Hi, I've been experiencing BSOD's on a daily basis (only when I am away from my computer) and I'd like to know the root cause of the problems. I've attached several minidump files below. Using Windbg (x64) the only problem I can see is ntoskrnl.exe being
unable to load (either corrupted or missing). sfc/scannow has detailed several problems relating to ntoskrnl.exe as well
https://onedrive.live.com/redir?resid=6e6984aa2d967f21%212299
Thanks!
Bill

You've recommended the opposite of what I was told last time: "The crashes are being caused by you
NVidia display driver. Please uninstall an "clean" reinstall the current driver version".
Last time I had BSOD problems I was using version 326.19 (at least one year old) and now I have the most recent version. As a result, I do not believe this is the cause of the BSOD's.
Also, I do not see the same thing you do when opening the minidump file, as follows:
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\040815-36484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
Executable search path is:
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17668.amd64fre.winblue_r8.150127-1500
Machine Name:
Kernel base = 0xfffff802`0a282000 PsLoadedModuleList = 0xfffff802`0a55b250
Debug session time: Wed Apr 8 14:02:21.387 2015 (UTC - 6:00)
System Uptime: 0 days 20:32:22.558
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, ffffe0019c12a760, fffff8020c30e960, ffffe001a1f67680}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: NT!_DEVICE_OBJECT ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_IRP ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_IRP ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!TRIAGE_9F_POWER ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_IRP ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_IO_STACK_LOCATION ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_IRP ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_DEVICE_OBJECT ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***

Having BSOD problem

Hi Microsoft professional team,
I am using Windows 8.1 pro and I keep having the BSOD problem everyday. I uploaded the memory dump file to OneDrive.
Can you give me a hand on this to find out where the problem is?
Many Thx.
Daniel

DMS
Driver verified and Related to ZoneAlarm Firewall Driver. I would remove it and use the built in defender in its place
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\New folder\031215-6609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17668.amd64fre.winblue_r8.150127-1500
Machine Name:
Kernel base = 0xfffff801`0b61a000 PsLoadedModuleList = 0xfffff801`0b8f3250
Debug session time: Wed Mar 11 13:03:15.527 2015 (UTC - 4:00)
System Uptime: 0 days 0:02:12.192
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck A, {ffffcf8094653000, 2, 1, fffff8010b702dde}
*** WARNING: Unable to verify timestamp for vsdatant.sys
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
Probably caused by : vsdatant.sys ( vsdatant+13bc0 )
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: ffffcf8094653000, 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: fffff8010b702dde, address which referenced memory
Debugging Details:
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8010b97d138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
ffffcf8094653000
CURRENT_IRQL: 2
FAULTING_IP:
nt!MmBuildMdlForNonPagedPool+ee
fffff801`0b702dde 48890c17 mov qword ptr [rdi+rdx],rcx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: AV
PROCESS_NAME: System
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
TRAP_FRAME: ffffd0014eba6290 -- (.trap 0xffffd0014eba6290)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffef8094703000 rbx=0000000000000000 rcx=00000000b8e00000
rdx=fffff6e7c04a3818 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8010b702dde rsp=ffffd0014eba6420 rbp=0000007ffffffff8
r8=00000067c04a3818 r9=ffffcf8094652fd0 r10=0000000000000000
r11=fffff6fb73e02518 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
nt!MmBuildMdlForNonPagedPool+0xee:
fffff801`0b702dde 48890c17 mov qword ptr [rdi+rdx],rcx ds:fffff6e7`c04a3818=78010b8e00000000
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8010b7764e9 to fffff8010b76a9a0
STACK_TEXT:
ffffd001`4eba6148 fffff801`0b7764e9 : 00000000`0000000a ffffcf80`94653000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffd001`4eba6150 fffff801`0b774d3a : 00000000`00000001 0000000f`ffffffff ffffd001`4eba4000 ffffd001`4ebaa000 : nt!KiBugCheckDispatch+0x69
ffffd001`4eba6290 fffff801`0b702dde : ffffd001`4eba6c60 ffffcf80`94416ac0 00000000`00000000 fffff800`b6936bc0 : nt!KiPageFault+0x23a
ffffd001`4eba6420 fffff800`b6936bc0 : ffffe001`2e27d580 ffffd001`4eba6600 ffffcf80`8f6bedf0 00000000`00000000 : nt!MmBuildMdlForNonPagedPool+0xee
ffffd001`4eba6440 ffffe001`2e27d580 : ffffd001`4eba6600 ffffcf80`8f6bedf0 00000000`00000000 00000000`00000000 : vsdatant+0x13bc0
ffffd001`4eba6448 ffffd001`4eba6600 : ffffcf80`8f6bedf0 00000000`00000000 00000000`00000000 00000000`00000040 : 0xffffe001`2e27d580
ffffd001`4eba6450 ffffcf80`8f6bedf0 : 00000000`00000000 00000000`00000000 00000000`00000040 ffffe001`2e27d680 : 0xffffd001`4eba6600
ffffd001`4eba6458 00000000`00000000 : 00000000`00000000 00000000`00000040 ffffe001`2e27d680 ffffd001`4eba6600 : 0xffffcf80`8f6bedf0
STACK_COMMAND: kb
FOLLOWUP_IP:
vsdatant+13bc0
fffff800`b6936bc0 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: vsdatant+13bc0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: vsdatant
IMAGE_NAME: vsdatant.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 538e623f
FAILURE_BUCKET_ID: AV_VRF_vsdatant+13bc0
BUCKET_ID: AV_VRF_vsdatant+13bc0
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_vrf_vsdatant+13bc0
FAILURE_ID_HASH: {cd69ac10-8557-151b-0942-e160e96e9310}
Followup: MachineOwner
0: kd> lmvm vsdatant
start end module name
fffff800`b6923000 fffff800`b69b8000 vsdatant T (no symbols)
Loaded symbol image file: vsdatant.sys
Image path: \SystemRoot\System32\drivers\vsdatant.sys
Image name: vsdatant.sys
Timestamp: Tue Jun 03 20:03:11 2014 (538E623F)
CheckSum: 00072B74
ImageSize: 00095000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Wanikiya and Dyami--Team Zigzag

Z87 MPOWER MAX - Killer E2200 BSOD problem on Win 8.1

Hello all!
I have a BSOD problem on win 8.1 with the mentioned motherboard . specifically with the Killer E2200 e22w8x64.sys driver.
No matter where I get the driver for it (MSI installation DVD, killer gaming homepage...) I still have the problem. And it was a bit hard to identify this driver, After 20-30 BSOD-s a day I had to start windows driver verifier to realize wich driver is failing. Is anybody else experiencing this problem? Is there any solution to this, maybe a driver under development?
I couldn't find the option to attach something ( because extarnal links are not allowed apparently (would have been to skydrive) ), I would have attached a miniDump which has the referrence to this driver.
Thank You.
Regards,
Takács Attila

Quote
My question is: can I somehow make it work, can YOU msi developers make it work, or I really need to buy new RAM?
This is a Users-to-Users Forum. For contacting MSI tech: >>How to contact MSI.<<
Be waware that your system is a dual cahnnel one and a three stick (triple channel) setup is not optimal. Also it is meant for old X58 systems and most likely 1.65v. Clear cmos and retry with just two sticks.

I get an error message when trying to install windows 7 on my macbook pro. The message says "windows has encountered a problem communicating with a device connected to your computer. I don't have anything connected to my computer. How do I fix this?

I'm trying to install windows 7 on my macbook pro. I went through the process of bootcamp telling it to install windows 7. Once the windows boot manager started an error message came up. The error message says " windows has encountered a problem communicating with a device connected to your computer. I don't have a usb connected to my computer. I am using windows 7 professional install disc. I can't figure out what i am doing wrong. The same message keeps coming up over and over. Am I doing something wrong or is it something else?

Well, shucks, i just spent almost 30 minutes trying to find your model user guide to explain it better, I guess they never got around to making it.....
I would just borrow another Windows disk and try installing it again and if it does it again then you might take it to an Apple Store and see if one of the "Genius' " can figure it out.
Make sure your internet is enabled and click on your blank desktop and at the top of your screen is a Help menu option, enter PRAM and it should give you a list of things relating to Pram. It may take a few seconds to list anything as it has to connect to Apples severs first. It should list the things you may have to fill back in when your done.
"P-ram" stores some common information that is used in the background, your date, time, startup disk, etc, that you don't have to re-fill when you restart, it's a little different for each computer.

Just purchased and installed photoshop and everytime i try to open it it says "windows has encountered a problem and must close the program" anyone else have this problem?

I have just purchased the photography package on my windows 8 computer and everytime I open photoshop an error message pops up saying that windows has encountered a problem and needs to close the program. I am really frustrated that this is happening after I purchased this plan and would like to be able to use the product I have purchased

+1 to Chris' assessment.
Keep in mind that it's your responsibility to provide a problem-free working environment on your computer for Photoshop, and system software (such as display drivers) can have problems.
Look in your Windows Event Logs (specifically, your Application Log) for the info requested above on the specific crashes.
-Noel

Windows 8.1 BSOD please help Minidump file attached

Windows 8.1 BSOD please help Minidump file and dxdiag info file link is below,
This BSOD frequency is about once every 1 hour to 4 hours,
Memtest passed with one pass on the one chip of 4GB
Brand new 8.1 install
https://drive.google.com/file/d/0B39S6eNyRvOHRnZHRG1Jd1lwT2M/view?usp=sharing
https://docs.google.com/document/d/1XueM-ov7wjfePJh45Pp3fg1QSSzFBqMuO1tfr9GZm8k/edit?usp=sharing

This is a crash related to some type of hardware failure. Please refer to the Wiki link below, for some troubleshooting tips.
BugCheck Code 124 Co-Authored by ZigZag3143& JMH3143
http://answers.microsoft.com/en-us/windows/wiki/windows_other-system/bugcheck-code-124/98c998d2-447a-40ce-ae1f-8211e355f14d
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 9600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
Machine Name:
Kernel base = 0xfffff800`c0e7b000 PsLoadedModuleList = 0xfffff800`c113f990
Debug session time: Tue Mar 3 23:19:34.178 2015 (UTC - 5:00)
System Uptime: 0 days 0:00:04.947
Loading Kernel Symbols
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, ffffe000016f88f8, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
1: kd> !analyze -v
* Bugcheck Analysis *
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe000016f88f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
BUGCHECK_STR: 0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
ffffd000`2087f6c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x81
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Followup: MachineOwner
1: kd> !errrec ffffe000016f88f8
===============================================================================
Common Platform Error Record @ ffffe000016f88f8
Record Id : 01d0563268a81312
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 3/4/2015 4:19:34
Flags : 0x00000002 PreviousError
===============================================================================
Section 0 : Processor Generic
Descriptor @ ffffe000016f8978
Section @ ffffe000016f8a50
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal
Proc. Type : x86/x64
Instr. Set : x64
Error Type : BUS error
Operation : Generic
Flags : 0x00
Level : 3
CPU Version : 0x0000000000100f42
Processor ID : 0x0000000000000000
===============================================================================
Section 1 : x86/x64 Processor Specific
Descriptor @ ffffe000016f89c0
Section @ ffffe000016f8b10
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
Local APIC Id : 0x0000000000000000
CPU Id : 42 0f 10 00 00 08 02 00 - 09 20 80 00 ff fb 8b 17
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
Proc. Info 0 @ ffffe000016f8b10
===============================================================================
Section 2 : x86/x64 MCA
Descriptor @ ffffe000016f8a08
Section @ ffffe000016f8b90
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4)
Status : 0xba00001000020c0f

Trying to connect my replacement Iphone 3GS to my windows 7 laptop but it is not recognised at all, my ipod can connect no problem, my iphone can connect to my windows vista computer no problem. Any ideas?

Trying to connect my replacement Iphone 3GS to my windows 7 laptop but it is not recognised at all, my ipod can connect no problem, my iphone can connect to my windows vista computer no problem. Any ideas?

More info,
I have bootcamp with Windows 7 installed, do I need to run some "Driver compatibility checker" after the Windows 7install?
if so what is the name of it?
thanks

Both xp and windows 7 have video problems with my VGA connection using TV

both xp and windows 7 have video problems with my VGA connection using TV as my monitor when it gets to starting up windows no matter what version it will not I have let my mac on all night and still says starting windows or the windows 7 logo and nothing else will happen also when I use a 3rd patty software like peraills or other it works like a charm how to fix it?

To map the drive on your computer click on Start - RUN - type "\\192.168.1.1" and click ok... When prompted for Username and Password type "admin" and click ok... Now you will be able to see the folder which you have shared on your router, right click on it and select "Map network drive" and click on finish.
Now it will map the drive on your computer and you should be able to transfer the file from your computer to the USB drive.

Itunes keeps closing as soon as i open it and states 'windows has detected a problem' HELP!!!!

Help!! Itunes keeps closing straight away and message states 'windows has detected a problem' HELP ASAP PLEASE!!!!

For general advice see Troubleshooting issues with iTunes for Windows updates.
The steps in the second box are a guide to removing everything related to iTunes and then rebuilding it which is often a good starting point unless the symptoms indicate a more specific approach. Review the other boxes and the list of support documents further down page in case one of them applies.
Your library should be unaffected by these steps but there is backup and recovery advice elsewhere in the user tip.
If you've already tried a complete uninstall and reinstall try opening iTunes in safe mode (hold down CTRL+SHIFT as you start iTunes) then going to Edit > Preferences > Store and turning off Show iTunes in the Cloud purchases. You may find iTunes will now start normally.
tt2

Will Developer 6i run on Windows 7 without any problems?

Will Developer 6i run on Windows 7 without any problems? and developer 6i supports on windows 7 or not.

Hi,
As a matter of fact the Dev 6i tools (form and report builder) is supported and will be supported as they are certified with E-business 11.5.x.x. version....product
Take a look at :
"Which Version Of Dev 6i Tools (Reports & Forms Builder) Is Supported With E-Business Suite 11.5" (Metalink Note:418667.1)
Greetings,
Sim

[IMPORTANT] BSoD Problem (CLOCK_WATCHDOG_TIMEOUT) with Win10

ENGLISH___
Hi. I bought some years ago an HP dv5-1110el with Windows Vista 32-bit.
I updated it first to Win7, than to Win8, without having problems or issues.
Last Saturday I installed Win10 Technical Preview on the PC. Today I tried to update drivers. Then, I updated BIOS. When I was updating BIOS with an HP software (Insyde? I don't remember so good...) a Blue Screen of Death came. The error was CLOCK_WATCHDOG_TIMEOUT.
Here you are an image: http://www.tomshw.it/forum/attachments/windows/134199d1415713193-urgente-problema-clock_watchdog_tim...
The computer didn't shut down, so I removed the battery.
When I restarted it the BIOS didn't start and the monitor remained black.
Now every time I start it, the BIOS and the OS don't start and I can't use the PC.
HOW CAN I RESTORE THE BIOS THO THE PREVIOUS STATE/SETTINGS?
Please, HELP ME!
ITALIAN___
Ciao gente. Qualche anno fa ho acquistato un HP dv5-1110el con Windows Vista 32-bit preinstallato.
L'ho aggiornato prima a Win7 e poi a Win8 senza avere problemi o malfunzionamenti di sorta.
Sabato scorso vi ho installato sopra Win10 Technical Preview. Nono ho avuto alcun problema finchè oggi non ho aggiornato i drivers. dopo, ho provato ad aggiornare il BIOS con un programma fornito dalla HP, che credo si chiamasse Insyde, o qualcosa del genere. Mentre stavo aggiornando il BIOS col software è comparsa la tanto temuta schermata blu di morte con l'errore CLOCK_WATCHDOG_TIMEOUT.
Ecco un'immagine: http://www.tomshw.it/forum/attachments/windows/134199d1415713193-urgente-problema-clock_watchdog_tim...
Il computer non reagiva alla pressione dei tasti, nè si spegneva come promesso invece dalla schermata, così ho rimosso la batteria.
Quando l'ho fatto ripartire, il BIOS semplicemente non si è avviato nonostante le luci e la ventola funzionassero e lo schermo è rimasto nero.
Adesso ogni volta che provo ad accenderlo nè il BIOS nè ovviamente il sistema operativo partono, il pc non reagisce a<lla pressione dei pulsanti e quindi non posso in alcun modo usare il dispositivo.
COME POSSO FARE PER RIPORTARE IL BIOS ALLE IMPOSTAZIONI DI FABBRICA O MEGLIO ANCORA ALLO STATO PRECEDENTE?
Per favore, AIUTATEMI!
This question was solved.
View Solution.

Follow the instructions on the following web document. Start with the Win+B key press combination.
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c02693833&tmp_task=solveCategory&cc=us&dlc=en&lc...
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Cannot email pdf using Acrobat Reader XI v11.0.3 in Windows 8. No problem when using in ms vista. ge

Cannot email pdf using Acrobat Reader XI v11.0.3 in Windows 8. No problem when using in ms vista. get "authentication error". Sometimes will get a very quick dialogue box showing the gmail login screen but then disappears. I use firefox and IE

Hi Rodney
Welcome to Apple Discussions
This sounds like one of those "oddities", contributed to by a few sources.
I can clear the Safari cache files as a temporary solution, but I encounter the same difficulties with the “problematic” files once they have been opened again.
Wondering if you disabled the Safari Cache would the refresh function work correctly? As a test you can disable the Safari Cache by Emptying the Cache first via the Safari menu, then Quit Safari. Now go to the Finder>Your User Library>Caches>Safari. Single click on the Safari folder, then Apple Key + I to open Info panel. There, check the "locked" box. This prevents further additions to the cache. The downside, you lose your ability to upload images etc. within Safari (my cache is disabled, so I use Firefox for the uploads).
Then restart Safari. Try the PDF from within Safari.
Post back

MacBook pro when windows 7 has startup problem and Mac os doesn't work

I installed windows 7 on my MacBook pro and it did work well. But now windows has a startup problem and "startup repair" couldn't solve it, so I can't use both Mac os and windows and my laptop has become completely useless. Any suggestion?

Reboot and hold down command-R at the sound of the chime, that should take you to the Lion recovery partition, if it does go to disk utility and see if you have an OSX partition at all.

Windows 8.1 BSOD problem

Similar Messages

Maybe you are looking for