Search
Search titles only
By:
Search titles only
By:
Forums
New posts
Search forums
What's new
New posts
Latest activity
Feedback
View Statistics
Members
Current visitors
Buy Sell Trade
WTB
Log in
Register
Search
Search titles only
By:
Search titles only
By:
New posts
Search forums
Menu
Install the app
Install
Reply to thread
Forums
Technology
Computer Hardware
Blue Screen of Death coming up
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="rohitshakti2" data-source="post: 2011336" data-attributes="member: 22059"><p><strong>Yesterday when I opened the PC it started but gave blue screen thrice. I changed the settings to normal in BIOS. I then recorded the error via the application whocrashedit and the following error was recorded. </strong></p><p></p><p></p><p><strong>Problem signature:</strong></p><p> Problem Event Name: BlueScreen</p><p> OS Version: 6.1.7601.2.1.0.256.1</p><p> Locale ID: 1033</p><p></p><p><strong>Additional information about the problem:</strong></p><p> BCCode: 3b</p><p> BCP1: 00000000C0000005</p><p> BCP2: FFFFF880019C9C10</p><p> BCP3: FFFFF88001FD5960</p><p> BCP4: 0000000000000000</p><p> OS Version: 6_1_7601</p><p> Service Pack: 1_0</p><p> Product: 256_1</p><p></p><p><strong>Files that help describe the problem:</strong></p><p> C:\Windows\Minidump\010110-31012-01.dmp</p><p> C:\Users\Sehgal\AppData\Local\Temp\WER-66066-0.sysdata.xml</p><p></p><p><strong>Read our privacy statement online:</strong></p><p><u><a href="http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409" target="_blank">http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409</a></u></p><p></p><p>If the online privacy statement is not available, please read our privacy statement offline:</p><p><u>C:\Windows\system32\en-US\erofflps.txt</u></p><p></p><p>Problem signature:</p><p> Problem Event Name: BlueScreen</p><p> OS Version: 6.1.7601.2.1.0.256.1</p><p> Locale ID: 1033</p><p></p><p>Additional information about the problem:</p><p> BCCode: 50</p><p> BCP1: FFFFF96000435A58</p><p> BCP2: 0000000000000000</p><p> BCP3: FFFFF96000175009</p><p> BCP4: 0000000000000002</p><p> OS Version: 6_1_7601</p><p> Service Pack: 1_0</p><p> Product: 256_1</p><p></p><p>Files that help describe the problem:</p><p> C:\Windows\Minidump\012615-30544-01.dmp</p><p> C:\Users\Sehgal\AppData\Local\Temp\WER-47003-0.sysdata.xml</p><p></p><p>Read our privacy statement online:</p><p> <a href="http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409" target="_blank">http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409</a></p><p></p><p>If the online privacy statement is not available, please read our privacy statement offline:</p><p> C:\Windows\system32\en-US\erofflps.txt</p><p></p><p></p><p>Crash Dump Analysis</p><p>--------------------------------------------------------------------------------</p><p></p><p>Crash dump directory: C:\Windows\Minidump</p><p></p><p>Crash dumps are enabled on your computer.</p><p></p><p>On Mon 1/26/2015 6:38:05 PM GMT your computer crashed</p><p>crash dump file: C:\Windows\Minidump\012615-28532-01.dmp</p><p>This was probably caused by the following module: Unknown ()</p><p>Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)</p><p>Error: CUSTOM_ERROR</p><p>A third party driver was identified as the probable root cause of this system error.</p><p>Google query: CUSTOM_ERROR</p><p></p><p></p><p></p><p>On Mon 1/26/2015 6:37:04 PM GMT your computer crashed</p><p>crash dump file: C:\Windows\Minidump\012615-41402-01.dmp</p><p>This was probably caused by the following module: Unknown ()</p><p>Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)</p><p>Error: CUSTOM_ERROR</p><p>A third party driver was identified as the probable root cause of this system error.</p><p>Google query: CUSTOM_ERROR</p><p></p><p></p><p></p><p>On Sun 1/25/2015 6:38:06 PM GMT your computer crashed</p><p>crash dump file: C:\Windows\Minidump\012615-30544-01.dmp</p><p>This was probably caused by the following module: win32k.sys (0xFFFFF96000175009)</p><p>Bugcheck code: 0x50 (0xFFFFF96000435A58, 0x0, 0xFFFFF96000175009, 0x2)</p><p>Error: PAGE_FAULT_IN_NONPAGED_AREA</p><p>file path: C:\Windows\system32\win32k.sys</p><p>product: Microsoft® Windows® Operating System</p><p>company: Microsoft Corporation</p><p>description: Multi-User Win32 Driver</p><p>Bug check description: This indicates that invalid system memory has been referenced.</p><p>This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.</p><p>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.</p><p></p><p></p><p></p><p>On Sun 1/25/2015 6:38:06 PM GMT your computer crashed</p><p>crash dump file: C:\Windows\memory.dmp</p><p>This was probably caused by the following module: win32k.sys (win32k!EngRestoreFloatingPointState+0xCF49)</p><p>Bugcheck code: 0x50 (0xFFFFF96000435A58, 0x0, 0xFFFFF96000175009, 0x2)</p><p>Error: PAGE_FAULT_IN_NONPAGED_AREA</p><p>file path: C:\Windows\system32\win32k.sys</p><p>product: Microsoft® Windows® Operating System</p><p>company: Microsoft Corporation</p><p>description: Multi-User Win32 Driver</p><p>Bug check description: This indicates that invalid system memory has been referenced.</p><p>This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.</p><p>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.</p><p></p><p></p><p></p><p>On Thu 12/31/2014 6:32:47 PM GMT your computer crashed</p><p>crash dump file: C:\Windows\Minidump\010110-33306-01.dmp</p><p>This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)</p><p>Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)</p><p>Error: KMODE_EXCEPTION_NOT_HANDLED</p><p>file path: C:\Windows\system32\ntoskrnl.exe</p><p>product: Microsoft® Windows® Operating System</p><p>company: Microsoft Corporation</p><p>description: NT Kernel & System</p><p>Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.</p><p>This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.</p><p>The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.</p><p></p><p></p><p></p><p></p><p></p><p>--------------------------------------------------------------------------------</p><p>Conclusion</p><p>--------------------------------------------------------------------------------</p><p></p><p>5 crash dumps have been found and analyzed.</p><p>Read the topic general suggestions for troubleshooting system crashes for more information.</p><p></p><p>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.</p><p><strong></strong></p><p><strong></strong></p><p><strong>Then I tried to uninstall the AMD graphics as suggested by my friend that graphics file could be a problem as I was getting kdbsync.exe error but it did not got uninstalled by its uninstaller or any normal uninstaller. Then I used AMD clean uninstaller and even the Display Driver Uninstaller but it is still present in my system.</strong></p><p></p><p><a href="http://www.imageupload.co.uk/images/2015/01/28/error_jan.th.png" target="_blank">http://www.imageupload.co.uk/images/2015/01/28/error_jan.th.png</a>[DOUBLEPOST=1422418058][/DOUBLEPOST]<a href="http://www.imageupload.co.uk/56jK" target="_blank">http://www.imageupload.co.uk/56jK</a></p><p><a href="http://www.imageupload.co.uk/56j5" target="_blank">http://www.imageupload.co.uk/56j5</a></p><p><a href="http://www.imageupload.co.uk/56jZ" target="_blank">http://www.imageupload.co.uk/56jZ</a></p></blockquote><p></p>
[QUOTE="rohitshakti2, post: 2011336, member: 22059"] [B]Yesterday when I opened the PC it started but gave blue screen thrice. I changed the settings to normal in BIOS. I then recorded the error via the application whocrashedit and the following error was recorded. [/B] [B]Problem signature:[/B] Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 [B]Additional information about the problem:[/B] BCCode: 3b BCP1: 00000000C0000005 BCP2: FFFFF880019C9C10 BCP3: FFFFF88001FD5960 BCP4: 0000000000000000 OS Version: 6_1_7601 Service Pack: 1_0 Product: 256_1 [B]Files that help describe the problem:[/B] C:\Windows\Minidump\010110-31012-01.dmp C:\Users\Sehgal\AppData\Local\Temp\WER-66066-0.sysdata.xml [B]Read our privacy statement online:[/B] [U][url]http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409[/url][/U] If the online privacy statement is not available, please read our privacy statement offline: [U]C:\Windows\system32\en-US\erofflps.txt[/U] Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional information about the problem: BCCode: 50 BCP1: FFFFF96000435A58 BCP2: 0000000000000000 BCP3: FFFFF96000175009 BCP4: 0000000000000002 OS Version: 6_1_7601 Service Pack: 1_0 Product: 256_1 Files that help describe the problem: C:\Windows\Minidump\012615-30544-01.dmp C:\Users\Sehgal\AppData\Local\Temp\WER-47003-0.sysdata.xml Read our privacy statement online: [url]http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409[/url] If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Mon 1/26/2015 6:38:05 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\012615-28532-01.dmp This was probably caused by the following module: Unknown () Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0) Error: CUSTOM_ERROR A third party driver was identified as the probable root cause of this system error. Google query: CUSTOM_ERROR On Mon 1/26/2015 6:37:04 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\012615-41402-01.dmp This was probably caused by the following module: Unknown () Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0) Error: CUSTOM_ERROR A third party driver was identified as the probable root cause of this system error. Google query: CUSTOM_ERROR On Sun 1/25/2015 6:38:06 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\012615-30544-01.dmp This was probably caused by the following module: win32k.sys (0xFFFFF96000175009) Bugcheck code: 0x50 (0xFFFFF96000435A58, 0x0, 0xFFFFF96000175009, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\win32k.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Multi-User Win32 Driver 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 Sun 1/25/2015 6:38:06 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: win32k.sys (win32k!EngRestoreFloatingPointState+0xCF49) Bugcheck code: 0x50 (0xFFFFF96000435A58, 0x0, 0xFFFFF96000175009, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\win32k.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Multi-User Win32 Driver 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 Thu 12/31/2014 6:32:47 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\010110-33306-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90) Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED 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 program generated an exception which the error handler did not catch. 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 -------------------------------------------------------------------------------- 5 crash dumps have been found and analyzed. 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. [B] Then I tried to uninstall the AMD graphics as suggested by my friend that graphics file could be a problem as I was getting kdbsync.exe error but it did not got uninstalled by its uninstaller or any normal uninstaller. Then I used AMD clean uninstaller and even the Display Driver Uninstaller but it is still present in my system.[/B] [url]http://www.imageupload.co.uk/images/2015/01/28/error_jan.th.png[/url][DOUBLEPOST=1422418058][/DOUBLEPOST][url]http://www.imageupload.co.uk/56jK[/url] [url]http://www.imageupload.co.uk/56j5[/url] [url]http://www.imageupload.co.uk/56jZ[/url] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Technology
Computer Hardware
Blue Screen of Death coming up
Top
Bottom