Blue screens, Windows 7, Need your help

[softgator]

Hello
I am getting random blue screens, while playing games (All kind, not a specific game) and even while just browsing the net.
I really don't know what is causing them, What I did was first opening the case and making sure everything seem OK there, tried reseating the GFX and the memory as well. Ran memtest for about 3 hours, no errors at all.

My computer specs:

GIGABYTE GA-EX58-UD3R
i7 2.67GHz 920
OCZ 6144MB (2048MBX3) DDR3 1600 PLATINUM
GAINWARD GeForce GTX260 216 SP 896MB DDR3
SAMSUNG F1 1TB 32MB SATA2 7200 RPM
PCP&COOLING SILENCER 610W
COOLERMASTER CM 690
Logitech G5 + G15
DELL ULTRASHARP 22" 2209WA

Using Windows 7 64bit, Enterprise

The below dumps are from today.

I have had like 4 blue screens in the last 3 hours or so...

Thank you

 

[CarlTR6]

Hi softgator and welcome to the forum. I am working on your dumps. Be back in a few minutes. You need to run memtest for at least seven passes.

Two of these dumps were nearly identical with a stop error code of 50. The other shows a stop error code of A. this indicate hardware/driver problems.

Stop error A - Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

Stop error 50 - Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

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


Loading Dump File [C:\Users\Owner\Downloads\A-Rar\062410-16317-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Mini Kernel Dump does not have process information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a16000 PsLoadedModuleList = 0xfffff800`02c53e50
Debug session time: Thu Jun 24 12:47:02.871 2010 (GMT-4)
System Uptime: 0 days 1:28:08.963
Loading Kernel Symbols
.................................................
Loading User Symbols
Loading unloaded module list
...Missing image name, possible paged-out or corrupt data.
...........Missing image name, possible paged-out or corrupt data.
.........Missing image name, possible paged-out or corrupt data.
......Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BugCheck 50, {fffff8a0435a84e0, 0, fffff8800fe2105b, 5}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40ecb )

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a0435a84e0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800fe2105b, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbe0e0
 fffff8a0435a84e0 

FAULTING_IP: 
+5e23952f01a2d97c
fffff880`0fe2105b 48392cf0        cmp     qword ptr [rax+rsi*8],rbp

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88003e17740 -- (.trap 0xfffff88003e17740)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a0435a84e0 rbx=0000000000000000 rcx=fffff8a00998c3d0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800fe2105b rsp=fffff88003e178d0 rbp=00000000001e7619
 r8=fffffa80058497e0  r9=fffff88003e17901 r10=0000000000000000
r11=fffffa8007adf010 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffff880`0fe2105b 48392cf0        cmp     qword ptr [rax+rsi*8],rbp ds:0002:fffff8a0`435a84e0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b05801 to fffff80002a86600

STACK_TEXT:  
fffff880`03e175d8 fffff800`02b05801 : 00000000`00000050 fffff8a0`435a84e0 00000000`00000000 fffff880`03e17740 : nt!KeBugCheckEx
fffff880`03e175e0 fffff800`02a846ee : 00000000`00000000 fffff8a0`0a6de1c0 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40ecb
fffff880`03e17740 fffff880`0fe2105b : fffff8a0`0b64da80 fffff880`0fe20d4b 00000000`00000095 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`03e178d0 fffff8a0`0b64da80 : fffff880`0fe20d4b 00000000`00000095 00000000`00000000 00000000`00000000 : 0xfffff880`0fe2105b
fffff880`03e178d8 fffff880`0fe20d4b : 00000000`00000095 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff8a0`0b64da80
fffff880`03e178e0 00000000`00000095 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`07ac0000 : 0xfffff880`0fe20d4b
fffff880`03e178e8 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`07ac0000 fffff880`0fe1e8af : <Unloaded_Unknown_Module_00000000`00000006>+0x8f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+40ecb
fffff800`02b05801 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+40ecb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+40ecb

BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+40ecb

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

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


Loading Dump File [C:\Users\Owner\Downloads\A-Rar\062410-18860-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a02000 PsLoadedModuleList = 0xfffff800`02c3fe50
Debug session time: Thu Jun 24 10:37:48.604 2010 (GMT-4)
System Uptime: 0 days 0:34:01.697
Loading Kernel Symbols
.................................................
Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BugCheck 50, {fffffa8045de5900, 0, fffff8800436dce5, 5}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa8045de5900, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800436dce5, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002caa0e0
 fffffa8045de5900 

FAULTING_IP: 
+5e23952f01f4d878
fffff880`0436dce5 ??              ???

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002a8013a to fffff88003de89c2

STACK_TEXT:  
fffff800`04143c98 fffff800`02a8013a : 00000000`0027b57b fffffa80`072042f8 fffff800`02bfac40 00000000`00000001 : 0xfffff880`03de89c2
fffff800`04143ca0 fffff800`02a7adcc : fffff800`02bece80 fffff800`00000000 00000000`00000000 fffff800`02b92ce0 : nt!PoIdle+0x53a
fffff800`04143d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PoIdle+53a
fffff800`02a8013a 0fba25061518000f bt      dword ptr [nt!PerfGlobalGroupMask+0x8 (fffff800`02c01648)],0Fh

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PoIdle+53a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x50_nt!PoIdle+53a

BUCKET_ID:  X64_0x50_nt!PoIdle+53a

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

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


Loading Dump File [C:\Users\Owner\Downloads\A-Rar\062410-19999-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a02000 PsLoadedModuleList = 0xfffff800`02c3fe50
Debug session time: Thu Jun 24 10:02:17.393 2010 (GMT-4)
System Uptime: 0 days 0:15:32.485
Loading Kernel Symbols
.................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa8045cb1620, 2, 1, fffff80002a76d2f}

Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+17f )

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

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: fffffa8045cb1620, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002a76d2f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002caa0e0
 fffffa8045cb1620 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTryUnwaitThread+17f
fffff800`02a76d2f 488908          mov     qword ptr [rax],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880030cc9f0 -- (.trap 0xfffff880030cc9f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8045cb1620 rbx=0000000000000000 rcx=fffffa80052e2100
rdx=fffffa80052838c8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a76d2f rsp=fffff880030ccb80 rbp=fffff880030a4180
 r8=0000000000000002  r9=0000000000000000 r10=00000000000001b4
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KiTryUnwaitThread+0x17f:
fffff800`02a76d2f 488908          mov     qword ptr [rax],rcx ds:fffffa80`45cb1620=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a71b69 to fffff80002a72600

STACK_TEXT:  
fffff880`030cc8a8 fffff800`02a71b69 : 00000000`0000000a fffffa80`45cb1620 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`030cc8b0 fffff800`02a707e0 : 00000000`00000000 fffffa80`05283760 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`030cc9f0 fffff800`02a76d2f : 00000000`000000ff 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`030ccb80 fffff800`02a766d2 : fffffa80`06f3ba20 00000000`00000002 00000000`00000000 fffff880`030a4180 : nt!KiTryUnwaitThread+0x17f
fffff880`030ccbe0 fffff880`03fbd5e8 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`06f3ba28 : nt!KeSetEvent+0x142
fffff880`030ccc50 fffffa80`00000000 : 00000000`00000000 00000000`00000000 fffffa80`06f3ba28 00000000`00000000 : 0xfffff880`03fbd5e8
fffff880`030ccc58 00000000`00000000 : 00000000`00000000 fffffa80`06f3ba28 00000000`00000000 00000000`00000004 : 0xfffffa80`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTryUnwaitThread+17f
fffff800`02a76d2f 488908          mov     qword ptr [rax],rcx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTryUnwaitThread+17f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0xA_nt!KiTryUnwaitThread+17f

BUCKET_ID:  X64_0xA_nt!KiTryUnwaitThread+17f

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

I found the driver, sptd.sys, at the time of the crash. Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use the driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

After you have uninstalled the program associated with this driver, reboot and let's see what happens. Please post back after you have uninstalled it. We will go from there.

 

[softgator]

Hello Carl

I will run memtest for as long as needed, I will wait your findings from my dumps first to see if it (The memory) might be the reason for my blue screens.

Thank you

 

[CarlTR6]

Dumps are posted and I made a suggestion. As I edited my post, you may have to refresh this page.

 

[softgator]

I have now uninstalled Dtools and then used the SPDT uninstaller provided in your link, both done - PC rebooted.
Shall I just keep using the computer as usual now and see what happens.
Thank you

 

[CarlTR6]

Yes, just keep using it and let's see if your problem is solved. It would be nice if the solution is that easy! Do post back in a couple of days - sooner if you have another BSOD - and let us know how your system is doing. Hopefully we will be able to mark this one as solved.

Good luck!

 

[softgator]

I really hope so too
P.S, I should delete the current files in C:\Windows\Minidump now, so in case and there will be a new BSOD it will be easier to spot the problem, or it doesn't matter?

 

[CarlTR6]

I would keep them until we know the problem is solved. They are dated; so if you have another BSOD you can just upload that latest file(s). Once you are running smoothly, you can definitely delete them.

 

[softgator]

Thanks Carl, I will post back either way!

 

[softgator]

That didn't last long Carl
Just got a BSOD while playing Counter Strike:Source.
From what I managed to see, the stop error this time was 50, and it had 'dxgmms1.sys' along the lines.

Here's the latest dump that has just been created.

Thanks

 

[CarlTR6]

Nuts, sorry the problem is not resolved. dxgmms1.sys is a directX driver and it may or may not be the cause. Now it is time to start looking at hardware. Here is link you might want to visit for more information regarding dxgmms1.sys.

dxgmms1.sys crash – Blue Screen Of Death

Please fill out your system information. Go to your User CP at the top of the page, look in the left column and click on Edit system specs. Filling in your specs will help us help you.

You can make this easier by downloading Speccy.

This could be triggered by your video card. What card are you using?

If you are overclocking please return to stock settings.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 7 passes. Post back with your results.

If Memtest checks back clean after 7+ passes, follow these instructions for enabling driver verifier: Using Driver Verifier to identify issues with Drivers
Please follow these instructions in order to run it:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, 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/Windows 7 Startup Repair feature).

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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Next, Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

