BSOD KSOD No Boot Win7 64bit Cold Boot

[roborabbit]

I'm at my wits end...

The problem:

First installed Windows 7 Proff 64-bit on this machine last monday after installing updates / drivers etc I began to recieve intermitent BSODs then began the trouble shooting. Tested memory with memtest86+ passed manually set voltages / timings ran memtest86+ again passed. Started driver verifier etc BSODs stopped. Shut down pc went to bed. Woke up turned on PC and was greeted with the "windows was unable to start up" screen. Rebooted PC tried to start it in safe-mode, couldn't would fail to boot. Tried booting with low res graphics... couldn't. Eventually I decided to do a system restore it finished and booted fine and was stable all day. Next morning I turn on my pc and I am greeted with windows boot error screen again. Getting fed up and figuring I don't have much on the machine anyway I reformat and reinstall windows 7. Wary of more errors I decide to test the drivers by installing them booting down for a bit then starting up again and then going into system restore to get rid of them so I have a clean enviroment for the next set. Finally I come to Ati's CCC 10.2 install it shut down reboot and I'm greeted with a blank screen login screen. At this point I am able to login but all that shows is a scaled down version of my wallpaper. No icons, no taskbar, nada. I can interact with the system ie start up task manager etc even though I still only see a blank wallpaper. Started going back through old drivers figuring that this was an error with ati's newest one. Went back as far as CCC 9.1 and the same thing happened. During all of these I was only able to successfully boot into safe mode. Eventually I decide to try booting in low res mode and walla it worked I was able to boot into windows and turn up my resolution to the max. However, this morning my PC booted back up into windows error screen. It boots gets to the windows icon flash screen and crashes / reboots. I cannot get into safe mode. The only thing that works is to run system restore and (luckily i made a restore point before shutting down last night) select the latest restore point.

Anyone have any idea how to fix this?

System Specs:
OS: Windows 7 Prof. 64-bit
CPU: AMD Phenom II X 4 945 Deneb
Motherboard: Asus M479XTD Evo
Memory: 4x2gB Adata DDR3 1600
Graphics Card: Sapphire Radeon HD 5850
Hard Drives: WD 500 gB Black PSU:
Antec Earthwatts 650
Case: Antec 300

AV: Windows Security EssentialsFirewall: Windows Firewall + Sphinx Firewall Controller

 

[zigzag3143]

I'm at my wits end...

The problem:

First installed Windows 7 Proff 64-bit on this machine last monday after installing updates / drivers etc I began to recieve intermitent BSODs then began the trouble shooting. Tested memory with memtest89+ passed manually set voltages / timings ran memtest89+ again passed. Started driver verifier etc BSODs stopped. Shut down pc went to bed. Woke up turned on PC and was greeted with the "windows was unable to start up" screen. Rebooted PC tried to start it in safe-mode, couldn't would fail to boot. Tried booting with low res graphics... couldn't. Eventually I decided to do a system restore it finished and booted fine and was stable all day. Next morning I turn on my pc and I am greeted with windows boot error screen again. Getting fed up and figuring I don't have much on the machine anyway I reformat and reinstall windows 7. Wary of more errors I decide to test the drivers by installing them booting down for a bit then starting up again and then going into system restore to get rid of them so I have a clean enviroment for the next set. Finally I come to Ati's CCC 10.2 install it shut down reboot and I'm greeted with a blank screen login screen. At this point I am able to login but all that shows is a scaled down version of my wallpaper. No icons, no taskbar, nada. I can interact with the system ie start up task manager etc even though I still only see a blank wallpaper. Started going back through old drivers figuring that this was an error with ati's newest one. Went back as far as CCC 9.1 and the same thing happened. During all of these I was only able to successfully boot into safe mode. Eventually I decide to try booting in low res mode and walla it worked I was able to boot into windows and turn up my resolution to the max. However, this morning my PC booted back up into windows error screen. It boots gets to the windows icon flash screen and crashes / reboots. I cannot get into safe mode. The only thing that works is to run system restore and (luckily i made a restore point before shutting down last night) select the latest restore point.

Anyone have any idea how to fix this?

System Specs:
OS: Windows 7 Prof. 64-bit
CPU: AMD Phenom II X 4 945 Deneb
Motherboard: Asus M479XTD Evo
Memory: 4x2gB Adata DDR3 1600
Graphics Card: Sapphire Radeon HD 5840
Hard Drives: WD 500 gB Black PSU:
Antec Earthwatts 650
Case: Antec 300

