at seemingly random times my pc will either bsod, or my computer will just freeze entirely and the only thing i can do is hard reset. so far, i have received stop error 0x1a, 0x50, 0xf7, 0x3b, 0x50, and 0xd1. any help would be appreciated.
bsod's and random freezes
posted in
Hardware
at seemingly random times my pc will either bsod, or my computer will just freeze entirely and the only thing i can do is hard reset. so far, i have received stop error 0x1a, 0x50, 0xf7, 0x3b, 0x50, and 0xd1. any help would be appreciated.
When it freezes does it freeze or does it blackscreen?
When it freezes does it freeze or does it blackscreen?
wareyaWhen it freezes does it freeze or does it blackscreen?
it simply freezes.
[quote=wareya]When it freezes does it freeze or does it blackscreen?[/quote]
it simply freezes.
it simply freezes.
Those stop errors are all pretty much caused by a faulty driver or new hardware with faulty drivers. Did you change drivers or install new hardware recently?
https://support.microsoft.com/en-us/kb/315263
Make sure you have minidump files enabled and next time your PC BSODs, follow the steps here to check the minidump file with dumpchk or windbg. It'll tell you "probably caused by <driver name>". It may point to a kernel driver but that's because another driver corrupted something in memory that the kernel driver stepped on. Based on the varied stop codes you've received, you'll probably get the problematic driver after a couple of crashes.
Those stop errors are all pretty much caused by a faulty driver or new hardware with faulty drivers. Did you change drivers or install new hardware recently?
http://www.techrepublic.com/blog/windows-and-office/how-do-i-use-windbg-debugger-to-troubleshoot-a-blue-screen-of-death/
https://support.microsoft.com/en-us/kb/315263
Make sure you have minidump files enabled and next time your PC BSODs, follow the steps here to check the minidump file with dumpchk or windbg. It'll tell you "probably caused by <driver name>". It may point to a kernel driver but that's because another driver corrupted something in memory that the kernel driver stepped on. Based on the varied stop codes you've received, you'll probably get the problematic driver after a couple of crashes.
http://www.techrepublic.com/blog/windows-and-office/how-do-i-use-windbg-debugger-to-troubleshoot-a-blue-screen-of-death/
https://support.microsoft.com/en-us/kb/315263
Make sure you have minidump files enabled and next time your PC BSODs, follow the steps here to check the minidump file with dumpchk or windbg. It'll tell you "probably caused by <driver name>". It may point to a kernel driver but that's because another driver corrupted something in memory that the kernel driver stepped on. Based on the varied stop codes you've received, you'll probably get the problematic driver after a couple of crashes.
thanks. i'll be sure to post the results the next time i blue screen.
thanks. i'll be sure to post the results the next time i blue screen.
whenever i blue screen it says that the physical memory dump is complete, and my pc is stuck on the blue screen. i have to manually restart and there is no minidump file created upon checking the folder.
whenever i blue screen it says that the physical memory dump is complete, and my pc is stuck on the blue screen. i have to manually restart and there is no minidump file created upon checking the folder.
Sorry for taking so long for a response, but here is the dump file for one of my system service exception crashes if it matters to anyone.
122215-29952-01.dmp 12/22/2015 3:33:50 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`03b6fa70 fffff880`061f9860 00000000`00000000 x64 C:\Windows\Minidump\122215-29952-01.dmp 2 15 7601 262,144 12/22/2015 3:34:41 PM
Sorry for taking so long for a response, but here is the dump file for one of my system service exception crashes if it matters to anyone.
122215-29952-01.dmp 12/22/2015 3:33:50 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`03b6fa70 fffff880`061f9860 00000000`00000000 x64 C:\Windows\Minidump\122215-29952-01.dmp 2 15 7601 262,144 12/22/2015 3:34:41 PM
122215-29952-01.dmp 12/22/2015 3:33:50 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`03b6fa70 fffff880`061f9860 00000000`00000000 x64 C:\Windows\Minidump\122215-29952-01.dmp 2 15 7601 262,144 12/22/2015 3:34:41 PM
You have to actually upload the .dmp file and link it here
You have to actually upload the .dmp file and link it here
In the meantime, it can't hurt to try sfc /SCANNOW via command prompt as an administrator.
In the meantime, it can't hurt to try sfc /SCANNOW via command prompt as an administrator.
The results from windbg:
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: CORRUPT_MODULELIST
Followup: MachineOwner
The results from windbg:
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: CORRUPT_MODULELIST
Followup: MachineOwner
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: CORRUPT_MODULELIST
Followup: MachineOwner
Please
sign in through STEAM
to post a comment.