BSOD, weet iemand wat de oorzaak hiervan is?

[Computer12]

Hallo, ik had vandaag een nieuwe WiFi Dongle gekocht van TP-Link, hij deed het gewoon,

Maar ik zette mn PC uit, zette hem aan, kreeg een BSOD, wat is de oorzaak? Hier is de info:

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. ([url]http://www.osr.com[/url])
Online Crash Dump Analysis Service
See [url]http://www.osronline.com[/url] for more information
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Machine Name:
Kernel base = 0xfffff802`01019000 PsLoadedModuleList = 0xfffff802`012f2850
Debug session time: Wed May  6 10:39:48.357 2015 (UTC - 4:00)
System Uptime: 0 days 0:00:19.059
*******************************************************************************
*                                                                             *
*                        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: fffff8020106f132, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
nt!MiZeroFault+a42
fffff802`0106f132 f7413800000004  test    dword ptr [rcx+38h],4000000h

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: fffff802012e0240: Unable to get special pool info
fffff802012e0240: Unable to get special pool info
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffffffffffffffff 

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:  WIN8_DRIVER_FAULT

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff802011b4bf1 to fffff80201169ca0

CONTEXT:  18478b000007b485 -- (.cxr 0x18478b000007b485)
Unable to read context, Win32 error 0n30

STACK_TEXT:  
ffffd001`1c7a4de8 fffff802`011b4bf1 : 00000000`0000001e ffffffff`c0000005 fffff802`0106f132 00000000`00000000 : nt!KeBugCheckEx
ffffd001`1c7a4df0 fffff802`011758c2 : fffff6bf`fc9307b8 fffff802`010756de 00000000`00000000 fffff6bf`fc9307b8 : nt! ?? ::FNODOBFM::`string'+0x3aa31
ffffd001`1c7a54e0 fffff802`01173dfe : ffffe001`63b28d98 00007ff9`25257a88 00000000`00000000 00000001`00000005 : nt!KiExceptionDispatch+0xc2
ffffd001`1c7a56c0 fffff802`0106f132 : 00000000`00000001 ffffd001`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0xfe
ffffd001`1c7a5850 fffff802`0106c357 : 00000000`00000008 00000000`00000000 00000000`00000000 ffffd001`1c7a59f0 : nt!MiZeroFault+0xa42
ffffd001`1c7a5940 fffff802`01173f2f : 00000000`00000008 00000022`6f07f6e8 00000000`00000001 ffffffff`ffffffff : nt!MmAccessFault+0x287
ffffd001`1c7a5b00 00007ff9`27b42010 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x12f
00000022`6f07f528 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff9`27b42010


FOLLOWUP_IP: 
nt!MiZeroFault+a42
fffff802`0106f132 f7413800000004  test    dword ptr [rcx+38h],4000000h

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MiZeroFault+a42

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  550f41a6

STACK_COMMAND:  .cxr 0x18478b000007b485 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1e_c0000005_nt!MiZeroFault+a42

BUCKET_ID:  X64_0x1e_c0000005_nt!MiZeroFault+a42

Followup: MachineOwner
---------

 

[Mik Zjegger]

Is de dongle compatible met Win 8?
Toevallig heb ik deze week ook een dongle (Sitecom die van Realtek bleek te zijn, die ik nog had liggen) op mijn pc aangesloten i.v.m. Chromecast.
Het bleek dat hij niet compatible was met Win 7, na de juiste driver van Realtek te hebben gedownload werkte hij perfect.
Ga naar apparaatbeheer, klik rechts op de usb adapter (onder "netwerkadapters") kies eigenschappen en kijk of het apparaat correct werkt.
Als dat niet het geval is zoek dan de juiste driver of probeer de optie "stuurprogramma's bijwerken".