BSOD just after start up

[Bendocherty]

Hi, as you can tell i'm new here

Iv been reading a few of the other random crash posts and have tried to follow them as best as I can.

Basically, my computer will freeze about a minute or 2 after login, and when I restart, I can login again either in safe mode or normal, and I will get a BSOD, again after 1 or 2 minutes after logging in. Iv attached the dmp file (I think Iv done it correctly)

I also saw that you were telling everyone that they should run the memory 86 thing, so I did that last night and after 12 passes leaving it on overnight, there were 0 errors.

So with that dmp file, what should I proceed to do next?

All I can find out at the moment about my pc (seens as its a generically built one, bought in August 06) is I have:

Windows 7 Ultimate 32 bit (previously I had windows xp professional - I never had Vista)

AMD athlon 64 x2 dual core processor 4600+

Nvidia 6100 graphics card

500gb sata hdd, I bought that from pc world after my other 300gb sata one failed about 9 months ago

2gb memory - not sure about any other info on that

BIOS is AMI

Also found that my motherboard is ALiveNF4G-DVI

I found most of that info using AIDA32 - alot of it says unknown or OEM will fill in

What should be my next steps, baring in mind that I can't use my computer for more than 2 minutes. I'm also not amazing with all the technical language, but I can follow instructions if you walk me though it

Hope you can help me out

Ben

 

[zigzag3143]

Hi, as you can tell i'm new here

Iv been reading a few of the other random crash posts and have tried to follow them as best as I can.

Basically, my computer will freeze about a minute or 2 after login, and when I restart, I can login again either in safe mode or normal, and I will get a BSOD, again after 1 or 2 minutes after logging in. Iv attached the dmp file (I think Iv done it correctly)

I also saw that you were telling everyone that they should run the memory 86 thing, so I did that last night and after 12 passes leaving it on overnight, there were 0 errors.

So with that dmp file, what should I proceed to do next?

All I can find out at the moment about my pc (seens as its a generically built one, bought in August 06) is I have:

Windows 7 Ultimate 32 bit (previously I had windows xp professional - I never had Vista)

AMD athlon 64 x2 dual core processor 4600+

Nvidia 6100 graphics card

500gb sata hdd, I bought that from pc world after my other 300gb sata one failed about 9 months ago

2gb memory - not sure about any other info on that

BIOS is AMI

Also found that my motherboard is ALiveNF4G-DVI

I found most of that info using AIDA32 - alot of it says unknown or OEM will fill in

What should be my next steps, baring in mind that I can't use my computer for more than 2 minutes. I'm also not amazing with all the technical language, but I can follow instructions if you walk me though it

Hope you can help me out

Ben

Hi Ben

There are two problems.

1- First sptd.sys (used by daemon tools & alcohol120) HUGE problem

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
[/quote]
You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

2-Your storage driver nvstor.sys. Needs to be updated and re-installed.

How To Find Drivers:

- 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 manufacturer links are on this page: Drivers and Downloads

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\111910-19578-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.20738.x86fre.win7_ldr.100618-1621
Machine Name:
Kernel base = 0x82839000 PsLoadedModuleList = 0x829795f0
Debug session time: Thu Nov 18 18:21:10.833 2010 (GMT-5)
System Uptime: 0 days 0:01:56.646
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
....
Unable to load image \SystemRoot\system32\DRIVERS\nvstor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: 80000003, The exception code that was not handled
Arg2: 8904888d, The address that the exception occurred at
Arg3: 919cb734, Trap Frame
Arg4: 00000000

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

*** WARNING: Unable to verify timestamp for halmacpi.dll
*** ERROR: Module load completed but symbols could not be loaded for halmacpi.dll
*** WARNING: Unable to verify timestamp for ACPI.sys
*** ERROR: Module load completed but symbols could not be loaded for ACPI.sys
*** WARNING: Unable to verify timestamp for fvevol.sys
*** ERROR: Module load completed but symbols could not be loaded for fvevol.sys
*** WARNING: Unable to verify timestamp for volsnap.sys
*** ERROR: Module load completed but symbols could not be loaded for volsnap.sys
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

FAULTING_IP: 
nvstor+288d
8904888d cc              int     3

