Blue Screen of Death on bootcamp windows 7?????

I had this problem since march and i never knew how to fix it everytime i watch a video i get the BSOD on windows 7 with bootcamp on the mac mini 2010 model. I bought a game that needed my nvidia 320m graphics updated and the update change my graphics to the 3D nvidia???? So now when i watch a video i get the BSOD. I could watch a video fine on snow leopard 10.6.1 with the mac shutting down....
Is this a windows 7 problem or is it the graphics??????

A. Heat
B. Did you manage to install the mobile driver correctly?
C. Dont' rule out memory errors - OS X I've come to learn is much more forgiving and Windows will not tolerate marginal / defective RAM
D. Did I say heat and lack of fan control?
E. I really see a lot of posts Mac-Mini owners have trouble with Windows....
http://www.nvidia.com/Download/index.aspx
http://www.nvidia.com/object/notebook-win7-winvista-64bit-296.10-whql-driver.htm l
These are from updating AMD drivers so basics are the same:
https://discussions.apple.com/thread/3346432
AMD Mobility (April 2012) Windows 7 64-bit
http://support.amd.com/us/gpudownload/windows/Pages/radeonmob_win7-64.aspx
The Unofficial TOR and Boot Camp Discussion Thread
http://www.swtor.com/community/showthread.php?t=11234
Bootcamp and Low FPS? Fix it here!
http://www.swtor.com/community/showthread.php?t=105045
Installing DirectX 11 on Boot Camp Windows 7
http://maxcho.com/2012/02/installing-directx-11-on-boot-camp-windows-7/
Driver Sweeper (3.2)
http://www.softpedia.com/get/Security/Secure-cleaning/Driver-Sweeper.shtml
Driver Sweeper does a better job of removing all the remnants of and does not leave behind files, registry entries that just using Programs control panel will. And always recommended for GPU driver uninstall and issues.
Another tip: don't let Windows install its own base graphic drivers, they are never as good or can cause some problems. Even if you install Nvidia driver over the one's Windows installed.

Similar Messages

K9N2 SLI Platinum Blue Screen of Death when installing Windows XP

My hardware includes:
•   MSI K9N2 SLI Platinum Motherboard
•   Corsair XMS2 TWIN2X4096-6400C5
•   GeForce 9800 GT 512MB GDDR3
•   AMD Phenom X4 9850 Quad Core Processor, Black Edition 2.5GHz
4MB Cache 2000MHz [4000 MT/s] FSB
•   Thermaltake Ruby Orb Aluminum Core CPU Cooler
•   UltraX3 850 Watt ATX Modular Power Supply
•   [1] Western Digital 200MB7200 ATA133 [Not connected yet]
•   [1] Maxtor 80MB ATA133 Drive [Not connected yet]
•   [1] Western Digital 500GB 7200RPM 16MB SATA II HARD DRIVE
•   [2] Seagate 7200.11 ST3500320AS 500GB SATA Hard Drives With 32 MB Cache
[Not connected yet]
•   LG DVD-RW
•   Toshiba DVD-ROM [Not connected yet]
•   AMI Bios v02.61
•   Antec Full Tower case
After partitioning my drive with Fdisk I tried to install Win Xp. My plan was to format the drive with XP. XP starts up and runs through the initial system check then when it prepares to install I get the blue screen that says [my words] "Windows has shut down to prevent damage to your system. If drivers are mentioned try disabling them in the BIOS or get the latest bios update from the equipment manufacturer..." The error is:
Stop 0x0000007E on the next line
pci.sys - address f7480BFbase at f7487000 Datestamp 3b7d855c
Just never had these problems setting up a system and soon I will be able to say it took me 2 years to get this running. Hope someone can help. Thanks

Use XP Installation disk with SP2 or SP3 included to fix the BSOD.
Simple your XP installation disk is outdated and cause troubles with latest hardware.

Blue Screen of Death of multiple Windows Multipoint Servers at the same time in NUServer64.sys

