BSODs

[Tervel]

Getting BSODs, ran some of the dumps through the Debugging Tools for Windows but couldn't make any sense of it.

Worth mentioning is that in addition to the BSODs I sometimes (rarely lately) have freezes where my entire PC just freeze up and I can't do anything - I have to shut it down by holding the power button.

Had my PSU replaced a couple of months ago so that is new.
My Motherboard and CPU is only a couple of months old as well.
Some of my harddrives are a few years old.
My graphics card 2-3 years old.

My system spec is in my profile.

Attached are the files needed as per the BSOD Posting Instructions.

Thanks in advance!

EDIT: Just ran "SFC /SCANNOW", as is suggested in some of the other threads, with the following result:

C:\Windows\system32>SFC /SCANNOW

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

 

[usasma]

I wonder about your PSU with all those hard drives.
Try unplugging all but the OS hard drive and see if that improves things.

More to follow once the memory dumps are finished....

 

[usasma]

8 memory dumps, from 12 May to 20 Jul 2010
5 different STOP errors, with 3 different causes blamed
This is most likely a hardware error.

Please start with these free diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Then, if the above tests pass, I'd try these free stress tests:

FurMark download site: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 20 15:30:39.305 2010 (UTC - 4:00)
System Uptime: 0 days 3:32:25.271
BugCheck D1, {0, 2, 0, fffffa80058ea001}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 19 22:44:32.455 2010 (UTC - 4:00)
System Uptime: 0 days 3:21:39.421
BugCheck 3D, {fffff80000b9c120, 0, 0, fffff8000320d8fb}
Probably caused by : ntkrnlmp.exe ( nt!KiInterruptDispatchNoLock+190 )
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 19 19:21:41.710 2010 (UTC - 4:00)
System Uptime: 0 days 8:16:28.286
BugCheck 50, {fffffa7ff7000045, 8, fffffa7ff7000045, 7}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40e4b )
BUGCHECK_STR:  0x50
PROCESS_NAME:  googletalk.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul 16 07:46:28.857 2010 (UTC - 4:00)
System Uptime: 2 days 23:14:12.823
BugCheck A, {c1e7, 2, 1, fffff80002cc684c}
Probably caused by : ntkrnlmp.exe ( nt!KeWaitForSingleObject+13c )
BUGCHECK_STR:  0xA
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 09:21:25.599 2010 (UTC - 4:00)
System Uptime: 10 days 21:27:15.203
BugCheck 50, {ffffffffffffffc1, 0, fffff80002ab1dd8, 0}
Probably caused by : hardware ( nt!_security_check_cookie+8 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  Wow.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jun 18 11:53:19.006 2010 (UTC - 4:00)
System Uptime: 12 days 8:42:01.047
BugCheck 1000007E, {ffffffffc0000005, fffff80002a852ed, fffff88005fbf388, fffff88005fbebf0}
Probably caused by : ntkrnlmp.exe ( nt!ExpAllocateBigPool+43d )
PROCESS_NAME:  dwm.exe
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun  6 03:10:46.926 2010 (UTC - 4:00)
System Uptime: 2 days 7:17:58.925
BugCheck A, {8, 2, 0, fffff80002a0d502}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iMapTransfer+24a )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May 11 18:21:38.007 2010 (UTC - 4:00)
System Uptime: 0 days 3:07:26.973
BugCheck A, {0, 2, 1, fffff80002ac784c}
Probably caused by : ntkrnlmp.exe ( nt!KeWaitForSingleObject+13c )
BUGCHECK_STR:  0xA
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]

 

[Tervel]

Thanks for the reply!

Started with removing 2 of my HDDs and moving them to another computer - meaning I'm down to 3 HDDs in the PC getting BSODs.
Ran the ESET online scan, found no infections.
~12 hours of memtest (11 passes) - zero errors.

Going to run the HDD diagnostic overnight but just had another BSOD so figured I would post that dump as well in case it gives any new info.

Thanks again!

EDIT: 24min of Furmark, temp seemed to not go higher than 107°C, minimum fps of 24 (how do I know if this is good or bad or if my graphics card passed or failed?)

EDIT2: Ran Prime95 for a while - will run for a longer duration tomorrow but here's the results:

