Exciting Blue Screen & other problems (?)

#1
Hello! I am very hopeful I can get help with this seemingly random problem. I have attached the dmp file, along with the "system info" file generated by the SF Diagnostic Tool (unfortunately, I can't get the computer to survive long enough to generate the other files using the tool).

This morning the video on my computer randomly died, and the computer would not boot. I switched over to the itegrated video and things seemed to work fine, so I bought another video card. The computer now has random blue screens and turns off more often than I would like, and I'm not really sure what the problem is. The blue screens are too fast for me to actually get any information out of them.

Please let me know if any other information is need - and thank you in advance!
 


Attachments

Trouble

Noob Whisperer
#2
Hello and welcome to the forum.
Start by uninstalling Daemon Tools and removing sptd.sys using this program from here DuplexSecure - Downloads get the correct version for your architecture and run it and click the UNINSTALL button.
then update these drivers
[TABLE="width: 1712"]
[TR]
[TD]ASACPI.sys[/TD]
[TD="align: right"]3/27/2005[/TD]
[TD]From here[/TD]
[TD]ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE[/TD]
[TD]Expand Utilities, 12th one down, ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit[/TD]
[/TR]
[TR]
[TD]Rt64win7.sys[/TD]
[TD="align: right"]2/26/2009[/TD]
[TD]From here[/TD]
[TD]Realtek[/TD]
[TD][/TD]
[/TR]
[TR]
[TD]nvlddmkm.sys[/TD]
[TD="align: right"]10/16/2010[/TD]
[TD]From here[/TD]
[TD]Drivers - Download NVIDIA Drivers[/TD]
[TD][/TD]
[/TR]
[/TABLE]
 


#3
Thank you, Trouble. I have followed your instructions, and the computer does seem more stable - a lot more stable. However, it still blue screens - this time, when attempting to load Civ5.

I have attached the dump.

Out of curiosity, why uninstall Daemon Tools? Do you have a recommendation for another (better?) emulation program?

Thanks for your help!
 


Attachments

Trouble

Noob Whisperer
#4
Thank you, Trouble. I have followed your instructions, and the computer does seem more stable - a lot more stable.
It would appear that you haven't.
According to the dump you just attached.
sptd.sys 10/11/2009
ASACPI.sys 3/27/2005
Rt64win7.sys 2/26/2009

Out of curiosity, why uninstall Daemon Tools? Do you have a recommendation for another (better?) emulation program?
Becasue sptd.sys (a product of Daemon Tools as well as Alchohol % softwre) is frequently a problem with BSODs. I am not a big emulator user but I do know many people suggest using Using MagicISO to create ISO image files as a substitute and it does seem to be more BSOD friendly.

EDIT: Additionally, going back to your original post, and presumably the nexus of the actual problem;
This morning the video on my computer randomly died, and the computer would not boot. I switched over to the itegrated video and things seemed to work fine
This may be what we might consider "a clue".
so I bought another video card. The computer now has random blue screens and turns off
This might suggest that you have either acquired a faulty card, or, and probably more likely the power demands of the new card may exceed your current Power Supply's ability to cope. As best I can determine you need something that provides
Requirements
Minimum of a 400 Watt power supply.
(Minimum recommended power supply with +12 Volt current rating of 24 Amps.)
So check the specs on you current PSU.
Regards
Randy
 


Last edited:
#5
It would appear that you haven't.
According to the dump you just attached.
sptd.sys 10/11/2009
ASACPI.sys 3/27/2005
Rt64win7.sys 2/26/2009
This is confusing - I have in fact followed your instructions. Is it possible that for some reason I was unable to change drivers, or a new dump file was not created? I only have two files in the minidump

Becasue sptd.sys (a product of Daemon Tools as well as Alchohol % softwre) is frequently a problem with BSODs. I am not a big emulator user but I do know many people suggest using Using MagicISO to create ISO image files as a substitute and it does seem to be more BSOD friendly.
Thanks for satisfying my curiosity!

EDIT: Additionally, going back to your original post, and presumably the nexus of the actual problem;

This may be what we might consider "a clue".

This might suggest that you have either acquired a faulty card, or, and probably more likely the power demands of the new card may exceed your current Power Supply's ability to cope. As best I can determine you need something that provides

So check the specs on you current PSU.
Regards
Randy
This had occurred to me as well - but my power supply is 600V, and I have tested the new video card in another computer - it seems to work fine.

I have been able to completely run the SF Diagnostic Tool now - so following your instructions did help. I have attached the ZIP file. Thanks for your help so far, I really appreciate it!
 


Attachments

#6
This morning I got another blue screen.
 


Attachments

Trouble

Noob Whisperer
#7
[FONT=&quot]Latest dump file reflects that your drivers look good now.
Please read the first post in this sticky thread here How to ask for help with a BSOD problem
[/FONT][FONT=&quot]Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, [/FONT]
Stick them in a folder, zip them up and attach to next post.
 


#8
Thanks! I really appreciate your help.
 


Attachments

Trouble

Noob Whisperer
#9
Looks fine, so....
You'll likely need to run Driver Verifier so here is my boiler plate disclaimer and a link you need to read.
Normally this is where I would recommend running Driver Verifier. You need to be aware that under some very rare circumstance the use of Driver Verifier can result in unexpected consequences you should probably only consider running it if you are relatively certain that you have the skill set to recover from a worst case scenario.
Please do some research and make sure you know how to run DV (how to start it and what to check) start by reading this reference Driver Verifier - Windows 7 & Vista (read it carefully) and probably just as important if not more how to stop running it.
 


#10
It seems like the worst that can happen is that my computer will be completely broken instead of only mostly broken... so I will I will give it a shot.
 


Trouble

Noob Whisperer
#11
Hopefully it will zero in on the offending driver and give us a better chance at resolving the issue.
Attach any new dump files produced by DV here.
Thanks
Randy
 


#12
Well, my computer locked up (screen froze, speakers buzzed) - but it didn't blue screen and no dump file was created. I was forced to turn it off and reboot (which it initially did not do - or at least, did not output video while it was doing so). After a couple of minutes I was able to get the computer to boot with no problem.

Driver Verifier is still running.
 


#13
Got a new blue screen. I still have Driver Verifier running - can I turn it off or ought I to leave it on?
 


Attachments

Trouble

Noob Whisperer
#14
Leave it run and use your computer normally. Try to get a 24 hour sampling unless it becomes too annoying, then or course turn it off and we'll see what we've got.
 


#15
I had a bunch more BSODs - and a pretty large amount of trouble turning the computer back on (I even had a blue screen in Safe Mode!). Only two dump files were created though, and one of them is 0 kb.

They have both been uploaded - but to do so, I had to turn the verifier off during one of the brief moments that safemode was allowed to run.
 


Attachments

Trouble

Noob Whisperer
#16
As to your two most recent dump files. One contained zero data the other reflects that DV was off.
Code:
BugCheck 116, {fffffa80073c44e0, fffff88004b38e64, 0, 2}
[U][B]Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys,[/B][/U] Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
[COLOR=#ff0000][U][B]Probably caused by : nvlddmkm.sys[/B][/U][/COLOR] ( nvlddmkm+12ee64 )
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80073c44e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004b38e64, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
FAULTING_IP: 
nvlddmkm+12ee64
fffff880`04b38e64 4883ec28        sub     rsp,28h
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT:  1
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
CURRENT_IRQL:  0
STACK_TEXT:  
fffff880`030a79c8 fffff880`040d1000 : 00000000`00000116 fffffa80`073c44e0 fffff880`04b38e64 00000000`00000000 : nt!KeBugCheckEx
fffff880`030a79d0 fffff880`040d0d0a : fffff880`04b38e64 fffffa80`073c44e0 fffffa80`07443d50 fffffa80`073f5410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`030a7a10 fffff880`04177f07 : fffffa80`073c44e0 00000000`00000000 fffffa80`07443d50 fffffa80`073f5410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`030a7a40 fffff880`041a1b75 : 00000000`ffffffff 00000000`0011ed0e 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`030a7b20 fffff880`041a02bb : 00000000`00000102 00000000`00000000 00000000`0011ed0e 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`030a7b50 fffff880`041732c6 : ffffffff`ff676980 fffffa80`073f5410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`030a7bf0 fffff880`0419fe7a : 00000000`00000000 fffffa80`055ad280 00000000`00000080 fffffa80`073f5410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`030a7d00 fffff800`02d2dfee : 00000000`fffffc32 fffffa80`0742a8c0 fffffa80`051e9040 fffffa80`0742a8c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`030a7d40 fffff800`02a845e6 : fffff800`02c08e80 fffffa80`0742a8c0 fffff800`02c16cc0 fffff880`0125dcb0 : nt!PspSystemThreadStartup+0x5a
fffff880`030a7d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
nvlddmkm+12ee64
fffff880`04b38e64 4883ec28        sub     rsp,28h
SYMBOL_NAME:  nvlddmkm+12ee64
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME:  nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4cb9dd0e
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
Code:
[COLOR=#ff0000][U][B]Verify Level 0[/B][/U][/COLOR] ... enabled options are:
Summary of All Verifier Statistics
RaiseIrqls                             0x0
AcquireSpinLocks                       0x0
Synch Executions                       0x0
Trims                                  0x0
Pool Allocations Attempted             0x0
Pool Allocations Succeeded             0x0
Pool Allocations Succeeded SpecialPool 0x0
Pool Allocations With NO TAG           0x0
Pool Allocations Failed                0x0
Resource Allocations Failed Deliberately   0x0
Current paged pool allocations         0x0 for 00000000 bytes
Peak paged pool allocations            0x0 for 00000000 bytes
Current nonpaged pool allocations      0x0 for 00000000 bytes
Peak nonpaged pool allocations         0x0 for 00000000 bytes
Interestingly in two of your other dump files, while not present in the stack trace, when looking at the raw stack you find this same driver mentioned again
062412-23088-01.dmp
Code:
fffff880`06c398c0  fffff880`113116f3Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
and
062512-25677.dmp
Code:
fffff880`038756d8  fffff880`11286125Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
So rather than completely ignore this, can we test and confirm, that if you revert back to your integrated graphics card (as noted in your OP) that your computer will run without issue?
If so, you may want to use something like Driver Sweeper from here Phyxion.net - Driver Sweeper to remove the Nvidia driver and try reinstalling from scratch.
Then use something like FurMark from here FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to stress test it and see what is produced.
Leave DV off for now, the single dump file that it produced was not very informative and if Blue Screens persist feel free to attach them here. I will continue to look through them.
 


#17
After switching over to the integrated graphics, I did have a blue screen - but I think driver verifier was still running. The ATI driver was fingered by the blue screen. There are two blue screen attached.

I will attempt to clense my Nvidia drivers and reinstall them.

I have to say, I really appreciate your help - your generosity has blown me away. Thank you.
 


Attachments

Trouble

Noob Whisperer
#18
Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD from a cold boot after leaving it off for an hour or more.
Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.
See this Guide to using Memtest 86+

Additionally, grab a blank CD and this program from here What is Windows Defender Offline? (get the correct version for your architecture) Boot from the CD that the program creates and perform a FULL system scan. I think the program defaults to a QUICK scan, so make sure you do the FULL scan.
Not very informative but:
Code:
BugCheck 1000007E, {ffffffffc0000005, fffff88004d35147, fffff880053be9e8, fffff880053be240}
[COLOR=#ff0000][U][B]Probably caused by : Unknown_Module_fffffa80`050019a8 ( Unknown_Module_fffffa80`050019a8>+5571d8 )[/B][/U][/COLOR]
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88004d35147, The address that the exception occurred at
Arg3: fffff880053be9e8, Exception Record Address
Arg4: fffff880053be240, Context Record Address
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
+5571d8
fffff880`04d35147 cf              iretd
EXCEPTION_RECORD:  fffff880053be9e8 -- (.exr 0xfffff880053be9e8)
ExceptionAddress: fffff88004d35147
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000004d35153
Attempt to write to address 0000000004d35153
CONTEXT:  fffff880053be240 -- (.cxr 0xfffff880053be240)
rax=5e75fc82e5c19bcd rbx=0000000000000000 rcx=0000000000000018
rdx=0000000000000000 rsi=cccccccccccccccd rdi=0000000000000000
rip=fffff88004d35147 rsp=fffff880053bec28 rbp=0000000000000400
 r8=fffff88004d35153  r9=fffff880053bec70 r10=000000e32987ad9a
r11=0000000000000156 r12=0000000000000000 r13=0000000000003130
r14=0000000000000020 r15=0000000000000000
iopl=0         nv up di pl nz ac po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010016
fffff880`04d35147 cf              iretd
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
CURRENT_IRQL:  0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1:  0000000000000001
EXCEPTION_PARAMETER2:  0000000004d35153
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003513100
 0000000004d35153 
FOLLOWUP_IP: 
Unknown_Module_fffffa80`050019a8>+5571d8
fffffa80`05558b80 ??              ???
FAILED_INSTRUCTION_ADDRESS: 
+5571d8
fffff880`04d35147 cf              iretd
BUGCHECK_STR:  0x7E
[COLOR=#ff0000][U][B]EXCEPTION_DOESNOT_MATCH_CODE:  This indicates a hardware error.
Instruction at fffff88004d35147 does not read/write to 0000000004d35153[/B][/U][/COLOR]
LAST_CONTROL_TRANSFER:  from fffff88004cf5821 to fffff88004d35147
SYMBOL_ON_RAW_STACK:  1
STACK_ADDR_RAW_STACK_SYMBOL: fffff880053bec98
STACK_COMMAND:  dds FFFFF880053BEC98-0x20 ; kb
STACK_TEXT:  
fffff880`053bec78  00000000 <Unloaded_Unknown_Module_00000000`00000000>
fffff880`053bec7c  fffffa80
fffff880`053bec80  002fb02c <Unloaded_Unknown_Module_00000000`00000000>+0x2fb02c
fffff880`053bec84  00000000 <Unloaded_Unknown_Module_00000000`00000000>
fffff880`053bec88  00000021 <Unloaded_Unknown_Module_00000000`00000000>+0x21
fffff880`053bec8c  00000000 <Unloaded_Unknown_Module_00000000`00000000>
fffff880`053bec90  05558b80 <Unloaded_Unknown_Module_00000000`00000000>+0x5558b80
fffff880`053bec94  fffffa80
fffff880`053bec98  00000008 <Unloaded_Unknown_Module_00000000`00000000>+0x8
fffff880`053bec9c  00000000 <Unloaded_Unknown_Module_00000000`00000000>
fffff880`053beca0  036ca040 <Unloaded_Unknown_Module_00000000`00000000>+0x36ca040
fffff880`053beca4  fffffa80
fffff880`053beca8  fff0bdc0
fffff880`053becac  ffffffff
fffff880`053becb0  05559b50 <Unloaded_Unknown_Module_00000000`00000000>+0x5559b50
fffff880`053becb4  fffffa80
fffff880`053becb8  00000002 <Unloaded_Unknown_Module_00000000`00000000>+0x2
fffff880`053becbc  00000000 <Unloaded_Unknown_Module_00000000`00000000>
fffff880`053becc0  00000020 <Unloaded_Unknown_Module_00000000`00000000>+0x20
fffff880`053becc4  00000000 <Unloaded_Unknown_Module_00000000`00000000>
fffff880`053becc8  8a0659b3
fffff880`053beccc  a1968c1b
fffff880`053becd0  a661449d
fffff880`053becd4  2f26fbef <Unloaded_Unknown_Module_00000000`00000000>+0x2f26fbef
fffff880`053becd8  fdf7ccbf
fffff880`053becdc  fffff800
fffff880`053bece0  050c4248 <Unloaded_Unknown_Module_00000000`00000000>+0x50c4248
fffff880`053bece4  fffff880
fffff880`053bece8  00000018 <Unloaded_Unknown_Module_00000000`00000000>+0x18
fffff880`053becec  00000000 <Unloaded_Unknown_Module_00000000`00000000>
fffff880`053becf0  00000001 <Unloaded_Unknown_Module_00000000`00000000>+0x1
fffff880`053becf4  00020000 <Unloaded_Unknown_Module_00000000`00000000>+0x20000
SYMBOL_NAME:  Unknown_Module_fffffa80`050019a8>+5571d8
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: Unknown_Module_fffffa80`050019a8
IMAGE_NAME:  Unknown_Module_fffffa80`050019a8
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  X64_0x7E_CODE_ADDRESS_MISMATCH_BAD_IP_Unknown_Module_fffffa80_050019a8_+5571d8
BUCKET_ID:  X64_0x7E_CODE_ADDRESS_MISMATCH_BAD_IP_Unknown_Module_fffffa80_050019a8_+5571d8
I really don't know the context of this particular dump or where you were in you diagnostic steps regarding your video card, so it may be completely out of context but I thought I would post it as it does suggest a hardware issue.
My suggestion would be to completely physically remove the new Video card, and use driver sweeper to get rid of all driver remnants. Revert to you integrated video and use your computer normally and see if we get any blue screens with that configuration.
 


#19
I have run a full scan with windows defender offline while I was at work, and it finished with no errors. Tonight I will run memtest86+ on all three sticks of RAM - if it finds an error, I will begin testing them one by one tomorrow.
 


#20
I have also run memtest86+ with no errors. I also have received no additional blue screens. This seems to imply that it is video card related - but is it the card its self (unlikely, as it happens with both cards), the drivers, or the pci-e slot?

I figure the best way to test this is to put a video card back into the computer and re-install the drivers, now that they have been removed with driver sweeper. Advice?
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.