Windows 7 64bit BSOD Problem

[sonavor]

I have been fighting a BSOD problem on a new system for a couple of weeks now. The history of the problem is as follows: Built a new PC using an Asus P7P55D-E Pro MB, 8 GB of DDR3 1600 RAM, 2 x WD 640GB HDs, XFX Geforce GTS250 video card, Corsair CMPSU-750HX power supply, Intel Core i5-661 3.33GHz CPU.

I had no problems installing Windows 7 64bit and all of the hardware was recognized by the Windows 7 install disk. After the Win7 install I began installing software. Everything installed and worked well. When I was finished I ran the Win7 backup and made an image. After that I shut down and went to bed.

The next morning when I turned on the PC Windows 7 started, I logged on, then shortly after - BSOD. On the reboot I tried to start Windows again but it crashed again. Next I selected safe mode. That worked.

Once Windows 7 launches successfully I am able to work for hours (even a couple of days). I installed more software and Microsoft installed updates. The problem continued. If I shut the computer down for a while I get the BSOD on restart.

The strangest occurrence I have seen is where Windows would not give me a Safe Mode option after a crash. In that case I had to use my system repair disk to boot up. However, it took a couple of tries before the repair boot disk was recognized. Once it came up I was able to use system restore to get back into Windows 7. Again, once it came up, I could run for hours without even a hiccup. The issue with the boot disc made me wonder if the DVD drive was a problem so I swapped it out with a spare I had. On reboot I was actually able to log on to Windows 7 and open a browser before the BSOD.

I am at a loss now on what to do next. I have updated the video card drivers to the latest version. Since the problem is always shortly after starting or logging in to windows I suspect some hardware problem that is still initializing. However, I don't know what. I also updated my motherboard bios to the most recent version.

The Windows 7 Event Viewer shows a Kernal-Power source and Event ID 41 (task category: 63) for this last BSOD I experienced. I was able to reboot to safe mode then back to normal windows login after that though. I am using the PC to post this message so the system came up fine and is working right now.

Additional information: I recently built another system using the same motherboard, CPU, hard drives and RAM. That build also was a Windows 7 64bit machine. It has run perfect from day 1 and has never had a BSOD.

So I don't know if I have a motherboard problem or what. I have installed some games and run them for hours so I don't think the video card is an issue. The audio card is using Microsoft Windows 7 supplied drivers. I wonder if I should switch those to audio drivers from the Asus installation disk.

If anyone has experience anything like this I would appreciate the help in fixing it.

I have attached my minidump file.

Thanks,
sonavor

 

[YakSipper]

You're getting a memory corruption error. There are many possible causes but first to look at is to completely uninstall your antivirus to see if the problems persists.

Excellent chance your current av is the cause, especially because I see you have a Symantec product on there.

 

[Crispy]

Uninstall your Symantec Ant-Virus with this program Download and run the Norton Removal Tool and you will have to find another Anti-Virus software.

 

[sonavor]

Might have solved the problem

I think I might have solved the problem. I don't think the problem has anything to do with Symantec Endpoint Protection. I am actually using SEP 11 (64bit) on four other Win7 Pro (64bit) builds I have done in the past few months. I am also using SEP (32bit) on a Win7 Pro (32bit) system I have. None of those machines have had any issues with it. Also, when the PC has got past the first couple of minutes of Windows 7 boot up, I have never had a BSOD. I have run SEP file scans and have even run Win7 backups to an external USB drive with SEP running.

I went back and looked at all of my drivers again. My Asus P7P55D-E Pro motherboard has an onboard audio device. I let Windows 7 install a driver for that device when I installed Win7 and the sound all worked fine. However, in looking at the driver yesterday, I realized that Windows 7 installed a driver that says it is for Realtek. The onboard audio device is a Via audio device and Asus had an updated driver for it on their web site.

I have now switched to using the Via audio driver and so far I haven't had a BSOD in the last two system boot ups. In both attempts I left the PC off for about 30 minutes.

