Hi, so my pc blue screens every now and then so when it happens for a few days it'll happen a few times then not happen for a few weeks. When my system showed the recovery bit when you log on I screen shot all the info? hoping someone can tell me whats causing my blue screen? - ps. I'm not too good with these kinds of things.
Problem event name: Blue Screen
OS Version: 6.1.7601.2.1.0.768.3
Additional infomation about the problem:
BCCode: d1
BCP1: 000000000000016C
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF88004CBDBE3
OS version: 6_1_7601
Service pack 1 0
Product: 768_1
Files that help describe the problem:
C:\Windows\minidump\022717-27955-01.dmp
C:\Users\Gabbie\AppData\Local\Temp\WER-66206-0.sysdata.xml
Hi, some reasons for Blue Screens
New hardware - Software installed.
Device driver - Video driver - corrupted - faulty.
Faulty Ram - Overheating - Dying hard drive, etc.
======
Post the Minidump files
Create a new folder on the desktop and call it dumpfiles [or something similar]
Look in c:\windows\minidump
Copy the last 4 minidump files to that folder.
Close the folder and right click on it and select Send To Compressed [zipped] Folder.
Windows will compress the file and then save the new zipped file in the same location.
Attach the zip folder by using the 'Upload a File' button.
======
Let us have some Pc specifications.
Check and post
TSG System Information Utility - found here. http://static.techguy.org/download/SysInfo.exe
Download the ISO file then burn to a DVD
Start the Pc using the DVD and run the memory test overnight or for at least 8 passes.
It is best to run a full scan on individual Ram sticks if you can.
Or run the test but if any errors are shown - then remove all sticks of Ram - test each Ram stick one at a time and test them in different slots.
There are some more errors showing.
WARNING: Unable to verify timestamp for mcupdate_AuthenticAMD.dll
ERROR: Module load completed but symbols could not be loaded for mcupdate_AuthenticAMD.dll
WARNING: Unable to verify timestamp for amdide64.sys
I also suffered from BSOD's with the IRQL_NOT_LESS_OR_EQUAL error.
However.. some time ago my desktop booted slow or sometimes not at all as well. At that time I noticed it was my additional usb device on the front panel causing the problem. It has no power itself and became flaky. I removed the PC power cable, dis- and re-connected the internal usb cables and after that this problem was solved.
Recently I now had the BSOD and whatever I tried.. no success. After maybe 10 minutes suddenly the PC crashed again and again. I thought I had a goner...
I took the vacuum cleaner.. Cleaned everything inside thoroughly, did the USB trick as descibed above again and.. problem solved!!! One USB optical mouse driver was installed at start-up but that was all.
So it was dust. Not a lot ;-) but enough to cause problems with the ventilator spreading it around on the boards inside I guess.
Advice.. Clean first and then try the rest of the tips and tricks..
Hi Henkie, thanks for your post and pointing to a possible cause of blue screens and how you solved your problem.
Checking and cleaning out the inner working of a pc should be done regularly. Just be careful using a vacuum cleaner as it can cause static to build up around components, which may add to the existing problem.
Status
Not open for further replies.
You have insufficient privileges to reply here.
Related Threads
?
?
?
?
?
Tech Support Guy
9.9M posts
859.7K members
Since 1998
A forum community dedicated to tech experts and enthusiasts. Come join the discussion about articles, computer security, Mac, Microsoft, Linux, hardware, networking, gaming, reviews, accessories, and more!