AV: Windows Security EssentialsFirewall: Windows Firewall + Sphinx Firewall Controller

I still suspect video, or driver. Are you over clocking cpu, or gpu? Now that you have restored can you safe boot? If so does driver show as working in device manager?

Ken

 

[usasma]

First, I do not recommend installing ATI's CCC program as there have been issues that may be associated with it. And, if you don't use the program, there's no point in installing it. When downloading the driver, look below the CCC download and you'll find the "display driver only" download - that's the one that you need.

Secondly, Driver Verifier does no good unless there's a reason to suspect certain conditions are occurring (the one's that Driver Verifier tests for). To determine that, the memory dumps must be analyzed. For example, if this is a hardware problem (as I suspect) then the Driver Verifier will just confuse the issue without giving any real feedback. Please turn Driver Verifier off until the memory dumps have been analyzed.

To get the memory dumps analyzed, please do the following:

Upload Dump Files:
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service (not RapidShare as the analysts usually can't download from it) - then post the link to it.
Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDump

While waiting for the analysis, you can try these free diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

*****
Additional tests for certain specific circumstances:
Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Try this free stress test: Free Software - GIMPS

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.

 

[roborabbit]

Nothing is overclocked and once I go through system restore I can get into safe mode etc. The device driver does show as working in device manager.

--
Don't have any dump files ATM seeing as how I formatted after the BSODs and have not experienced any since reinstalling(wish I did... sorta). Just the Blank boot screen / failure to boot. My system is not infected by any virus / malware.

Will run Prime95, Furmark, & the other diagnostics.

--

Uninstalling CCC and installing the stand alone driver.

 

[roborabbit]

All the hardware diagnostics are saying all is good. Prime95 @ 5~ hours no errors. HDD tests are clear. No errors / anomalies while running FurMark stability tests. Attached GPU-Z min/max readings while running FurMark. Guess I'm going to be a bit out of luck unless unistalling CCC and installing the stand alone driver resolved the issue or I get a BSOD / dump file...

 

[roborabbit]

Woke up, started pc, enabled boot logging went. On the first boot I was greeted with a blank screen (this is actually progress! it made it past the windows logo screen on a cold boot!) for logon however unlike before i was not able to login and a get a rescaled wallpaper it just stayed at a blank screen it didnt auto reboot etc. So I shut the pc down started it up again enabling boot logging again and everything went fine. Attached are the boot logs of the "failed" boot and successful one. All I can see is that it stopped at / after mouhid.sys and that the one that came after mouhid in the successfull boot was monitor.sys. Any ideas & or help would be appreciated.

--

ATM I'm using a DVI-D -> VGA dongle to connect to my monitor and I have a driver for the display(Acer X193W) installed if this means anything.



--

All hardware diagnostics came back clear. Prime95 @ 12 hours showed no errors.

--

Another thing that I found seems to lead to w7 & video card driver compatibility:

Source
Driver software installation
Summary
Installed generic driver software
Date
2/25/2010 2:37 PM
Status
Solution available
Description
Windows installed driver software that supports the basic features of your Standard VGA Graphics Adapter. Its manufacturer may provide software that enables additional features.
Problem signature
Problem Event Name: PnPGenericDriverFound
Architecture: x64
Hardware Id: PCI\VEN_1002&DEV_6899&SUBSYS_0B001002&REV_00
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Extra information about the problem
Bucket ID: 652490435
---
Solution:
Download and install the driver for your video card

Your video card is missing a driver.
The model name of your video card is Radeon HD 5700 Series.

Click to download the new driver from the AMD website

---

Incorrect seeing as how I have a Radeon HD 5850 (I know this, I bought it and installed it myself). And the Device Manager is showing this: "Display Adapters: Radeon HD 5800 Series" and that it's using the latest driver.

---

Think I may format and reinstall win7 again.

 

[roborabbit]

Well, I'm back and with dump file! Everything was going "ok" for awhile still had cold boot issues where windows would crash at the logo screen but would boot right up afterwards. However, last night while playing Battlefield Bad Company 2 for about 3~ hours straight I got a BSOD. Looking at the GPU-z log for that time I don't see anything abnormal with my cards temp /current / voltage. Booted up the pc this morning and I got a BSOD at the logo screen. Booted into safe mode and grabbed the dump files. There are 2, a mini dump and a Memory dump I'll post the mini dump now while I upload the memory dump to a fileshare (its about 400 mB). Any help would be appreciated.

----
Memory Dump (100 mB~) linked bellow:
http://www.mediafire.com/?xfjylyhenaz

 

[zigzag3143]

Well, I'm back and with dump file! Everything was going "ok" for awhile still had cold boot issues where windows would crash at the logo screen but would boot right up afterwards. However, last night while playing Battlefield Bad Company 2 for about 3~ hours straight I got a BSOD. Looking at the GPU-z log for that time I don't see anything abnormal with my cards temp /current / voltage. Booted up the pc this morning and I got a BSOD at the logo screen. Booted into safe mode and grabbed the dump files. There are 2, a mini dump and a Memory dump I'll post the mini dump now while I upload the memory dump to a fileshare (its about 400 mB). Any help would be appreciated.

This crash is pretty straight forward. Memory corruption.

I would download memtestx86 and run it for at least 5 passes.


Ken

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\032110-54678-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a1f000 PsLoadedModuleList = 0xfffff800`02c5ce50
Debug session time: Sun Mar 21 01:06:54.494 2010 (GMT-4)
System Uptime: 5 days 13:45:40.001
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
...........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {58, 2, 0, fffff80002b4da10}

Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+40 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000058, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002b4da10, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc70e0
 0000000000000058 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReleaseConfirmedPageFileSpace+40
fffff800`02b4da10 4c8b6e58        mov     r13,qword ptr [rsi+58h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002ffc900 -- (.trap 0xfffff88002ffc900)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002ffcb08 rbx=0000000000000000 rcx=0000000000000006
rdx=fffff88002ffcac0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b4da10 rsp=fffff88002ffca90 rbp=00000000fa800ccf
 r8=0000000000000110  r9=000000000019453d r10=000000000000612d
r11=0000000000000110 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiReleaseConfirmedPageFileSpace+0x40:
fffff800`02b4da10 4c8b6e58        mov     r13,qword ptr [rsi+58h] ds:c800:00000000`00000058=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a90469 to fffff80002a90f00

STACK_TEXT:  
fffff880`02ffc7b8 fffff800`02a90469 : 00000000`0000000a 00000000`00000058 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02ffc7c0 fffff800`02a8f0e0 : 00000000`00000000 fffffa80`099fea90 00000000`00000000 fffff8a0`03a09000 : nt!KiBugCheckDispatch+0x69
fffff880`02ffc900 fffff800`02b4da10 : 00000980`00000000 0000007f`fffffff8 fffffa80`099a66b0 fffff800`02bc4200 : nt!KiPageFault+0x260
fffff880`02ffca90 fffff800`02a7b20a : fa800ccf`0000000c fa80099f`ea9004c0 fffffa80`099fea90 fa800ccf`0000000c : nt!MiReleaseConfirmedPageFileSpace+0x40
fffff880`02ffcb10 fffff800`02d7ef13 : fffffa80`099f8c60 00000000`00000000 00000000`0008c081 fffffa80`0008c081 : nt!MiDeleteSegmentPages+0x316
fffff880`02ffcbc0 fffff800`02bb6f6b : fffffa80`099f8c68 00000000`00000001 00000000`00000000 00000000`00000631 : nt!MiSegmentDelete+0x7b
fffff880`02ffcc00 fffff800`02bb75dd : 00000000`00000000 00000000`00000080 fffffa80`06a2b040 00000000`00000012 : nt!MiProcessDereferenceList+0x23b
fffff880`02ffccc0 fffff800`02d34166 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDereferenceSegmentThread+0x10d
fffff880`02ffcd40 fffff800`02a6f486 : fffff880`02d64180 fffffa80`06a4c040 fffff880`02d6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02ffcd80 00000000`00000000 : fffff880`02ffd000 fffff880`02ff7000 fffff880`02ffc800 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiReleaseConfirmedPageFileSpace+40
fffff800`02b4da10 4c8b6e58        mov     r13,qword ptr [rsi+58h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiReleaseConfirmedPageFileSpace+40

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+40

BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+40

Followup: MachineOwner
---------

 

[roborabbit]

I have run it overnight before with no errors popping up. :/ Oh well I'll take out the 2 new sticks and see if that changes anything. Thanks.

 

[QUADratic]

Hi did you get any resolution to this issue, I am having similar issues with 0x000000f4 BSOD. I note there are a few users who are reporting simialr behaviour.


I am hoping maybe we can all disect our systems to see if there is a common component or maybe someonw has a solution that isn't posted.


My issue here : http://www.sevenforums.com/crashes-debugging/214915-bsod-0x000000f4-cold-boot-up.html


Thanks