Getting a BSOD while idling. New system

[fondupot]

interesting. I think for now I will leave the 3.0 header unplugged. It seems to not bsod then.

 

[writhziden]

My guess is it is something involving the new technology. 3.0 still is not fully tested. My Microsoft Kinect kills my laptop if I plug it into the 3.0 ports in Ubuntu.

 

[fondupot]

Extremely annoying tho.

 

[fondupot]

System was running great all day yesterday. Doing a variety of different tasks. I had to leave it on overnight to transfer some large movie files and woke up to an unresponsive tower. Restarted and got this minidump.

The windows event viewer showed it happening around 6:54 my time, so basically RIGHT before i sat down, or it happened when trying to wake it up. What does the minidump show it being caused by?

Thanks

 

[writhziden]

memory_corruption; could be hardware or a driver. Re-enable Verifier:

• a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 213163
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset​
  -> Restart your computer.

If Verifier does not yield any new information after a few days (let us analyze the .dmps before proceeding to the next steps), then do the following:

   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!!!

Strip down your system to run only the bare essentials: one RAM module, the CPU, motherboard, one hard disk, one graphics card (or use onboard graphics if you have it), keyboard, mouse, and one monitor. See how the system behaves by running Windows for twice as long as it typically takes for you to get a crash. If it is stable, add one piece of hardware back at a time until you get crashes again. Take notes of what hardware you add and how the system responds to the hardware changes.

As you add and remove hardware, 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.

 

[fondupot]

Thanks. I will try this tonight.

 

[writhziden]

You're welcome. I also just noticed your 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, uninstall it in device manager and see if the system performs better.

It appears you do have a Marvell controller installed. It is probably out of date and causing conflicts with your SSD. Do the above steps for the SSD before testing Verifier. See if the SSD steps provide stability by running for twice as long as it normally takes to get a crash.

 

[fondupot]

Will do thanks.

 

[fondupot]

You're welcome. I also just noticed your 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, uninstall it in device manager and see if the system performs better.

It appears you do have a Marvell controller installed. It is probably out of date and causing conflicts with your SSD. Do the above steps for the SSD before testing Verifier. See if the SSD steps provide stability by running for twice as long as it normally takes to get a crash.

SSD Firmware: Corsair Force 3 60gb version 1.3.3, up to date.
Mobo BIOS: Gigabyte F7, up to date
Chipset: I downloaded and installed both drivers on the Gigabyte website and installed them to be sure. They are up to date.

Marvell: There werent any marvell devices, but there was a marvel controller installed so i uninstalled that in control panel.

I guess ill monitor the system for now.

 

[writhziden]

Good to see you re-installed the drivers mentioned and everything else is up to date. I am also glad you removed the Marvell controller for now. Let us know if you need help; otherwise, let us know how things are running in a few days.

 

[fondupot]

Good to see you re-installed the drivers mentioned and everything else is up to date. I am also glad you removed the Marvell controller for now. Let us know if you need help; otherwise, let us know how things are running in a few days.

10-4. Been good for tonight. I'm a little hesitant to leave it on overnight again. but i think i might just to see if crashes or not after long idle.

 

[fondupot]

Well, no crashes overnight. Was still running perfect when I woke up this morning.

I also changed some of the power settings to "never turn off hard disks" idk if that was messing something up with the SSD over long idle times, but its off now.

 

[writhziden]

Looks good. I do not have an SSD, so I am not familiar with them. I did some research to see if you changing that setting would be a bad thing for the SSD hardware, and it appears some actually recommend it. I saw a guide that suggested having the SSD on all the time so it can perform garbage collection even when logged off.

Windows 7 SSD Setup

 

[fondupot]

Looks good. I do not have an SSD, so I am not familiar with them. I did some research to see if you changing that setting would be a bad thing for the SSD hardware, and it appears some actually recommend it. I saw a guide that suggested having the SSD on all the time so it can perform garbage collection even when logged off.

Windows 7 SSD Setup

Hmm ok. I will read that and play around. Chances are it was probably the marvell driver and or the out of date chipset.

I usually never leave my computer on unless I am physically using it. Especially now with the SSD it starts up in less than 10 seconds. no need to waste the energy to keep it running.

 

[writhziden]

Glad the system is more stable. Let us know if you need further help. Otherwise, post back in a few days how the system is responding.

 

[fondupot]

got this one today while it was idling. I went upstairs to shower and came back to an unresponsive system. the tower was on, but the screens were acting like they wre in sleep. couldnt wake them up by doing anything.

 

[writhziden]

Crashes still point to memory. Any new symptoms?

 

[fondupot]

no its been much more stable lately. i will run memtest again.

 

[writhziden]

Glad it has at least been more stable. Need to get it so it is completely stable, though. Good luck with the memtest!

 

[fondupot]

ran memtest overnight. for about 8 hours, 11 passes. no errors.....

I havent had any bsods in normal operation. it was just when I had left it for a while to idle.