BSOD in Windows 7 on 5 MacMini's

I have been trying to determin what the cause is of this for over a week now but I am getting really frustrated with constant failures and could use a little direction.
I have 5 Macmini's that I am setting up for work with Windows 7 x64. This is a VLK version not retail. Four of the Mini's are late 2012 Models, one is a mid 2010 version. The 2012 Mini's are running Bootcamp 4.1 software and the 2010 Mini is running Bootcamp 3.3 software. They all seem to function correctly except for the random shutdown after a BSOD. Most of the time it happens after work hours or maybe once or twice during the day when I am not around to see it. Below is an image with some information about the crash:
I thought at first it was a bad copy of the OS so I burned a new disk from the VLK image we have on a server, and also tried an official Retail Disk that I had as well but both still gave the BSOD. So I thought maybe an update is problematic so I installed it with only Bootcamp drivers and Kaspersky but it is still giving the BSOD. The image above is from this last minimal attempt. It is always the same BSOD error though Paramiter 2, 3, and 4 are slightly different. I don't really have much exp reading and understanding dump files so not sure what to do next. I will post a link to the dump file once I get it uploaded.

The drivers are fine? the systems are at least running something to report temps? there is almost zero support for the fans in Windows to respond to thermal sensors.
Windows is good in one respect, it will react more often to marginal and bad RAM that is not picked up with AHT or OS X and there is Windows own single user memory test utility.
Same pretty much true for weak and bad disk sectors.
So ruling out the OS and trying to rule out drivers. Apple drivers for accessing HFSX volumes is a bit weak (and if you did have an Apple software RAID online it would crash but usually that is on startup when it tries to access and mount all volumes‚.

Similar Messages

Z61p ATI Mobility FireGL BSOD on Windows 7 64 bit

Am having many BSOD and 'windows reported and error'
... Have tried Lenovo 64 driver 8.361 per system update, tried 8.561 per Vista 64 / Win 7 on Lenovo Support and now trying ATI Beta 10.1 CCC pack.
All crash and burn
Recreating: ... Either try any of the Catalyst Control Centre 3D setting - trip down to DOA machine
or
work for a while and periodically when doing non 3D things such as trying to watch a DVD or web browsing ... Windows BSOD with dump ... 'Windows has recovered from and error ...'
Has anyone found a solution to this?
IBM pointed me to two Lenovo web pages about support for Windows 7 - basicaly the Z series ThinkPads are not listed ????
Any help would be welcome.
Rgs
Bruce

Give this a shot at your own risk, although some people on TPF have been praising it...
http://forums.mydigitallife.info/archive/index.php/t-13124.html
The only reason why I'm saying "at your own risk" is because I haven't tested it personally, because I don't have a machine running W7 with an appropriate GPU.
Good luck.
Cheers,
George
In daily use: R60F, R500F, T61, T410
Collecting dust: T60
Enjoying retirement: A31p, T42p,
Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

BSOD in Windows 7 x64 Nvidia Graphics Driver problem Is there a solution

Help me!!! This looks familiar =)
I have just came out of the multiple BSOD in windows 7 and have been on the BSOD Microsoft Boat for about 2 weeks.
Stats:
Asus MotherBoard, amd fx 8core processor, nvidia graphics card, 650watt power supply
This is crap an has to stop, Is there any help.
NVLDDMKM.sys is obviosly the culprate ...

So I disabled the driver using the right mouse click on the computer icon in the start menu yeah the Icons are huge but as long as I dont get the BSOD I can live with that thankx
lol
Once again its on!!! lol
Please start by updating NVLDDMKM.sys driver. You can also report that to NVIDIA Technical Support.
If this does not help, proceed like 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
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

BSOD in Windows XP after connecting a USB hard drive

Hi everyone!
I have a mid 2009 iMac i5. After plugging in an external hard drive I get a BSOD in Windows XP SP3.
I first installed Win XP using Bootcamp and later on I also installed Parallels 6.0
to avoid rebooting in order to get to Win XP. Windows running on Parallels displays BSOD as well
when a hard drive is plugged in.
Everything works fine under Mac OS X (latest version available).
Thank you in advance for any suggestions.
Lukasz

