Windows 7 64bit blue screen

Windows 7 64bit blue screen

Witam, mam poważny i uciążliwy problem na Windows 7 64bit.

Wyskakuje mi często (przynajmniej ze 2 razy podczas użytkowania komputera ok 4 godzin dziennie) błąd jak na zamieszczonym obrazku. Nie wiem co z tym zrobić... Pomoże ktoś proszę?

właśnie, że nie robię nic specjalnego (przeglądam internet i robię kosztorys w odpowiednim programie). to co mam podłączone pod usb: mysz laserowa, nadajnik do klawiatury bezprzewodowej, zewnętrzna karta dźwiękowa Creative SB Live

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 2011-11-21 17:25:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112111-77766-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0x4F004C, 0x2, 0x0, 0xFFFFF8800FFE019B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Mon 2011-11-21 17:25:32 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: sptd.sys (sptd+0x46570)
Bugcheck code: 0xD1 (0x4F004C, 0x2, 0x0, 0xFFFFF8800FFE019B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\sptd.sys
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: sptd.sys .
Google query: sptd.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Mon 2011-11-21 06:14:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112111-79123-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF8800444C19B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

sptd.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

No wlasnie, jestem ciekaw, jak do tego doszlo, po raz pierwszy widze BS na windowsie Vista/7.

Zapraszam do mnie, mogę załatwić jednym kliknięciem :P (za mały prąd na procku po OC do 4,7Ghz ;)) BSów miałem całe multum :D