Please keep us updated on your progress.

 

[softgator]

Hello Carl, thank you for your time.
I have mentioned my system information in the first post: Everything is on stock settings.

Motherboard: GIGABYTE GA-EX58-UD3R
CPU: i7 2.67GHz 920
Memory: OCZ 6144MB (2048MBX3) DDR3 1600 PLATINUM
GFX CARD: GAINWARD GeForce GTX260 216 SP 896MB DDR3
HDD: SAMSUNG F1 1TB 32MB SATA2 7200 RPM
PSU: PCP&COOLING SILENCER 610W
CASE: COOLERMASTER CM 690
Mouse & Keyboard: Logitech G5 + G15
Monitor: DELL ULTRASHARP 22" 2209WA

Please see the attached picture for my memtest results, please note that it got to 7 (and not just 5 as it shows in the picture) 'passes' with just 1 error showing in the picture.

Do you think the memory is valid or it can be faulty due to that error showing? I have ran the test with 3 sticks of ram (3X2GB) all-together.

Let me know what do you think and whether or not I should move on to the next step, driver verifier and then GPU stress check etc.

Thanks

 

[Lordbob75]

Softgator, that would seem to indicate that you have a bad RAM stick. Now you need to isolate it. Open the case and remove all but one stick, then run the test again. Repeat this for all the RAM sticks.

