Windows 7 Crashes with BSOD - RDR_FILE_SYSTEM mrxsmb2.0

OS is Win 7 Pro 64-bit in AD with SBS 2011 on back end
Users PC crashes every few days with stop error that includes RDR_FILE_SYSTEM mrxsmb2.0
Typically happens when user is using Adobe Acrobat Standard, often creating, moving, deleting and renaming PDFs on a network share, bit not always.
Using msconfig I have disabled everything from starting with Windows. Have not disabled any services yet.
I tried to apply the hot fix associated with KB2494418 but get the message that it does not apply to this PC.
Ran SFC /SCANNOW but it finished with message that no protected files were recovered.
Cleaned PC with cleanmgr.exe and ccleaner.
I appreciate any help to resolve this issue!
Charlie O'Hearn
http://www.plexus-it.com
Charlie O'Hearn http://www.plexus-it.com

We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  
WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.
If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If
you dont know what it is you probably are not overclocking.
You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
If you are overclocking stop.  (chances are if you dont know if you are, you are not)
To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  
The procedure:
* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy (compress them)
*Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.
Link for how to  upload below.
http://www.wikihow.com/Use-SkyDrive
To ensure minidumps are enabled:
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.
Please also run MSinfo32 and upload the output as well.
To run MSinfo32 please go to start>run>MSinfo32
Go to "file" "save" and upload the saved file with the DMPS
System specs are extremely useful so please include whatever you know.
Blue Screen View & Who Crashed are often wrong and should only be used in an emergency...
Basic troubleshooting Windows/hardware here
You can read more about BSODS here
You can learn how to test your memory here
Asking an effective question gets help faster read how here
Driver verifier-Tracking down a mis behaving driver  here
Co-Authored by  JMH3143
Team Zigzag3143.com
Wanikiya and Dyami--Team Zigzag

