Quantcast
Channel: Intel Communities : Discussion List - Intel® NUC
Viewing all articles
Browse latest Browse all 18668

DC3217IYE Keeps Crashing

$
0
0

I have a fresh install of Windows 7 64-bit. The NUC has a 16GB of memory and a 256GB SSD card.

I downloaded the newest driver pack from Intel and applied them.

I have amulet devices remote control driver installed, XBMC and voxcommando and that's basically it

I'm experiencing crashes every day, sometimes multiple times a day.

 

This is the output from whocrashed:

 

System Information (local)

--------------------------------------------------------------------------------

 

computer name: KITCHENNUC

windows version: Windows 7 Service Pack 1, 6.1, build: 7601

windows dir: C:\Windows

Hardware: Intel, Intel Corporation, D33217GKE

CPU: GenuineIntel Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz Intel586, level: 6

4 logical processors, active mask: 15

RAM: 17109196800 total

VM: 2147352576, free: 1932152832

 

 

Crash dump directory: C:\Windows\Minidump

 

Crash dumps are enabled on your computer.

 

On Wed 12/4/2013 3:17:56 AM GMT your computer crashed

crash dump file: C:\Windows\Minidump\120313-5694-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002AC2E94, 0xFFFFF88007969DE0, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

file path: C:\Windows\system32\ntoskrnl.exe

product: MicrosoftÆ WindowsÆ Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

 

On Wed 12/4/2013 3:17:56 AM GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002AC2E94, 0xFFFFF88007969DE0, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

 

On Wed 12/4/2013 12:48:05 AM GMT your computer crashed

crash dump file: C:\Windows\Minidump\120313-5304-01.dmp

This was probably caused by the following module: usbport.sys (0xFFFFF88002D7A16D)

Bugcheck code: 0xD1 (0xFFFFF8800CB749C0, 0x2, 0x0, 0xFFFFF88002D7A16D)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\drivers\usbport.sys

product: MicrosoftÆ WindowsÆ Operating System

company: Microsoft Corporation

description: USB 1.1 & 2.0 Port Driver

Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

 

 

On Mon 12/2/2013 7:24:34 AM GMT your computer crashed

crash dump file: C:\Windows\Minidump\120213-5881-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002A4CED3, 0xFFFFF880079E4880, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

file path: C:\Windows\system32\ntoskrnl.exe

product: MicrosoftÆ WindowsÆ Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Viewing all articles
Browse latest Browse all 18668

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>