If get another BSOD right after Windows7 starts up I will update this post.

 

[sonavor]

A different kind of BSOD

Well, I got another BSOD...but this is different. To explain, I actually have received two kinds of BSOD events on this PC.

The BSOD that I attached the minidump file for on this thread was a case where Windows 7 started, I got to the login screen and after I logged in the error occurred.

The other BSOD I have seen previously (and now just got again) is where the PC starts (after being off for several hours), Windows 7 starts and during the Windows 7 logo display (prior to the login screen) - a BSOD flashes on the screen.

In the case where a BSOD occurred after the Windows 7 login I would get an option on restart to enter Safe Mode. With the BSOD that occurs during the Windows 7 startup prior to the login screen, I only get two options: attempt the Windows 7 start again or run the repair disk. Trying to start Windows 7 again always fails so I use my Windows 7 repair disk and it always fixes the problem.

Using the Windows 7 repair disk you have two options: Attempt a repair using the disk or replace the Windows 7 drive with a backup image (usually from an external USB drive or another drive on the computer). The repair option has always worked for me.

After the repair has run its course a popup dialog window appears and gives an option to view the results. Here is a summary of what my repair action shows:

Number of repair attempts: 1

System Disk = \Device\Harddisk0
Windows = E:\Windows
AutoChkRun = 0
Number of root causes = 2
​

I don't know why it shows Windows = E:\Windows when it is actually on Drive C.
Following that information the report continues with some information about tests on Harddisk0 - all of those tests pass:

System disk test
Result: Completed successfully
​

After the system disk tests the report has this information:

Root cause found
Boot Manager failed to find OS Loader
Result: Failed. Error Code = 0x490

Repair actions: Boot Configuration data store repair
Result: Failed. Error Code = 0x490

Repair Action System Restore
Result: Failed. Error Code = 0x490
​

From that bit of information I thought the repair was not successful. However, the popup dialog has a button to Finish (and reboot). When I select that button the computer restarts and Windows 7 starts up without any problems.

So is the cause of this annoying BSOD actually because the Boot Manager fails to find OS Loader? If so, what does that mean? A bad harddisk?

 

[zigzag3143]

I have been fighting a BSOD problem on a new system for a couple of weeks now. The history of the problem is as follows: Built a new PC using an Asus P7P55D-E Pro MB, 8 GB of DDR3 1600 RAM, 2 x WD 640GB HDs, XFX Geforce GTS250 video card, Corsair CMPSU-750HX power supply, Intel Core i5-661 3.33GHz CPU.

I had no problems installing Windows 7 64bit and all of the hardware was recognized by the Windows 7 install disk. After the Win7 install I began installing software. Everything installed and worked well. When I was finished I ran the Win7 backup and made an image. After that I shut down and went to bed.

The next morning when I turned on the PC Windows 7 started, I logged on, then shortly after - BSOD. On the reboot I tried to start Windows again but it crashed again. Next I selected safe mode. That worked.

Once Windows 7 launches successfully I am able to work for hours (even a couple of days). I installed more software and Microsoft installed updates. The problem continued. If I shut the computer down for a while I get the BSOD on restart.

The strangest occurrence I have seen is where Windows would not give me a Safe Mode option after a crash. In that case I had to use my system repair disk to boot up. However, it took a couple of tries before the repair boot disk was recognized. Once it came up I was able to use system restore to get back into Windows 7. Again, once it came up, I could run for hours without even a hiccup. The issue with the boot disc made me wonder if the DVD drive was a problem so I swapped it out with a spare I had. On reboot I was actually able to log on to Windows 7 and open a browser before the BSOD.

I am at a loss now on what to do next. I have updated the video card drivers to the latest version. Since the problem is always shortly after starting or logging in to windows I suspect some hardware problem that is still initializing. However, I don't know what. I also updated my motherboard bios to the most recent version.

