CPU/Mobo Blue Screen of Death coming up

rohitshakti2

rohitshakti2

Adept
Hi friends

I am using PC with AMD Quadcore athlon 635, 785G mobo, 4 GB Corsair ram. I have OC my PC to normal 3.2 ghz from 2.9 ghz.

Recently I formatted my C drive and installed Win7 again and it was working fine but from the last 2-3 days my PC starts and gives error of BLUE SCREEN OF DEATH a copy of which is enclosed just after 2-3 min of opening the PC.

I removed the OC but even then it showed the error. Then I open the PC and pushed all wires but this time it hangs on opening and nothing happens. I even tried putting the PC on save mode but it also gave blue screen....

Please help...

2myc9jq.jpg
[/IMG]

IMG_20150108_230932878.jpg
[/url]

[/IMG]

23gz09y.jpg
[/IMG]
 
haiprazzad said:
ry removing the RAM and insert again after cleaning. Dust might cause this issue.
Click to expand...
Use a soft eraser along the ram pins. this gets rid of stubborn dirt without scratching the contacts.
An old toothbrush is effective in cleaning out the ram slot on the motherboard.

Also, when the system hangs on startup, is it hanging before or after the os loads? If its after, then it could be a faulty driver.
 
Last edited:
a1preo.jpg

169ne5y.jpg


169ne5y.jpg


I cleaned the ram, its slots, the whole PC from inside and now the Blue screen is not coming up.

Now my PC worked for error free for one whole week but now again a new problem has started.

Now it started showing me during the boot process that my BIOS has encountered error due to Overclocking... THen I changed the bios setting to normal but it did not worked. I then used to press enter Key in order to access my PC. This worked for 2 days.

Now yesterday when I opened the PC, I could not see anything on the monitor. Then I checked the CMOS cell and even changed it but did not helped. Then I removed the Cell from MB for nearly 15-20 min and put it back but it also did'nt helped.

Please tell what to do.....

http://postimg.org/image/53fks7rzl/full/
 
Last edited by a moderator:
I am also new to BIOS errors. Lets hope for more experienced people to come and guide you. Meabwhile try setting your BIOS to default few more times.
 
I'm also a noob with the intricacies of a bios and the bsod. however, the screenshot shows something about a 'page fault in a non-paged area'. if possible, can you try to get your hands on another ram module? swap it out with your current stick and see if it recurs.
 
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.


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: 3b
BCP1: 00000000C0000005
BCP2: FFFFF880019C9C10
BCP3: FFFFF88001FD5960
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\010110-31012-01.dmp
C:\Users\Sehgal\AppData\Local\Temp\WER-66066-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

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:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

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.


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.

http://www.imageupload.co.uk/images/2015/01/28/error_jan.th.png[DOUBLEPOST=1422418058][/DOUBLEPOST]http://www.imageupload.co.uk/56jK
http://www.imageupload.co.uk/56j5
http://www.imageupload.co.uk/56jZ
 
rohitshakti2 said:
I tried it in all 4 slots.
Click to expand...
Instead of changing the slot, did you try using a different memory stick altogether? Try to borrow one from a friend if possible.

Doubt it's a psu issue. you'd have a different set of problems for that.

Most likely a freak driver issue - your last option i guess would be a reformat since DDU didn't get it all. I hope you ran DDU in safe mode, otherwise do that.
 
What applications do you have on startup? Disable them one by one and boot the system. See if it crashes. If this fails, it's probably your RAM at fault.
 
Crapmypants said:
Instead of changing the slot, did you try using a different memory stick altogether? Try to borrow one from a friend if possible.

Doubt it's a psu issue. you'd have a different set of problems for that.

Most likely a freak driver issue - your last option i guess would be a reformat since DDU didn't get it all. I hope you ran DDU in safe mode, otherwise do that.
Click to expand...

THanks for the replies friends.

I ran DDU in normal mode and it uninstalled the Graphics file. Then I reinstalled the Graphics file and it worked.

Then I ran Memtest86+ and my ram passed 7 passes and after that I closed the PC.

Today when I tried to open the PC in morning, it was again not showing anything on the monitor, then I tried restarting the PC 3 times but it did'nt showed anything on monitor. As I was in hurry to go to office, I closed it.

pls help what could be the trouble.
 
Mostly a PSU issue, try booting without graphics card if you have a PCi one. Have you tried replacing the CMOS battery? If possible do try with another PSU unit and if you are able to get in windows, try and update your motherboard BIOS.
 
Need more details
-does the rest of the pc start?
-can you hear the fans spin or the hard drive indicator light up?
-do you hear a beep on start-up? how many?
 
Back
Top