BSOD instantly after turning on from sleep mode

[Stav]

Hi guys,

Recently purchased a refurbished PC (last week) and have come across my first BSOD. I'm really hoping it's just a one off and not a sign of things to come. Sorry i don't know the code of the BSOD.

Basically what happened is, i was using Sony Vegas (a video editing software), put the computer to sleep (for around 10mins i think) and when i turned it back on i was instantly met with the BSOD. I really don't have any more info to divulge than that.

I've been told my PSU is underpowered for this machine (405w) and i am currently in the process of purchasing a 650w PSU. Just throwing that out there, not sure if that has anything to do with the BSOD.

Spec

Processor Intel® Core™ i7-2600
Operating System Windows 7 Home Premium 64bit
RAM 8 GB

Sorry not sure how old the hardware is, as i said above i bought a refurb.

All help much appreciated, thanks.

 

[writhziden]

I still see some remnants of Kaspersky on your system: Removal tool for Kaspersky Lab products may be necessary.

Take care of Kaspersky first. Having remnants of security software can cause many different crash errors because it will cause conflicts with current security software.

 

[Stav]

I still see some remnants of Kaspersky on your system: Removal tool for Kaspersky Lab products may be necessary.

Take care of Kaspersky first. Having remnants of security software can cause many different crash errors because it will cause conflicts with current security software.

Hi mate, thanks for the reply.

I used the removal tool and it say's it finished successfully. Just to note, when i bought the PC, it also had an out of date version of Norton also installed, not sure if that has any significance here.

Are there any hints that this could have been an hardware problem? If it was, i still have the opportunity to take it back for a refund, also have a years warranty too.

Also, i've only just noticed, but there are two .dmp files, one was obviously created yesterday, but there is another (only the one file mind, possibly a good sign?) that was created on 31/8/2011, so at the time of the guy who had it before me. Are there any signs that the BSOD i received yesterday and the one he received are similar?

Again thanks for the help, very much appreciated!.

 

[Stav]

I've just received my second BSOD, again after switching on from sleep mode. Getting slightly concerned now. Copied down the error code this time:

BCCode: 1000007e
BCP1: FFFFFFFFC0000096
BCP2: FFFFF8800562914C
BCP3: FFFFF8800335B3E8
BCP4: FFFFF8800335AC40
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Dmp report attached.

Edit: Just to clarify, this does not happen every time the computer powers up from sleep mode, i use sleep mode quite a lot and it has only happened a couple of times.

Edit 2: It's also worth mentioning that i installed some windows updates yesterday as well as malwarebytes (that i later uninstalled)

 

[Stav]

Anyone?

 

[writhziden]

The crash you are getting is actually known to be caused by ZoneAlarm, as well. You may consider removing the program to test.


Sorry, got the BugCheck 0x7E mixed up with 0x7F; the crash you are getting is not a known crash due to ZoneAlarm, but uninstalling ZoneAlarm is still a good test.

Your crash is likely hardware related. Run some hardware checks.

• If you are overclocking any hardware, please stop.
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
• Run all but the advanced tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS​
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!
  
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[Stav]

The crash you are getting is actually known to be caused by ZoneAlarm, as well. You may consider removing the program to test.

Thanks for the reply.

Are there any hints that it could be a hardware problem? I hope not, because as i said above i bought this as a refurb computer and so i am always slightly concerned with any problem that comes up.

The thing is, it's only happened a couple of times, and since the second time it happened i've had it on sleep mode numerous times and no BSOD.

Edit: Ok, just seen the rest of your post.

Thank again.

 

[Stav]

How long roughly do the 'long generic' tests take on seatools?

 

[writhziden]

You're welcome.


Long tests in SeaTools take a few hours per 500 GB, in my experience.