~Lordbob

 

[softgator]

Hello,
I did another test while being away, attached the results of the new memtest (This test as well is with all 3 sticks), it doesn't somewhere say what stick is faulty in the results?

For how long would I need to run the test again on each stick?

And I remember once I had a problem with the memoy, memtest was giving an error as well (Old PC), updating the BIOS fixed it back then. Is it something that's worth checking this time?

Thanks

 

[ttran]

During the test with first stick, did you test it on different slot? If you continue to test, I think still at least 6, 7 passes.
It never hurt to try. Manufacture's site always give out the last update for Bios that can fix some problems (BSODs). Go ahead and do it

~Tuan

 

[softgator]

Hello,
There was no test with first stick, as mentioned, both tests were with the 3 sticks all together.
The slot on the motherboard can cause the errors as well?
7 passes takes about 7 hours each time, doing that on each stick and on different slots can take a very long time of memtesting
Thanks

 

[ttran]

For your first question: Yes, why not
Do one stick on different slot first. If no error-->slot ok. Then you don't have to test it on diffferent slot. Got what I meant???

 

[softgator]

Yes
I just updated my BIOS to the latest version, now I have F11, previously F6.
I will post back regarding the sticks after I will do some more testing.
Thanks

 

[CarlTR6]

Softgator, take a known good stick and test it in each slot. Five passes should do for these tests. After you determine that all of your slots are good, you can test the remaining sticks, singly, in any slot. Yes, it is involved and tedious; but it is the only way.

 

[Lordbob75]

Looking at that screenshot, I can tell you that you have a bad RAM stick, maybe more than one.

The ways to test it can take a while yes, but the good news is that the bad sticks should show an error very quickly, so you don't need to run it for all 7 hours.

~Lordbob