Blue Screen Happening Constantly
Tags:
- Blue Screen
- Configuration
- Windows 7
Last response: in Windows 7
AngeloXD
December 7, 2013 12:58:14 PM
Hello guys.
First,sorry about my english.
So, i have Win 7 64bits. and this config:
Thermaltake Commander MS I
Asrock Z77 Extreme 4
Intel Core i5 3570K
Noctua NH-U12P SE2
Noctua NF-S12A
Corsair Vengeance 8GB (2X4GB) 1600MHz
Zotac GTX660
Corsair CX600
Western Digital Caviar Green 1TB
Everytime i try to play games that require more GPU, i get BS.
some times even not trying to open games, it happens too.
This is the ERROR i got:
It's in portuguese, because i'm from brazil.
Thank you guys for the help.
First,sorry about my english.
So, i have Win 7 64bits. and this config:
Thermaltake Commander MS I
Asrock Z77 Extreme 4
Intel Core i5 3570K
Noctua NH-U12P SE2
Noctua NF-S12A
Corsair Vengeance 8GB (2X4GB) 1600MHz
Zotac GTX660
Corsair CX600
Western Digital Caviar Green 1TB
Everytime i try to play games that require more GPU, i get BS.
some times even not trying to open games, it happens too.
This is the ERROR i got:
Spoiler
Nome do Evento de Problema: BlueScreen
Versão do sistema operacional: 6.1.7601.2.1.0.256.48
Identificação da Localidade: 1046
Informações adicionais sobre o problema:
BCCode: 116
BCP1: FFFFFA800A1B54E0
BCP2: FFFFF880051A66CC
BCP3: FFFFFFFFC00000B5
BCP4: 000000000000000A
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Arquivos que ajudam a descrever o problema:
C:\Windows\Minidump\120613-34133-01.dmp
C:\Users\Admin\AppData\Local\Temp\WER-104380-0.sysdata.xml
Leia nossa declaração de privacidade online:
http://go.microsoft....88&clcid=0x0416
Se a declaração de privacidade online não estiver disponível, leia nossa declaração de privacidade offline:
C:\Windows\system32\pt-BR\erofflps.txt
Quote:
Assinatura do problema:Nome do Evento de Problema: BlueScreen
Versão do sistema operacional: 6.1.7601.2.1.0.256.48
Identificação da Localidade: 1046
Informações adicionais sobre o problema:
BCCode: 116
BCP1: FFFFFA800A1B54E0
BCP2: FFFFF880051A66CC
BCP3: FFFFFFFFC00000B5
BCP4: 000000000000000A
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Arquivos que ajudam a descrever o problema:
C:\Windows\Minidump\120613-34133-01.dmp
C:\Users\Admin\AppData\Local\Temp\WER-104380-0.sysdata.xml
Leia nossa declaração de privacidade online:
http://go.microsoft....88&clcid=0x0416
Se a declaração de privacidade online não estiver disponível, leia nossa declaração de privacidade offline:
C:\Windows\system32\pt-BR\erofflps.txt
It's in portuguese, because i'm from brazil.
Thank you guys for the help.
More about : blue screen happening constantly
-
Reply to AngeloXD
icraft
December 7, 2013 2:37:35 PM
AngeloXD
December 7, 2013 3:19:59 PM
Related resources
- Blue screen constatly happening - Forum
- Constantly have blue screen when disable iGPU in a APU - Forum
- blue screen of death keeps happening on high usage - Forum
- how do i do a factory reset with blue screen and system thread exception not handled constantly appering - Forum
- Blue Screen Of Death Happening For The First Time - Forum
coastie65
December 7, 2013 6:05:02 PM
coastie65
December 7, 2013 6:09:37 PM
AngeloXD
December 7, 2013 6:11:07 PM
If all drivers are up to date try running memtest on your ram http://memtest.org/ first sign of ram failure are BSOD's that get blamed on drivers but really the just get corrupt in the ram.
-
Reply to rolli59
m
0
l
AngeloXD
December 7, 2013 7:17:30 PM
So. I updated/reinstalled BIOS, GPU and Chipset drivers. Then Restarted the computer, tried to open a game (Far cry 3), it was an instantly Blue screen.
So i restarted the PC again, when windows loaded, the pc just turned off.
So, can it be some problem with the PSU? Is there a way to check it?
ps: I did windows memory test. it was fine. anyways, i'll make memtest too.
Thx guys.
So i restarted the PC again, when windows loaded, the pc just turned off.
So, can it be some problem with the PSU? Is there a way to check it?
ps: I did windows memory test. it was fine. anyways, i'll make memtest too.
Thx guys.
-
Reply to AngeloXD
m
0
l
Nuno Silva
December 7, 2013 7:24:52 PM
AngeloXD
December 7, 2013 7:28:43 PM
Nuno Silva
December 7, 2013 8:40:56 PM
AngeloXD
December 7, 2013 8:43:50 PM
Nuno Silva
December 7, 2013 8:53:57 PM
AngeloXD
December 7, 2013 9:03:14 PM
AngeloXD
December 8, 2013 3:15:07 PM
Nuno Silva
December 9, 2013 7:47:32 AM
-
Reply to Nuno Silva
m
0
l
AngeloXD
December 11, 2013 8:21:36 AM
AngeloXD
December 11, 2013 8:22:39 AM
AngeloXD
September 27, 2014 7:58:32 AM
Hello back again guys, here i am 10 months later.
My PC have been working pretty OK since yesterday, when everything started to happen again.
Getting this error: (which i think is the same as before)
I've already re-instaled the GPU drivers.
But this time i got this on Whocrashed:
How am i supposed to proceed? Thank you all.
Hope it isn't PSU again :X
----
Memtest done, 0 errors.
My PC have been working pretty OK since yesterday, when everything started to happen again.
Getting this error: (which i think is the same as before)
Spoiler
Assinatura do problema:
Nome do Evento de Problema: BlueScreen
Versão do sistema operacional: 6.1.7601.2.1.0.256.48
Identificação da Localidade: 1046
Informações adicionais sobre o problema:
BCCode: 116
BCP1: FFFFFA800E0FE010
BCP2: FFFFF8800577E67C
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Arquivos que ajudam a descrever o problema:
C:\Windows\Minidump\092614-27206-01.dmp
C:\Users\Admin\AppData\Local\Temp\WER-106673-0.sysdata.xml
Leia nossa declaração de privacidade online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...
Se a declaração de privacidade online não estiver disponível, leia nossa declaração de privacidade offline:
C:\Windows\system32\pt-BR\erofflps.txt
Nome do Evento de Problema: BlueScreen
Versão do sistema operacional: 6.1.7601.2.1.0.256.48
Identificação da Localidade: 1046
Informações adicionais sobre o problema:
BCCode: 116
BCP1: FFFFFA800E0FE010
BCP2: FFFFF8800577E67C
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Arquivos que ajudam a descrever o problema:
C:\Windows\Minidump\092614-27206-01.dmp
C:\Users\Admin\AppData\Local\Temp\WER-106673-0.sysdata.xml
Leia nossa declaração de privacidade online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...
Se a declaração de privacidade online não estiver disponível, leia nossa declaração de privacidade offline:
C:\Windows\system32\pt-BR\erofflps.txt
I've already re-instaled the GPU drivers.
But this time i got this on Whocrashed:
Spoiler
System Information (local)
--------------------------------------------------------------------------------
computer name: ADMIN-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASRock, Z77 Extreme4
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8470274048 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 27/09/2014 01:07:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092614-27206-01.dmp
This was probably caused by the following module: virtuwddm.sys (VirtuWDDM+0x867C)
Bugcheck code: 0x116 (0xFFFFFA800E0FE010, 0xFFFFF8800577E67C, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\virtuwddm.sys
product: VIRTU
company: Lucidlogix Inc.
description: LucidInterop WDDM Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: virtuwddm.sys (LucidInterop WDDM Driver, Lucidlogix Inc.).
Google query: Lucidlogix Inc. VIDEO_TDR_ERROR
On Sat 27/09/2014 01:07:05 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: virtuwddm.sys (0xFFFFF8800577E67C)
Bugcheck code: 0x116 (0xFFFFFA800E0FE010, 0xFFFFF8800577E67C, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\virtuwddm.sys
product: VIRTU
company: Lucidlogix Inc.
description: LucidInterop WDDM Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: virtuwddm.sys (LucidInterop WDDM Driver, Lucidlogix Inc.).
Google query: Lucidlogix Inc. VIDEO_TDR_ERROR
On Wed 17/09/2014 23:23:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091714-29078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFFA800D3A3860, 0x390424F)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 28/08/2014 15:55:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082814-34507-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0x0, 0xFFFFF8800DBC1700, 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 Mon 21/07/2014 01:05:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072014-45380-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFFA800CC03A30, 0x728312B8)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 04/05/2014 15:23:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050414-31590-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFFA800DCDD310, 0x16667C0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 04/05/2014 00:18:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050314-24616-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0x80, 0x2, 0x1, 0xFFFFF80003284F0F)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
7 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:
virtuwddm.sys (LucidInterop WDDM Driver, Lucidlogix Inc.)
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 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.
System Information (local)
--------------------------------------------------------------------------------
computer name: ADMIN-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASRock, Z77 Extreme4
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8470274048 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 27/09/2014 01:07:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092614-27206-01.dmp
This was probably caused by the following module: virtuwddm.sys (VirtuWDDM+0x867C)
Bugcheck code: 0x116 (0xFFFFFA800E0FE010, 0xFFFFF8800577E67C, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\virtuwddm.sys
product: VIRTU
company: Lucidlogix Inc.
description: LucidInterop WDDM Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: virtuwddm.sys (LucidInterop WDDM Driver, Lucidlogix Inc.).
Google query: Lucidlogix Inc. VIDEO_TDR_ERROR
On Sat 27/09/2014 01:07:05 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: virtuwddm.sys (0xFFFFF8800577E67C)
Bugcheck code: 0x116 (0xFFFFFA800E0FE010, 0xFFFFF8800577E67C, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\virtuwddm.sys
product: VIRTU
company: Lucidlogix Inc.
description: LucidInterop WDDM Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: virtuwddm.sys (LucidInterop WDDM Driver, Lucidlogix Inc.).
Google query: Lucidlogix Inc. VIDEO_TDR_ERROR
On Wed 17/09/2014 23:23:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091714-29078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFFA800D3A3860, 0x390424F)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 28/08/2014 15:55:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082814-34507-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0x0, 0xFFFFF8800DBC1700, 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 Mon 21/07/2014 01:05:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072014-45380-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFFA800CC03A30, 0x728312B8)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 04/05/2014 15:23:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050414-31590-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFFA800DCDD310, 0x16667C0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 04/05/2014 00:18:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050314-24616-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0x80, 0x2, 0x1, 0xFFFFF80003284F0F)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
7 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:
virtuwddm.sys (LucidInterop WDDM Driver, Lucidlogix Inc.)
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 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.
How am i supposed to proceed? Thank you all.
Hope it isn't PSU again :X
----
Memtest done, 0 errors.
-
Reply to AngeloXD
m
0
l
AngeloXD
September 27, 2014 2:48:51 PM
tiny voices said:
Could be PSU again. Wouldn't surprise me as the Cx units are not great quality.I've got a TX650. After the first problem..
About the Whocrashed result, i don't understand a lot, but there says some of the errors were related to kernel and video.
How do i fix that?
ps: i wanna check everything before PSU, because i really cant afford a new one right now. :X
-
Reply to AngeloXD
m
0
l
AngeloXD
September 27, 2014 6:16:31 PM
AngeloXD
September 29, 2014 6:36:10 PM
Memtest was done, 0 errors.
Whocrash give the results about the drive: virtuwddm.sys and ntoskrnl.exe .
Already re-installed NVidia drivers.
I already did chkdsk /f.
i took off the GPU, then updated HD 4000 drivers, and tried to remove VIRTU MVP programs ( which didn't work, because system cant find unnins000.dat).
Without the GPU, i don't get BSODed.
about ntoskrnl.exe, i find a lot of related things over the internet, but none of them seems to work.
So, opnions ?
----------
i had to be afk for 2 hours and when i came back i had this :
whocrashe result:
Whocrash give the results about the drive: virtuwddm.sys and ntoskrnl.exe .
Already re-installed NVidia drivers.
I already did chkdsk /f.
i took off the GPU, then updated HD 4000 drivers, and tried to remove VIRTU MVP programs ( which didn't work, because system cant find unnins000.dat).
Without the GPU, i don't get BSODed.
about ntoskrnl.exe, i find a lot of related things over the internet, but none of them seems to work.
So, opnions ?
----------
i had to be afk for 2 hours and when i came back i had this :
Spoiler
Assinatura do problema:
Nome do Evento de Problema: BlueScreen
Versão do sistema operacional: 6.1.7601.2.1.0.256.48
Identificação da Localidade: 1046
Informações adicionais sobre o problema:
BCCode: 50
BCP1: FFFFF6D21C521450
BCP2: 0000000000000000
BCP3: FFFFF800034AF401
BCP4: 0000000000000005
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Arquivos que ajudam a descrever o problema:
C:\Windows\Minidump\092914-28376-01.dmp
C:\Users\Admin\AppData\Local\Temp\WER-129215-0.sysdata.xml
Leia nossa declaração de privacidade online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...
Se a declaração de privacidade online não estiver disponível, leia nossa declaração de privacidade offline:
C:\Windows\system32\pt-BR\erofflps.txt
Nome do Evento de Problema: BlueScreen
Versão do sistema operacional: 6.1.7601.2.1.0.256.48
Identificação da Localidade: 1046
Informações adicionais sobre o problema:
BCCode: 50
BCP1: FFFFF6D21C521450
BCP2: 0000000000000000
BCP3: FFFFF800034AF401
BCP4: 0000000000000005
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Arquivos que ajudam a descrever o problema:
C:\Windows\Minidump\092914-28376-01.dmp
C:\Users\Admin\AppData\Local\Temp\WER-129215-0.sysdata.xml
Leia nossa declaração de privacidade online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...
Se a declaração de privacidade online não estiver disponível, leia nossa declaração de privacidade offline:
C:\Windows\system32\pt-BR\erofflps.txt
whocrashe result:
Spoiler
Crash dumps are enabled on your computer.
On Tue 30/09/2014 02:46:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092914-28376-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFF6D21C521450, 0x0, 0xFFFFF800034AF401, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Tue 30/09/2014 02:46:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: volsnap.sys (volsnap+0x2F20)
Bugcheck code: 0x50 (0xFFFFF6D21C521450, 0x0, 0xFFFFF800034AF401, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\volsnap.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver de cópia de sombra de volume
Bug check description: This indicates that invalid system memory has been referenced.
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 30/09/2014 02:46:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092914-28376-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFF6D21C521450, 0x0, 0xFFFFF800034AF401, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Tue 30/09/2014 02:46:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: volsnap.sys (volsnap+0x2F20)
Bugcheck code: 0x50 (0xFFFFF6D21C521450, 0x0, 0xFFFFF800034AF401, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\volsnap.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver de cópia de sombra de volume
Bug check description: This indicates that invalid system memory has been referenced.
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.
-
Reply to AngeloXD
m
0
l
Related resources
- Constantly getting Blue Screen of Death. Forum
- BLUE SCREEN - happening a lot lately! please help! Forum
- Windows 8 Blue Screen Constantly Forum
- Different Blue Screens that keep happening Forum
- SolvedHD Radeon 7770 constantly crashing/blue screening. Forum
- Computer powers down randomly no blue screen of death but this keeps happening Forum
- Desktop constantly freezing and blue screening. Forum
- SolvedConstantly getting blue screens with different errors Forum
- Computer Constantly Blue Screens After Resolving Previous Issue Forum
- Asus G53sw Blue Screen constantly Forum
- Blue Screens been happening for months(ntoskrnl.exe, nvlddmkm.sys, plus others) Forum
- PC constantly blue screens Forum
- Constantly blue screening Forum
- Brand new homebuilt gaming PC constantly freezes and blue screens Forum
- SolvedConstant Blue Screen of Death Forum
- More resources
Read discussions in other Windows 7 categories
!