Hi, we are running
Windows MultiPoint Server 2011 on 4 Dell 9010 machines and 45 Wyse E02 clients connected by 4 switches. Every week we got 2 or 3 random BSoD for all servers at the same time. Memory dump for server 2,3,4 show that the exception is from NUServer64.sys.
Please check below for the system event logs and memory dump analysis output. Any help would be appreciated!
server1:
Warning 11/17/2013 8:55:52 PM
e1cexpress 27
None
Critical 11/17/2013 8:55:48 PM
Kernel-Power 41
(63)
Error 11/17/2013 8:56:08 PM
BugCheck 1001
None
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000005, 0x0000000000000000, 0x0000000000000008, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 111813-19765-01.
Error 11/17/2013 8:56:03 PM
EventLog 6008
None
The previous system shutdown at 12:53:40 on 2013/11/18 was unexpected.
Error 11/17/2013 6:55:49 PM
Disk 11
None
The driver detected a controller error on \Device\Harddisk2\DR2.
Error 11/17/2013 6:55:48 PM
Disk 11
None
The driver detected a controller error on \Device\Harddisk2\DR2.
Warning 11/17/2013 3:42:08 PM
Microsoft-Windows-TerminalServices-Licensing
18 None
server2:
Warning 11/17/2013 8:55:39 PM
e1cexpress 27
None
Critical 11/17/2013 8:55:31 PM
Kernel-Power 41
(63)
Error 11/17/2013 8:55:52 PM
BugCheck 1001
None
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80002c80166, 0xfffff880023397e8, 0xfffff88002339040). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 111813-17518-01.
Error 11/17/2013 8:55:44 PM
EventLog 6008
None
The previous system shutdown at 12:53:53 on 2013/11/18 was unexpected.
Warning 11/17/2013 7:16:07 PM
NUServer64 3
None
server3:
Warning 11/17/2013 8:55:38 PM
Microsoft-Windows-TerminalServices-Licensing
18 None
Error 11/17/2013 8:55:31 PM
BugCheck 1001
None
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x000000000000009a, 0x0000000000417c94, 0x0000000000000006, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 111813-9937-01.
Warning 11/17/2013 8:55:24 PM
e1cexpress 27
None
Critical 11/17/2013 8:55:21 PM
Kernel-Power 41
(63)
Error 11/17/2013 8:55:27 PM
EventLog 6008
None
The previous system shutdown at 12:53:49 on 2013/11/18 was unexpected.
server4:
Warning 11/17/2013 8:55:33 PM
Microsoft-Windows-TerminalServices-Licensing
18 None
Warning 11/17/2013 8:55:09 PM
e1cexpress 27
None
Critical 11/17/2013 8:55:05 PM
Kernel-Power 41
(63)
Error 11/17/2013 8:55:25 PM
BugCheck 1001
None
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000100000001, 0x0000000000000002, 0x0000000000000001, 0xfffff8000328abe6). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 111813-14055-01.
Error 11/17/2013 8:55:14 PM
EventLog 6008
None
The previous system shutdown at 12:53:21 on 2013/11/18 was unexpected.
Error 11/17/2013 8:51:47 PM
NUServer64 4
None
\Device\NUServer_995D6600
<995D6600_3> Disconnect fail.
Error 11/17/2013 8:51:47 PM
NUServer64 4
None
\Device\NUServer_995D6600
<995D6600_3> Connect fail.
Warning 11/17/2013 8:51:47 PM
NUServer64 3
None
\Device\NUServer_995D6600
<995D6600_3> Connect time-out.
Warning 11/17/2013 8:50:00 PM
NUServer64 3
None
\Device\NUServer_995B9000
<995B9000_3> Hi-Perf socket active clear.
Error 11/17/2013 8:49:25 PM
NUServer64 4
None
\Device\NUServer_995D6600
<995D6600_3> Disconnect fail.
Error 11/17/2013 8:49:25 PM
NUServer64 4
None
\Device\NUServer_995D6600
<995D6600_3> Connect fail.
Warning 11/17/2013 8:49:25 PM
NUServer64 3
None
\Device\NUServer_995D6600
<995D6600_3> Connect time-out.

