Windows 7: BSOD and no POST

Britton30 · 13 Nov 2011

I've been overclocking with some success until I got to RAM. After setting the Command to 1T, the PC would not POST, monitor black and "asleep" as LCDs do when rebooting. Could not get to advanced start options via F8, windows DVD went to boot sector repair loop. It kept asking to insert the Windows DVD, which was in.
I switched GFX card and remove all but one Ram module without change. I could get to POST and enter BIOS only by resetting the CMOS CLR on the board. Still no POST afterwords.
I unplugged the OS drive and attached a 2nd HDD and the Windows install was successful on it and it could see the OS drive. I set the OS to first in boot sequence and now it works again fine.
I started driver sweeper to get a BSOD, which happened as soon as the desk top was active and after I clicked Computer. Perf mon report included in the .zip.
Attachment 183556

zigzag3143 · 14 Nov 2011

Quote: Originally Posted by Britton30

I've been overclocking with some success until I got to RAM. After setting the Command to 1T, the PC would not POST, monitor black and "asleep" as LCDs do when rebooting. Could not get to advanced start options via F8, windows DVD went to boot sector repair loop. It kept asking to insert the Windows DVD, which was in.
I switched GFX card and remove all but one Ram module without change. I could get to POST and enter BIOS only by resetting the CMOS CLR on the board. Still no POST afterwords.
I unplugged the OS drive and attached a 2nd HDD and the Windows install was successful on it and it could see the OS drive. I set the OS to first in boot sequence and now it works again fine.
I started driver sweeper to get a BSOD, which happened as soon as the desk top was active and after I clicked Computer. Perf mon report included in the .zip.
Attachment 183556

Gary

Sorry I missed this earlier. Was distracted by an HD crashing here.

This assumes you can boot into normal, or safe mode.

There are several different causes of these. I suspect each the result of something that was done to get it to boot.

Though there is no direct evidence I would remove Symantec at least to test and replace it with Microsoft Security essentials

ftp://ftp.symantec.com/public/englis...moval_Tool.exe

Microsoft Security Essentials - Free Antivirus for Windows

Them two most obvious are BCC 101, and BCC 124. See below for an explanation. These are about half (and the most recent ones)

It is either hardware (again probably ram, or a vital driver). The uptimes in the most recent ones are more than an hour so probably not a driver that loads at start up

I would revert back to stock on everything and then run these tests.
Run the SFC first for it is the easiest and fastest

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

It may need to be run up to three times before successful

Read here for more information SFC /SCANNOW Command - System File Checker

Let us know the results from the report at the end.

Please run these two tests to verify your memory and find which driver is causing the problem.

1-Memtest.

Quote:

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+

2-Driver verifier

Quote:

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/Windows 7 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.

Driver Verifier - Enable and Disable

BCC EXPLANATIONS FROM ABOVE

BCC 101 (called a clock watchdog)
The CLOCK_WATCHDOG_TIMEOUT bug check has a value of 0x00000101. This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.

Best advice that I've seen about this error (from here: http://www.sevenforums.com/crashes-d...tml#post356791 )

Quote:

What you're looking for will be in one of the following categories:

a) BIOS bug

Quote:

b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)

So, check the drivers and make sure everything is put back to default.
Then check the inside of the case (temperature, voltage, dust, etc).
Then run some hardware stress tests

Quote:

Try this free video stress test:

Quote:

FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Try this free stress test: Free Software - GIMPS

Quote:

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Then try replacing parts.
Then look up the versions of your BIOS to see what changes were done.

BCC 124

The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

Some generic advice.

If you are overclocking STOP. return to the default settings at least for now.
If you are running a RAID update its driver.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try

Britton30 · 14 Nov 2011

Thanks Ken, I am most concerned about events on 11-12 and 11-13, with the earlier ones, I know the problem - me.
On the 12th I flashed the BIOS in an effort to gain some overclocking settings which didn't work so I restored the one I had. I OCd the CPU fine and it passed IntelBurn and Prime95 although it got hot but not overly so.

Your conclusions, I think, confirm my suspicions about the RAM. It was my setting the command rate to 1T and my particular hardware config won't handle it. So when I forcefully reset my CMOS, the RAM was reset to default as well. I also ran the furry donut too and that was fine but pushed the GFX temp to 100C, which is allegedly the max temp for it.

Another experiment I tried was too attach a HDD with Window 8 on it as the only drive and the problem still was present, which again led me to hardware, or specifically, my mucking around.

I am in Win 8 at the moment and it is OK (as much as 8 can be) and my Win 7 seems to be purring along as it should.

The BC101 makes sense too because during initial CPU stressing, one or more cores would throttle down.

Should I run Driver Verifier again for a few BSODs? As I said this one happened very quickly after starting it.

zigzag3143 · 14 Nov 2011

The newest are memory management and that usually is a driver. I would run verifier if the BSOD's bother you or are interfering.

You do have several drivers in need of updating

Old drivers

Code:

tifsfilt.sys    8/29/2007 7:37:29 AM        fffff880`04476000    fffff100`0448d000    0xfffff88000017000    0x46d56889                        
timntr.sys    8/29/2007 7:38:23 AM        fffff880`01add000    fffff880`01b8d000    0x000b0000    0x46d568bf                        
tdrpman.sys    11/12/2007 8:36:33 AM        fffff880`01c40000    fffff880`01cd4000    0x00094000    0x473856e1                        
snapman.sys    11/22/2007 3:19:33 AM        fffff880`01ce6000    fffff880`01d21000    0x0003b000    0x47453b95                        
Rt64win7.sys    2/26/2009 4:04:13 AM        fffff880`04dba000    fffff300`04dec000    0xfffffa8000032000    0x49a65b0d

How To Find Drivers:

Quote:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Britton30 · 15 Nov 2011

Okidoki, I'm now working on a clean install on a new SSD. The last driver in the list is Realtek Audio and I've installed it. All the others are from Seagate Disk Wizard or Acronis (same program) which I used several weeks ago to clone the HDD, or Seatools I ran diags with.
The memory issues were likely my not being careful when adjusting other settings which effect memory speed which cause either a non-boot, boot loop, or BSOD.
Thanks, at least this helps confirm I don't have a "real" hardware failure.

EDIT: I spoke too soon, it happened again after switching the drives both to SATAII headers. I have no POST and can't boot any kind of device. New motherboard will be on the way.

Windows 7: BSOD and no POST

BSOD and no POST problems?