[Jul 22 08:49] Torture Test completed 54 tests in 1 hours, 36 minutes - 0 errors, 0 warnings.
[Jul 22 08:49] Torture Test completed 59 tests in 1 hours, 36 minutes - 0 errors, 0 warnings.
[Jul 22 08:49] Torture Test completed 59 tests in 1 hours, 36 minutes - 0 errors, 0 warnings.
[Jul 22 08:49] Torture Test completed 60 tests in 1 hours, 36 minutes - 0 errors, 0 warnings.

 

[usasma]

With Furmark - if the video card starts to melt you know that there's a problem
Seriously, we just look for temps and for problems with the display (black screen, distorted screen, etc).

You can't tell from just one dump file if it's a hardware error - it's the pattern of errors that suggests that it's hardware.

That being said, try running Driver Verifier according to these instructions:

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/Win7 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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

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

If it continues to point at different errors - or at Windows errors - then it's probably confirming that it's hardware.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 21 23:24:11.718 2010 (UTC - 4:00)
System Uptime: 0 days 10:42:27.294
BugCheck 1E, {ffffffffc0000005, fffff80002c843b7, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSecondaryClockInterrupt+247 )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  Wow.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]

 

[Tervel]

Activated Driver Verifier, had a BSOD instantly in a Virtual CD app I installed a few days ago - it's not been installed since I started having the BSODs - I uninstalled it and my PC has been running for ~30 hours now with driver verifier on without any BSOD.

Attaching four minidumps anyway - these may or may not all be related to that Virtual CD application.

What is the next step if I don't get a BSOD in the next day or so with Driver Verifier on?

 

[Tews]

If you dont get anymore BSOD crashes, then it is probably safe to turn driver verifier off....

 

[Tervel]

Glad I kept Driver Verifier on for a little bit longer as I just had another BSOD! Attaching dump file.

 

[CarlTR6]

The error code is 1A and suggests your graphics card may be involved. It blames direct X: dxgmms1.sys.

STOP 0x0000001A: MEMORY_MANAGEMENT