Fingers crossed we might be able to track down the cause of the problem by interrogating minidumps of the blue screens with Windows debugging tools.
So first we'd better check to see if your PC has been collecting minidumps of the crash.
Open My Computer, and see if you can find a directory called C:\Windows\Minidump. (That's where minidumps usually go on a PC, so long as the Systemroot hasn't been set to some other folder.)
If it's been collecting minidumps, there should be files in there with names like "Mini(number-numbers).dmp" or just "(numbers-numbers).dmp".
(If you have "Hide filename extensions for known file types" enabled on the PC, the ".dmp" extension may not appear on the dump files. The numbers in the file name will be different for each minidump, if minidumps are present.)
Are there any minidumps about on the PC? If so, we'll go digging in them.
1. Download and install the Windows debugging tools from here:
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
2. Go "Start > All Programs > Debugging Tools For Windows > Windbg". Once you open Windbg, you will presented with a blank screen.
3. Click on "File > Symbol File Path". Here you will enter the symbols path. Symbols are needed to effectively debug.The path will be:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
4. Enter in this path and click OK. Now, go to "File > Save Workspace" so that your symbols path is saved for future use.
5. Go to "File > Open Crash Dump" and load the file.
(An "Open Crash Dump" screen will appear ... doubleclick "My Computer", doubleclick "Local Disk", doubleclick "Windows", doubleclick "Minidump", and doubleclick on one of the minidumps in there that was generated at the same time as the Classic was plugged in.)
You will/should get a message to save base workspace information. Choose no.
Now you will get a debugging screen. It takes a little bit to run it, as the symbols have to be downloaded as they are needed.
After the "bugcheck analysis" part of the screen comes up, look for the component that seems to be causing the crash. (It'll say "Probably caused by" ...)
Let us know the precise name of the component. (Include any file name extensions like .dll or .sys.)
If you can, have a look at several of your crash dumps generated by USB-pluggings-in. Are all the crashes being caused by the same component? If not, could you let us know the names of the various components being cited in the various crash dumps?

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

Storport.sys BSOD on Windows Server 2012 R2

I recently purchased a Server that houses 45 4TB drives to use as my backup to disk solution. I installed Windows Server 2012 R2 Standard so that I could take advantage of Microsoft's Storage Spaces. I have configured the Storage Pool
with Dual Parity with 3 hot spares. I have also updated every thing to the most current firmware, drivers and Windows Updates that I could find but I am still getting the BSOD. I am using Symantec Backup Exec 2010 R3 to backup my file server to this server.
It will run for anywhere between 12 to 31 hours transferring 1.5 to 3TB and then my server will Blue Screen and every time it Blue Screens it says it is caused by the storport.sys Driver. I've found articles talking about the storport.sys driver causing nonpaged
pool leaks but that was for Windows Server 2008 R2, I can't find anything for Windows Server 2012 R2. If you need additional information just let me know and I will provide it. Any help you can give would be greatly appreciated.

Hi,
This article provided the limitation of Storage Pool in Windows Server 2012 R2:
https://social.technet.microsoft.com/wiki/contents/articles/11382.storage-spaces-frequently-asked-questions-faq.aspx#What_are_the_recommended_configuration_limits
Yor current situation is still in supported configuration.
Also there is no hotfix for Windows Server 2012 R2 regarding storport.sys yet. Which means your current issue is not a known issue.
For further troubleshooting purpose you may need to collect dump files for analysis. However it will take a long time to do the troubleshooting process on forum. Thus it is recommended to submit a ticket to Microsoft online support for a professional troubleshooting.
To obtain the phone numbers for specific technology request please take a look at the web site listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you have any feedback on our support, please send to [email protected]

Perpetual BSOD on Windows 7 Enterprise machine

Hello guys, I have a Dell Optiplex 780 with Windows 7 Enterprise which makes me hard days trying to get it healthy. There is a BSOD once in a while, well basically weekly if not daily and I could't get rid of it.
The Log is:
Microsoft (R) Windows Debugger Version 6.2.9200.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [\\EB-OR1019945\c$\Windows\Minidump\011515-11310-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*;c:\symbols
Executable search path is: srv*
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`03010000 PsLoadedModuleList = 0xfffff800`03253890
Debug session time: Thu Jan 15 09:47:28.179 2015 (UTC + 2:00)
System Uptime: 0 days 10:53:13.263
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                        Bugcheck Analysis
Use !analyze -v to get detailed debugging information.
BugCheck 1, {77a1132a, 0, ffff, fffff88009921c60}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
Followup: MachineOwner
0: kd> !analyze -v
*                        Bugcheck Analysis
APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 0000000077a1132a, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff88009921c60, Call type (0 - system call, 1 - worker routine)
Debugging Details:
FAULTING_IP:
+0
00000000`77a1132a ??              ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x1
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80003085169 to fffff80003085bc0
STACK_TEXT:
fffff880`09921a28 fffff800`03085169 : 00000000`00000001 00000000`77a1132a 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffff880`09921a30 fffff800`030850a0 : 00000000`00000000 0000007f`ffffffff 00000000`00000000 00000980`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`09921b70 00000000`77a1132a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`00fbe318 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a1132a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSystemServiceExit+245
fffff800`030850a0 4883ec50        sub     rsp,50h
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiSystemServiceExit+245
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 531590fb
FAILURE_BUCKET_ID: X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245
BUCKET_ID: X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245
Followup: MachineOwner
I made a BIOS update, Video Card, Chipset, all windows updates ar done, antivirus also. I ran a check disk and a SFC Scan, non solved the problem yet..
Any help is much appreciated!

CV
Only one of the DMP files contained information. It was memory related and pointed to McAfee (yours is 3+ years old)> I would remove it and use MSE in its place and if you continue to crash I would run driver verifier
McAffe often contributes to BSOD'S
I would remove and replace it with Microsoft Security Essentials
http://download.mcafee.com/products/licensed/cust_support_patches/MCPR.exe
http://www.microsoft.com/security_essentials/
These crashes were related to memory corruption (probably caused by a driver).
Please run these two tests to verify your memory and find which driver is causing the problem. Please run verifier first
If you are over-clocking anything reset to default before running these tests.
In other words STOP!!!
If you do not know what this means you probably are not
1-Driver verifier (for complete directions see our wiki here)
2-Memtest. (You can read more about running memtest here)
Wanikiya and Dyami--Team Zigzag

BSOD with Windows 8.1 Pro 64 bit

I'm having a strange problem here, I had been experincing daily BSODs, so i figured perhaps my windows install got corrupted, and did a full format/Reinstall. I seem to still be getting BSODs however, so i dug into the dump files, and discovered, its saying Skype is responsible. I am running Skype Desktop 7.2 and I do NOT have a HP Fixed Webcam or any webcam, as i've seen as the common culprit around these fourms.
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff802ddb6102c, Address of the instruction which caused the bugcheck
Arg3: ffffd000221a9d90, 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:
nt!KxWaitForLockOwnerShipWithIrql+14
fffff802`ddb6102c 48890a mov qword ptr [rdx],rcx
CONTEXT: ffffd000221a9d90 -- (.cxr 0xffffd000221a9d90;r)
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd000221aa810
rdx=0000800000000000 rsi=ffffe001ce7ff080 rdi=ffffd000221aa810
rip=fffff802ddb6102c rsp=ffffd000221aa7c0 rbp=0000000000000001
r8=ffffd000221aa860 r9=0000000000000000 r10=fffff901400020f8
r11=fffff9014519c228 r12=0000000000000000 r13=0000000000000000
r14=0000000000010001 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010046
nt!KxWaitForLockOwnerShipWithIrql+0x14:
fffff802`ddb6102c 48890a mov qword ptr [rdx],rcx ds:002b:00008000`00000000=????????????????
Last set context:
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd000221aa810
rdx=0000800000000000 rsi=ffffe001ce7ff080 rdi=ffffd000221aa810
rip=fffff802ddb6102c rsp=ffffd000221aa7c0 rbp=0000000000000001
r8=ffffd000221aa860 r9=0000000000000000 r10=fffff901400020f8
r11=fffff9014519c228 r12=0000000000000000 r13=0000000000000000
r14=0000000000010001 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010046
nt!KxWaitForLockOwnerShipWithIrql+0x14:
fffff802`ddb6102c 48890a mov qword ptr [rdx],rcx ds:002b:00008000`00000000=????????????????
Resetting default scope
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: Skype.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre
LAST_CONTROL_TRANSFER: from fffff802ddafe668 to fffff802ddb6102c
STACK_TEXT:
ffffd000`221aa7c0 fffff802`ddafe668 : ffffe001`cff817e0 fffff901`4519c005 00000000`00000001 fffff802`ddaf2e16 : nt!KxWaitForLockOwnerShipWithIrql+0x14
ffffd000`221aa7f0 fffff802`ddafd37b : 00000000`80000002 ffffe001`cff817e0 00000000`00000000 00000000`00000000 : nt!ExAcquireResourceExclusiveLite+0x218
ffffd000`221aa860 fffff960`001f71fc : ffffe001`cff817e0 00000000`00000000 00000000`00000000 00000000`7f3ad000 : nt!ExEnterCriticalRegionAndAcquireResourceExclusive+0x1b
ffffd000`221aa890 fffff960`002c8f80 : 00000000`80000002 ffffe001`cff817e0 00000000`00000000 00000000`00000000 : win32k!EngAcquireSemaphore+0x1c
ffffd000`221aa8c0 fffff960`002c8f56 : 00000000`00000000 ffffd000`221aa9e0 00000000`00000000 fffff960`001f5e5d : win32k!GreAcquireHmgrSemaphore+0x10
ffffd000`221aa900 fffff960`001ffbce : 00000000`00000000 00000000`00000000 00000000`80000012 00000000`0000177c : win32k!MLOCKFAST::MLOCKFAST+0xe
ffffd000`221aa930 fffff960`002017f9 : 00000000`000021e4 00000000`00000000 00000000`5401177c 00000000`00000000 : win32k!HmgDecProcessHandleCount+0x1e
ffffd000`221aa960 fffff960`001d5487 : fffff901`402333a0 00000000`80000012 00000000`00000001 fffff901`00000001 : win32k!GreSetDCOwnerEx+0x413
ffffd000`221aaa00 fffff960`002000c6 : 00000000`00000000 ffffd000`221aab00 00000000`5401177c 00000000`7f3ad000 : win32k!ReleaseCacheDC+0x107
ffffd000`221aaa40 fffff802`ddbe31b3 : ffffe001`ce7ff080 ffffd000`00000014 00000000`7f3af000 00000000`00000000 : win32k!NtUserCallOneParam+0xe6
ffffd000`221aaa80 00000000`77ce59ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03e5e218 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ce59ea
FOLLOWUP_IP:
win32k!EngAcquireSemaphore+1c
fffff960`001f71fc 4883c420 add rsp,20h
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: win32k!EngAcquireSemaphore+1c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 54ee5a22
IMAGE_VERSION: 6.3.9600.17694
STACK_COMMAND: .cxr 0xffffd000221a9d90 ; kb
BUCKET_ID_FUNC_OFFSET: 1c
FAILURE_BUCKET_ID: 0x3B_win32k!EngAcquireSemaphore
BUCKET_ID: 0x3B_win32k!EngAcquireSemaphore
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x3b_win32k!engacquiresemaphore
FAILURE_ID_HASH: {91ce18ba-878a-ee79-a2df-29f0d12dd984}
Followup: MachineOwner
Now I don't pretend to understand what all that means, but it says skype specifically, so its the only clue i have right now.
Thanks for any help.

Please, run the DirectX diagnostics tool.
Go to Windows Start and in the Run box type dxdiag.exe and press the OK button. This will start the DirectX diagnostics program. Run this diagnostics and save the results to a file. Please, attach this file to your post.
Be aware that you will have to zip this file before attaching it here.

How Do I Install Windows 7 Or Windows XP on Apple MacMini 2006 1.1

Hello ,
I could use some help please with installing Windows 7 or Xp (If Supported) on MacMini 1.1 2006 upgraded.
The problem is that the superdrive is not working ,and I have swapped it with the one from the MacBook Pro and I got some errors during the installation to do with the Disk inserted being damaged although I have tested the DVD before and after and it is fine.
Is there any other way of installing Windows via Bootcamp from the USB, because when I restart the Mac Mini with the Windows Bootable USB in it won't see the USB & on the boot screen is asking to insert boot device

Hi, don't know much about Bootcamp, but is this Win7 32 bit... or 64 bit, which I don't think will work on yours?
Without Botcamp & if you don't need Windows for speed, like gaming...
Parallels...
http://www.parallels.com/
VmWare Fusion...
http://www.vmware.com/mac
VirtualBox...
http://www.virtualbox.org/wiki/Downloads

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 Overlay Filter (wof.sys), file in Windows 8.1, is associated with BSOD in Windows 10 bld 9879

BSOD in Win 10 build 9879 is with bug check 0x1e. Wof.sys is a file that is in Win 8.1. HP g7-1310us (refurbished) laptop has been having BSOD's even when it had Win 7 installed. Checked RAM, hardware, and SATA disk but there is no specific lead to why BSOD's
happen routinely. Interestingly, there were no problems while this laptop was running Ubuntu 14. Any details on what Windows Overlay Filter driver named wof.sys does? Also, could this error be caused by faulty CPU? It has an Intel i3-2350M CPU @2.3Ghz, x64
based processor.
==================================================
Dump File         : 121114-22984-01.dmp
Crash Time        : 12/11/2014 5:23:05 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : ffffffff`c0000005
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000008
Parameter 4       : 00000000`00000000
Caused By Driver : Wof.sys
Caused By Address : Wof.sys+1e40
File Description : Windows Overlay Filter
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.4.9879.0 (fbl_release.141103-1722)
Processor         : x64
Crash Address     : ntoskrnl.exe+161109
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\121114-22984-01.dmp
Processors Count : 4
Major Version     : 15
Minor Version     : 9879
Dump File Size    : 282,776
Dump File Time    : 12/11/2014 5:26:16 PM
==================================================
Gilda Sanchez

Here is the CPU data:
Intel(R) Processor Identification Utility
Version: 5.01.20140910
Time Stamp: 2014/12/11 19:28:20
Operating System: 6.2-9200-
Number of processors in system: 1
Current processor: #1
Active cores per processor: 2
Disabled cores per processor: 0
Processor Name: Intel(R) Core(TM) i3-2350M CPU @ 2.30GHz
Type: 0
Family: 6
Model: 2A
Stepping: 7
Revision: 29
Maximum CPUID Level: D
L1 Instruction Cache: 2 x 32 KB
L1 Data Cache: 2 x 32 KB
L2 Cache: 2 x 256 KB
L3 Cache: 3 MB
Packaging: µPGA/BGA
Enhanced Intel SpeedStep(R) Technology: Yes
MMX(TM): Yes
Intel(R) SSE: Yes
Intel(R) SSE2: Yes
Intel(R) SSE3: Yes
Intel(R) SSE4: Yes
Intel(R) AES-NI: No
Intel(R) AVX: Yes
Enhanced Halt State: Yes
Execute Disable Bit: Yes
Gilda Sanchez

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.

BSOD Error Windows 2008 R2 Terminal Server

Hi guys
I have a unique issue on a Windows 2008 R2 Enterprise Terminal Server where it keeps blue screening every so often (from every 2 or 3 days to some times once a week) with the exact same BSOD error. After countless hours Googling and researching I am simply
at a dead end and desperately require some guidance if possible. I have ran malware bytes and other tools and the TS does not have any malware or viruses. I have ran a chkdsk and everything is also okay with that.
It has happened about 5 times now with the same errors every time:
29/05/2014 09:42:18
Bug Check String: CRITICAL_OBJECT_TERMINATION
Bug Check Code: 0x000000f4
Parameter 1: 00000000`00000003
2: fffffa80`243c5060
3: fffffa80`243c5340
4: fffff800`01bc70d0
Caused by driver: ntoskrnl.exe
Caused by address: ntoskrnl.exe+75b80
Processor: x64
I have uploaded the DMP to OneDrive: edit: it won't let me post a link until my account is verified?
Thanks
Dan

Hi,
Thank you for posting in Windows Server Forum.
The problem which you are facing seems to be due to ntoskrnl.exe. There might be some corruption in ntoskrnl.exe file.It’s responsible for various system services such as hardware virtualization, process and memory management, thus making it a fundamental part
of the system. It contains the cache manager, the executive, the kernel, the security reference monitor, the memory manager, and the scheduler.
Please check below articles to fix the issue of ntoskrnl.exe.
1. NTOSKRNL.EXE is missing or corrupt
2. How to Fix Ntoskrnl.exe Missing or Corrupt Error
Hope it helps!
Thanks.
Dharmesh Solanki

Error 1401 when installing Acrobat 9 Std on Windows 8.1 on MacMini running Parallels

I am running Windows 8.1 using Parallels version 10.1.3 on a MacMini running OS X 10.10.1. Partway through the install when the status is "Writing system registry values" I get this error:
"Error 1404. Could not create key \Software\Microsoft\Internet Explorer\MenuExt\Convert to Adobe PDF. Verify that you have sufficient access to that key, or contact your support personnel."
FYI: I have installed and and uninstalled this very product several times before on my previous machine, but that was running Windows Pro in a bootcamp situation, not through Parallels.
Thank you for any help at all.
Sandi

Moving this discussion to the Acrobat Installation & Update Issues forum.

Apple iTunes 10.0.1 = BSOD in Windows 7

Okay! I always upgrade to the latest version of software, chiefly as a test bed for others with whom I consult. I have been running Windows 7 since it was released (well before actually ).
I have never ever had a BSOD for any reason on ANY of my Windows 7 machines. Until today. I upgraded iTunes from 10.0.68 to 10.0.1, and now, as I navigate around iTunes, I either get a program has stopped working and will be closed message, or the BSOD. The BSOD message, high flyover is the error was in Memory_Management.
Here are my computer specs:
Model: HP Pavilion DV6756
OS: Windows 7 64-bit
Memory: 3 Gigabytes
CPU: Intel Centrino
Anyone else having as much fun as I am?

I see the system has been saving memory dumps for the crashes. With any luck, if we interrogate the dump files with the 64-bit version of WinDbg, we can track down the component causing the crash.
1. Download and install the 64-bit version of Windows debugging tools from here:
http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx
2. Go to Start, All Programs, Debugging Tools For Windows, Windbg
Once you open Windbg, you will presented with a blank screen.
3. Click on "File > Symbol File Path". Here you will enter the symbols
path. Symbols are needed to effectively debug.
The path will be:
SRVc:symbolshttp://msdl.microsoft.com/download/symbols
4. Enter in this path and click OK. Now, go to "File > Save Workspace"
so that your symbols path is saved for future use.
5. Go to "File > Open Crash Dump" and load the file.
(An "Open Crash Dump" screen will appear ... navigate to C:\Windows\MEMORY.DMP\, or C:\Windows\Minidump\, and doubleclick on one of the dump files there.)
If you get a dialog at this point saying you don't have permission to open the file, try this: OK out of the permission warning dialog. Right-click on the dump file (In the "Open Crash Dump" screen), and select "Properties". Click the "Security" tab. Click the "Advanced" button. Click "Continue". Check the "Include inheritable permissions from this object's parent" checkbox, and click OK. Click Yes when the Windows security box comes up. Close the "properties" screens at this point, and go back to "Open Crash Dump", and try doubleclicking on the dump file again.
You will/should get a message to save base workspace information. Choose no.
Now you will get a debugging screen. It takes a little bit to run it,
as the symbols have to be downloaded as they are needed.
After the "bugcheck analysis" part of the screen comes up, look for the component that seems to be causing the crash.
Let us know the precise name of the component. (Include any file name extensions like .dll or .sys.)
If you can, have a look at several of the dumps that seem to be associated with the BSODs. Are all the crashes being caused by the same component? If not, could you let us know the names of the various components being cited in the various crash dumps?

BSOD in Windows 7 on 5 MacMini's

Similar Messages

Maybe you are looking for