CSA causing BSOD - btaudio.sys

Hey Guys,
We're trying to build a new SOE, but on a laptop when you turn on/off bluetooth we recieve a Blue screen of death. With CSA uninstalled the error does not occur. With CSA turned off (right clicked on task bar) we still get a BSOD, so that kinda rules out any rules/policies.
Any ideas without upgrading the server to version 5 or 6? I'm not confident with this software to upgrade.
V4.5.1 build v657
Thanks!

btaudio.sys is part of the bluetooth stack for windows, it can be from WIDCOMM or a repackaged version from ibm/ms/dell/hp whatever, i would consider searching for BSOD in regards to the bluetooth driver for that specific platform, otherwise you are looking at a bug, which is not easily solved by changing rules in csa, in 5.x there is a class called "only needing kernel protection", which sometimes can be used, but this sounds like a bad driver, that tries to install itself in the same call tables as csa, and causes a BSOD, so looking into fixing the driver problem, might be simpler and quicker than trying to fix csa.

Similar Messages

T410 NVIDIA BSOD caused by nvlddmkm.sys

Hi all,
I have lot of BSOD (1/week at least) caused by nvlddmkm.sys
I have the latest driver according to lenovo update.
I'm on Win7 x64.
This is not caused by overheating I'm not running any game or 3d application,
GPU idles ~60C.
Could someone help me what to do?
(Some time ago I tried the driver from NVIDIA page, but had the same experience, now I'm back on the Lenovo "official" driver.)

hey nuri,
could you try the following ?
- uninstall the current driver you have installed
- -restart your system and let Win7 install its generic driver
- check if it happens again
WW Social Media
Important Note: If you need help, post your question in the forum, and include your system type, model number and OS. Do not post your serial number.
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
Follow @LenovoForums on Twitter!
Have you checked out the Community Knowledgebase yet?!
How to send a private message? --> Check out this article.

Windows Server 2008 Enterprise SP2 64bit BugCheck 3B Probably caused by : win32k.sys ( win32k!PFFOBJ::pPvtDataMatch+12 )

Hi Guys,
Has anyone come across this BSOD error and found a fix, as I'm at a lost as to what is causing the BSOD
Please see Windows Debugger output below:-
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Transfer\Minidumps\Mini051414-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (8 procs) Free x64
Product: Server, suite: Enterprise TerminalServer
Built by: 6002.23154.amd64fre.vistasp2_ldr.130707-1535
Machine Name:
Kernel base = 0xfffff800`01c18000 PsLoadedModuleList = 0xfffff800`01dd7e30
Debug session time: Wed May 14 12:01:16.178 2014 (UTC + 1:00)
System Uptime: 3 days 7:15:01.532
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                        Bugcheck Analysis
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff9600030271e, fffffa603d967ec0, 0}
Probably caused by : win32k.sys ( win32k!PFFOBJ::pPvtDataMatch+12 )
Followup: MachineOwner
7: kd> !analyze -v
*                        Bugcheck Analysis
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff9600030271e, Address of the instruction which caused the bugcheck
Arg3: fffffa603d967ec0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
win32k!PFFOBJ::pPvtDataMatch+12
fffff960`0030271e f6430804        test    byte ptr [rbx+8],4
CONTEXT: fffffa603d967ec0 -- (.cxr 0xfffffa603d967ec0)
rax=fffff900c277dd10 rbx=6364735523080013 rcx=fffffa603d968790
rdx=fffff900c2cc92a0 rsi=fffff900c2ade350 rdi=fffffa80369f6680
rip=fffff9600030271e rsp=fffffa603d968720 rbp=0000000000000000
r8=0000000000000000 r9=fffffa80369f6680 r10=fffffa803b6cdc48
r11=fffffa603d9687c8 r12=fffffa603d968810 r13=0000000000000000
r14=000000000000301f r15=0000000000000001
iopl=0         nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b             efl=00010202
win32k!PFFOBJ::pPvtDataMatch+0x12:
fffff960`0030271e f6430804        test    byte ptr [rbx+8],4 ds:002b:63647355`2308001b=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT_SERVER
BUGCHECK_STR: 0x3B
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff960003009b1 to fffff9600030271e
STACK_TEXT:
fffffa60`3d968720 fffff960`003009b1 : 00000000`0000301f 00000000`00004fbc 00000000`00000000 fffffa80`3b6cdbb0 : win32k!PFFOBJ::pPvtDataMatch+0x12
fffffa60`3d968750 fffff960`001aacb6 : fffff900`c2ade350 fffff900`c3fa59e0 00000000`00000000 fffffa80`369f6680 : win32k!PFTOBJ::bUnloadWorkhorse+0x55
fffffa60`3d9687d0 fffff960`001ab8d8 : fffff900`c2ade2d0 00000000`00000000 00000000`00000001 00000000`00000001 : win32k!vCleanupPrivateFonts+0x72
fffffa60`3d968810 fffff960`0019fbc0 : 00000000`00000000 fffff800`01ebfe00 fffff900`c277dd10 fffffa80`38d5b800 : win32k!NtGdiCloseProcess+0x4a8
fffffa60`3d968870 fffff960`0019f423 : 00000000`00000000 fffff900`c277dd10 00000000`00000000 fffff800`01ebfe48 : win32k!GdiProcessCallout+0x1f4
fffffa60`3d9688f0 fffff800`01ecc924 : 00000000`00000000 00000000`00000000 fffff800`01db6ec0 00000000`00000000 : win32k!W32pProcessCallout+0x6f
fffffa60`3d968920 fffff800`01ebfe65 : fffffa60`00000000 fffff800`01c89701 fffffa80`57c73810 00000000`78457350 : nt!PspExitThread+0x41c
fffffa60`3d968a10 fffff800`01c89881 : fffffa60`3d968ad8 00000000`00000000 fffffa80`382fe430 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffffa60`3d968a40 fffff800`01c8d935 : fffffa60`3d968ca0 fffffa60`3d968ae0 fffff800`01ebfe74 00000000`00000001 : nt!KiDeliverApc+0x441
fffffa60`3d968ae0 fffff800`01c6721d : fffffa80`3b6cdbb0 00000000`0038f2f4 fffffa60`3d968bf8 fffffa80`597301e0 : nt!KiInitiateUserApc+0x75
fffffa60`3d968c20 00000000`74c93d09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0xa2
00000000`000eebd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74c93d09
FOLLOWUP_IP:
win32k!PFFOBJ::pPvtDataMatch+12
fffff960`0030271e f6430804        test    byte ptr [rbx+8],4
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!PFFOBJ::pPvtDataMatch+12
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52f4cf4d
STACK_COMMAND: .cxr 0xfffffa603d967ec0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_win32k!PFFOBJ::pPvtDataMatch+12
BUCKET_ID: X64_0x3B_win32k!PFFOBJ::pPvtDataMatch+12
Followup: MachineOwner
7: kd> lmvm win32k
start             end                 module name
fffff960`000e0000 fffff960`0039a000   win32k     (pdb symbols)          c:\symbols\win32k.pdb\E3E9D4C3813E470A90F52FAEC6461A252\win32k.pdb
    Loaded symbol image file: win32k.sys
    Mapped memory image file: c:\symbols\win32k.sys\52F4CF4D2ba000\win32k.sys
    Image path: win32k.sys
    Image name: win32k.sys
    Timestamp:        Fri Feb 07 12:19:25 2014 (52F4CF4D)
    CheckSum:         002AD344
    ImageSize:        002BA000
    File version:     6.0.6002.23325
    Product version: 6.0.6002.23325
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     win32k.sys
    OriginalFilename: win32k.sys
    ProductVersion:   6.0.6002.23325
    FileVersion:      6.0.6002.23325 (vistasp2_ldr.140207-0038)
    FileDescription: Multi-User Win32 Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