Usual causes: Device driver, memory, kernel

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_073010-23025-01.zip\073010-23025-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c54000 PsLoadedModuleList = 0xfffff800`02e91e50
Debug session time: Fri Jul 30 13:19:41.576 2010 (GMT-4)
System Uptime: 1 days 6:07:00.558
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {411, fffff6fc50076cc8, a16000009ce68882, d89}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000411, The subtype of the bugcheck.
Arg2: fffff6fc50076cc8
Arg3: a16000009ce68882
Arg4: 0000000000000d89

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


BUGCHECK_STR:  0x1a_411

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

TRAP_FRAME:  fffff880066e6750 -- (.trap 0xfffff880066e6750)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a0099dea00 rbx=0000000000000000 rcx=fffffa8006343000
rdx=fffffa80058bd9a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004f6fcf7 rsp=fffff880066e68e0 rbp=fffffa8004eaeb00
 r8=fffffa80051ad301  r9=0000000000000000 r10=0000000000000000
r11=0000000000000090 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b:
fffff880`04f6fcf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh ds:00000000`00000054=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c8b6ae to fffff80002cc4600

STACK_TEXT:  
fffff880`066e63f8 fffff800`02c8b6ae : 00000000`0000001a 00000000`00000411 fffff6fc`50076cc8 a1600000`9ce68882 : nt!KeBugCheckEx
fffff880`066e6400 fffff800`02cf667d : fffff8a0`0ed99ea4 fffff6fc`50076cc8 0000007f`fffffff8 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x6051
fffff880`066e6450 fffff800`02ce0c06 : 00000000`00000000 fffff8a0`099dea00 00000000`00000000 fffff800`02e50b40 : nt!MiResolveTransitionFault+0x38d
fffff880`066e64e0 fffff800`02cdebd1 : fffffa80`00000051 00000000`00000040 a0900000`140f8882 00000000`00000002 : nt!MiDispatchFault+0x946
fffff880`066e65f0 fffff800`02cc26ee : 00000000`00000000 fffff8a0`0ed99e50 fffffa80`06343000 fffffa80`05fe6370 : nt!MmAccessFault+0x8f1
fffff880`066e6750 fffff880`04f6fcf7 : 00000000`00000000 fffff880`04f6cc0a 00000000`00000010 00000000`00010246 : nt!KiPageFault+0x16e
fffff880`066e68e0 fffff880`04f6ced3 : 00000000`00000000 fffffa80`04c823a8 00000000`0000001b 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b
fffff880`066e6910 fffff880`04f8765d : 00000000`00000000 fffff8a0`0357f090 fffffa80`00000000 fffffa80`051ad380 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`066e6ae0 fffff880`04f87398 : fffff800`00b96080 fffff880`04f86d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`066e6cd0 fffff880`04f86e96 : 00000000`00000000 fffffa80`05c3c310 00000000`00000080 fffffa80`05fe6370 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`066e6d00 fffff800`02f69a86 : 00000000`02d6eaca fffffa80`039f4b10 fffffa80`039e8040 fffffa80`039f4b10 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`066e6d40 fffff800`02ca2b06 : fffff800`02e3ee80 fffffa80`039f4b10 fffff800`02e4cc40 fffff880`01222534 : nt!PspSystemThreadStartup+0x5a
fffff880`066e6d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
fffff880`04f6fcf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0x1a_411_VRF_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

BUCKET_ID:  X64_0x1a_411_VRF_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

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

Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net. Post back with the results.

Here are three threads you might want to read:

http://www.nvnews.net/vbulletin/showthread.php?t=142821

http://nzgeek.org/blog/dxgmms1-sys-crash-blue-screen-of-death/

http://forums.guru3d.com/showthread.php?t=309360

 

[Tervel]

Sorry for the very slow reply.

20 minutes of Furmark with no issues.
I had a week or so without BSODs, but they have returned.
What is the next step? Any point in reformatting or is it definitely a hardware issue? If so, how do I determine what hardware?

 

[usasma]

Is Driver Verifier turned off? If not, please do so.
Please upload the dump files so we can have a look at them.

 

[Tervel]

Verifier is off.

Attaching the 2 dumps I've had since my last upload.

 

[usasma]

Can we get someone to run an analysis on these? (My system won't be back up until the weekend at the earliest).

 

[usasma]

IME there are 4 reasons for most BSOD's - in this order:

- 3rd party drivers
- compatibility problems (either hardware or software)
- broken hardware
- Windows problems

When the memory dump files are randomly spitting out errors (especially when you're testing for 3rd party driver issues with Driver Verifier) - then that generally rules out 3rd party drivers (and that leaves the rest of the stuff).

So the next step is to check compatibility using this link: Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads

If everything (and I do mean EVERYTHING) is listed as compatible, then the next most likely thing is broken hardware. To test for that, you'll have to run as many diagnostics as you can get your hands on - and that may still not be enough. Then, you'll have to check for hardware issues using the suggestions at this post: Hardware Troubleshooting Via System Stripdown

Finally, you can fix Windows problems by ensuring that you're up-to-date on Windows Updates, and by running SFC.EXE /SCANNOW. If that doesn't work, then you can wipe the hard drive and reinstall Windows to see if that fixes the problems.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Aug 15 11:56:57.348 2010 (UTC - 4:00)
System Uptime: 0 days 1:42:10.289
BugCheck 1E, {ffffffffc0000005, 0, 8, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  wmpnetwk.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Aug 10 20:06:03.421 2010 (UTC - 4:00)
System Uptime: 6 days 7:51:35.858
BugCheck A, {720, f, 0, fffff80002d92075}
*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
Probably caused by : Wdf01000.sys ( Wdf01000+73e2b )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/font]

http://www.bleepingcomputer.com/forums/topic70216.html

 

[Tervel]

Yet another one...

What may or may not be interesting with this BSOD is that just before the BSOD I had a complete system freeze - I was playing Starcraft II and the computer completely froze.
I could move my mouse pointer around but nothing else worked, game froze, audio froze (I could hear the audio stuttering in the background) even toggling num lock/caps lock didn't work.

I had to push the button to reboot, quickly started it up again to play another game and within a few minutes I had another BSOD (the memory dump of which is attached).

I don't know if this helps pinpointing the problem at all.

Thanks again!

 

[Tews]

The dmp(s) point to ntkrpamp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause.

At this point, I would follow usasmas' advice and back up your data and do a format/clean install. Your .dmp files are leading us in a big circle, and a clean install will probably be the quickest solution...

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffff8000000320, 2, 0, fffff80002c87328}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+28 )

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

 

[CarlTR6]

BugCheck A IRQL_NOT_LESS_OR_EQUAL - BSOD Index

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_082310-18220-01.zip\082310-18220-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c0b000 PsLoadedModuleList = 0xfffff800`02e48e50
Debug session time: Mon Aug 23 16:32:42.862 2010 (GMT-4)
System Uptime: 0 days 0:06:13.454
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffff8000000320, 2, 0, fffff80002c87328}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+28 )

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

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

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: ffffff8000000320, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002c87328, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb30e0
 ffffff8000000320 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerExpiration+28
