BSOD Crash after logging in.

[FuNkYBoY]

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 3081

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002F04795
BCP3: 0000000000000000
BCP4: FFFFFFFFFFFFFFFF
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\062010-25303-01.dmp
C:\Users\FuNkYBoY\AppData\Local\Temp\WER-63523-0.sysdata.xml

Minidump attatched.

 

[FuNkYBoY]

This has been a consistant crash with 7 recorded mini dumps prior since i've turned on minidump recording for BSOD's..

Prior to that its been going on with the same errror code to my best guess for a good 4-6months now.
I did report not to long ago on these forums in regards to this but the error i was getting was only recorded through even viewer and not as accurate as this.

I've done Memory tests on my ram through the windows 7 memtest but it brings up no errors.
I did notice the other day i tried to overclock my cpu from default bus speed 200mhz to 210mhz, got into windows and within 30seconds it BSOD with error code 0x3b..

So i'm a bit stumped as to what it is exactly..

If someone can determine better through the minidump please let me know, i do have a few more i can post from previous days but i'm guessing its all the same info!?!

 

[FuNkYBoY]

Just got another BSOD just then while running lowerping (proxy program to connect to world of warcraft on a faster ping).
Though just before that i did the Win 7 upgrade advisor to see what was and wasn't compatible and i had to turn on my 2 external hard drives to check them as well.
I have a feeling it could be a power supply problem? as the other day some friends and i were talking about strange instances when you open your dvd drive tray and close it again and then you get a BSOD.
Low and behold, i opened my dvd tray the other day and yep.. a BSOD. one of my mates found it to be his power supply not giving the right amount of power out for the PC to operate correctly?

Though i still don't get how that cause my pc to BSOD straight after logging into windows as that is 90% of the time when it happens?!

Attatched is another minidump

 

[reventon]

Hi,

You have more than a few out of date drivers:

[font=lucida console]
ASACPI.sys   Mon Mar 28 15:30:36 [COLOR=Red]2005[/COLOR]
ctac32k.sys  Wed Jul 02 20:38:22 [COLOR=Red]2008[/COLOR]
Mo3Fltr.sys  Thu Sep 18 14:50:37 [COLOR=Red]2008[/COLOR]
nvm62x64.sys Sat Oct 18 10:01:06 [COLOR=Red]2008[/COLOR]
wdcsam.sys   Wed Apr 16 20:39:08 [COLOR=Red]2008[/COLOR]
[/font]

ASACPI.sys - Asus ACPI, guaranteed to cause BSODs. Go here, choose your motherboard model and OS, then select the ATK 0110 driver under the Utilities subsection.

ctac32k.sys - Creative Driver Downloads: Creative Worldwide Support

Mo3Fltr.sys - Razer mouse driver: Razer Support