Similar Messages

  • ITuneHelper crashing with BSOD on Windows 7

    iTunesHelper.exe in crashing sometimes with BSOD on Windows 7 64 bit.
    here is part of WinCrashReport :
    Crash Report For iTunesHelper.exe
    Created by using WinCrashReport
    http://www.nirsoft.net/utils/application_crash_report.html
    General Exception Information:
    Operating System: Windows 7 Home Premium    (6.1.7601)
    Report Time: 05/01/2013 08:57:33
    Process Filename: C:\Program Files (x86)\iTunes\iTunesHelper.exe
    Process ID: 4236
    Thread ID: 5432
    Process Description: iTunesHelper
    Process Version: 11.0.1.12
    Process Company: Apple Inc.
    Product Name: iTunes
    Product Version: 11.0.1.12
    Crash Address: 75CCC41F
    Crash Address (Relative): KERNELBASE.dll!RaiseException+0x58
    Exception Code: 406D1388
    Exception Description:
    Exception Parameter (1): 00001000
    Exception Parameter (2): 72FF8914
    Exception Parameter (3): 00001538
    Exception Parameter (4): 00000000
    Crash Code Bytes:
    C9 C2 10 00 CC CC CC CC CC 8B FF 55 8B EC 56 8B
    75 08 83 FE F4 72 18 83 FE F6 77 13 8D 45 08 50
    6A 00 56 E8 DD 02 00 00 85 C0 74 03 8B 75 08 56
    FF 15 34 10 CC 75 5E 85 C0 7C 05 33 C0 40 EB 08
    Strings in the stack:
    033DF414 77E14880 -> TCF
    033DF454 72C6DE28 -> KERNEL32.DLL
    033DF680 033DFAF8 -> Ui2
    033DF868 72FF8914 -> com.apple.CFSocket.private
    Call Stack (Method 1):
    033DFD54 72F4E24C  CoreFoundation.dll!CFDataGetBytes+0x60
    033DFD68 00000018
    033DFE3C 5D00015C
    Call Stack (Method 2):
    033DF85C 75CCC41F  KERNELBASE.dll!RaiseException+0x58
    033DFA28 77D43C94  ntdll.dll!RtlImageNtHeader+0xb10
    033DFA2C 77D43CC3  ntdll.dll!RtlImageNtHeader+0xb3f
    033DFAF4 77D871D5  ntdll.dll!WinSqmSetIfMaxDWORD+0x31
    033DFAFC 77D3E38C  ntdll.dll!RtlInitUnicodeString+0x164
    033DFB70 77D3E023  ntdll.dll!RtlFreeHeap+0x7e
    033DFB88 77D3E0F2  ntdll.dll!RtlAllocateHeap+0xac
    033DFB90 75ED11E0  kernel32.dll!TlsGetValue
    033DFBB0 76EA2E4D  WS2_32.dll!htons+0xc2
    033DFBC0 76EA6AD6  WS2_32.dll!__WSAFDIsSet+0x4c
    033DFBD4 77D2F89C  ntdll.dll!NtWaitForSingleObject
    033DFBE8 77D2F8B1  ntdll.dll!NtWaitForSingleObject+0x15
    033DFBEC 75166F0F  mswsock.dll+0x6f0f
    033DFC2C 75166D30  mswsock.dll+0x6d30
    033DFCAC 77D2FE36  ntdll.dll!NtDuplicateObject+0x12
    033DFCC0 75164200  mswsock.dll+0x4200
    033DFCE8 7516432A  mswsock.dll+0x432a
    033DFD00 76EA2F7D  WS2_32.dll!WahReferenceContextByHandle+0x5d
    033DFD08 75182F27  mswsock.dll!s_perror+0x1343
    033DFD18 76EA6A28  WS2_32.dll!select+0x9f
    033DFD58 72F4E24C  CoreFoundation.dll!CFDataGetBytes+0x60
    033DFD88 76EC3912  WS2_32.dll!WahWriteLSPEvent+0x2ad
    033DFD98 72F7560B  CoreFoundation.dll!CFSocketGetDefaultNameRegistryPortNumber+0x863
    033DFDC0 77D438BE  ntdll.dll!RtlImageNtHeader+0x73a
    033DFDC8 77D4389A  ntdll.dll!RtlImageNtHeader+0x716
    033DFEB0 77D43492  ntdll.dll!RtlImageNtHeader+0x30e
    033DFED0 75ED14DD  kernel32.dll!HeapFree+0x14
    033DFEE4 730D4C39  MSVCR80.dll!free+0xcd
    033DFEF0 730D4C58  MSVCR80.dll!free+0xec
    033DFF08 731613D8  MSVCR80.dll!__badioinfo+0x40
    033DFF10 730D2C78  MSVCR80.dll!__set_flsgetvalue+0xd
    033DFF24 72F97A05  CoreFoundation.dll!CFHashBytes+0x113
    033DFF30 730D29BB  MSVCR80.dll!_endthreadex+0x3b
    033DFF58 730D8CED  MSVCR80.dll!__dllonexit+0x9d
    033DFF68 730D2A47  MSVCR80.dll!_endthreadex+0xc7
    033DFF70 75ED33AA  kernel32.dll!BaseThreadInitThunk+0x12
    033DFF7C 77D49EF2  ntdll.dll!RtlInitializeExceptionChain+0x63
    033DFFBC 77D49EC5  ntdll.dll!RtlInitializeExceptionChain+0x36
    033DFFC0 730D29E1  MSVCR80.dll!_endthreadex+0x61

    iTunesHelper.exe in crashing sometimes with BSOD on Windows 7 64 bit.
    here is part of WinCrashReport :
    Crash Report For iTunesHelper.exe
    Created by using WinCrashReport
    http://www.nirsoft.net/utils/application_crash_report.html
    General Exception Information:
    Operating System: Windows 7 Home Premium    (6.1.7601)
    Report Time: 05/01/2013 08:57:33
    Process Filename: C:\Program Files (x86)\iTunes\iTunesHelper.exe
    Process ID: 4236
    Thread ID: 5432
    Process Description: iTunesHelper
    Process Version: 11.0.1.12
    Process Company: Apple Inc.
    Product Name: iTunes
    Product Version: 11.0.1.12
    Crash Address: 75CCC41F
    Crash Address (Relative): KERNELBASE.dll!RaiseException+0x58
    Exception Code: 406D1388
    Exception Description:
    Exception Parameter (1): 00001000
    Exception Parameter (2): 72FF8914
    Exception Parameter (3): 00001538
    Exception Parameter (4): 00000000
    Crash Code Bytes:
    C9 C2 10 00 CC CC CC CC CC 8B FF 55 8B EC 56 8B
    75 08 83 FE F4 72 18 83 FE F6 77 13 8D 45 08 50
    6A 00 56 E8 DD 02 00 00 85 C0 74 03 8B 75 08 56
    FF 15 34 10 CC 75 5E 85 C0 7C 05 33 C0 40 EB 08
    Strings in the stack:
    033DF414 77E14880 -> TCF
    033DF454 72C6DE28 -> KERNEL32.DLL
    033DF680 033DFAF8 -> Ui2
    033DF868 72FF8914 -> com.apple.CFSocket.private
    Call Stack (Method 1):
    033DFD54 72F4E24C  CoreFoundation.dll!CFDataGetBytes+0x60
    033DFD68 00000018
    033DFE3C 5D00015C
    Call Stack (Method 2):
    033DF85C 75CCC41F  KERNELBASE.dll!RaiseException+0x58
    033DFA28 77D43C94  ntdll.dll!RtlImageNtHeader+0xb10
    033DFA2C 77D43CC3  ntdll.dll!RtlImageNtHeader+0xb3f
    033DFAF4 77D871D5  ntdll.dll!WinSqmSetIfMaxDWORD+0x31
    033DFAFC 77D3E38C  ntdll.dll!RtlInitUnicodeString+0x164
    033DFB70 77D3E023  ntdll.dll!RtlFreeHeap+0x7e
    033DFB88 77D3E0F2  ntdll.dll!RtlAllocateHeap+0xac
    033DFB90 75ED11E0  kernel32.dll!TlsGetValue
    033DFBB0 76EA2E4D  WS2_32.dll!htons+0xc2
    033DFBC0 76EA6AD6  WS2_32.dll!__WSAFDIsSet+0x4c
    033DFBD4 77D2F89C  ntdll.dll!NtWaitForSingleObject
    033DFBE8 77D2F8B1  ntdll.dll!NtWaitForSingleObject+0x15
    033DFBEC 75166F0F  mswsock.dll+0x6f0f
    033DFC2C 75166D30  mswsock.dll+0x6d30
    033DFCAC 77D2FE36  ntdll.dll!NtDuplicateObject+0x12
    033DFCC0 75164200  mswsock.dll+0x4200
    033DFCE8 7516432A  mswsock.dll+0x432a
    033DFD00 76EA2F7D  WS2_32.dll!WahReferenceContextByHandle+0x5d
    033DFD08 75182F27  mswsock.dll!s_perror+0x1343
    033DFD18 76EA6A28  WS2_32.dll!select+0x9f
    033DFD58 72F4E24C  CoreFoundation.dll!CFDataGetBytes+0x60
    033DFD88 76EC3912  WS2_32.dll!WahWriteLSPEvent+0x2ad
    033DFD98 72F7560B  CoreFoundation.dll!CFSocketGetDefaultNameRegistryPortNumber+0x863
    033DFDC0 77D438BE  ntdll.dll!RtlImageNtHeader+0x73a
    033DFDC8 77D4389A  ntdll.dll!RtlImageNtHeader+0x716
    033DFEB0 77D43492  ntdll.dll!RtlImageNtHeader+0x30e
    033DFED0 75ED14DD  kernel32.dll!HeapFree+0x14
    033DFEE4 730D4C39  MSVCR80.dll!free+0xcd
    033DFEF0 730D4C58  MSVCR80.dll!free+0xec
    033DFF08 731613D8  MSVCR80.dll!__badioinfo+0x40
    033DFF10 730D2C78  MSVCR80.dll!__set_flsgetvalue+0xd
    033DFF24 72F97A05  CoreFoundation.dll!CFHashBytes+0x113
    033DFF30 730D29BB  MSVCR80.dll!_endthreadex+0x3b
    033DFF58 730D8CED  MSVCR80.dll!__dllonexit+0x9d
    033DFF68 730D2A47  MSVCR80.dll!_endthreadex+0xc7
    033DFF70 75ED33AA  kernel32.dll!BaseThreadInitThunk+0x12
    033DFF7C 77D49EF2  ntdll.dll!RtlInitializeExceptionChain+0x63
    033DFFBC 77D49EC5  ntdll.dll!RtlInitializeExceptionChain+0x36
    033DFFC0 730D29E1  MSVCR80.dll!_endthreadex+0x61

  • After windows crashes with firefox open profile always needs to be recreated

    Anytime windows crashes or my computer unexpectedly restarts and Firefox is open, the "restore session" screen comes up, then no matter what (if anything) is clicked, Firefox promptly locks up.
    I have to create a new profile and copy over the profile folder contents every single time. It is very annoying and frustrating.
    I have tried deleting the entire profile folder after the crash, no change.
    I have uninstalled and reinstall Firefox (with and without thunderbird), no change.
    I have even go through the registry and manually deleted any mozilla and firefox key.
    It has been going on in releases 4.x, 6, and now 7.0.1

    Why not back up your profile (back to the Firefox parent directory), so that you can put it back easily? That way, you save the profiles.ini file as well as the profile.
    http://kb.mozillazine.org/Protect_the_profiles_contents

  • Windows crashed with Blue Screen. Dump file content attached.

    Loading Dump File [C:\Windows\Minidump\121712-35786-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: SRV*c:\debug_symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333 Machine Name: Kernel base = 0xfffff800`03407000 PsLoadedModuleList = 0xfffff800`0364b670 Debug session time: Mon Dec 17 11:57:26.477 2012 (UTC - 4:00) System Uptime: 4 days 17:23:45.304 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ........ Loading User Symbols Loading unloaded module list .................................................. ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck A, {10, 2, 0, fffff8000341f852}
    Unable to load image \SystemRoot\System32\drivers\lcencvm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for lcencvm.sys *** ERROR: Module load completed but symbols could not be loaded for lcencvm.sys Unable to load image \SystemRoot\System32\Drivers\lcfiltvm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for lcfiltvm.sys *** ERROR: Module load completed but symbols could not be loaded for lcfiltvm.sys Probably caused by : lcencvm.sys ( lcencvm+26b9a )
    Followup: MachineOwner ---------
    2: 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: 0000000000000010, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, 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: fffff8000341f852, address which referenced memory
    Debugging Details: ------------------
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036b5100  0000000000000010
    CURRENT_IRQL:  2
    FAULTING_IP: nt!IopInsertRemoveDevice+62 fffff800`0341f852 48393a          cmp     qword ptr [rdx],rdi
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  Rim.Desktop.ex
    TRAP_FRAME:  fffff8800c8a52f0 -- (.trap 0xfffff8800c8a52f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=00000000000000a0 rdx=0000000000000010 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8000341f852 rsp=fffff8800c8a5480 rbp=0000000000000000  r8=fffff88003365890  r9=0000000000000000 r10=0000000000000000 r11=fffffa800ec2a900 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0         nv up ei pl nz na pe nc nt!IopInsertRemoveDevice+0x62: fffff800`0341f852 48393a          cmp     qword ptr [rdx],rdi ds:00000000`00000010=???????????????? Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80003485569 to fffff80003485fc0
    STACK_TEXT:  fffff880`0c8a51a8 fffff800`03485569 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0c8a51b0 fffff800`034841e0 : fffffa80`0e0cdbf0 fffff880`01202bcf fffff880`0c8a5300 fffffa80`0a272300 : nt!KiBugCheckDispatch+0x69 fffff880`0c8a52f0 fffff800`0341f852 : 00000000`00000000 fffffa80`0a272300 00000000`00000000 fffffa80`07d6e8d0 : nt!KiPageFault+0x260 fffff880`0c8a5480 fffff800`0341f729 : fffffa80`0a272350 fffffa80`07d6e8d0 fffffa80`07d6e8d0 00000000`0000000a : nt!IopInsertRemoveDevice+0x62 fffff880`0c8a54b0 fffff800`0377dfb7 : fffffa80`0f871a30 fffffa80`0a5aa070 00000000`00000001 fffffa80`07321210 : nt!IopCompleteUnloadOrDelete+0x9d fffff880`0c8a5560 fffff800`0348f1d4 : fffff880`0c8a5660 fffffa80`0a447ab8 fffffa80`07321210 fffff880`0c8a5668 : nt!IopDeleteFile+0x1a7 fffff880`0c8a55f0 fffff880`0146db9a : fffffa80`0a447ab8 fffffa80`0a491c28 fffffa80`0a54e628 fffff880`0144ac90 : nt!ObfDereferenceObject+0xd4 fffff880`0c8a5650 fffffa80`0a447ab8 : fffffa80`0a491c28 fffffa80`0a54e628 fffff880`0144ac90 00000000`000003e3 : lcencvm+0x26b9a fffff880`0c8a5658 fffffa80`0a491c28 : fffffa80`0a54e628 fffff880`0144ac90 00000000`000003e3 fffff880`00ff86d0 : 0xfffffa80`0a447ab8 fffff880`0c8a5660 fffffa80`0a54e628 : fffff880`0144ac90 00000000`000003e3 fffff880`00ff86d0 fffff8a0`14ddc760 : 0xfffffa80`0a491c28 fffff880`0c8a5668 fffff880`0144ac90 : 00000000`000003e3 fffff880`00ff86d0 fffff8a0`14ddc760 fffff880`00ff58d8 : 0xfffffa80`0a54e628 fffff880`0c8a5670 00000000`000003e3 : fffff880`00ff86d0 fffff8a0`14ddc760 fffff880`00ff58d8 fffff880`00ff86d0 : lcencvm+0x3c90 fffff880`0c8a5678 fffff880`00ff86d0 : fffff8a0`14ddc760 fffff880`00ff58d8 fffff880`00ff86d0 00000000`00000000 : 0x3e3 fffff880`0c8a5680 fffff8a0`14ddc760 : fffff880`00ff58d8 fffff880`00ff86d0 00000000`00000000 fffff880`0c8a5840 : lcfiltvm+0xf6d0 fffff880`0c8a5688 fffff880`00ff58d8 : fffff880`00ff86d0 00000000`00000000 fffff880`0c8a5840 fffff880`012016df : 0xfffff8a0`14ddc760 fffff880`0c8a5690 fffff880`00ff86d0 : 00000000`00000000 fffff880`0c8a5840 fffff880`012016df fffffa80`0b5236f0 : lcfiltvm+0xc8d8 fffff880`0c8a5698 00000000`00000000 : fffff880`0c8a5840 fffff880`012016df fffffa80`0b5236f0 00000000`00000000 : lcfiltvm+0xf6d0
    STACK_COMMAND:  kb
    FOLLOWUP_IP: lcencvm+26b9a fffff880`0146db9a ??              ???
    SYMBOL_STACK_INDEX:  7
    SYMBOL_NAME:  lcencvm+26b9a
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: lcencvm
    IMAGE_NAME:  lcencvm.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e3c8eac
    FAILURE_BUCKET_ID:  X64_0xA_lcencvm+26b9a
    BUCKET_ID:  X64_0xA_lcencvm+26b9a
    Followup: MachineOwner ---------
    2: 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: 0000000000000010, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, 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: fffff8000341f852, address which referenced memory
    Debugging Details: ------------------
    READ_ADDRESS:  0000000000000010
    CURRENT_IRQL:  2
    FAULTING_IP: nt!IopInsertRemoveDevice+62 fffff800`0341f852 48393a          cmp     qword ptr [rdx],rdi
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  Rim.Desktop.ex
    TRAP_FRAME:  fffff8800c8a52f0 -- (.trap 0xfffff8800c8a52f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=00000000000000a0 rdx=0000000000000010 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8000341f852 rsp=fffff8800c8a5480 rbp=0000000000000000  r8=fffff88003365890  r9=0000000000000000 r10=0000000000000000 r11=fffffa800ec2a900 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0         nv up ei pl nz na pe nc nt!IopInsertRemoveDevice+0x62: fffff800`0341f852 48393a          cmp     qword ptr [rdx],rdi ds:00000000`00000010=???????????????? Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80003485569 to fffff80003485fc0
    STACK_TEXT:  fffff880`0c8a51a8 fffff800`03485569 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0c8a51b0 fffff800`034841e0 : fffffa80`0e0cdbf0 fffff880`01202bcf fffff880`0c8a5300 fffffa80`0a272300 : nt!KiBugCheckDispatch+0x69 fffff880`0c8a52f0 fffff800`0341f852 : 00000000`00000000 fffffa80`0a272300 00000000`00000000 fffffa80`07d6e8d0 : nt!KiPageFault+0x260 fffff880`0c8a5480 fffff800`0341f729 : fffffa80`0a272350 fffffa80`07d6e8d0 fffffa80`07d6e8d0 00000000`0000000a : nt!IopInsertRemoveDevice+0x62 fffff880`0c8a54b0 fffff800`0377dfb7 : fffffa80`0f871a30 fffffa80`0a5aa070 00000000`00000001 fffffa80`07321210 : nt!IopCompleteUnloadOrDelete+0x9d fffff880`0c8a5560 fffff800`0348f1d4 : fffff880`0c8a5660 fffffa80`0a447ab8 fffffa80`07321210 fffff880`0c8a5668 : nt!IopDeleteFile+0x1a7 fffff880`0c8a55f0 fffff880`0146db9a : fffffa80`0a447ab8 fffffa80`0a491c28 fffffa80`0a54e628 fffff880`0144ac90 : nt!ObfDereferenceObject+0xd4 fffff880`0c8a5650 fffffa80`0a447ab8 : fffffa80`0a491c28 fffffa80`0a54e628 fffff880`0144ac90 00000000`000003e3 : lcencvm+0x26b9a fffff880`0c8a5658 fffffa80`0a491c28 : fffffa80`0a54e628 fffff880`0144ac90 00000000`000003e3 fffff880`00ff86d0 : 0xfffffa80`0a447ab8 fffff880`0c8a5660 fffffa80`0a54e628 : fffff880`0144ac90 00000000`000003e3 fffff880`00ff86d0 fffff8a0`14ddc760 : 0xfffffa80`0a491c28 fffff880`0c8a5668 fffff880`0144ac90 : 00000000`000003e3 fffff880`00ff86d0 fffff8a0`14ddc760 fffff880`00ff58d8 : 0xfffffa80`0a54e628 fffff880`0c8a5670 00000000`000003e3 : fffff880`00ff86d0 fffff8a0`14ddc760 fffff880`00ff58d8 fffff880`00ff86d0 : lcencvm+0x3c90 fffff880`0c8a5678 fffff880`00ff86d0 : fffff8a0`14ddc760 fffff880`00ff58d8 fffff880`00ff86d0 00000000`00000000 : 0x3e3 fffff880`0c8a5680 fffff8a0`14ddc760 : fffff880`00ff58d8 fffff880`00ff86d0 00000000`00000000 fffff880`0c8a5840 : lcfiltvm+0xf6d0 fffff880`0c8a5688 fffff880`00ff58d8 : fffff880`00ff86d0 00000000`00000000 fffff880`0c8a5840 fffff880`012016df : 0xfffff8a0`14ddc760 fffff880`0c8a5690 fffff880`00ff86d0 : 00000000`00000000 fffff880`0c8a5840 fffff880`012016df fffffa80`0b5236f0 : lcfiltvm+0xc8d8 fffff880`0c8a5698 00000000`00000000 : fffff880`0c8a5840 fffff880`012016df fffffa80`0b5236f0 00000000`00000000 : lcfiltvm+0xf6d0
    STACK_COMMAND:  kb
    FOLLOWUP_IP: lcencvm+26b9a fffff880`0146db9a ??              ???
    SYMBOL_STACK_INDEX:  7
    SYMBOL_NAME:  lcencvm+26b9a
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: lcencvm
    IMAGE_NAME:  lcencvm.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e3c8eac
    FAILURE_BUCKET_ID:  X64_0xA_lcencvm+26b9a
    BUCKET_ID:  X64_0xA_lcencvm+26b9a
    Followup: MachineOwner ---------

    The best working solution at this time is to download and install Skype 6.14 and disable updates.  If you still get prompts to upgrade you can ignore them and the program should continue to function as it has not been retired as of yet.  Hopefully there will be a resolution in a future Skype update or an updated driver from HP that might resolve the issue.
    http://community.skype.com/t5/Windows-desktop-client/BSOD-on-startup-and-installation/m-p/3511645/hi...

  • Clean install of windows 8 crashing with BSoD: "attempted execute of noexecute memory"

    I recently bought this computer (sorry for hyperlink, but it is much easier than trying to list all the components):
    http://www.newegg.com/Product/Product.aspx?Item=N82E16883227593
    I added a Samsung 840 EVO 250gb SSD to it, and then I attempted to do a clean install of windows 8.1 onto the SSD from
    the reinstall DVD that came with the system. Windows 8.1 appears to install correctly, but when the computer restarts to load windows for the first time, I get a BSoD with the error "attempted execute of noexecute memory". I tried reinstalling, but
    got the same error.
    Note that for testing purposes, I installed windows 7 on the SSD, and it works great. Unfortunately, I do not have a windows
    7 key, so this is only a temporary solution. I would like to figure out how to get windows 8.1 on the SSD and running on the my computer.
    Thank you in advance for any help or advice that you can give me.
    Here are the minidump files if helpful:
     https://drive.google.com/file/d/0B1fPQ--DwbjOV2ZuT0xoeWR6QXc/view?usp=sharing
     https://drive.google.com/file/d/0B1fPQ--DwbjOOUtrWUhfZmRMM1E/view?usp=sharing

    P
    These were Related to RTL8192cu.sys USB NDIS Driver from Realtek Semiconductor Corporation  I would remove the current driver and install the newest driver available
    Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Ken\Desktop\120414-8515-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*f:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*f:\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 Personal
    Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623
    Machine Name:
    Kernel base = 0xfffff801`1981d000 PsLoadedModuleList = 0xfffff801`19ae49b0
    Debug session time: Thu Dec 4 05:16:31.298 2014 (UTC - 5:00)
    System Uptime: 0 days 0:00:12.923
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck FC, {ffffd000217aaa00, 8000000104112963, ffffd000217aa7a0, 2}
    *** WARNING: Unable to verify timestamp for rtwlanu.sys
    *** ERROR: Module load completed but symbols could not be loaded for rtwlanu.sys
    Probably caused by : rtwlanu.sys ( rtwlanu+10d69a )
    Followup: MachineOwner
    2: kd> !analyze -v
    * Bugcheck Analysis *
    ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
    An attempt was made to execute non-executable memory. The guilty driver
    is on the stack trace (and is typically the current instruction pointer).
    When possible, the guilty driver's name (Unicode string) is printed on
    the bugcheck screen and saved in KiBugCheckDriver.
    Arguments:
    Arg1: ffffd000217aaa00, Virtual address for the attempted execute.
    Arg2: 8000000104112963, PTE contents.
    Arg3: ffffd000217aa7a0, (reserved)
    Arg4: 0000000000000002, (reserved)
    Debugging Details:
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    BUGCHECK_STR: 0xFC
    PROCESS_NAME: System
    CURRENT_IRQL: 0
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    TRAP_FRAME: ffffd000217aa7a0 -- (.trap 0xffffd000217aa7a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffd000217aaa08 rbx=0000000000000000 rcx=ffffe00003734a70
    rdx=ffffd000217aa9f0 rsi=0000000000000000 rdi=0000000000000000
    rip=ffffd000217aaa00 rsp=ffffd000217aa938 rbp=ffffd000217aa9a8
    r8=ffffd000217aaa00 r9=ffffd000217aa9f8 r10=ffffd00020640000
    r11=ffffd000217aa940 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po nc
    ffffd000`217aaa00 0000 add byte ptr [rax],al ds:ffffd000`217aaa08=00
    Resetting default scope
    LAST_CONTROL_TRANSFER: from fffff801199c3e32 to fffff8011996d0a0
    STACK_TEXT:
    ffffd000`217aa578 fffff801`199c3e32 : 00000000`000000fc ffffd000`217aaa00 80000001`04112963 ffffd000`217aa7a0 : nt!KeBugCheckEx
    ffffd000`217aa580 fffff801`19853bc6 : 80000001`04112963 00000000`00000000 ffffd000`217aa720 00000000`00000008 : nt! ?? ::FNODOBFM::`string'+0x468a2
    ffffd000`217aa5c0 fffff801`19885ffd : 00000000`00000008 ffffe000`02759880 ffffd000`217aa7a0 ffffe000`052a0000 : nt!MiSystemFault+0xaf6
    ffffd000`217aa660 fffff801`1997732f : 00000000`00000008 ffffe000`03734a70 00000000`00000000 ffffd000`217aa7a0 : nt!MmAccessFault+0x7ed
    ffffd000`217aa7a0 ffffd000`217aaa00 : fffff800`01db969a ffffe000`03734a70 ffffe000`03000000 00000000`00000001 : nt!KiPageFault+0x12f
    ffffd000`217aa938 fffff800`01db969a : ffffe000`03734a70 ffffe000`03000000 00000000`00000001 00000000`00000000 : 0xffffd000`217aaa00
    ffffd000`217aa940 ffffe000`03734a70 : ffffe000`03000000 00000000`00000001 00000000`00000000 ffffd000`217aaa08 : rtwlanu+0x10d69a
    ffffd000`217aa948 ffffe000`03000000 : 00000000`00000001 00000000`00000000 ffffd000`217aaa08 fffff800`01ccf62e : 0xffffe000`03734a70
    ffffd000`217aa950 00000000`00000001 : 00000000`00000000 ffffd000`217aaa08 fffff800`01ccf62e 00000000`00000004 : 0xffffe000`03000000
    ffffd000`217aa958 00000000`00000000 : ffffd000`217aaa08 fffff800`01ccf62e 00000000`00000004 ffffe000`03000000 : 0x1
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    rtwlanu+10d69a
    fffff800`01db969a ?? ???
    SYMBOL_STACK_INDEX: 6
    SYMBOL_NAME: rtwlanu+10d69a
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: rtwlanu
    IMAGE_NAME: rtwlanu.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 51dd743f
    FAILURE_BUCKET_ID: 0xFC_rtwlanu+10d69a
    BUCKET_ID: 0xFC_rtwlanu+10d69a
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0xfc_rtwlanu+10d69a
    FAILURE_ID_HASH: {095bf10a-821a-1045-f529-a4601d2cff4f}
    Followup: MachineOwner
    2: kd> lmvm rtwlanu
    start end module name
    fffff800`01cac000 fffff800`01ea4000 rtwlanu T (no symbols)
    Loaded symbol image file: rtwlanu.sys
    Image path: \SystemRoot\system32\DRIVERS\rtwlanu.sys
    Image name: rtwlanu.sys
    Timestamp: Wed Jul 10 10:48:31 2013 (51DD743F)
    CheckSum: 001EE009
    ImageSize: 001F8000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Wanikiya and Dyami--Team Zigzag

  • Windows 8.1 BSOD RDR_FILE_SYSTEM 0x27

    A customer of ours is experiencing random BSODs, it seems to have something to do with avp.exe or rdbss.sys.
    I analyzed the MEMORY.DMP file with the Windows Debugging Tools, see below, can anyone tell me what is causing the BSODs? I already ran sfc /scannow, but it didn't find any problems.
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    Machine Name:
    Kernel base = 0xfffff801`6847f000 PsLoadedModuleList = 0xfffff801`687492d0
    Debug session time: Mon Jul 28 15:09:04.104 2014 (UTC + 2:00)
    System Uptime: 13 days 3:53:35.466
    Loading Kernel Symbols
    ....................................................Page 6a3b not present in the dump file. Type ".hh dbgerr004" for details
    ...Page baa75 not present in the dump file. Type ".hh dbgerr004" for details
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 00000000`7e76f018).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    *                        Bugcheck Analysis                                   
    Use !analyze -v to get detailed debugging information.
    BugCheck 27, {baad0073, ffffd001a9df6b18, ffffd001a9df6320, fffff801f9474ed0}
    Page 6a3b not present in the dump file. Type ".hh dbgerr004" for details
    Probably caused by : rdbss.sys ( rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+60 )
    Followup: MachineOwner
    1: kd> !analyze -v
    *                        Bugcheck Analysis                                   
    RDR_FILE_SYSTEM (27)
        If you see RxExceptionFilter on the stack then the 2nd and 3rd parameters are the
        exception record and context record. Do a .cxr on the 3rd parameter and then kb to
        obtain a more informative stack trace.
        The high 16 bits of the first parameter is the RDBSS bugcheck code, which is defined
        as follows:
         RDBSS_BUG_CHECK_CACHESUP  = 0xca550000,
         RDBSS_BUG_CHECK_CLEANUP   = 0xc1ee0000,
         RDBSS_BUG_CHECK_CLOSE     = 0xc10e0000,
         RDBSS_BUG_CHECK_NTEXCEPT  = 0xbaad0000,
    Arguments:
    Arg1: 00000000baad0073
    Arg2: ffffd001a9df6b18
    Arg3: ffffd001a9df6320
    Arg4: fffff801f9474ed0
    Debugging Details:
    Page 6a3b not present in the dump file. Type ".hh dbgerr004" for details
    EXCEPTION_RECORD:  ffffd001a9df6b18 -- (.exr 0xffffd001a9df6b18)
    ExceptionAddress: fffff801f9474ed0 (rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+0x0000000000000060)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000130
    Attempt to read from address 0000000000000130
    CONTEXT:  ffffd001a9df6320 -- (.cxr 0xffffd001a9df6320;r)
    rax=fffff801f9453010 rbx=0000000000000000 rcx=fffff801f9453800
    rdx=0000000000000000 rsi=0000000000000130 rdi=0000000000000000
    rip=fffff801f9474ed0 rsp=ffffd001a9df6d50 rbp=ffffc0005e647280
     r8=ffffe00161e52080  r9=ffffd001a9df7630 r10=fffff780000003b0
    r11=fffff78000000008 r12=ffffd001a9df7630 r13=ffffe00161e52080
    r14=ffffc0004e87a010 r15=ffffe0015e9ab860
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+0x60:
    fffff801`f9474ed0 488b1e          mov     rbx,qword ptr [rsi] ds:002b:00000000`00000130=????????????????
    Last set context:
    rax=fffff801f9453010 rbx=0000000000000000 rcx=fffff801f9453800
    rdx=0000000000000000 rsi=0000000000000130 rdi=0000000000000000
    rip=fffff801f9474ed0 rsp=ffffd001a9df6d50 rbp=ffffc0005e647280
     r8=ffffe00161e52080  r9=ffffd001a9df7630 r10=fffff780000003b0
    r11=fffff78000000008 r12=ffffd001a9df7630 r13=ffffe00161e52080
    r14=ffffc0004e87a010 r15=ffffe0015e9ab860
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+0x60:
    fffff801`f9474ed0 488b1e          mov     rbx,qword ptr [rsi] ds:002b:00000000`00000130=????????????????
    Resetting default scope
    PROCESS_NAME:  avp.exe
    CURRENT_IRQL:  0
    ERROR_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. Een lees- of schrijfbewerking op het geheugen is mislukt: %s.
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. Een lees- of schrijfbewerking op het geheugen is mislukt: %s.
    EXCEPTION_PARAMETER1:  0000000000000000
    EXCEPTION_PARAMETER2:  0000000000000130
    READ_ADDRESS: unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
     0000000000000130
    FOLLOWUP_IP:
    rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+60
    fffff801`f9474ed0 488b1e          mov     rbx,qword ptr [rsi]
    FAULTING_IP:
    rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+60
    fffff801`f9474ed0 488b1e          mov     rbx,qword ptr [rsi]
    BUGCHECK_STR:  0x27
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    LAST_CONTROL_TRANSFER:  from fffff801f94655c2 to fffff801f9474ed0
    STACK_TEXT: 
    ffffd001`a9df6d50 fffff801`f94655c2 : 00000000`00000000 ffffc000`5b033a90 ffffe001`5e2873f0 fffff801`f9453010 : rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+0x60
    ffffd001`a9df6dc0 fffff801`f94649f0 : ffffe001`5e287300 ffffe001`62344c00 fffff801`f9453010 ffffd001`a9df6e00 : rdbss!RxCollapseOrCreateSrvOpen+0x3f2
    ffffd001`a9df6e50 fffff801`f946407d : ffffe001`5e2873f0 00000000`00000004 ffffe001`5e2873f0 ffffe001`618fa590 : rdbss!RxCreateFromNetRoot+0x1b0
    ffffd001`a9df6f80 fffff801`f942ed9e : 01cfaa65`1b27c42d ffffe001`62344c00 ffffe001`62344d18 00000000`00000000 : rdbss!RxCommonCreate+0x1bd
    ffffd001`a9df7030 fffff801`f945f7df : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : rdbss!RxFsdCommonDispatch+0x56e
    ffffd001`a9df71a0 fffff801`fa3bf1b3 : 00000000`00000000 ffffe001`62344c01 ffffe001`62344c00 fffff801`f88bf010 : rdbss!RxFsdDispatch+0xcf
    ffffd001`a9df7210 fffff801`f88c4682 : ffffe001`61e06300 ffffe001`62344c00 ffffc000`4eb0c140 00000000`00000000 : mrxsmb!MRxSmbFsdDispatch+0x83
    ffffd001`a9df7250 fffff801`f88c2c07 : ffffc000`4eb0c140 00000000`00000000 fffff801`f88bf010 ffffe001`6248f630 : mup!MupiCallUncProvider+0xc2
    ffffd001`a9df72c0 fffff801`f8344cf8 : ffffe001`618fa590 00000000`00000022 ffffe001`618fa590 ffffe001`6248f630 : mup!MupCreate+0x5f8
    ffffd001`a9df7360 fffff801`f836d341 : ffffe001`5f571010 ffffe001`62344c00 ffffe001`5e4ccad0 00000000`00000801 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x258
    ffffd001`a9df7400 fffff801`68872593 : 00000000`00000000 00000000`00000005 00000000`00000000 00000000`000007ff : fltmgr!FltpCreate+0x342
    ffffd001`a9df74b0 fffff801`688784f8 : ffffc000`4dc14188 ffffc000`4dc14188 ffffc000`4eb0f8d0 ffffe001`5da4a320 : nt!IopParseDevice+0x7b3
    ffffd001`a9df76b0 fffff801`68875e53 : 00000000`00000000 ffffd001`a9df78a8 00000000`00000040 ffffe001`5ce39840 : nt!ObpLookupObjectName+0x6d8
    ffffd001`a9df7830 fffff801`688449a2 : 00000000`00000001 ffffe001`61e3f838 00000000`0bb5e830 00000000`00000020 : nt!ObOpenObjectByName+0x1e3
    ffffd001`a9df7960 fffff801`68844628 : 00000000`0bb5e818 00000000`80100080 00000000`0bb5f0d0 fffff801`6887c1c6 : nt!IopCreateFile+0x372
    ffffd001`a9df7a00 fffff801`685de7b3 : ffffe001`60341de8 ffffe001`61e52080 fffff6fb`7dbed000 fffff6fb`7da00000 : nt!NtCreateFile+0x78
    ffffd001`a9df7a90 00007ffc`dfebb25a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0bb5e7a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`dfebb25a
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+60
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: rdbss
    IMAGE_NAME:  rdbss.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  52affb72
    STACK_COMMAND:  .cxr 0xffffd001a9df6320 ; kb
    BUCKET_ID_FUNC_OFFSET:  60
    FAILURE_BUCKET_ID:  0x27_rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance
    BUCKET_ID:  0x27_rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x27_rdbss!rdbssstatisticsentryarrayfindorcreateprimaryinstance
    FAILURE_ID_HASH:  {153fa92a-562a-8bd4-d56c-4e02c62b008f}
    Followup: MachineOwner

    VinnieL
    Upon double checking it was not the correct DMP file.  I am sorry about the mix up.  Given that it is a full DMP file I was not able to use the tools I use to double check.  Lets try this again and you can confirm this is the correct DMP but
    the headers you got and in the snip below
    This was Related to rdbss.sys Redirected Drive Buffering SubSystem Driver from Microsoft Corporation and this makes more sense.  Given that it is an OS driver your first step should be to run a system file check to repair it.  If SFC is unable
    to repair it you should run DISM the instructions for which are at the end of the wiki. 
    Again I am sorry for the mix up.  With over 100 DMPS a day sometimes an old DMP isnt deleted.
    Please run a system file check (SFC)
    All instructions are in our Wiki article below...
    Should you have any questions please ask us.
    System file check (SFC) Scan and Repair System Files
    Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Ken\Desktop\MEMORY.DMP]
    Kernel Bitmap Dump File: Only kernel address space is 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 8 Kernel Version 9600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    Machine Name:
    Kernel base = 0xfffff801`6847f000 PsLoadedModuleList = 0xfffff801`687492d0
    Debug session time: Mon Jul 28 09:09:04.104 2014 (UTC - 4:00)
    System Uptime: 13 days 3:53:35.466
    Loading Kernel Symbols
    ....................................................Page 6a3b not present in the dump file. Type ".hh dbgerr004" for details
    ...Page baa75 not present in the dump file. Type ".hh dbgerr004" for details
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 00000000`7e76f018). Type ".hh dbgerr001" for details
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck 27, {baad0073, ffffd001a9df6b18, ffffd001a9df6320, fffff801f9474ed0}
    Page 6a3b not present in the dump file. Type ".hh dbgerr004" for details
    Probably caused by : rdbss.sys ( rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+60 )
    Followup: MachineOwner
    1: kd> !analyze -v
    * Bugcheck Analysis *
    RDR_FILE_SYSTEM (27)
    If you see RxExceptionFilter on the stack then the 2nd and 3rd parameters are the
    exception record and context record. Do a .cxr on the 3rd parameter and then kb to
    obtain a more informative stack trace.
    The high 16 bits of the first parameter is the RDBSS bugcheck code, which is defined
    as follows:
    RDBSS_BUG_CHECK_CACHESUP = 0xca550000,
    RDBSS_BUG_CHECK_CLEANUP = 0xc1ee0000,
    RDBSS_BUG_CHECK_CLOSE = 0xc10e0000,
    RDBSS_BUG_CHECK_NTEXCEPT = 0xbaad0000,
    Arguments:
    Arg1: 00000000baad0073
    Arg2: ffffd001a9df6b18
    Arg3: ffffd001a9df6320
    Arg4: fffff801f9474ed0
    Debugging Details:
    Page 6a3b not present in the dump file. Type ".hh dbgerr004" for details
    EXCEPTION_RECORD: ffffd001a9df6b18 -- (.exr 0xffffd001a9df6b18)
    ExceptionAddress: fffff801f9474ed0 (rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+0x0000000000000060)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 0000000000000130
    Attempt to read from address 0000000000000130
    CONTEXT: ffffd001a9df6320 -- (.cxr 0xffffd001a9df6320;r)
    rax=fffff801f9453010 rbx=0000000000000000 rcx=fffff801f9453800
    rdx=0000000000000000 rsi=0000000000000130 rdi=0000000000000000
    rip=fffff801f9474ed0 rsp=ffffd001a9df6d50 rbp=ffffc0005e647280
    r8=ffffe00161e52080 r9=ffffd001a9df7630 r10=fffff780000003b0
    r11=fffff78000000008 r12=ffffd001a9df7630 r13=ffffe00161e52080
    r14=ffffc0004e87a010 r15=ffffe0015e9ab860
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
    rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+0x60:
    fffff801`f9474ed0 488b1e mov rbx,qword ptr [rsi] ds:002b:00000000`00000130=????????????????
    Last set context:
    rax=fffff801f9453010 rbx=0000000000000000 rcx=fffff801f9453800
    rdx=0000000000000000 rsi=0000000000000130 rdi=0000000000000000
    rip=fffff801f9474ed0 rsp=ffffd001a9df6d50 rbp=ffffc0005e647280
    r8=ffffe00161e52080 r9=ffffd001a9df7630 r10=fffff780000003b0
    r11=fffff78000000008 r12=ffffd001a9df7630 r13=ffffe00161e52080
    r14=ffffc0004e87a010 r15=ffffe0015e9ab860
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
    rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+0x60:
    fffff801`f9474ed0 488b1e mov rbx,qword ptr [rsi] ds:002b:00000000`00000130=????????????????
    Resetting default scope
    PROCESS_NAME: avp.exe
    CURRENT_IRQL: 0
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_PARAMETER1: 0000000000000000
    EXCEPTION_PARAMETER2: 0000000000000130
    READ_ADDRESS: unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
    0000000000000130
    FOLLOWUP_IP:
    rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+60
    fffff801`f9474ed0 488b1e mov rbx,qword ptr [rsi]
    FAULTING_IP:
    rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+60
    fffff801`f9474ed0 488b1e mov rbx,qword ptr [rsi]
    BUGCHECK_STR: 0x27
    DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    LAST_CONTROL_TRANSFER: from fffff801f94655c2 to fffff801f9474ed0
    STACK_TEXT:
    ffffd001`a9df6d50 fffff801`f94655c2 : 00000000`00000000 ffffc000`5b033a90 ffffe001`5e2873f0 fffff801`f9453010 : rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+0x60
    ffffd001`a9df6dc0 fffff801`f94649f0 : ffffe001`5e287300 ffffe001`62344c00 fffff801`f9453010 ffffd001`a9df6e00 : rdbss!RxCollapseOrCreateSrvOpen+0x3f2
    ffffd001`a9df6e50 fffff801`f946407d : ffffe001`5e2873f0 00000000`00000004 ffffe001`5e2873f0 ffffe001`618fa590 : rdbss!RxCreateFromNetRoot+0x1b0
    ffffd001`a9df6f80 fffff801`f942ed9e : 01cfaa65`1b27c42d ffffe001`62344c00 ffffe001`62344d18 00000000`00000000 : rdbss!RxCommonCreate+0x1bd
    ffffd001`a9df7030 fffff801`f945f7df : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : rdbss!RxFsdCommonDispatch+0x56e
    ffffd001`a9df71a0 fffff801`fa3bf1b3 : 00000000`00000000 ffffe001`62344c01 ffffe001`62344c00 fffff801`f88bf010 : rdbss!RxFsdDispatch+0xcf
    ffffd001`a9df7210 fffff801`f88c4682 : ffffe001`61e06300 ffffe001`62344c00 ffffc000`4eb0c140 00000000`00000000 : mrxsmb!MRxSmbFsdDispatch+0x83
    ffffd001`a9df7250 fffff801`f88c2c07 : ffffc000`4eb0c140 00000000`00000000 fffff801`f88bf010 ffffe001`6248f630 : mup!MupiCallUncProvider+0xc2
    ffffd001`a9df72c0 fffff801`f8344cf8 : ffffe001`618fa590 00000000`00000022 ffffe001`618fa590 ffffe001`6248f630 : mup!MupCreate+0x5f8
    ffffd001`a9df7360 fffff801`f836d341 : ffffe001`5f571010 ffffe001`62344c00 ffffe001`5e4ccad0 00000000`00000801 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x258
    ffffd001`a9df7400 fffff801`68872593 : 00000000`00000000 00000000`00000005 00000000`00000000 00000000`000007ff : fltmgr!FltpCreate+0x342
    ffffd001`a9df74b0 fffff801`688784f8 : ffffc000`4dc14188 ffffc000`4dc14188 ffffc000`4eb0f8d0 ffffe001`5da4a320 : nt!IopParseDevice+0x7b3
    ffffd001`a9df76b0 fffff801`68875e53 : 00000000`00000000 ffffd001`a9df78a8 00000000`00000040 ffffe001`5ce39840 : nt!ObpLookupObjectName+0x6d8
    ffffd001`a9df7830 fffff801`688449a2 : 00000000`00000001 ffffe001`61e3f838 00000000`0bb5e830 00000000`00000020 : nt!ObOpenObjectByName+0x1e3
    ffffd001`a9df7960 fffff801`68844628 : 00000000`0bb5e818 00000000`80100080 00000000`0bb5f0d0 fffff801`6887c1c6 : nt!IopCreateFile+0x372
    ffffd001`a9df7a00 fffff801`685de7b3 : ffffe001`60341de8 ffffe001`61e52080 fffff6fb`7dbed000 fffff6fb`7da00000 : nt!NtCreateFile+0x78
    ffffd001`a9df7a90 00007ffc`dfebb25a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0bb5e7a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`dfebb25a
    SYMBOL_STACK_INDEX: 0
    SYMBOL_NAME: rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+60
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: rdbss
    IMAGE_NAME: rdbss.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 52affb72
    STACK_COMMAND: .cxr 0xffffd001a9df6320 ; kb
    BUCKET_ID_FUNC_OFFSET: 60
    FAILURE_BUCKET_ID: 0x27_rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance
    BUCKET_ID: 0x27_rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x27_rdbss!rdbssstatisticsentryarrayfindorcreateprimaryinstance
    FAILURE_ID_HASH: {153fa92a-562a-8bd4-d56c-4e02c62b008f}
    Followup: MachineOwner
    1: kd> lmvm rdbss
    start end module name
    fffff801`f942d000 fffff801`f949d000 rdbss (pdb symbols) c:\symbols\rdbss.pdb\79F4162F81A5409285603135A1E6DB592\rdbss.pdb
    Loaded symbol image file: rdbss.sys
    Image path: \SystemRoot\system32\DRIVERS\rdbss.sys
    Image name: rdbss.sys
    Timestamp: Tue Dec 17 02:21:22 2013 (52AFFB72)
    CheckSum: 0006BFA7
    ImageSize: 00070000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
    1: kd> .exr 0xffffd001a9df6b18
    ExceptionAddress: fffff801f9474ed0 (rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+0x0000000000000060)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 0000000000000130
    Attempt to read from address 0000000000000130
    Wanikiya and Dyami--Team Zigzag

  • Satellite C660-2EV crashed with BSOD and does not boot

    My Satellite laptop C660-2EV running Windows 7, for no apparent reason crashed to the blue screen of death, after which it would not reboot.
    I have attempted to reboot in safe mode using the function keys but it gets as far as loading: windows\system32\drivers/classpnp.sys and then just sits there. From the various Internet posts it would appear that there is no definitive answer to this problem. Recommendation is to reload using recovery disks or the hidden image.
    I cannot access the user manual as it is on the laptop so i have referenced the various posts on the internet. I had created repair and recovery disks when i purchased the laptop and so following various posts I booted my system with the repair disk and the process started.
    Unfortunately the screens that appeared were different than those in the posts and as I do not have access to a user manual, I do not know if I am following the correct procedure.
    Can anybody provide me with a PDF user manual for a C660-2EV laptop ?
    Alternatively can anybody advise me how to reload Windows 7 ?
    Thank you in anticipation.

    Users manuals document can be downloaded from http://www.toshiba.eu/innovation/download_manuals.jsp
    Anyway, if you have created recovery discs please start your notebook and press f12 to enter boot menu. When boot menu is shown on the screen put recovery disc 1 into optical disc drive and choose CD/DVD device as bootable device and press ENTER.
    Installation should start. What you must do is just to follow menu on the screen. It must be similar as sown on http://aps2.toshiba-tro.de/kb0/HTD1303440001R01.htm
    If you have more questions or if you need some assistance let us know.

  • Windows crashing - random BSOD on Windows 7 64-bit

    Hello
    I tried reading this forum and tried IMO everything but computer still gets BSOD. I'm including Dump File. I don't know how to read it. Any advice?
    http://sdrv.ms/1gwJEKq
    What I did:
    memtest86 - passed
    ccleaner
    regcleaner
    antivirus scan
    reinstalled drivers
    chkdsk
    I have mirrored drives on windows. It shows 'resynching'. Could it be failing and causing the problem?

    Mindau
    This one crash was Related to the
    nvvad64v.sys NVIDIA Virtual Audio Driver from NVIDIA Corporation  I would install the newest driver available.
    Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Ken\Desktop\013114-22495-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (12 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
    Machine Name:
    Kernel base = 0xfffff800`03467000 PsLoadedModuleList = 0xfffff800`036a3e70
    Debug session time: Fri Jan 31 05:39:43.583 2014 (UTC - 5:00)
    System Uptime: 0 days 0:00:28.095
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck D1, {10, 2, 0, fffff880044f8689}
    *** WARNING: Unable to verify timestamp for nvvad64v.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvvad64v.sys
    Probably caused by : nvvad64v.sys ( nvvad64v+1689 )
    Followup: MachineOwner
    8: 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: 0000000000000010, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff880044f8689, address which referenced memory
    Debugging Details:
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000370e0e0
    GetUlongFromAddress: unable to read from fffff8000370e198
    0000000000000010 Nonpaged pool
    CURRENT_IRQL: 2
    FAULTING_IP:
    nvvad64v+1689
    fffff880`044f8689 488b4810 mov rcx,qword ptr [rax+10h]
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    BUGCHECK_STR: 0xD1
    PROCESS_NAME: audiodg.exe
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    TRAP_FRAME: fffff8800eb894c0 -- (.trap 0xfffff8800eb894c0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80179a6fd0
    rdx=0000000000003fdc rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880044f8689 rsp=fffff8800eb89650 rbp=0000000000000000
    r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
    r11=fffffa80179a6fd0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    nvvad64v+0x1689:
    fffff880`044f8689 488b4810 mov rcx,qword ptr [rax+10h] ds:00000000`00000010=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER: from fffff800034d5de9 to fffff800034d6880
    STACK_TEXT:
    fffff880`0eb89378 fffff800`034d5de9 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0eb89380 fffff800`034d4a60 : 00000000`00000000 00000000`0000100c fffffa80`1611a260 fffff880`035e61c0 : nt!KiBugCheckDispatch+0x69
    fffff880`0eb894c0 fffff880`044f8689 : 00000000`0031c8d3 fffffa80`179a4000 00000000`00000000 fffff800`03665888 : nt!KiPageFault+0x260
    fffff880`0eb89650 00000000`0031c8d3 : fffffa80`179a4000 00000000`00000000 fffff800`03665888 00000000`00000028 : nvvad64v+0x1689
    fffff880`0eb89658 fffffa80`179a4000 : 00000000`00000000 fffff800`03665888 00000000`00000028 00000000`00524fbc : 0x31c8d3
    fffff880`0eb89660 00000000`00000000 : fffff800`03665888 00000000`00000028 00000000`00524fbc 00000000`00002fbc : 0xfffffa80`179a4000
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    nvvad64v+1689
    fffff880`044f8689 488b4810 mov rcx,qword ptr [rax+10h]
    SYMBOL_STACK_INDEX: 3
    SYMBOL_NAME: nvvad64v+1689
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nvvad64v
    IMAGE_NAME: nvvad64v.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 529fb649
    FAILURE_BUCKET_ID: X64_0xD1_nvvad64v+1689
    BUCKET_ID: X64_0xD1_nvvad64v+1689
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:x64_0xd1_nvvad64v+1689
    FAILURE_ID_HASH: {58ea0214-7b27-7dc6-5a00-c215a7e166cc}
    Followup: MachineOwner
    Wanikiya and Dyami--Team Zigzag

  • Windows crashing with kernal_security_check_failure

    A few months ago my pc started crashing. As time went on, the crashes because more consistent. Now it crashes after about 30min of it running every time I boot it up. The error i'm getting is the kernal_security_check_failure. Here are my .DMP files: https://www.dropbox.com/s/ci66qynoby61vo0/DMP.rar?dl=0
    Any help would be really appreciated!
    -Thanks in advance :)  

    Hello Ches Rowe,
    I apologize for the delay.
    About the shared link, I got the error message ‘The file you're looking for has been moved or deleted.’
    Please upload to OneDrive and share it with us.
    Upload to OneDrive:
    http://windows.microsoft.com/en-us/onedrive/add-photos-files
    Share files:
    http://windows.microsoft.com/en-us/onedrive/share-file-folder
    Please take a look at the following article about resolving stop (blue screen) errors.
    http://windows.microsoft.com/en-us/windows7/resolving-stop-blue-screen-errors-in-windows-7
    1. Undo recent changes using system restore
    2. Check windows updates for software updates
    3. Search for drivers on the manufacturer’s websites
    4. Check your computer for hard disk and memory error
    Best regards,
    Fangzhou CHEN
    Fangzhou CHEN
    TechNet Community Support

  • G570 Crashes with BSOD on startup

    In Februrary, my trusty T61P Thinkpad failed with the well-known GPU failure while on a business trip in Melbourne, Australia.  The only option was a motherboard replacedment as $600-700 so I had to buy another laptop downunder and ended up with a cheap G570 to get me through for a few months.  It is now failing on startup. When it reaches the Win 7 desktop, I get a BSOD that reads: PAGE_FAULT_IN_NONPAGED_AREA
    See this link for some details on the error and its causes: http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023%28v=vs.85%29.aspx
    I have tried every possible remedy.  I have run a chkdsk /f /r which thoroughly scanned the hard drive and reported no NTFS file system errors.  I have booted from a CD into memtest86+ and run the tests for several hours on the RAM.  It passed all tests and did not report any RAM errors.
    I have booted into Advanced Options|Last known good configuration from the F8 menu and run a Windows repair which reports that it cannot fix the problem.
    Based on the possible causes for this memory related error, my guess it that the CPU had a cache memory failure or video card RAM problem (I don't know if this model has dedicated video RAM).
    The error occured when I tried to hook up an external monitor to the VGA port.  I have run projectors off this laptop with no problems several times.  The desktop locked up and when I rebooted, the page_fault error occured and has been with me ever since.
    When I boot into Safe Mode, I get a totally black desktop and can do nothing but power off the computer and reboot
    It boots fine and lets me login, but, when the desktop loads, its BSOD time.  Any ideas?

    Hi Hoopster,
    First of all - I'm sorry for Your T61p, it is a great machine indeed.
    You can check detailed specification on this page or google Your product ID number - the one that starts with 59-. The BSOD You have (0x50, am I correct?) may indicate L2 cache issue, in this case try the Intel Processor Diagnostic Tool. If you have a discrete GPU try some third-party diagnostic tool like Video Card Stability Test.
    You can also try downloading a bootable Linux distribution and trying to duplicate the issue by stressing the CPU and/or GPU.
    T60/T618895-W4M, UXGA, T9300, 8GB RAM, Vertex3, Intel 6300 Win8.1
    R61e 7649-W1Z, T7250, Intel 6300

  • Windows Crashes with JRE 1.4.2  When Moving around JDialog

    Hi!
    I work on a Java Applet/application that was originally written to run on java 1.1 -- only AWT that too. Recently I managed to convince my manager (and his manager and his manager) to migrate from the AWT framework on java 1.1 (Microsoft JVM that is ) to Swing/JFC on Sun Java 1.4.2 ... it took a lot of explaining, demostrating, begging, pleading etc., to get this project funded.
    Now, my app is all developed in JFC and ready for deployment and during testing found a potential show stopper -- When a Dialog Box or any moveable componant (internal windows etc) is moved around (holding down the mouse on the title bar of a dialog and dragging it around), the OS simply froze up ... nothing could be done other than power cycling the PC. Does anyone know if its a bug in JRE 1.4.2 and if it has been fixed?? This could potentially result in rolling back to AWT :(( .... and of course me looking like a fool in front of my manager!!
    ..... Please provide any suggestion other than moving to JRE 1.5.x beta. I've also noticed this happening in other Java Applications (Netbeans for example). So, I think this is a major bug the JRE 1.4.2.
    A million thanks and few Duke Dollars for anyone pointing me in the right direction.
    Note:
    1. This problem is not just with my app ... some other java apps that are installed on my workstation (like netbeans) behave the same when Moving Around dialog boxes.
    2. The behaviour is very random. But it has happened multiple times (and the very first time my manager run our app on jre 1.4.2)
    I would give a million dollars if I had them. But for now, please do with the million thanks and few duke dollars.

    Have you tried this on another machine?Yes ... actually this has happened on a few workstations here ... all of them are Pentium IV based dell workstations running Windows 2000.
    What exact version of 1.4.2 did you download?Java(TM) Plug-in: Version 1.4.2_04
    Using JRE version 1.4.2_04 Java HotSpot(TM) Client VM
    Have you searched the bug database? This one could be related to yours:
    http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4673572
    This sounds similar but the difference is its not just the app that feezes up (so that you could do an alt+ctrl+del and kill it)..... the OS freezes up and you can move the mouse around still the system even queu e is not full and eventuall all I hear is the beeping. At this point I've to power cycle.
    Is there any way you could post the code or is it too big? Or, have you tried just creating a very small >application or applet that just shows one dialog, and if so, does that show the same problem? (What I'm >trying to get at here is - is it something in your code that is causing this, or something in the JRE, or >perhaps something to do with your machine's configuration/OS?)Unfortunately I cannot post the code ... its company rules and regulations. I've tried creating a very small app and it appears to work ok .... but randomly causes this freeze up. There is no definate pattern (except that it happens when you move around a JDialog or a JInternalFrame) . It could freeze up some time and work perfectly fine at other times. It has actually happened on other applications too (Netbeans, JEdit etc). That's why I suspect this might be a obscure bug in the JRE.
    I'll try to find a pattern so that it can be re-produced by everyone.
    Thanks for the help.

  • Windows Crashes with JRE 1.4.2

    Hi!
    I work on a Java Applet/application that was originally written to run on java 1.1 -- only AWT that too. Recently I managed to convince my manager (and his manager and his manager) to migrate from the AWT framework on java 1.1 (Microsoft JVM that is ) to Swing/JFC on Sun Java 1.4.2 ... it took a lot of explaining, demostrating, begging, pleading etc., to get this project funded.
    Now, my app is all developed in JFC and ready for deployment and during testing found a potential show stopper -- When a Dialog Box or any moveable componant (internal windows etc) is moved around (holding down the mouse on the title bar of a dialog and dragging it around), the OS simply froze up ... nothing could be done other than power cycling the PC. Does anyone know if its a bug in JRE 1.4.2 and if it has been fixed?? This could potentially result in rolling back to AWT :(( .... and of course me looking like a fool in front of my manager!!
    ..... Please provide any suggestion other than moving to JRE 1.5.x beta. I've also noticed this happening in other Java Applications (Netbeans for example). So, I think this is a major bug the JRE 1.4.2.
    A million thanks and few Duke Dollars for anyone pointing me in the right direction.
    Note: I would give a million dollars if I had them. But for now, please do with the million thanks and few duke dollars.

    I seriously doubt that it's a jvm flaw (possible, but very unlikely). Start stripping out code until you get down to a minimum size that still exhibits the problem. If then you can't clear it, post the minimal code and some information as to what's happening - you may want to try an analyzer.
    If the problem appears to be a GUI issue, post into the Swing forum, otherwise post into the Java Programming forum - more people read those.

  • Windows crashes with Blue Screen

    i'm working with windows XP and after installing the BB Desktop software, i get quite often a blue screen.... Can anybody help me with this? Is a special Service pack necessary to run it properly? Thanks in advance for any help.
    J-P

    Which version of desktop manager you're trying to install?
    tanzim                                                                                  
    If your query is resolved then please click on “Accept as Solution”
    Click on the LIKE on the bottom right if the post deserves credit

  • Windows Crashes with Bootcamp Driver Instal

    Just loaded Windows XP SP2 on my new IMac...partition and Windows load went fine. When I loaded the OSX Windows drivers, per the instructions, after quite a few driver installations, the blue screen of death came up stating Windows was closed due to errors (twenty digit error number...who in the world would know what that means). This happened several times after numerous attempts. Bottom line; everything (Internet, ISight, etc.) in Windows works except no sound...so a lot of drivers where loaded. Downloaded the latests Apple update for windows and latests windows update. Device manager states all audio codecs, etc. are fine...but no audio is detected in audio manager, and no sound. Sound in OSX is fine. I suppose there is a driver download available, but I could not find a sound driver on the OSX install disk for bootcamp...if there is one in the OSX install disk, you'd need to be a cryptologist to figure out which one it is. So, could the OSX disk be bad for the driver install?? If so, would that screw up the Apple for Windows update, which should have loaded the right drivers??

    For MacPro 2008, BootCamp (OSX Disk 1)->Drivers->RealTekSetup.exe (Not in a sub folder) is the audio in my case. You should be able to run individual rather than whole BC setup.

  • Windows 7 crashes after disconnecting iPhone 3GS iOS 5 with BSOD 1000007e?

    Ever since i have update iOS 5 on my iPhone 3GS after disconnecting the usb cable my windows 7 system crashes with BSOD 1000007e and restarts and this happens all the time. When it is connected no issues only after disconnecting you get this BSOD 1000007e. It was not an issue on iOS 4.3.5? I have updated all the drivers and removed all the softwares which can cause a problem also i have disconnected all possible usb devices now my webcam, bluetooth are connected internally so i hv no option to remove them? what shud i do different here?
    =====================================
    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7601.2.1.0.256.1
      Locale ID:    16393
    Additional information about the problem:
      BCCode: 1000007e
      BCP1:    C0000005
      BCP2:    82C4658A
      BCP3:    8AF40B78
      BCP4:    8AF40750
      OS Version:    6_1_7601
      Service Pack:    1_0
      Product:    256_1
    Files that help describe the problem:
      C:\Windows\Minidump\102211-18408-01.dmp
      C:\Users\iMyPc\AppData\Local\Temp\WER-47393-0.sysdata.xml
    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt
    ==========================================================

    Instructions on restoring the phone as a new device are found in the iPhone User Guide
    http://manuals.info.apple.com/en_US/iphone_user_guide.pdf

Maybe you are looking for