7: kd> .cxr 0xfffffa603d967ec0
rax=fffff900c277dd10 rbx=6364735523080013 rcx=fffffa603d968790
rdx=fffff900c2cc92a0 rsi=fffff900c2ade350 rdi=fffffa80369f6680
rip=fffff9600030271e rsp=fffffa603d968720 rbp=0000000000000000
r8=0000000000000000 r9=fffffa80369f6680 r10=fffffa803b6cdc48
r11=fffffa603d9687c8 r12=fffffa603d968810 r13=0000000000000000
r14=000000000000301f r15=0000000000000001
iopl=0         nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b             efl=00010202
win32k!PFFOBJ::pPvtDataMatch+0x12:
fffff960`0030271e f6430804        test    byte ptr [rbx+8],4 ds:002b:63647355`2308001b=??
Thanks
JT

Getting BSOD's pointing to this dll also. Started at around the same date as Jitinder's post. Maybe a new issue introduced has been introduced?
7: kd> !analyze -v
* Bugcheck Analysis *
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff9600011fda0, Address of the instruction which caused the bugcheck
Arg3: fffffa6027acd1d0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
"kernel32.dll" was not found in the image list.
Debugger will attempt to load "kernel32.dll" at given base 00000000`00000000.
Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to add module at 00000000`00000000
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
win32k!PFEOBJ::vFreepfdg+e8
fffff960`0011fda0 0fba60300f bt dword ptr [rax+30h],0Fh
CONTEXT: fffffa6027acd1d0 -- (.cxr 0xfffffa6027acd1d0)
rax=00000000014c0000 rbx=0000000000000000 rcx=fffff900c009c2a0
rdx=fffffa802735ab80 rsi=fffff900c0b9b010 rdi=fffffa6027acda80
rip=fffff9600011fda0 rsp=fffffa6027acda30 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=fffffa802800a288
r11=fffffa802800a060 r12=0000000000000000 r13=0000000000000000
r14=000000001539ed50 r15=0000000000000001
iopl=0 nv up ei pl nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010207
win32k!PFEOBJ::vFreepfdg+0xe8:
fffff960`0011fda0 0fba60300f bt dword ptr [rax+30h],0Fh ds:002b:00000000`014c0030=????????
Resetting default scope
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: iexplore.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff960002e66d4 to fffff9600011fda0
STACK_TEXT:
fffffa60`27acda30 fffff960`002e66d4 : 00000000`00000000 fffffa80`2735ab50 00000000`00000001 00000000`746e6647 : win32k!PFEOBJ::vFreepfdg+0xe8
fffffa60`27acda60 fffff960`002f0cb7 : 00000000`00000000 fffff900`c008f000 fffff900`c0010000 00000000`00000000 : win32k!RFONTOBJ::vDeleteRFONT+0x210
fffffa60`27acdac0 fffff960`002f0926 : 00000000`00000000 fffff900`c2bfcca0 fffff900`c0ae4010 00000000`00000000 : win32k!vRestartKillRFONTList+0xab
fffffa60`27acdb10 fffff960`00275c79 : 00000000`00000000 00000000`00000001 fffffa80`235762b0 fffff900`00000002 : win32k!PFTOBJ::bUnloadWorkhorse+0x196
fffffa60`27acdb90 fffff960`002978e2 : fffffa80`2800a060 fffff900`c0b932a0 fffffa60`27acdca0 00000000`7457c444 : win32k!GreRemoveFontMemResourceEx+0xad
fffffa60`27acdbf0 fffff800`01a64173 : fffffa80`2800a060 fffffa60`27acdca0 00000000`7ee9f000 fffffa80`25803040 : win32k!NtGdiRemoveFontMemResourceEx+0x12
fffffa60`27acdc20 00000000`74513d09 : 00000000`74513cc5 00000023`77300682 00000000`00000023 00000000`00000202 : nt!KiSystemServiceCopyEnd+0x13
00000000`1539ed48 00000000`74513cc5 : 00000023`77300682 00000000`00000023 00000000`00000202 00000000`1767d5e0 : wow64cpu!CpupSyscallStub+0x9
00000000`1539ed50 00000000`7457ab36 : 00000000`77120000 00000000`1539fd20 00000000`60c8f022 00000000`1539f450 : wow64cpu!Thunk0Arg+0x5
00000000`1539edc0 00000000`7457a13a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : wow64!RunCpuSimulation+0xa
00000000`1539edf0 00000000`771847c8 : 00000000`00000000 00000000`00000000 00000000`7efdf000 00000000`00000000 : wow64!Wow64LdrpInitialize+0x4b6
00000000`1539f350 00000000`771461be : 00000000`1539f450 00000000`00000000 00000000`7efdf000 00000000`00000000 : ntdll! ?? ::FNODOBFM::`string'+0x1fba1
00000000`1539f400 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe
FOLLOWUP_IP:
win32k!PFEOBJ::vFreepfdg+e8
fffff960`0011fda0 0fba60300f bt dword ptr [rax+30h],0Fh
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!PFEOBJ::vFreepfdg+e8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5202fc4d
STACK_COMMAND: .cxr 0xfffffa6027acd1d0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_win32k!PFEOBJ::vFreepfdg+e8
BUCKET_ID: X64_0x3B_win32k!PFEOBJ::vFreepfdg+e8
Followup: MachineOwner
7: kd> lmv m win32k
start end module name
fffff960`000d0000 fffff960`00389000 win32k (pdb symbols) c:\symcache\win32k.pdb\54B8C53009264F08A9D8CF1B4B56BCDC2\win32k.pdb
Loaded symbol image file: win32k.sys
Image path: \SystemRoot\System32\win32k.sys
Image name: win32k.sys
Timestamp: Thu Aug 08 04:02:53 2013 (5202FC4D)
CheckSum: 002B126B
ImageSize: 002B9000
File version: 6.0.6002.18912
Product version: 6.0.6002.18912
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: win32k.sys
OriginalFilename: win32k.sys
ProductVersion: 6.0.6002.18912
FileVersion: 6.0.6002.18912 (vistasp2_gdr.130807-1537)
FileDescription: Multi-User Win32 Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
7: kd> .cxr 0xfffffa6027acd1d0
rax=00000000014c0000 rbx=0000000000000000 rcx=fffff900c009c2a0
rdx=fffffa802735ab80 rsi=fffff900c0b9b010 rdi=fffffa6027acda80
rip=fffff9600011fda0 rsp=fffffa6027acda30 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=fffffa802800a288
r11=fffffa802800a060 r12=0000000000000000 r13=0000000000000000
r14=000000001539ed50 r15=0000000000000001
iopl=0 nv up ei pl nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010207
win32k!PFEOBJ::vFreepfdg+0xe8:
fffff960`0011fda0 0fba60300f bt dword ptr [rax+30h],0Fh ds:002b:00000000`014c0030=????????