Memory dumps:
server1:
2: kd> !analyze -v
* Bugcheck Analysis *
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
+3031623733386137
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000008
EXCEPTION_PARAMETER2: 0000000000000000
WRITE_ADDRESS: 0000000000000000
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR: 0x1E_c0000005
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800c744860 -- (.trap 0xfffff8800c744860)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff8800c7449f0 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000f44 r10=fffff80003602000
r11=0000000000000358 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
00000000`00000000 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800036c2738 to fffff80003677bc0
STACK_TEXT:
fffff880`0c743fd8 fffff800`036c2738 : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
fffff880`0c743fe0 fffff800`03677242 : fffff880`0c7447b8 00000000`00000030 fffff880`0c744860 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x487ed
fffff880`0c744680 fffff800`03675dba : 00000000`00000008 00000000`00000000 00000009`00000000 00000000`00000030 : nt!KiExceptionDispatch+0xc2
fffff880`0c744860 00000000`00000000 : 00000000`00000030 ffffffff`fffe7960 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+487ed
fffff800`036c2738 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+487ed
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035
FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+487ed
BUCKET_ID: X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+487ed
Followup: MachineOwner
server2:
0: kd> !analyze -v
* Bugcheck Analysis *
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002c80166, The address that the exception occurred at
Arg3: fffff880023397e8, Exception Record Address
Arg4: fffff88002339040, Context Record Address
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!KeSetEvent+16
fffff800`02c80166 f6037f test byte ptr [rbx],7Fh
EXCEPTION_RECORD: fffff880023397e8 -- (.exr 0xfffff880023397e8)
ExceptionAddress: fffff80002c80166 (nt!KeSetEvent+0x0000000000000016)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000010f7f0a50
Attempt to read from address 000000010f7f0a50
CONTEXT: fffff88002339040 -- (.cxr 0xfffff88002339040)
rax=0000000000000000 rbx=000000010f7f0a50 rcx=0000000000000001
rdx=0000000000000000 rsi=fffffa800f7ec050 rdi=fffffa800f7ec1a0
rip=fffff80002c80166 rsp=fffff88002339a20 rbp=000000010f7f0a50
r8=0000000000000000 r9=0000000000000150 r10=fffff80002c06000
r11=fffff88002339a30 r12=0000000000000000 r13=fffffa800de82220
r14=fffffa800f7f0ae0 r15=0000000000000002
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!KeSetEvent+0x16:
fffff800`02c80166 f6037f test byte ptr [rbx],7Fh ds:002b:00000001`0f7f0a50=??
Resetting default scope
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 000000010f7f0a50
READ_ADDRESS: 000000010f7f0a50
FOLLOWUP_IP:
NUServer64+65f1
fffff880`0ab8c5f1 488b6c2448 mov rbp,qword ptr [rsp+48h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff8800ab8c5f1 to fffff80002c80166
STACK_TEXT:
fffff880`02339a20 fffff880`0ab8c5f1 : 00000000`000003f0 00000001`00000000 fffffa80`0f7ec000 00000000`00000500 : nt!KeSetEvent+0x16
fffff880`02339a90 fffff880`0ab8c8aa : fffffa80`0f7ec1a0 fffffa80`0f7eeb0c fffffa80`0f7ee2c8 00000000`00000002 : NUServer64+0x65f1
fffff880`02339ad0 fffff800`02f721d3 : fffffa80`0f7f0ae0 fffffa80`0f7ec260 fffffa80`0f7ec050 fffffa80`0c72e040 : NUServer64+0x68aa
fffff880`02339b40 fffff800`02c85261 : fffff800`02e21200 fffff800`02f72101 fffffa80`0c72e000 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`02339b70 fffff800`02f182ea : 501a7d4d`a14dcd79 fffffa80`0c72e040 00000000`00000080 fffffa80`0c70b6f0 : nt!ExpWorkerThread+0x111
fffff880`02339c00 fffff800`02c6c8e6 : fffff880`01f42180 fffffa80`0c72e040 fffff880`01f4d0c0 9ae0ec34`00b81aae : nt!PspSystemThreadStartup+0x5a
fffff880`02339c40 00000000`00000000 : fffff880`0233a000 fffff880`02334000 fffff880`02339370 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: NUServer64+65f1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NUServer64
IMAGE_NAME: NUServer64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4f66a064
STACK_COMMAND: .cxr 0xfffff88002339040 ; kb
FAILURE_BUCKET_ID: X64_0x7E_NUServer64+65f1
BUCKET_ID: X64_0x7E_NUServer64+65f1
Followup: MachineOwner
server3:
0: kd> !analyze -v
* Bugcheck Analysis *
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 000000000000009a,
Arg2: 0000000000417c94
Arg3: 0000000000000006
Arg4: 0000000000000002
Debugging Details:
BUGCHECK_STR: 0x4E_9a
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002d629ef to fffff80002cd3bc0
STACK_TEXT:
fffff880`14417968 fffff800`02d629ef : 00000000`0000004e 00000000`0000009a 00000000`00417c94 00000000`00000006 : nt!KeBugCheckEx
fffff880`14417970 fffff800`02e0403b : fffff880`14417a08 fffffa80`10cd1b88 fffff880`144179e0 00000000`000005a0 : nt!MiBadRefCount+0x4f
fffff880`144179b0 fffff800`02e078a7 : fffffa80`12894000 00000000`00000000 fffff6fb`7ea004a0 fffff800`00000001 : nt!MiFreePoolPages+0xa8b
fffff880`14417ac0 fffff880`0ad8d07a : 00000000`00000003 fffffa80`0f4471a0 fffffa80`36747345 fffffa80`00000000 : nt!ExFreePoolWithTag+0x7c7
fffff880`14417b70 fffff800`02f702ea : fffffa80`10cd1a80 00000000`00000080 fffffa80`0c70a740 003f005c`005c0000 : NUServer64+0x1707a
fffff880`14417c00 fffff800`02cc48e6 : fffff800`02e4ee80 fffffa80`10cd1a80 fffff800`02e5ccc0 00310026`00330023 : nt!PspSystemThreadStartup+0x5a
fffff880`14417c40 00000000`00000000 : fffff880`14418000 fffff880`14412000 fffff880`144174b0 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
NUServer64+1707a
fffff880`0ad8d07a 440f20c0 mov rax,cr8
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: NUServer64+1707a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NUServer64
IMAGE_NAME: NUServer64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4f66a064
FAILURE_BUCKET_ID: X64_0x4E_9a_NUServer64+1707a
BUCKET_ID: X64_0x4E_9a_NUServer64+1707a
Followup: MachineOwner

Blue Screen of Death when calling skype on iphone/...

Every time i call a person on skype on iphone or s6 (i think any smartphone) my computer crashes and causes blue screen of death. i have windows 8.1 running and this also happened on win 8. i have tried uninstalling, clean installing, deleting all old files of skype and then installing but nothing has worked.
on aside, when i get a call from another desktop skype as well, invariably, i cant connect the call at first attempt. clicking on accept does nothing and it will continue rining. even clicking on reject does not work after. the only option is to kill skype from task manager and then restart it. it then works fine for first call i make. it then has similar issue on later calls. not neccessarily the 2nd call. its regular but also random in nature.
i have not idea what is the problem. do you?
skype version 7.5.0.102
here is the summary of BSoD last night
Fault bucket AV_rtsuvc!Unknown_Function, type 0
Event Name: BlueScreen
Response: http://wer.microsoft.com/responses/resredir.aspx?sid=10&Bucket=AV_rtsuvc!Unknown_Function&State=1&ID...
Cab Id: 820ea6ec-6de2-4d12-bd98-0fdae73a883d
Problem signature:
P1: 50
P2: ffffe000ef655ff8
P3: 0
P4: fffff800e54fc0c0
P5: 0
P6: 6_3_9600
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
C:\Windows\Minidump\061315-85671-01.dmp
C:\Users\Madhvendra\AppData\Local\Temp\WER-220125-0.sysdata.xml
C:\Windows\MEMORY.DMP
C:\Users\Madhvendra\AppData\Local\Temp\WER2DD3.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_a9ac997f524f3a2a4a3ec8b634fedacf174d_00000000_cab_15346984
Analysis symbol:
Rechecking for solution: 0
Report Id: 061315-85671-01
Report Status: 0
Attachments:
BSoD 14 June 15.zip ‏10 KB

Your Realtek camera drivers are crashing. Make sure you have the latest drivers installed for your video card and camera. If the problem continues to occur update the camera drivers to the generic Microsoft camera drivers that come with the OS. Steps on how to update to those drivers are covered in the below graphic:

Blue Screen of Death when calling skype on iphone/s6

Every time i call a person on skype on iphone or s6 (i think any smartphone) my computer crashes and causes blue screen of death. i have windows 8.1 running and this also happened on win 8. i have tried uninstalling, clean installing, deleting all old files of skype and then installing but nothing has worked. on aside, when i get a call from another desktop skype as well, invariably, i cant connect the call at first attempt. clicking on accept does nothing and it will continue rining. even clicking on reject does not work after. the only option is to kill skype from task manager and then restart it. it then works fine for first call i make. it then has similar issue on later calls. not neccessarily the 2nd call. its regular but also random in nature. i have not idea what is the problem. do you? skype version 7.5.0.102here is the summary of BSoD last night Fault bucket AV_rtsuvc!Unknown_Function, type 0
Event Name: BlueScreen
Response: http://wer.microsoft.com/responses/resredir.aspx?sid=10&Bucket=AV_rtsuvc!Unknown_Function&State=1&ID=820ea6ec-6de2-4d12-bd98-0fdae73a883d
Cab Id: 820ea6ec-6de2-4d12-bd98-0fdae73a883dProblem signature:
P1: 50
P2: ffffe000ef655ff8
P3: 0
P4: fffff800e54fc0c0
P5: 0
P6: 6_3_9600
P7: 0_0
P8: 768_1
P9:
P10:Attached files:
C:\Windows\Minidump\061315-85671-01.dmp
C:\Users\Madhvendra\AppData\Local\Temp\WER-220125-0.sysdata.xml
C:\Windows\MEMORY.DMP
C:\Users\Madhvendra\AppData\Local\Temp\WER2DD3.tmp.WERInternalMetadata.xmlThese files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_a9ac997f524f3a2a4a3ec8b634fedacf174d_00000000_cab_15346984Analysis symbol:
Rechecking for solution: 0
Report Id: 061315-85671-01
Report Status: 0

Your Realtek camera drivers are crashing. Make sure you have the latest drivers installed for your video card and camera. If the problem continues to occur update the camera drivers to the generic Microsoft camera drivers that come with the OS. Steps on how to update to those drivers are covered in the below graphic:

NI Raptor Runtime: Blue screen of death

Hi
We've suffered two blue screens of death on a Windows 8 system running LabView code in the last couple of months. The event logs show the cause to be the NI Raptor Runtime driver. We are running LabView 2012 SP1 with all critical updates installed. Are there any known issues with this driver?
Best regards,
Chris

Hi Robert
Thanks for your reply. I resinstalled and updated all of the National Instruments software on the machine this week so the DAQmx version should be up-to-date. I've pasted the versions below. We experienced another blue screen within a day of the reinstall/update though.
With regards to the code, it isn't mine so I don't know it inside out. However, the general architecture is a flat sequenece in a while loop. The total loop rate is around 1-3Hz. Within individual frames of the sequence, analogue and digital input tasks are created, run, stopped and cleared in series on each loop iteration. Individual frames may not have rate limiting timers, so a create may happen quite quickly after a clear. State changes on the front panel can cause certain frames to create and run digital output tasks that change the value of output lines, however no front panel interaction was performed within at least a few hours of any of the crashes.
Do you think that it would be worth placing a frame-rate-limiting timer into the code, to reduce the rate at which tasks are stopped and started?
Best regards,
Chris
National Instruments Software: Version:
CVI Run-Time 10.0.1.434
NI-DAQmx Device Driver 14.2.0f1
NI-DAQmx ADE Support 14.2.0
NI-DAQmx MAX Configuration 14.2.0
NI Script Editor 1.3.4
NI-DMM 3.0.5
DMM Soft Front Panel 3.0.5
NI-FGEN 2.8.1
FGEN Soft Front Panel 2.7
NI-488.2 Software 2.81
NI I/O Trace 14.0.0f0
IVI Compliance Package 4.4
LabVIEW Run-Time 2010 SP1 10.0.1
LabVIEW Run-Time 2009 SP1 (64-bit) 9.0.1
Measurement & Automation Explorer 14.0.0f0
Measurement Studio Visual Studio 2010 Support - See individual versions below.
DotNET
Common 13.0.40.190
Common (64-bit) 13.0.40.190
NI-USI 2.0.0.4901
NI-DCPower 1.6.1
NI-DCPower Soft Front Panel 1.6.1
NI-HSDIO 1.7.5.1
NI-HWS 1.4.9
NI PXI Platform Services Configuration 14.0.0f0
NI PXI Platform Services Runtime 14.0.0f0
NI-RFSA 2.4.5
NI-RFSA Soft Front Panel 2.4
NI-RFSG 1.7.2
NI-PAL Software 14.0.1
NI-SCOPE
Configuration Support 3.8.5
Development Support 3.8.5
Run-Time 3.8.5
SCOPE Soft Front Panel 3.8
LabVIEW SignalExpress 6.0
NI-SWITCH 4.3.5f0
Soft Front Panel 4.3.5.49152
NI System Configuration 14.0.0f0
NI-TClk 1.9.1
NI-VISA 5.2
NiVisaServer.exe 5.1.0.49152
NIvisaic.exe 5.1.0.49152
NI-VISA Runtime 5.2
LabVIEW 12.0.1
LabVIEW Run-Time 2011 SP1 f2 11.0.1
LabVIEW Run-Time 2012 SP1 f9 12.0.1
LabVIEW Run-Time 8.2.1 8.2.1
LabVIEW Run-Time 8.5.1 8.5.1
LabVIEW Run-Time 8.6.1 8.6.1
LabVIEW Run-Time 2009 SP1 9.0.1

Bootcamp Windows 7 Blue Screen of Death on MBPwR

Hello all, I've never needed to use this before but gosh darn it I need some advice, because I can't figure this out...
I'd rate myself a 9 out of 10 in "Windows PC" experience
And maybe a 6 out of 10 with Macs, I'm still new!
I just bought the new Mac Book Pro with Retina Screen in early July, I can't remember the exact date. But it hasn't been thirty days yet, so if you think that's my best bet to try and get an exchange here, let me know.
MC975LL/A
PROBLEM : Mac OSX Lion 10.7 works wonderfully, not a problem in the world, smooth as butter – the issue is Windows. I like to play some games and OSX doesn't play well with some Windows based games so I always install it on Bootcamp. Well, this has been a neverending issue on my new MBPwR because I can't seem to get it to work correctly.
      1. Here's how it started - I installed Windows 7 Ultimate x64 through Bootcamp, via my Superdrive and it ran well for a week or so. After installing a game and some other software (Steam) please take that as a coincidence as I did, I don't think Steam had anything to do with the crash, more likely it was something 'game' related, HDD, RAM, CPU, GPU? The computer started to get the "Blue Screen of Death" that Windows computers get, specifically: page_fault_in_nonpaged_area, I've never seen it before and I've owned a number of Windows computers over the years!
     2. Is this my fault, or something deeper? - I can't figure it out, is this a hardware problem or a software one? I reinstalled Windows 7 yesterday and attempted to try again. Just a chance my installation was messed or something, well it happened literally after five minutes of booting into Windows 7. After it happened the first time I used a memory check and a hard drive check software and both came up flawless. Some online on other boards although Windows based have suggested this error can be caused by the RAM and the CPU or the GPU, even... Is this true? As there is no way to test it, maybe exchanging this computer is the best option?
    3. As as a side note... - Has anyone else had a crawling slow boot into Windows 7? It takes my MBPwR almost five minutes of a top left-hand blinking cursor to actually boot to Windows 7.
So did I have some really, really bad luck here with a new computer? Or is this somehow software related? I can answer any questions if you have them so we can try and figure this out!
Thanks!

Did the Nvidia driver install okay? Some users had to reinsall just the driver from Apple Windows Software Support.
Did Windows DVD not find anything wrong?
Is Windows set to be default boot OS in the control panel for selecting the boot volume?
There probably is a leaning curve and bleeding edge sortof with any new logicboard and setup.
Apple has issued a firmware upgrade for some models - I thought Retina - the MacBook Air has a serious problem under Windows.
Mac will run hotter under Windows. Maybe an error message.
GPU-Z:
http://www.techpowerup.com/downloads/SysInfo/GPU-Z/
AIDA64 Extreme Edition
http://www.aida64.comhttp://www.aida64.com/product/aida64-extreme-edition/overview
CCleaner
http://www.piriform.com/ccleaner
How to view error message:
From Control Panel-> Admin. Tools-> Event Viewer-> Windows logs:
Check Application and System Folders for Red highlit messages. Note that you can right-click clear these log folders.
Memtest
This is a step by step guide with audio and video to explain how to use memtest to see if your memory is defect. Another thing to add is that some errors will not be found on the first pass, best to do at least 3 passes.

How to fix blue screen of death of windows xp with a bootcamp hard drive

i have a macbook with intel 2 duo core with 4gb ram and 1tb hard drive with lepord on it i bootcamped the hard and installed windows xp and now i am gettind a blue screen of death. so i know there repair utlite on windows xp disc when you boot to it but can't do it on the mac it there a repair utlite for windows xp cause i can still into sindows xp for like an hour before it crashes

JFJ_595 wrote:
the start-up music still plays.
The POST for the hardware checks out then.
JFJ_595 wrote:
I turn on my computer and all i get is a blank white/grey screen. No logo, no loading symbol, just a blank screen;
Command+R does nothing,
Holding Shift does nothing
Press and hold the power button down to turn of the machine.
Press and hold the Command Option R keys on the built in keyboard and press the power button, you have to be near your high speed Internet connection.
If you get something like "Install OS X" do that, it will overwrite your old copy with a new one and not touch your files or most programs.
If you can't install OS X, head to Disk Utility and First Aid > Repair Disk and Permissions and try reisntalling OS X again. (do not erase the drive as this will wipe your data off, unless your sure)
If you still get the white/gray screen with nothing while holding the Command Option R keys at boot time, I suspect your EFI firmware has been borked somehow and it's not loading to respond to the at boot key commands.
We are able to reinstall the EFI firmware ourselves, but the current method requires a machine with a internal optical drive. This problem occurs so rarely that it's not been used much and certainly unknown how well it works off a USB thumb drive, which is what I suspect the Apple Store/Repair will do.
Since your under warranty, I would have Apple replace the EFI firmware and check the machine out for hardware issues as well.
Buy AppleCare and a external drive for TimeMachine backups.

Blue Screen of Death from Apple Wireless Keyboard in Windows 7

Hi all,
Situation: I have Windows 7 Professional 64 bit installed (boot camp) on my late 2008 MBP. Oftentimes, I'm plugged in to an LED Cinema display and work off of the Apple Wireless Keyboard & Magic Mouse. The Boot Camp partition / Drivers were originally installed from a Snow Leopard DVD. My Apple Software update reports that all my Apple Windows Software is up-to-date.
Problem: Since installing Windows 7 back in May, I've experienced the Blue Screen of Death (BSOD) 5 times. Each time has resulted from a key press on my bluetooth keyboard after it had been sitting idle for some time and presumably gone into power save mode. Any key press causes an instantaneous BSOD. It only occurs when I'm running windows and I'm working off my bluetooth keyboard so it's hard to replicate and likewise hard to troubleshoot and determine if a fix has worked.
*Error Details:* Here's some information I've extracted from the BSOD dump files.
IRQLNOT_LESS_OREQUAL
+The problem seems to be caused by the following file: ntoskrnl.exe+
+Technical Information:+
+* STOP: 0x0000000a (0xfffff80003032f00, 0x0000000000000002, 0x0000000000000008,+
0xfffff80003032f00)
+* ntoskrnl.exe - Address 0xfffff80002cbf600 base at 0xfffff80002c4f000 DateStamp+
0x4b88cfeb
Thanks for the help!
Paul

I'm experiencing the same problem with the BSODs while using my Apple wireless keyboard (latest model).
I'm running Windows 7 x64 and admit that I bypassed the BootCamp software/driver installation wizard after it complained that my model didn't support installation of the x64 drivers. Its a bit of a gray area, as my system is 64-bit capable and many services and applications run in 64-bit mode without my intervention.
Just curious if Windows 7 x86 users are experiencing these BSODs or is it a coincidence that you all are installing the drivers creatively.

Windows 7 - Blue screen of death after Boot Camp install

Hello! I have done some searches with no answers, so...
After installing Windows 7 from scratch I then install Boot Camp 3.0 which then leads to the Windows blue screen of death upon reboot. I then have to recover Windows to the previous state prior to installing Boot Camp.
Help!?

Most likely, Apple HFS read-only, which is AppleHFS.sys and AppleMNT.sys - rename those and see.
You might want to run chkdsk after all this to make sure there are no errors with the drive and file system.
Windows Explorer will not accept HFS+ filenames with special characters and will "green bar" and hang when it does, too.
The faulty HFS driver is a valid concern.
Rename AppleHFS.sys and AppleMNT.sys
By doing the following you will disable HFS mount / read mode on windows XP, Vista, 7.
Navigate to c:/windows/system32/drivers/AppleMNT.sys, rename the AppleMNT.sys file to something like AppleMNT_keep.sys or something of your likings.
The faulty HFS driver is a valid concern. It seems to happen on many systems.
You find it in Windows/system32/drivers/AppleHFS.sys
Renaming to AppleHFS_disabled.sys will avoid the blue screens until you have found another solution or Apple updates Bootcamp 3
After renaming both myself because they are no longer "*.sys" or something? they are gone. In my case AppleHFS prevented Windows Backup from running to end and was causing error "some files skipped" and while some might find reading convenient, I prefer Windows not have even read-only access.
You can probably do better with MacDrive, or probably Paragon's HFS driver, to read AND write if needed, to HFS from Windows.

Windows Blue Screen of Death

I keep getting the Blue Screen of Death when I am booted in Bootcamp. Everything appears to boot fine. I can load applications, but then shortly after using the Windows partition the Blue Screen of Death appears. I have a MacBook Pro with retina display. 16GB RAM. The Windows partition has 40GB dedicated to it. Running Windows 7. Everything was working fine last week. I installed some new programs on the Mac Side. I also run Parallels sometimes.

I was able to fix this by restoring to a previous backup of the machine. It must have been a bad driver.

Blue screen of death after installing Boot Camp on Windows 7

Hello and thanks for the help!
Brnad new user to Boot Camp here. After a new install of Windows 7, I install Boot Camp but then when rebooting Windows I get the blue screen of death. When letting Windows attempt a repair, it fails and I am forced to Recover Windows 7 to a state before I installed Boot Camp.
Help!?

Solution for this problem is simple. You have to apply Mac Book Air SMC Update 1.7 which you can do from Mac OS X with Software Update or you can download required update manually from Apple support site. If you don't use BootCamp and have installed Windows without it, you will have to boot Mac OS X from external drive just to apply required update. After you applied SMC update, you can boot to Windows and apply BootCamp update 3.2 and 3.3.
There is a known problem with Mac Book Air EFI Update 2.3, which you won't be able to apply and it will show in Software Update every time you check for updates. There is no solution for it yet.
You get BSOD if you have BootCamp 3.1 and Windows 7 SP1 installed and you have commited Windows update which will break applemtp.sys as your SMC firmware is too old. It applies to Windows 7 32 bit and 64 bit versions in BootCamp or native install.

Windows 7 - Memory Dump problem ! Blue screen of death !! HELP

Hey guys,
I have an iMac 27 inch 2011 running Windows 7 home premium 64bit using bootcamp. My computer specs are
I Mac OSX 10.7
CPU - Intel i7 3.4 ghz quad core
RAM - (16 gb )
VIDEO - ATI Radeon HD 2 GB
I installed windows 7 on my imac using bootcamp today. It was working fine until i started installing things and i ran into the blue screen of death saying Memory dump. This message only shows for about 2 seconds and then restarts my computer. It randomly happens, such as internet explorer or just on my homescreen.
Thanks in advance for you help.
Thank you

To locate any of the forums click the Apple Support Communities link in the upper left of this page, then type in the first word of what you're looking for.
As for returning the machine no, I suspect you just have an installation problem. Macs run MS Windows in Boot Camp better than most dedicated Windows boxes.

Bootcamp Blue Screen of Death.. Apple USB Driver ?

This started to occur to me after I upgraded to the Leopard
drivers for Bootcamp.
I have seen this occur two times while booted in Windows XP.
Both after I left the machine idle for a long period of time..
about 3-4 hrs.
1) Conditions - machine is idle.. the screen energy saver is on
and the monitor is in low power/sleep mode.
2) Conditions - both times occured when i had no internet access
connected. It occured when I took my imac to a location where
i dont have the wifi access as usual at my home.
3) Conditions - i did have the trial of Parallels 3.0 installed
but i dont use it nor did i purchase the full version.. i need
to uninstall those components from XP still.
4) I think in both instances Autodesk Inventor 11 was running.
The 2nd time it was, i dont remember the first time this crash happened.
I have installed all the latest service packs of this software on
the system.
5) Windows XP SP2, FAT32 partition, 32 GB on my iMac harddisk.
6) Error - Windows Blue Screen of Death... i caught it only momentarily
as the machine goes into automatic reboot. I did catch USB DRIVER
in the most recent crash.
7) Error - Upon reboot, the machine asks to send the error report
to Micosoft. I cant because I dont have an internet access. It did
say that Windows rebooted due to a serious error and asked to send
the info back to MS.
8) Error - i was able to screen shot a bit of the error report
but i cant attach a jpeg of the window to this post unfortunately.
Any insight would be appreciated on this.
Edgar

okay.. i have recreated this hard crash for a third time:
it is definitely the USB Drivers used... blue screen of death states:
BUGCODE_USB DRIVER
other notes:
i had no other applications running when the system crashed this third time.
Power Settings (from Win control panel):
Turn off monitor: after 3 min
Turn off HDs: after 1 hr
System standby: after 1 hr
System hibernate: after 2 hrs

Ipod crashes windows (blue screen of death)

Hi all. A bit of background info:
A couple of months ago the hard drive crashed on my friends computer. They had to reinstall their OS. Thankfully they had made backups of most everything and were able to get most things reinstalled successfully.
Now they are using a 15g ipod connected through a firewire port on an HP laptop. They do not have a USB adaptor, so gotta go with the FW.
Anyway, when they connect the ipod the computer completely crashes to the blue screen of death and does the physical memory dump. There is an error message, something along the lines of a driver issue.
I know this is vague information, but any pointers on how to proceed in troubleshooting this would be greatly appreciated, thanks
Frost

hi Frostine!
Anyway, when they connect the ipod the computer completely crashes to the blue screen of death and does the physical memory dump. There is an error message, something along the lines of a driver issue.
we can sometimes narrow this down a bit by checking on the numerical and text codes showing up with the blue screen. (ie 0x[zeros/letters/numbers] CAPSANDUNDERSCORES)
here's a reference on the sorts of things i'm checking on:
Troubleshooting Windows Stop Messages
can you get that information for us from their PC?
(if the screen is specifying the file that Windows is crashing on, that would be helpful to know too.)
love, b

Blue Screen of Death on bootcamp windows 7?????

Similar Messages

Maybe you are looking for