AvalonBright
New member
- Local time
- 3:19 PM
- Messages
- 11
So, out of nowhere last night, my PC suddenly BSOD'd suddenly while just browsing things. It's never had any issues, it's about a year old now. It happened again at some point overnight as I woke up to the login screen and it telling me it recovered from a blue screen. Then, it happened once more today about 2 hours ago during a League of Legends Dominion match.
My girlfriend suggested from what little I knew that I update my graphics drivers, which I did and rebooted. Still, if I could get anything more concrete it'd really help.
The last error that popped up was
I'm using an HP Pavilion Elite HPE, with an i7-480 processor, 8GB of RAM, and a Radeon 5770 graphics card. I ran a monitoring program and the core temperatures were around 55-68 C while idling, and the graphics card never got above 57 C, so it doesn't look like it's overheating. I'm including the minidumps, hopefully someone can help point me in the right direction here.Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: c2
BCP1: 0000000000000007
BCP2: 0000000000001097
BCP3: 0000000009060001
BCP4: FFFFFA8007D8CDD0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1.
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Fantastic. I thought everything was fine, then suddenly, it bsod's again. I don't know what the hell is going on. I need the computer for work atm, I can't just shut it down for hours to let this memory scan run until overnight. I'm stuck until I go to bed.
I wasn't even doing anything intensive, just sitting here talking to someone on IRC when it just flickered to black out of nowhere, then popped up with this.
Attaching the most recent minidump as well. Someone please help more, with a better explanation of things.. (i.e. why it's memory, or whatever else one finds in the dump... )Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFFA8007C787A7
BCP3: 0000000000000000
BCP4: 0000000076CE0000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
I'm at wits' end with the inability to figure out wtf is causing this. It's not overheating, it's not the graphics drivers, running malwarebytes now to see if it's a virus, the computer itself says everything is behaving properly... idk what to do... ~.~ This computer isn't even a year old, and I don't have money for a new one. Could really use some more concrete help...
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
I've been letting it run while working for the past 6 1/2 hours. Nothing yet.
...Not seeing how that's helpful. If I knew what caused the blue screen then I wouldn't be here. The whole POINT is I don't know what I'm doing that causes it. Sometimes it crashes in the middle of League of Legends, sometimes it crashes when I'm not doing anything but chatting in IRC. The whole point of it driving me up a wall is that it's completely unreproducible. Still running though.