nvm62x64.sys - nVidia Networking driver: Drivers - Download NVIDIA Drivers (you will need to know what chipset your motherboard uses - if you don't know just tell me your motherboard model#)

wdcsam.sys - Western Digital External Drive RAID Manager: WD Support > Downloads > Select Product

Both BSODs occured while executing the same instruction (nt!HvpFindFreeCellInThisViewWindow+45) - however 2 different programs called this instruction and both received a BSOD, which means that something else like a driver/hardware is at fault.

Regards,
Reventon

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 20 10:33:12.947 2010 (GMT+12)
System Uptime: 0 days 0:41:14.246
BugCheck 3B, {c0000005, fffff80002f3c795, fffff8800a18ad10, 0}
Probably caused by : ntkrnlmp.exe ( nt!HvpFindFreeCellInThisViewWindow+45 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  wmpnetwk.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 20 09:51:58.368 2010 (GMT+12)
System Uptime: 0 days 0:01:18.475
BugCheck 1E, {ffffffffc0000005, fffff80002f04795, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!HvpFindFreeCellInThisViewWindow+45 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  services.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[FuNkYBoY]

OMG This is driving me insane!!
Just had another 0x3B BSOD while i was updating the Creative sound card drivers.
Then when its rebooting, before even getting to the windows logon screen i get:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 3081

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002EF0795
BCP3: FFFFF880033A7C88
BCP4: FFFFF880033A74F0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Minidump attatched..

 

[reventon]

So had you updated the ASACPI.sys driver by that point? That is the driver that I suspect the most.

 

[FuNkYBoY]

No and i'm having alot of problems updating that file.
I downloaded the utility update from the asus website for my exact motherboard model which is the M2N-Sli Deluxe and its coming up with errors.
I'm currently in safe mode because whenever i tried to do this update in normal windows it kept bluescreening with that.

So annoying
I was able to update my nforce drivers, but have to redownload the creative soundcard drivers.

 

[FuNkYBoY]

OK i've been update to update the ASACPI.sys but its saying the "version for it" is dated 26/62006??
So i'm a bit lost as to where i can find the most recent version as going to the main asus website to update it from what they provide you there either crashes my machine or does not want to install.

I've now got the problem my machine bluescreened when i was installing the latest Creative soundcard drivers, my sound card is getting this error in device manager "This device cannot start. (Code 10)"

Everytime i try to update it to the most recent driver version, it asks me to restart, get back into windows and there is still no soundcard in the sound properties and in device manager the soundcard has a yellow "?" on it with that error.

I've tried uninstalling/reinstalling.. I opened the machine and physically removed the sound card, booted into windows, shut down again, reinstalled the soundcard back into a DIFFERENT PCI slot and still same issue.

Currently downloading the driver version prior to the current one, which is the version i originally had.

 

[Jonathan_King]

I agree with reventon- the problem is most likely ASACPI.sys.

Please read this post by the famed usasma: http://www.sevenforums.com/787431-post2.html

 

[reventon]

I've now got the problem my machine bluescreened when i was installing the latest Creative soundcard drivers, my sound card is getting this error in device manager "This device cannot start. (Code 10)"

Everytime i try to update it to the most recent driver version, it asks me to restart, get back into windows and there is still no soundcard in the sound properties and in device manager the soundcard has a yellow "?" on it with that error.

I've tried uninstalling/reinstalling.. I opened the machine and physically removed the sound card, booted into windows, shut down again, reinstalled the soundcard back into a DIFFERENT PCI slot and still same issue.

Fix the BSODs first - then we will see what we can do about your sound card.

 

[FuNkYBoY]

Having alot of problems tracking down a "windows 7 ATK 0110" driver.
The only thing i've been able to read upon so far is that, mentioned on the asus forums for my motherboard.. the M2N-Sli Deluxe.
That the Windows Vista 64bit driver can be used because apparently that board is not supported by Windows 7!?

 

[FuNkYBoY]

OK According to Device Manager my current version that i just installed from the Vista 64bit package for the ATK0110 driver from the asus website for my M2N-Sli Deluxe board is as follows.

Driver Date: 16/07/2009
Driver Version: 1043.6.0.0

Now if anyone knows of a newer more updated driver, please let me know.
I'm gonna monitor this from this second on, as soon as i get another BSOD relating to a 0x3b or 0x1e i'm gonna scream!

 

[FuNkYBoY]

AWESOME!!
Time to scream starts now..

AAAAAAAARRRRRRRRRRRGGGGGGGGGGGHHHHHHHHHHHHH!!!!!!!
Just installed the drivers for the nForce chipset 15.53 from the nvidia website, latest drivers for my board which included the ethernet driver and storage driver..
That part went fine, got to the 2nd part "would you like to install the nvidia network access manager" ... Sure why not?!?!

BAM!! BSOD
Minidump attatched

 

[ttran]

is the computer ok now? is there any BSODs occur after the one you posted?

 

[FuNkYBoY]

Not since my last post there hasn't been.

I'm not entirely sure if the nforce drivers i installed were completed correctly or not, because usually when a BSOD occurs, anything you've done in that session is usually lost.

 

[reventon]

Hi,

If you get more BSODs try driver verifier

I'd suggest that you first backup your stuff 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/Win7 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.

 

[FuNkYBoY]

Yeah its still happening unfortunately..
its 99% of the time the 0x3b error.

 

[Jonathan_King]

Please follow reventon's instructions above for enabling Driver Verifier.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\Desktop\062310-28423-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\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.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c09000 PsLoadedModuleList = 0xfffff800`02e46e50
Debug session time: Tue Jun 22 18:16:54.787 2010 (UTC - 4:00)
System Uptime: 0 days 0:09:01.893
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002ef0795, fffff8800b18c840, 0}

Probably caused by : ntkrnlmp.exe ( nt!HvpFindFreeCellInThisViewWindow+45 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002ef0795, Address of the instruction which caused the bugcheck
Arg3: fffff8800b18c840, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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!HvpFindFreeCellInThisViewWindow+45
fffff800`02ef0795 418b840ca8000000 mov     eax,dword ptr [r12+rcx+0A8h]

CONTEXT:  fffff8800b18c840 -- (.cxr 0xfffff8800b18c840)
rax=0000000001bc7000 rbx=0000000001bc7000 rcx=fffff8a000b9d010
rdx=0000000000000002 rsi=0000000000000000 rdi=fffff8a000b9d010
rip=fffff80002ef0795 rsp=fffff8800b18d210 rbp=0000000000000000
 r8=0000000000000018  r9=0000000000000000 r10=0000000001bc8000
r11=0000000000000006 r12=ffed7c1b65470e00 r13=fffff8a000b9d010
r14=0000000001bc8000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!HvpFindFreeCellInThisViewWindow+0x45:
fffff800`02ef0795 418b840ca8000000 mov     eax,dword ptr [r12+rcx+0A8h] ds:002b:ffed74bb`6600deb8=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  SearchIndexer.

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002ef0795

STACK_TEXT:  
fffff880`0b18d210 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvpFindFreeCellInThisViewWindow+0x45


FOLLOWUP_IP: 
nt!HvpFindFreeCellInThisViewWindow+45
fffff800`02ef0795 418b840ca8000000 mov     eax,dword ptr [r12+rcx+0A8h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!HvpFindFreeCellInThisViewWindow+45

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

STACK_COMMAND:  .cxr 0xfffff8800b18c840 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!HvpFindFreeCellInThisViewWindow+45

BUCKET_ID:  X64_0x3B_nt!HvpFindFreeCellInThisViewWindow+45

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

 

[FuNkYBoY]

So i'm guessing what this driver verifier does is basically flag the driver at fault of causing the actual BSOD.

I thought that was supposed to be mentioned in the minidump it takes?

Question remains, is if the driver thats at fault has been updated to the most recent driver yet the BSOD continues, it would most likely have to be a direct hardware failure?

 

[Jonathan_King]

New drivers can be buggy, and old ones can be buggy and incompatible. Sadly, newer isn't always better. I often tell people that the latest nVidia drivers for my card have issues, and the September drivers Windows Update finds work best.

Driver Verifier strains the drivers, and hopefully flags the correct one in the dump.