Drajver za Bluetooth- Dell Inspiron 15R N5110

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Možeš li mi samo reći kako da udjem u safe mod?
Probao sam na f8 i neće.

I ako možeš pošalji mi poseban drajver za wireless jer ako zeznem nema šanse da pokrenem internet bez njega.

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Napisano: 12 Avg 2013 19:32

Ako neće na F8 probaj na F5

Drajver za wireless može instalirati ručno samo njega..
Znači skineš oficijelni drajver već ga imaš http://downloads.dell.com/network/R312280.exe
Kad ga skineš napravi novi folder i desni klik na drajver koji si skinuo raspakuj ga u taj novi folder što si ga napravio.
Zatim idi u device menager desni klik na wireless adaptere i idi na update drivera. I odredi da potražiš drajver u svom računaru i nađeš taj folder gde si ga raspakovao i i on bi trebao da bude u WLAN folderu pa na Drivers > Win7 klikneš na njega i ok i on će početi da traži ako ga pronađe prebaciće potrebne fajlove u kada završi restartuj računar.

Dopuna: 12 Avg 2013 19:42

A sad sam ga skinuo ja i raspakovao da pogledam, ti njega kad skineš i raspakuješ možeš i regularno njega samo instalirati samo u folderu WLAN pokreni setup i samo će se instalirati drajver za Wireless.

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Dusan.cz ::Možeš li mi samo reći kako da udjem u safe mod?
Probao sam na f8 i neće.
Kako neće?!
U Safe mode se ulazi na F8.

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Napisano: 13 Avg 2013 19:33

SlobaBgd ::Dusan.cz ::Možeš li mi samo reći kako da udjem u safe mod?
Probao sam na f8 i neće.
Kako neće?!
U Safe mode se ulazi na F8.

Jeste, čeprkao sam po google pa sam saznao da trebam da držim f8 dok se ne pokrene safe mod a ne da ga pritiskam nekoliko puta
Sada ću da obrišem iz safe moda pa ću da vidim kakvo je stanje.

Dopuna: 14 Avg 2013 12:47

Obrisao sam bluetooth ali je situacija loša, ne znam da li da sada postavim novu temu u delu Windows?
Nijedan drugi drajver za bluetooth ne mogu da instaliram, program WhoCrasshed i dalje javlja neke greške, a računar kada se startuje treba mu mnoooogo vremena da pokrenem bilo koji program, uz to on i sporo radi, tj. stalno zakucava na kratko. Šta da radim?

Dopuna: 14 Avg 2013 12:52

A u device manageru i posle brisanja nikakva upozorenja, ne znam o čemu se radi..

Dopuna: 14 Avg 2013 14:33

Da li je moguće da mi računar sporo radi zbog drajvera?

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Dusan.cz ::

Da li je moguće da mi računar sporo radi zbog drajvera?

Kako nije moguće, moguće je baš to štekanje što se dešava kod teba, e sad da li je sam drajver neki uzrok kod tebe ja nisam više siguran.

Ako imaš CD od sedmice ja bih ti savetovao da probaš odraditi repair sistema, možda i donese poboljšanje.

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Imam disk, kako mogu da odradim repair? To mi neće obrisati nešto sa računara?

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Ma greška mislio sam sistemske fajlove da probamo popraviti ako je oštećen neki ali ti si na sedmici em ti ne treba CD em smo to već probali pre pa nije urodilo plodom.

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Šta predlažeš da uradim?

• 1Ovo se svidja korisniku: Dusan.cz
  
  Registruj se da bi pohvalio/la poruku!

Dusan.cz ::Šta predlažeš da uradim?

Ništa nemam ideje više stvarno , a možda se neko javi sa sa mogućim rešenjem.

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Može li neko da pomogne?
Danas mi se 5 puta za redom restartovao.
Evo opet izveštaj iz WhoCrashed

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 8/16/2013 10:09:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081613-29998-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF8800175E6FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF8800175E6FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 Fri 8/16/2013 10:09:50 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: netio.sys (NETIO!RtlCopyBufferToMdl+0x1D)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF8800175E6FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 Fri 8/16/2013 10:01:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081613-35724-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF880017546FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880017546FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 Fri 8/16/2013 9:53:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081613-29109-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF880017546FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880017546FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 Fri 8/16/2013 9:49:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081613-35412-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF880017886FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880017886FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 Fri 8/16/2013 9:45:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081613-28080-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF880016106FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880016106FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 Thu 8/15/2013 9:45:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081513-30295-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF880017736FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880017736FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 Thu 8/15/2013 12:20:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081513-40232-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF880016106FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880016106FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 Thu 8/15/2013 12:12:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081513-51386-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF880016106FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880016106FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 Tue 8/13/2013 7:44:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081313-37315-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF880016106FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880016106FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 Tue 8/13/2013 5:45:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081313-30700-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF8800171F6FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF8800171F6FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 8/12/2013 3:34:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081213-24663-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF880016106FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880016106FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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.