TRAP_FRAME:  919cb734 -- (.trap 0xffffffff919cb734)
ErrCode = 00000000
eax=00000001 ebx=859d64d4 ecx=84864000 edx=00000000 esi=85676288 edi=84864000
eip=8904888e esp=919cb7a8 ebp=919cb7b0 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000246
nvstor+0x288e:
8904888e cc              int     3
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 8905b191 to 8904888e

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
919cb7b0 8905b191 84864000 85676288 85676288 nvstor+0x288e
919cb7cc 89058a5b 85676288 84864000 859d64d4 nvstor+0x15191
919cb7f8 8906d614 85542004 00000008 919cb830 nvstor+0x12a5b
919cb808 8906f000 85528188 859d64d4 85676008 storport!RaCallMiniportBuildIo+0x24
919cb830 8906f27f 855280e8 8486aa60 86985544 storport!RaidAdapterPostScatterGatherExecute+0x5e
919cb848 82806a2e 85528030 00000000 8567605c storport!RaidpAdapterContinueScatterGather+0x3f
919cb874 89072e19 8567605c 85528030 86985508 hal+0x4a2e
919cb8a4 8906f31b 85528294 85528030 86985508 storport!RaidDmaBuildScatterGatherList+0x2c
919cb8e4 8906f36b 85528294 00008000 919cb914 storport!RaidAdapterScatterGatherExecute+0x65
919cb8f4 8907cb30 855280e8 85676008 859d6320 storport!RaidAdapterExecuteXrb+0x24
919cb914 890743e9 00000000 859d6320 919cb934 storport!RaUnitStartIo+0xbf
919cb954 8907a82c 0086a9e8 859d6320 00000000 storport!RaidStartIoPacket+0x100
919cb974 8907d262 8486a9e8 859d6320 859d6320 storport!RaidUnitSubmitRequest+0x4e
919cb994 89073511 8486a9e8 859d6320 859d6320 storport!RaUnitScsiIrp+0x114
919cb9b0 828680ed 8486a930 859d6320 ffcd3ff4 storport!RaDriverScsiIrp+0x60
919cb9c8 88ed83b8 ffcd3ff4 919cb9e8 88edebfe nt!IofCallDriver+0x63
919cb9d4 88edebfe 85532c10 859d6320 859d63d8 ACPI+0x93b8
919cb9e8 88ed8642 85532c10 859d6320 00008000 ACPI+0xfbfe
919cba18 828680ed 85532c10 854eecb8 859d6428 ACPI+0x9642
919cba30 8967a5a4 867cf530 859d6428 919cba80 nt!IofCallDriver+0x63
919cba40 89679fe8 85532c10 8574c0e8 8574d008 CLASSPNP!SubmitTransferPacket+0x103
919cba80 8967a303 00000000 007cf530 8574cdd0 CLASSPNP!ServiceTransferRequest+0x225
919cbaa8 8967a3bf 8574c030 00000000 8574c030 CLASSPNP!ClassReadWrite+0x172
919cbabc 828680ed 8574c030 867cf530 867cf6b8 CLASSPNP!ClassGlobalDispatch+0x20
919cbad4 88f55230 2ad81800 867cf530 867cf530 nt!IofCallDriver+0x63
919cbae8 88f552e5 8574cdd0 867cf69c 8574cd18 partmgr!PmReadWrite+0x112
919cbafc 828680ed 8574cd18 867cf530 85750be0 partmgr!PmGlobalDispatch+0x1d
919cbb14 88f669ae 867cf530 85750b28 00000002 nt!IofCallDriver+0x63
919cbb30 828680ed 85750b28 867cf530 867cf530 volmgr!VmReadWrite+0x1a8
919cbb48 89634475 857532c0 919cbb70 89634548 nt!IofCallDriver+0x63
919cbb54 89634548 857532c0 867cf530 828de97c fvevol+0x1475
919cbb70 89634759 857532c0 867cf500 857519a8 fvevol+0x1548
919cbba0 828680ed 85753208 867cf530 857519a8 fvevol+0x1759
919cbbb8 895fa701 857519a8 867cf530 00000002 nt!IofCallDriver+0x63
919cbc98 895fa8a5 857519a8 867cf530 00000000 rdyboost!SmdProcessReadWrite+0x9a7
919cbcb8 828680ed 857519a8 867cf530 00000000 rdyboost!SmdDispatchReadWrite+0xcb
919cbcd0 895a9996 8574f020 919cbd28 866ee778 nt!IofCallDriver+0x63
919cbce4 895ab9c9 8574f0d8 8574f020 867cf530 volsnap+0x2996
919cbcf8 828680ed 8574f020 867cf530 918fb818 volsnap+0x49c9
919cbd10 8911295c 918fb778 919cbd34 8289613a nt!IofCallDriver+0x63
919cbd1c 8289613a 918fb818 00000000 ffffffff Ntfs+0x1295c
919cbd1c 82896231 918fb818 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x15a
918fb788 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvstor+288d
8904888d cc              int     3

SYMBOL_NAME:  nvstor+288d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvstor

IMAGE_NAME:  nvstor.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a13a6b9

FAILURE_BUCKET_ID:  0x8E_nvstor+288d

BUCKET_ID:  0x8E_nvstor+288d

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

Let us know if you need help


Ken J

 

[Bendocherty]

Hi Ken

Thanks for the reply, iv removed the daemon tools sptd.sys with the program you provided - thanks, I had read about daemon causing problems with BSOD's, but with them being so common, I thought it wouldn't be that and I had already uninstalled daemon, but I didn't know it left a file on the system. I'l use magic from now on.

With regards to the 2nd point you made (my computer has actually no crashed for once, very occasionaly it will work, as long as I don't turn it off!) I went to device manager and looked at all the drivers that were installed for the each component of my computer. The nvstor.sys driver I found is for my nvidia nforce serial ATA controller which was underneath storage controllers.

What does this mean? Does this mean my graphics card or something controlling my graphics card?
I also have a radeon 9200 (i think that model number) lying around which is basically brand new. Would it be better if I put that in my computer (would there be compatibility issues or power issues etc)

Does that mean if i googled that with drivers, if I install the latest one it could potentially work fine?

Ben

 

[Bendocherty]

NVIDIA DRIVERS 260.99 WHQL

This was the drivers I found from nvidia, will this be ok for all my nvidia things or not?

Im not very good with drivers unfortunately

Also, is there a freeware tool to analyze my current installed drivers for all my components to see if there up-to-date and then I can update the ones that arnt?

 

[Bendocherty]

well i havnt had a bsod for the last 2 days after finding nvstor.sys to 10.6.0.18, which is from 10th march 2010, so hopefully this has fixed the problem. If there is anymore problems should I open a new thread or just post in this one? Cheers for the help