fffff800`02c87328 8b08            mov     ecx,dword ptr [rax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002d1baa0 -- (.trap 0xfffff88002d1baa0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffff8000000320 rbx=0000000000000000 rcx=0000000000005d83
rdx=00000000000012c8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c87328 rsp=fffff88002d1bc30 rbp=0000000000005d83
 r8=0000000000000000  r9=0000000000000f44 r10=00000000000196af
r11=00000000002f9d00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na po nc
nt!KiTimerExpiration+0x28:
fffff800`02c87328 8b08            mov     ecx,dword ptr [rax] ds:ffffff80`00000320=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c7aca9 to fffff80002c7b740

STACK_TEXT:  
fffff880`02d1b958 fffff800`02c7aca9 : 00000000`0000000a ffffff80`00000320 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02d1b960 fffff800`02c79920 : fffffa80`04f8cd00 fffff780`00000008 00000000`00005d83 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02d1baa0 fffff800`02c87328 : 00000000`de988710 fffff880`02d1bc58 00000000`00005d83 fffff880`009ea5e8 : nt!KiPageFault+0x260
fffff880`02d1bc30 fffff800`02c86cb7 : 00000000`38920aa1 00000000`3892142a 00000000`38920aa1 00000000`00000083 : nt!KiTimerExpiration+0x28
fffff880`02d1bcd0 fffff800`02c83eea : fffff880`009e7180 fffff880`009f1fc0 00000000`00000000 fffff880`04eff588 : nt!KiRetireDpcList+0x277
fffff880`02d1bd80 00000000`00000000 : fffff880`02d1c000 fffff880`02d16000 fffff880`02d1bd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTimerExpiration+28
fffff800`02c87328 8b08            mov     ecx,dword ptr [rax]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTimerExpiration+28

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+28

BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+28

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

Unfortunately, the dumps does not pinpoint anything it only tells us there is still a hardware/hardware related problem. I have to agree with Tews recommendation. It is time for a clean install.

Tews and I were posting at the same time.

 

[Tervel]

I'll do a clean install during the weekend and report back a while after that with results whether I'm still getting BSODs or not.

Thanks again for all the help!

 

[Jonathan_King]

Test hardware.

First test your temps with Speedfan: SpeedFan - Access temperature sensor in your computer

Test hard drive: HD Diagnostic

Test RAM: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Test CPU: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

Test GFX card: http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Aug 15 11:56:57.348 2010 (UTC - 4:00)
System Uptime: 0 days 1:42:10.289
BugCheck 1E, {ffffffffc0000005, 0, 8, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  wmpnetwk.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 23 16:32:42.862 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:13.454
BugCheck A, {ffffff8000000320, 2, 0, fffff80002c87328}
Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+28 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨[/font]

 

[Tervel]

Hello!

Here I am again after a few months, a complete reformat and a graphics card upgrade and still seeing BSODs.

My updated system specs are in my profile.

I noticed one of the harddrives I use for storage was getting several bad blocks and removed it, no clue if this could have caused any BSODs.

With my limited knowledge I used Bluescreenviewer and saw two of the BSODs pointing at my NIC driver and updated that.

I am however still having bluescreens!

It seems to mainly happen if I do multiple things at once - gaming on one monitor while downloading, but also rarely happens without multitasking.
Something that seems to cause them pretty reliably is gaming on one monitor while watching youtube on my secondary monitor, usually makes them happen within an hour or so, often faster.

Is this definitely a hardware issue? If so how do I reliably determine what hardware, these BSODs are getting frustrating and I'm at the point where I'd just prefer spending some money on parts to get it sorted, I was sort of hoping buying a new graphics card would fix it as it needed upgrading anyway, but no luck.

Memory dumps are attached, thanks in advance for the help!