The Windows 7 Event Viewer shows a Kernal-Power source and Event ID 41 (task category: 63) for this last BSOD I experienced. I was able to reboot to safe mode then back to normal windows login after that though. I am using the PC to post this message so the system came up fine and is working right now.

Additional information: I recently built another system using the same motherboard, CPU, hard drives and RAM. That build also was a Windows 7 64bit machine. It has run perfect from day 1 and has never had a BSOD.

So I don't know if I have a motherboard problem or what. I have installed some games and run them for hours so I don't think the video card is an issue. The audio card is using Microsoft Windows 7 supplied drivers. I wonder if I should switch those to audio drivers from the Asus installation disk.

If anyone has experience anything like this I would appreciate the help in fixing it.

I have attached my minidump file.

Thanks,
sonavor

This crash was caused by memory corruption. I would download memtestx86 and run it for 5 passes to check your ram.

Let us know if you need help

Ken

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


Loading Dump File [D:\Users\K\Desktop\041610-31839-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: F:\Symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a05000 PsLoadedModuleList = 0xfffff800`02c42e50
Debug session time: Fri Apr 16 03:37:52.028 2010 (GMT-4)
System Uptime: 0 days 0:02:34.432
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002a96765, 0, ffffffffffffffff}

Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+265 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002a96765, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!MiUnlinkPageFromLockedList+265
fffff800`02a96765 410fb6511b      movzx   edx,byte ptr [r9+1Bh]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cad0e0
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  acrodist.exe

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff880078d06e8 -- (.exr 0xfffff880078d06e8)
ExceptionAddress: fffff80002a96765 (nt!MiUnlinkPageFromLockedList+0x0000000000000265)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff880078d0790 -- (.trap 0xfffff880078d0790)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=08000000001e03ab rbx=0000000000000000 rcx=00000000001c1095
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a96765 rsp=fffff880078d0920 rbp=0000000000000005
 r8=0000058000000000  r9=7ffffa8005a0b010 r10=0000000fffffffff
r11=2aaaaaaaaaaaaaab r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         ov up ei pl nz na pe nc
nt!MiUnlinkPageFromLockedList+0x265:
fffff800`02a96765 410fb6511b      movzx   edx,byte ptr [r9+1Bh] ds:7ffe:7ffffa80`05a0b02b=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002aaf929 to fffff80002a75600

STACK_TEXT:  
fffff880`078cff18 fffff800`02aaf929 : 00000000`0000001e ffffffff`c0000005 fffff800`02a96765 00000000`00000000 : nt!KeBugCheckEx
fffff880`078cff20 fffff800`02a74c42 : fffff880`078d06e8 fffffa80`05a1abe0 fffff880`078d0790 00000000`00000001 : nt!KiDispatchException+0x1b9
fffff880`078d05b0 fffff800`02a7354a : 00000000`00000001 00000000`00000000 00000000`00000000 fffff8a0`06400330 : nt!KiExceptionDispatch+0xc2
fffff880`078d0790 fffff800`02a96765 : fffffa80`09a90690 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`078d0920 fffff800`02a91a6c : fffffa80`09089830 00000000`00000000 fffff880`09089830 fffffa80`05a1abe0 : nt!MiUnlinkPageFromLockedList+0x265
fffff880`078d09b0 fffff800`02a8f623 : ffffffff`ffffff00 00000000`01ec0000 00000000`00018000 fffff800`00000000 : nt!MiDispatchFault+0x7ac
fffff880`078d0ac0 fffff800`02a736ee : 00000000`00000000 00000000`00000004 00000000`7efa4001 fffffa80`0871fb30 : nt!MmAccessFault+0x343
fffff880`078d0c20 00000000`72d25478 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`03f8fc1c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x72d25478


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiUnlinkPageFromLockedList+265
fffff800`02a96765 410fb6511b      movzx   edx,byte ptr [r9+1Bh]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MiUnlinkPageFromLockedList+265

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1E_nt!MiUnlinkPageFromLockedList+265

BUCKET_ID:  X64_0x1E_nt!MiUnlinkPageFromLockedList+265

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

 

[sonavor]

Next step

I have memtestx86 so I will try that tonight. The system has 8GB of RAM so it will probably take a while.

The only thing is - the minidump you are looking at (the one I attached for the original BSOD) is no longer happening on this machine. I think my MB bios update and/or the update to the audio card driver fixed that problem.

The current BSOD happens before Windows 7 starts and does not produce a minidump file.

I Googled other people that have had the -
Boot Manager failed to find OS Loader
Result: Failed. Error Code = 0x490

message from the repair disk run.

I didn't find anyone that had an answer for that but it was interesting that other people have seen it.

I am wondering if the problem is because I installed Windows 7 on a disk with partitions. When I installed Windows 7 on my 640GB drive I allotted about 350GB for Windows 7. The installation created that C partition along with an (unmounted volume) System Reserved partition of 100MB. Later I created a third partition (D drive letter) that is around 220GB.

When the system starts up with the Windows 7 repair disk, the repair disk always says that windows is here: E:\Windows

I don't understand why that is but the repair disk always fixes my errors.

On my other Windows 7 machines all of the installations for the Windows 7 OS are on a single harddisk with no other partitions. I don't know if that is why they don't have any issues or not.

But I will run the memory test to eliminate that possibility. I might also pull two of the memory sticks so I am only running 4 GB of RAM for a while to see how that affects the problem.

 

[sonavor]

Update - memtestx86 results

I ran memtestx86 up to test 10 and no errors were found. I felt the memory was okay because I have never had a BSOD after the machine has started up and was past the login for a few minutes. The BSOD incidents I have seen have been within a minute or two after login (that's the one I think the MB bios update and audio driver update fixed) and during the Windows 7 start splash screen (prior to a login screen). Once passed those two conditions the machine has been solid.

 

[Jonathan_King]

Keep uploading the dmps as they come.

Memtest should be run for about 12 hours for your amount of RAM, more if you can bear to wait that long.

 

[sonavor]

No minidump file

With the current BSOD (I'll call it the "Quick One") there is no minidump file written. The BSOD occurs when the Windows 7 logo is displayed on the screen - immediately after the PC boot bios information. The Windows 7 login page has been rendered yet. So I think there is some glitch that occurs preventing anything from happening.

I did have Raxco Perfect Disk setup to defrag the drives so I disabled that. If the problem persists I am going to put my Windows 7 "C" drive on its own physical diskdrive (with just one partition) and see if that fixes the problem.

As for the memory, I will try and run a lengthy test using memtestx86. However, I really don't think it is causing my current problem. I have been running the PC for several hours now with some memory intensive applications and I never get a BSOD.

 

[zigzag3143]

With the current BSOD (I'll call it the "Quick One") there is no minidump file written. The BSOD occurs when the Windows 7 logo is displayed on the screen - immediately after the PC boot bios information. The Windows 7 login page has been rendered yet. So I think there is some glitch that occurs preventing anything from happening.

I did have Raxco Perfect Disk setup to defrag the drives so I disabled that. If the problem persists I am going to put my Windows 7 "C" drive on its own physical diskdrive (with just one partition) and see if that fixes the problem.

As for the memory, I will try and run a lengthy test using memtestx86. However, I really don't think it is causing my current problem. I have been running the PC for several hours now with some memory intensive applications and I never get a BSOD.

We actually need the DMP files created in the crash. use these to find and upload to us. http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

thanks

Ken

 

[sonavor]

Update on testing the memory

The only location on my PC where I have found the DMP crash files is at:
C:\Windows\Minidump

The only DMP files there are from my two BSOD incidents that happened after I logged in to Windows 7. Those dates were 4/2/2010 and 4/16/2010. The latter DMP file is the one I uploaded on this thread.

Since that time I have not had any BSOD incidents after logging on to Windows 7. I have had three or four BSOD incidents during the Windows 7 startup (prior to the login screen). There are no DMP files on my machine for those BSOD events. I don't know why but there aren't but there aren't any.

Meanwhile, I have continued on with my system memory testing as suggested by an earlier posting in this thread.

I found something interesting in my memory testing (morning of 4/19/2010). After letting the computer sit powered off over night, I started it up and immediately started with the memtest86(+) instead of trying Windows 7.

On test 5 my memory block from 4000 to 6000 (rounded) failed. So I immediately thought this was it. To further test it I pulled out the memory stick (I have four two GB RAM sticks) in the third slot. I ran the test again - up through test 6. There were no errors. To double check I put the RAM stick I took out back in to slot 3 and removed the slot 4 RAM stick. I re-ran the memory test but nothing failed up through test 6. I tried a few more tests, trading out the RAM sticks from slot 3 and slot 4. I could not get any failure again.

I decided to see what would happen if I took out the memtest86(+) disk and let the machine start up Windows 7. It started fine and I am still running the PC twelve hours later.

Now my questions to resolve are these -
1. Was the RAM test error due to a bad test run?
2. Is the RAM bad? (and is it causing the BSOD on start up?)
3. Is the problem temperature related since I haven't seen the error after the machine gets into Windows 7 (or after the memory test has run a while)?
4. Could the problem be with the motherboard (like maybe a bad memory slot)?

When I power down my PC tonight I will leave the slot 3 empty and put the suspect RAM stick in slot 4. When I start the PC up cold in the morning I will run memtest86(+) again. If the RAM stick is bad I should see a failure in the slot 4 RAM. If I don't get a failure then I will suspect the motherboard slot 3 RAM connector and setup a test for that.

 

[Jonathan_King]

Just a thought, you may try increasing your RAM voltage slightly. Be careful, to much juice will fry your RAM. Increase it one level, the smallest amount possible.

 

[sonavor]

Testing RAM voltage

Thanks for the RAM voltage suggestion. I talked to an Asus technician and he also suggested that. I am trying out a higher voltage now. The real test will be in the morning after the machine has been idle for an extended period of time. I turned it off for about three hours today and ran the memory tests with the higher DRAM voltage and didn't get any errors. However, I don't know if that was a long enough time to say the problem is fixed.

FYI - The Asus technician is also having me check the system voltages using the bios on start up so I can eliminate any power supply problem. As for the DRAM voltage - the voltage was originally set to "Auto". The bios showed that voltage measuring around 1.54v. I check my G.Skill RAM specs and saw that it is supposed to be able to handle 1.6v without any danger. So I am currently running with the DRAM voltage setting at 1.6v.

NOTE:
Since I have been verifying the RAM using memtest86(+) and doing the voltage change I haven't had any Windows BSOD events.

 

[sonavor]

BSOD Resolved - RAM fails even at 1.6v

Well, leaving the machine off overnight then restarting and running memtest86 this morning resulted in the RAM failing at the same place: Test 5 (Block Move, 80 moves). So the DRAM voltage setting at 1.6v didn't help. A support guy from G.Skill told me to send my RAM in to them for replacement so I will do that.

I believe the Windows 7 BSOD in my case can be put down as a PC memory hardware problem.

Note: I am on the PC and in Windows 7 writing this message. After the failed Test 5 memtest86, I rebooted and ran the test a second time. As usual it passed the second time. Once the RAM test passes I can always continue on and login in to Windows 7 without any BSOD.

 

[neodeep2001]

sonavor, I am also having the same problem as you. My motherboard is also the same as yours (ASUS P7P55D-E).
I have just clean installed windows 7 sp1 and I have had several BSOD incidents during the Windows 7 startup (prior to the login screen). The problem only occurs after the computer turns off for a long period of time (overnight).
sonavor, have you ever found any solutions for the problem?
Thank you.