2008R2 server crash caused by srv2.sys, MS Netherlands SA support tells me to ..

Last night 1 of our 2008r2 sp1 Enterprise crashed and auto rebooted. With the debugger tool I checked the minidump and at the bottom it states:
Probably caused by : srv2.sys ( srv2+212e )
This is the SMB driver. There is a KB that acknowledges that there is a bug in this driver and a hot fix is available. However.. the date of the driver in the hotfix is older than the date of the driver in use by the server. Get my point? Should I install
the "older" hotfix or not.
This is the KB: http://support.microsoft.com/kb/2394911
I contacted MS SA support in the Netherlands and the literally stated that the server is now up and running so there is no problem hence they can not support this. Ridiculous. I told him that we have a server running that we can't rely on. They did not care..
I asked they guy to ask his manager and they just refuse to support me. Instead they sad I should contact a MS Partner because the question was about "implementation ".
Can you imagine that I not impressed at all by this...

Hello,
So it is a BSOD.
Please start by that:
Update all possible drivers
Uninstall all unused programs
Run chkdsk /r /f and sfc /scannow
Perform a clean boot: http://support.microsoft.com/kb/929135
Disable temporary all security softwares you have
Run memtest86+ to check your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support for assistance
Once done, check results. If this does not help then use Microsoft Skydrive to upload dump files. Once done, post a link here.
You can also contact Microsoft CSS for assistance.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner 2010 / 2011
Microsoft
Certified Professional
Microsoft
Certified Systems Administrator: Security
Microsoft
Certified Systems Engineer: Security
Microsoft
Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows 7, Configuring
Microsoft
Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
Microsoft Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer

Probably caused by : atikmdag.sys ( atikmdag+127f8 )

I just purchased a new HP ProLiant MicroServer G7 N54L
Here is a short history:
I replaced the 4GB ECC memory to 8GN non-ECC
I originally used a 25ft VGA cable on the on-board VGA port, but had a blue tinge, couldn't recognize the monitor properly, and a bluescreen shutdown, so I removed it.
There is nothing connected to the VGA port now
I now connect using RDP only
The computer freezes randomly and seems to happen when I launch the chrome browser (through RDP)
The dump files are at: https://onedrive.live.com/redir?resid=A19E045098FB769C!1399&authkey=!APLz-efriDf5wAs&ithint=file%2czip
According to my limited knowledge, it seems that the dump files indicate a video problem, but I am not completely sure. Can this be a problem with the motherboard?
Any help is greatly appreciated.

GG
These were related to your 5 year old video driver and may simply need a driver update. It is called a BCC116 and is either the driver or perhaps heat. I would start by removing the current driver and installing the newest driver available.
"It's not a true crash, in the sense that the Blue Screen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".
Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OS's like XP to crash.
As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.
If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.
If playing with video driver versions hasn't helped, make sure the box is not overheating.
Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.
Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.
If so, it might be as simple as dust buildup and subsequently inadequate cooling.
I would download cpu-z and gpu-z (both free) and keep an eye on the video temps
For more information please read this blog http://captaindbg.com/bug-check-0x116-video_tdr_error-troubleshooting-tips/
http://msdn.microsoft.com/en-us/library/windows/hardware/ff557263%28v=vs.85%29.aspx
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\082614-25833-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0280a000 PsLoadedModuleList = 0xfffff800`02a4d890
Debug session time: Tue Aug 26 23:27:25.092 2014 (UTC - 4:00)
System Uptime: 8 days 2:58:31.684
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80093cd4e0, fffff88004cc57f8, 0, 2}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+127f8 )
Followup: MachineOwner
0: kd> !analyze -v
* Bugcheck Analysis *
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80093cd4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004cc57f8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
Debugging Details:
FAULTING_IP:
atikmdag+127f8
fffff880`04cc57f8 48895c2408 mov qword ptr [rsp+8],rbx
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
STACK_TEXT:
fffff880`05a5f9c8 fffff880`05327134 : 00000000`00000116 fffffa80`093cd4e0 fffff880`04cc57f8 00000000`00000000 : nt!KeBugCheckEx
fffff880`05a5f9d0 fffff880`05326e3e : fffff880`04cc57f8 fffffa80`093cd4e0 fffffa80`0841cc00 fffffa80`085ce010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05a5fa10 fffff880`04c0ff13 : fffffa80`093cd4e0 00000000`00000000 fffffa80`0841cc00 fffffa80`085ce010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`05a5fa40 fffff880`04c39cf1 : 00000000`ffffffff 00000000`02ae8b02 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05a5fb20 fffff880`04c38437 : 00000000`00000102 00000000`00000000 00000000`02ae8b02 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`05a5fb50 fffff880`04c0b2d2 : ffffffff`ff676980 fffffa80`085ce010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`05a5fbf0 fffff880`04c37ff6 : 00000000`00000000 fffffa80`08641830 00000000`00000080 fffffa80`085ce010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`05a5fd00 fffff800`02b1b73a : 00000000`fffffc32 fffffa80`085cf610 fffffa80`06702040 fffffa80`085cf610 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`05a5fd40 fffff800`028708e6 : fffff800`029fae80 fffffa80`085cf610 fffff800`02a08cc0 fffff880`031b5801 : nt!PspSystemThreadStartup+0x5a
fffff880`05a5fd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmdag+127f8
fffff880`04cc57f8 48895c2408 mov qword ptr [rsp+8],rbx
SYMBOL_NAME: atikmdag+127f8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a8a1a8b
FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmdag.sys
BUCKET_ID: X64_0x116_IMAGE_atikmdag.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x116_image_atikmdag.sys
FAILURE_ID_HASH: {7527b2fa-489f-c504-9452-1a10bd154401}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag

Reader 9 causes BSOD on Windows XP Pro

We have a few systems here that are having real problems with Adobe Reader 9. When the users attempt to open a .pdf file, they get a BSOD, and the system reboots. Once the system comes back up, they are able to open the offending file with no problems.
Here are details of our systems:
Dell Optiplex 755
Windows XP Pro SP3
2GB Ram
32 Bit OS
I have found this occurs most often when opening pdf's that were created with earlier versions.
I'm sure I have left out some vital piece of information, so if you need clarification on something, please ask. Any suggestions would be greatly appreciated!

[While the original post was for Reader 9, I found this same problem with Acrobat 9 Pro, and found a solution.]
Problem: Opening one PDF file is fine, but once you open the second file -- BSOD.
Cause: There is still a problem with Adobe's 2D GPU Acceleration feature.
Per http://kb.adobe.com/selfservice/viewContent.do?externalId=kb405218&sliceId=1, "If acceleration hardware is detected, then optimization is enabled for all files except the first one opened when Acrobat launches." That is why the first file opens OK, but the second causes BSOD. Adobe is either not detecting acceleration hardware correctly, or is not calling it correctly.
Temporary Solution:
1. In Acrobat or Adobe Reader, choose to Edit > Preferences.
2. Go to the Page Display panel.
3. Uncheck Use 2D GPU acceleration.
I tested my machine [Dell Optiplex 755, ATI Radion HD 2400 XT 8.420.0.0, Win XP Pro, Adobe 9 Pro] with "2D GPU acceleration" checked, attempted open of 4 PDFs from File Explorer -->first one opened, then BSOD, rebooted, unchecked "2D GPU", attempted the exact same operation --> all four opened in their windows and now I am happily typing on this page.
This is per http://kb.adobe.com/selfservice/viewContent.do?externalId=324073, which is a post from two years ago and relates to Adobe 8. So, Dell has been fielding calls on this for at least two years. Way to stick in there, Dell. Two years ago, Adobe knew the problem ("You are using an desktop ATI video card with driver version 8.291 or 8.301 and have the Acrobat Page Display Preference 'Use 2D GPU acceleration' enabled." was what they said back then, and recommended updating the video drivers. So, Dell stays with it, Adobe says to update your drivers. Well, I bought an entirely new Dell to get the latest drivers and it didn't help.
Permanent solution:
Adobe needs to get 2D GPU acceleration to really work (how about a line of code where you check whether it is going to work before you execute it?) or ship their product with that feature off by default.

0x7_8 stop error caused by NTFS.SYS , please help with dump file analysis

My 2003 server rebooted unexpected twice today and yesterday.
I've run Windbg to analysis the dump file, but i really don't know what to do next to resolve my problem.
Can any one give some suggestion? thanks in advance.
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: csrss.exe
FAILURE_BUCKET_ID: 0x7f_8_Ntfs+5f74
BUCKET_ID: 0x7f_8_Ntfs+5f74
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\temp\ads02 memory dump 20140218\MEMORY_20140217.DMP]
Kernel Summary Dump File: Only kernel address space is available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols.sympath
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: LanManNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_qfe.130703-1535
Machine Name:
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a8ee8
Debug session time: Mon Feb 17 08:37:34.653 2014 (UTC + 8:00)
System Uptime: 1 days 2:57:43.093
WARNING: Process directory table base BFF9C6C0 doesn't match CR3 005F2000
WARNING: Unable to reset page directories
Loading Kernel Symbols
Loading User Symbols
WARNING: Process directory table base BFF9C6C0 doesn't match CR3 005F2000
Unable to get PEB pointer
Loading unloaded module list
*                        Bugcheck Analysis
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80042000, 0, 0}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Unable to read selector for PCR for processor 1
Unable to read selector for PCR for processor 2
Unable to read selector for PCR for processor 3
Unable to read selector for PCR for processor 1
Unable to read selector for PCR for processor 2
Unable to read selector for PCR for processor 3
Probably caused by : Ntfs.sys ( Ntfs+5f74 )
Followup: MachineOwner
0: kd> !analyze -v
*                        Bugcheck Analysis
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
Unable to read selector for PCR for processor 1
Unable to read selector for PCR for processor 2
Unable to read selector for PCR for processor 3
Unable to read selector for PCR for processor 1
Unable to read selector for PCR for processor 2
Unable to read selector for PCR for processor 3
BUGCHECK_STR: 0x7f_8
TSS: 00000028 -- (.tss 0x28)
eax=00000000 ebx=8b4f1100 ecx=8ac87d03 edx=8687ddc0 esi=b83481a0 edi=b8348028
eip=f7addf74 esp=b8348000 ebp=b8348014 iopl=0         nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000             efl=00010202
Ntfs+0x5f74:
f7addf74 0000            add     byte ptr [eax],al          ds:0023:00000000=??
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 1
LAST_CONTROL_TRANSFER: from 00000000 to f7addf74
STACK_TEXT:
b8348014 00000000 00000000 00000000 00000000 Ntfs+0x5f74
STACK_COMMAND: .tss 0x28 ; kb
FOLLOWUP_IP:
Ntfs+5f74
f7addf74 0000            add     byte ptr [eax],al
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: Ntfs+5f74
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x7f_8_Ntfs+5f74
BUCKET_ID: 0x7f_8_Ntfs+5f74
Followup: MachineOwner

According to your post bug check 0x7F is recorded. Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails.
I suggest you check below link and troubleshoot it accordingly.
Bug Check 0x7F
Regards, Ravikumar P

Drivers cause BSOD {URGENT}

Good day
About 2 years ago I bought this laptop for a really good deal and i was impressed with the performance i got with it. Its quite a powerful and quality piece of tech.
There are some drawbacks...
In the two years ive had it ive formatted the laptop twice. Once to upgrade to windows 8.1, and now because windows got corrupted and it didnt want to use a restore point. Which is normal for windows, it doesnt last forever.
Drivers are a mess. Most i can gather is i'm suppose to download my laptop's drivers from here.
http://support.hp.com/us-en/drivers/selfservice/HP-Pavilion-dv6-Entertainment-Notebook-PC-series/522...
There are 3 different wireless lan drivers, the chipset drivers cause BSOD's, i can install every single driver on the list and i still have about 4 unknown devices in my device manager.
Point is Im better off googling for the hardware ID's and scrubbing forums for my drivers.
Please could Someone supply me a link where i can download a complete Driver DVD image for my laptop model that works. I am more than willing to download a 1.4 gig torrent if it has proper work everytime drivers.
Infact i would even drive to hp head office if they could supply me with a hardcopy.
Help Please!
Before i break something.
Back on windows 7 btw

Hi @Pixelite ,
Thank you for visiting the HP Support Forums and Welcome. I have looked into your issue about your HP Pavilion dv6-7030ei Notebook and needing a recovery disk. Here is a link to show you how to and or order the Recovery Media you need.
FWI: The driver page shows all drivers that were installed on all HP Pavilion Notebooks.
I would uninstall all the drivers with a yellow mark or caution on it. Restart the Notebook and if they are still there right click on the device and install or update the drivers.
I hope this helps you out.
Thanks.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

Stop 0x0000001e (0xffffffffc0000005, 0xfffff8800a07d7f0 - Windows Server 2008r2 SP1 patch level March 2014 - WinDbg probably caused by mrxsmb10.sys

we run several Windows Server 2008r2 SP1 Enterprise as VM on two Stratus Avance xenserver based VM hosts. On both hosts we run a VM as file-server, RDS server including a little bit of DFS traffic. the underling physical machines are Intel based S5520UR
with plenty full of needed resources, running since 2012 more or less without problems.
Recently we on both physical hosts the STOP error 0x0000001e (0xffffffffc0000005, 0xfffff8800a07d7f0, 0x0000000000000000, 0x0000000000000000).
This has happended now twice and we have no clue or idea why the Stop error arrives now were the VM is running for month without such an error.
We have tried to analyze the problem with WnDbg and the result reported: Probably caused by : mrxsmb10.sys ( mrxsmb10!MRxSmbDeferredCreate+18a )
We have searched for a solution and have identified some hotfixes which could be related to our problem
Hotfix http://support.microsoft.com/kb/2521220/en-us
and / or
Hotfix http://support.microsoft.com/kb/2764302/en-us
The latter one matches the typical use of the VMs in question, file-server function and a flat file based database system with corresponding file I/O. (However, no dramatic system load and approx. 20 concurrent users on the system.)
The file NTFS.sys in the folder System32 are with a newer date and version as the version from the hotfix and we are not sure if this would be a good idea to replace it with the hotfix version.
As we are a small cap company we could not test the outcome of such a change of essential OS files and we tend to stay away from this approach. On the other hand we have a high pressure to solve this issue as we have to rely on the function of this core
system.
WinDbg points us towards mrxsmb10.sys as a possible root cause, but my believe is limited and we have not the knowledge to understand the output of the memory dump file. (mrxsmb was over the last 15 years always a difficult “thing”!)
Would someone so kind to point us to some useful steps or direct us to any helpful advise?
Thank you!

1. Share your minidump file - someone may see content and help.
2. Consider this
http://support.microsoft.com/kb/2521220
3. Error description
http://msdn.microsoft.com/en-us/library/windows/hardware/ff557408(v=vs.85).aspx
Regards
Milos

BSOD caused by e22win7x64.sys

Hey all,
recently I have some issues related with e22win7x64.sys. I believe this BSOD is caused by Killer network manager.
I have checked all possible solutions like uninstall Killer network, and only install the drivers.
Unfortunately, it doesn't help me much. I still have BSOD problems.
Does anyone know if there exist another network adapter that can replace Killer network?
My motherboard is X99S Gaming 9 ACK
Memorary: G.SKILL Ripjaws 4 series 32GB (4 x 8GB) 288-Pin DDR4 SDRAM DDR4 2666
GPU: MSI GTX 980 GAMING 4G GeForce GTX 980 4GB
CPU: I7-5960X

which killed driver version you are using?

Audigy SE causes BSOD on my sys

My system is as such:
Motherboard - Abit IP35 Pro
CPU - Intel Core 2 Quad Q6600 2.4GHz
Ram - 8GB Corsair TWIN2X4096-6400C5
Video Card - Nvidia 8800GTS
Disk dri've - Asus Sata DVD/CD combo
Hard dri've configuration:
80GB OS Dri've
300GB storage
200GB "Programs"
60GB Raid 0 array (two 80GB)
TB Backup dri've "The Repository"
Sound card: Audigy SE
OS: Windows Vista Ultimate x64
Drivers for all hardware: Current as of 3 days ago.
This setup works perfectly without the sound card, which I added 2 days ago. When the sound card is installed, the card itself works fine. But eventually if I use the internet my onboard NIC starts giving me IRQL Not Equal or Less or something like that BSOD's, and it names a driver file used by the NIC!
I checked the IRQs, and at first they were the same, both 22 or something like that right
So I moved the card down a PCI Slot, to the lowest slot, and its IRQ changed to 23. But the problem persists.
How do I fix this crap I'm a big MMO player and it seems to happen whenever I have any network activity and sound going at the same time...you know, with Vent or Teamspeak and a MMO running at once.
Am thinking about getting an actual Network card. Would that fix it's
I saw earlier some pack or other with some application in it to control speakers. I'm just using the card with pure drivers so I don't have to use onboard audio, it crackles and pops when my PC is on. It gets worse when I turn on a game, and, with my latest terabyte HDD added, the static actually spins up when the dri've spins up lol. All I have is a headset and microphone..

Ok then try disabling graphics hardware acceleration. Since this feature was added to Firefox, it has gradually improved, but there still are a few glitches as you have already seen.
You might need to restart Firefox in order for this to take effect, so save all work first (e.g., mail you are composing, online documents you're editing, etc.).
Then perform these steps:
*Click the orange Firefox button at the top left, then select the "Options" button, or, if there is no Firefox button at the top, go to Tools > Options.
*In the Firefox options window click the ''Advanced'' tab, then select "General".
*In the settings list, you should find the ''Use hardware acceleration when available'' checkbox. Uncheck this checkbox.
*Now, restart Firefox and see if the problems persist.
Additionally, please check for updates for your graphics driver by following the steps mentioned in the following Knowledge base articles:
* [[Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems]]
* [[Upgrade your graphics drivers to use hardware acceleration and WebGL]]
Did this fix your problems? Please report back to us!
Thank you.

MOVED: BSOD caused by nvlddmkm.sys in Vista Ultimate x64

This topic has been moved to Vista problems.
https://forum-en.msi.com/index.php?topic=121723.0

hey nuri,
could you try the following ?
- uninstall the current driver you have installed
- -restart your system and let Win7 install its generic driver
- check if it happens again
WW Social Media
Important Note: If you need help, post your question in the forum, and include your system type, model number and OS. Do not post your serial number.
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
Follow @LenovoForums on Twitter!
Have you checked out the Community Knowledgebase yet?!
How to send a private message? --> Check out this article.

JDK 7u2 download causes BSOD

A funny anomaly for those who use JDK on Windows 7, just for your info.
On Windows 7 Professional ver.6.1 (Build 7601: Service Pack 1) that has Adobe Reader 9 Automatic Updater enabled, an attempt to download jdk-7u2-windows-i586.exe resulted in Blue Screen of Death every time when the Adobe Updater has "Click here for Updating for the newest version of Adobe Reader" displayed (as a sign of a completed automatic installer download, and the message ignored by the user).
The BSOD occurred at the last part of the download, occurred every time without failure, until I finally gave up enjoying the good old Blue Screen and installed the latest Adobe Reader 9(version 9.4.7) before downloading the JDK 7u2 installer. After this Adobe install, the download and the installation of the SE JDK went smoothly without a hitch.

Thanks for the comment. It prompted me to describe the BSOD in more detail.
Out of the 11 times I experienced these BSOD's while downloading 7u2, I got several different bug check strings:
MEMORY_MANAGEMENT 4 times, Points to ntkrnlpa.exe
IRQL_NOT_LESS_OR_EQUAL 3 times, Points to fltmgr.sys, MpFilter.sys, ntkrnlpa.exe (once)
Points to halmacpi.dll, ntkrnlpa.exe (twice)
BAD_POOL_HEADER Twice, Points to fltmgr.sys, halmacpi.dll, ntkrnlpa.exe
KERNEL_MODE_EXCEPTION_NOT_HANDLED Once, Points to ntkrnlpa.exe
PFN_LIST_CORRUPT Once, Points to ntkrnlpa.exe
Interesting, isn't it? It seems Windows is not quite sure what to blame the blue screen for. While I am quite aware of app developers' tendency to blame device drivers, driver coders blaming BIOS, BIOS coders pointing to hardware for the "cause" of a problem, I am not interested in semantics on the difference between causing and triggering. It is certainly true that many BSOD has their roots in device driver and BIOS bugs, but I am not so sure if this is the case here. As I don't have the time to look into the way Adobe lets its updater to make downloaded file status to survive a reboot, how Oracle installer performs CRC and other operations, and how Windows system files and config protection schemes interact with them, I chose to be a news reporter.

Creative webcam Pro eX BSOD [usbuhci.sys] irql_driver_not_less_or_equal *helpp*

HP Pavilion ZE 5500
Windows XP Professional + SP2
Creative webcam Pro eX [driver version .02.0] (29 Jan 03)
So now i've been using this webcam for about 7 months with much pleasure as I can speak to my family in other countries and are able to see them and they see me while talking on skype and msn.
Sometimes my laptop just crashed with a BSOD (blue screen of death) and parse an error message about some problem with usbuhci.sys and then simply reboot the whole system.
The Creative webcam Pro eX produces this error when I am broadcasting for about 5-45 minutes on msn and occurs also with other video messaging systems and while recording or broadcasting li've streaming video-messages too.
It seems that for whatever reason the driver of the webcam is having trouble with usbuhci (as the cam is connected to an usb 2.0 port on the laptop) and after 30 till about hour the laptop crashes with this nasty BSOD and after the system was rebooted and the cam put back online again the same thing happens again but in shorter time frame somewhere between 5 to 5 minutes.
I have all the latest updates for hardware and software on my laptop, this includes the driver update for creative webcam Pro eX but this doesn;t solve the problem, furthermore XP says the drivers arren;t signed and could lead to instable system sorta like i'm experiencing right now perhaps..
Could someone please help me out here, it would be crazy if this could not be solved and me having to buy yet another webcam and so on every 7 months because of some driver incompatibility stuff :-s
Thanks,
Spablauw
Message Edited by spablauw on 03-31-2005 01:46 AM

never mind i've sold my creative webcam pro ex to another idiot and going to buy a new one today, i looked at mediamarkt and saw some other creative (pro) webcams sold at almost the same price as my previous Creative Pro eX, however knowing how Creative thinks about updating drivers and misleading people saying the product is working with Windows XP when it does not, i will never ever in my entire life buy a product from Creative anymore..
think it's kinda stupid to say "hey my software is compatible with XP" when it's not and when it hassen't been updated for quite some time, do you live in 2005. you know XP has updated to SP2? right...
this expensive webcam has worked 7 months for me and now? it just keeps crashing my laptop saturating my USB, conflicting with [usbuhci] and then give a moran BSOD which i haven;t seen since windows ME :-s
the latest drivers for this webcam arren't signed and they do not work with Windows XP Professional SP2 so anyone who's planning to buy this webcam today, please buy it somewhere that has a return policy because this webcam was the best but now has become cripple.
one thing more, if you people at Creative are to busy with making money with products and don;t have time to develop working drivers then maybe consider giving out the source code so that serious developers are able to create working drivers for people that don't want to buy you're webcam every 7 months not because the webcam is broken, but because you where too lazy and money hungry just want to push people into buying yet another one of these webcams.
oh well not my problem anymore you will see someday the consumer strikes back and then you will be left with a magazine full of hardware nobody wants to buy cause the compagny doesn't provide updates on their own drivers and software..
--i'm out of this mess--
Message Edited by spablauw on 04-01-2005 03:36 PM

Usb 6501 unresponsive causing BSOD(Blue Screen Error)

There are a lot posts about the same issue but mine is a little peculiar so i decided to post it.
I am using two usb DAQ in the same pc(usb-6501, usb-6001), connected to the usb port on the back. The usb-6501 is used to obtain digital inputs from read switches, Sensors through an ssr. The usb-6001 is used to control 2 double valve solenoid, 1 dc motor, 2 indicator lamps. usb-6001 is also used to read analog values of current(using hall effect sensor) and voltage(using potentiometer).
At first i was facing problems with the usb-6001(the usb-6501 was working fine at this point) resetting during operation accompanied by BSOD. Then i learned it was due to my relay, which requires 30 mA of current to switch so i used the ULN2003a to interface the usb-6001 with the relays and after that the application was running perfectly for 4 days.
Now the usb-6501 is having the same problem and when i perform "Self Test" from NI MAX it shows "Error Code:50405" and i am able to reset the device from NI MAX only sometimes, other times i would have to unplug the USB device then plug it back in. As the application is used for an automated test rig the customer is frustrated by this problem. Once the card becomes unresponsive(or after the card is reset) BSOD occours.
I have checked all the device drivers and OS for any errors but they are fine. i have even tried changing the ram to solve the BSOD with no use.
System Details:
Windows 7 SP1
NI MAX 14.0
power saving is disabled
I have attached the latest mini dump files as they might help in finding out the reason behind this problem(File extensions changed for the purpouse of uploading).
I need to know: Is there any permanent solution for this problem? and what is the reason for this problem.
Attachments:
060115-12480-01.txt ‏315 KB
053015-12324-01.txt ‏315 KB
052615-17440-01.txt ‏315 KB

Additional info : i did an analysis of the dump files and this is the result
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: fffff88009fe10b1, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800657922e, address which referenced memory
Debugging Details:
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c30e8
fffff88009fe10b1
CURRENT_IRQL: 2
FAULTING_IP:
nifslk+822e
fffff880`0657922e 0fb650ff movzx edx,byte ptr [rax-1]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff80000b9c6b0 -- (.trap 0xfffff80000b9c6b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88009fe10b2 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff80000b9c8e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800657922e rsp=fffff80000b9c840 rbp=fffff88009fe10b1
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nifslk+0x822e:
fffff880`0657922e 0fb650ff movzx edx,byte ptr [rax-1] ds:c8e0:fffff880`09fe10b1=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003091be9 to fffff80003092640
STACK_TEXT:
fffff800`00b9c568 fffff800`03091be9 : 00000000`0000000a fffff880`09fe10b1 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c570 fffff800`03090860 : fffffa80`06adc250 fffffa80`05c3a060 fffffa80`06adc250 00000000`0000ffff : nt!KiBugCheckDispatch+0x69
fffff800`00b9c6b0 fffff880`0657922e : fffff880`05d47468 fffff880`01d91f90 00000000`00000000 fffff880`09fe0770 : nt!KiPageFault+0x260
fffff800`00b9c840 fffff880`05d47468 : fffff880`01d91f90 00000000`00000000 fffff880`09fe0770 fffff880`09fe17a0 : nifslk+0x822e
fffff800`00b9c848 fffff880`01d91f90 : 00000000`00000000 fffff880`09fe0770 fffff880`09fe17a0 fffff880`09fe10b1 : 0xfffff880`05d47468
fffff800`00b9c850 00000000`00000000 : fffff880`09fe0770 fffff880`09fe17a0 fffff880`09fe10b1 fffff800`00b9c8e0 : nipalk+0x75f90
STACK_COMMAND: kb
FOLLOWUP_IP:
nifslk+822e
fffff880`0657922e 0fb650ff movzx edx,byte ptr [rax-1]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nifslk+822e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nifslk
IMAGE_NAME: nifslk.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 51f2daeb
FAILURE_BUCKET_ID: X64_0xD1_nifslk+822e
BUCKET_ID: X64_0xD1_nifslk+822e
Can anyone help me with what this means?

CSA causing BSOD - btaudio.sys

Similar Messages

Maybe you are looking for