BSOD after playing Minecraft

[writhziden]

It may be due to application conflicts. You can http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html and find the program/service that is causing problems if there is one.

 

[kylendm]

Alright so it's been a while, and I tried a clean startup and still getting errors. I just got a new case with very sufficient cooling and I removed and applied coolant to the CPU and the cpu cooler. Just got a BSOD. I'll attach the minidump, not sure if it's the same error or not.

Here's the case I got.

I also bought a 200mm fan to pull air in on the side.

 

[kylendm]

Alright, as soon as I edited that post my computer froze. Figures this is happening after spending a bunch of money making sure my computer is cool.

When I turned it on it got stuck at the screen where I can select to go to bios or change order of start up. I restarted again and it froze. I unplugged the power, turned it on and now I'm here posting. Not sure if it's windows related anymore.

No dump file from the freezing that just happened.

When I got the BSOD I was playing Grand Theft Auto 4 by the way.

 

[writhziden]

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


Loading Dump File [C:\Users\Mike\Downloads\kylendm Feb 9th minidump\020912-20342-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 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03208000 PsLoadedModuleList = 0xfffff800`0344d670
Debug session time: Thu Feb  9 14:28:32.721 2012 (GMT-7)
System Uptime: 0 days 16:30:14.938
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10D, {8, 57ff8e46da8, 3, fffffa800621f750}

Unable to load image \SystemRoot\System32\Drivers\Saffire.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Saffire.sys
*** ERROR: Module load completed but symbols could not be loaded for Saffire.sys
Probably caused by : 1394ohci.sys ( 1394ohci!IsochTx::HandleIsochAttachBuffers+3ce )

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

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

WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error 
in a framework-based driver. In general, the dump file will yield additional 
information about the driver that caused this bug check.
Arguments:
Arg1: 0000000000000008, An operation occurred on a DMA transaction object while it
	was not in the correct state.
Arg2: 0000057ff8e46da8, Reserved.
Arg3: 0000000000000003, Reserved.
Arg4: fffffa800621f750, Reserved.

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


BUGCHECK_STR:  0x10D_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff88000eae3e1 to fffff80003284c40

STACK_TEXT:  
fffff880`030ae238 fffff880`00eae3e1 : 00000000`0000010d 00000000`00000008 0000057f`f8e46da8 00000000`00000003 : nt!KeBugCheckEx
fffff880`030ae240 fffff880`00eac12c : fffffa80`071b9250 0000057f`f8e46da8 00000000`00001401 fffffa80`0621f750 : Wdf01000!FxDmaTransactionBase::Initialize+0xf1
fffff880`030ae2a0 fffff880`0fddb36e : fffffa80`071b9250 00000000`00000000 fffff880`0fdda980 fffff880`00000001 : Wdf01000!imp_WdfDmaTransactionInitialize+0x278
fffff880`030ae340 fffff880`0fdd2c04 : fffffa80`00000005 fffffa80`06356c90 0000057f`00000006 fffff880`030ae470 : 1394ohci!IsochTx::HandleIsochAttachBuffers+0x3ce
fffff880`030ae3e0 fffff880`0fdd2069 : 0000057f`f7b20538 0000057f`f9ca9718 00000000`00000028 fffffa80`06353930 : 1394ohci!Isoch::HandleIsochAttachBuffers+0x100
fffff880`030ae440 fffff880`00ef2047 : fffffa80`084dfac0 fffffa80`0621f750 fffffa80`0621f750 00000000`00000000 : 1394ohci!Isoch::WdfEvtIoInternalDeviceControl+0x121
fffff880`030ae4b0 fffff880`00ef199f : fffffa80`063568e0 fffffa80`084dfac0 fffffa80`063568e0 fffffa80`084dfb02 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x56f
fffff880`030ae530 fffff880`00ef11ab : fffffa80`063568e0 00000000`00000002 00000000`00000000 00000000`00000000 : Wdf01000!FxIoQueue::DispatchEvents+0x4df
fffff880`030ae5a0 fffff880`00eeff1e : 00000000`00000002 fffffa80`063538d0 fffffa80`063568e0 fffffa80`084dfbe8 : Wdf01000!FxIoQueue::QueueRequestFromForward+0x1f7
fffff880`030ae600 fffff880`00ef0555 : fffff880`03087102 fffff800`03290f58 fffffa80`063538d0 00000000`00000011 : Wdf01000!FxIoQueue::ForwardRequestWorker+0x17a
fffff880`030ae670 fffff880`00ecdcd6 : fffffa80`06353900 fffffa80`0621f750 00000000`00000000 fffffa80`084dfa00 : Wdf01000!FxIoQueue::ForwardRequest+0x185
fffff880`030ae6e0 fffff880`0fdce8c4 : fffffa80`063568e0 0000057f`f7b20538 fffffa80`084dfac0 fffffa80`06353c80 : Wdf01000!imp_WdfRequestForwardToIoQueue+0x12e
fffff880`030ae730 fffff880`0fdce605 : 0000057f`f7b20538 0000057f`f9cac728 00000000`00000028 fffffa80`06353c80 : 1394ohci!Dispatch::DispatchIrbRequest+0xa8
fffff880`030ae780 fffff880`00ef2047 : fffffa80`084dfac0 fffffa80`0621f750 fffffa80`0621f750 fffffa80`063538d0 : 1394ohci!Dispatch::WdfEvtIoInternalDeviceControl+0x131
fffff880`030ae7f0 fffff880`00ef199f : 00000000`00000000 fffffa80`084dfac0 fffffa80`063538d0 fffffa80`063538d0 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x56f
fffff880`030ae870 fffff880`00ef0f98 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`084dfc12 : Wdf01000!FxIoQueue::DispatchEvents+0x4df
fffff880`030ae8e0 fffff880`00ef6558 : fffffa80`07a45902 fffffa80`084dfac0 fffffa80`07a45840 fffffa80`084dfac0 : Wdf01000!FxIoQueue::QueueRequest+0x2bc
fffff880`030ae950 fffff880`00ee0245 : fffffa80`084dfac0 00000000`00000000 00000000`00000000 0000057f`f847baa8 : Wdf01000!FxPkgIo::Dispatch+0x37c
fffff880`030ae9d0 fffff880`00ecc6d0 : 00000000`00000000 00000000`00000000 0000057f`f847baa8 fffff880`030aea80 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`030aea00 fffff880`0fdcc178 : fffffa80`0621f8a0 fffffa80`07b84550 fffffa80`07243df0 fffffa80`0763a390 : Wdf01000!imp_WdfRequestSend+0x37c
fffff880`030aea50 fffff880`0fdcc3af : fffffa80`046d47e0 0000057f`f847baa8 00000000`00000000 00001f80`00000200 : 1394ohci!ChildDevice::DispatchIrbRequest+0x60
fffff880`030aeaa0 fffff880`0fdcb289 : 0000057f`f847baa8 0000057f`f8a5cfd8 00000000`00000028 fffffa80`0763a390 : 1394ohci!ChildDevice::HandleIrbRequest+0x1db
fffff880`030aeae0 fffff880`00ef2047 : fffffa80`07b84550 fffffa80`0621f750 fffffa80`0621f750 fffff880`03087180 : 1394ohci!ChildDevice::WdfEvtIoInternalDeviceControl+0x141
fffff880`030aeb50 fffff880`00ef199f : 00000000`00000000 fffffa80`07b84550 fffffa80`075a3020 fffffa80`075a3020 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x56f
fffff880`030aebd0 fffff880`00ef0f98 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`07b846a2 : Wdf01000!FxIoQueue::DispatchEvents+0x4df
fffff880`030aec40 fffff880`00ef6558 : fffffa80`07a45902 fffffa80`07b84550 fffffa80`07a45840 fffffa80`07b84550 : Wdf01000!FxIoQueue::QueueRequest+0x2bc
fffff880`030aecb0 fffff880`00ee0245 : fffffa80`07b84550 fffffa80`07a45840 fffff880`06ee2c00 fffffa80`040a5ec0 : Wdf01000!FxPkgIo::Dispatch+0x37c
fffff880`030aed30 fffff880`06edc537 : fffffa80`00000246 fffffa80`07a45840 fffff880`06ee2c00 00000000`000007ff : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`030aed60 fffffa80`00000246 : fffffa80`07a45840 fffff880`06ee2c00 00000000`000007ff 00000000`00000000 : Saffire+0x27537
fffff880`030aed68 fffffa80`07a45840 : fffff880`06ee2c00 00000000`000007ff 00000000`00000000 00000000`00000000 : 0xfffffa80`00000246
fffff880`030aed70 fffff880`06ee2c00 : 00000000`000007ff 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`07a45840
fffff880`030aed78 00000000`000007ff : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Saffire+0x2dc00
fffff880`030aed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`00000000 : 0x7ff


STACK_COMMAND:  kb

FOLLOWUP_IP: 
1394ohci!IsochTx::HandleIsochAttachBuffers+3ce
fffff880`0fddb36e 413bc5          cmp     eax,r13d

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  1394ohci!IsochTx::HandleIsochAttachBuffers+3ce

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: 1394ohci

IMAGE_NAME:  1394ohci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a6a8

FAILURE_BUCKET_ID:  X64_0x10D_8_1394ohci!IsochTx::HandleIsochAttachBuffers+3ce

BUCKET_ID:  X64_0x10D_8_1394ohci!IsochTx::HandleIsochAttachBuffers+3ce

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

The crash appears to have something to do with your Saffire sound again. It did not appear that you had a temperature problem, so I highly doubt that is the case unless your temperatures have been higher than what you gave in your previous post during gaming. You previous temperatures were well within limits and not an issue, which is why I suggested it may be an application problem.

It appears that you have three sound devices in your system. Microsoft, NVIDIA, and Saffire.

Name	NVIDIA High Definition Audio
Manufacturer	NVIDIA
Status	Error
PNP Device ID	HDAUDIO\FUNC_01&VEN_10DE&DEV_0012&SUBSYS_10DE0101&REV_1001\5&2147B7AA&0&0301
Driver	c:\windows\system32\drivers\nvhda64v.sys (1.2.24.0, 170.10 KB (174,184 bytes), 10/25/2011 9:46 AM)
	
Name	High Definition Audio Device
Manufacturer	Microsoft
Status	Error
PNP Device ID	HDAUDIO\FUNC_01&VEN_1106&DEV_0397&SUBSYS_104383C4&REV_1000\4&87F9872&0&0001
Driver	c:\windows\system32\drivers\hdaudio.sys (6.1.7601.17514, 342.00 KB (350,208 bytes), 11/20/2010 10:23 PM)
	
Name	Saffire Audio
Manufacturer	Focusrite A.E.
Status	OK
PNP Device ID	SAFFIRE\AUDIO&ADAPTER01\DICEPARENTPREFIX&A00130E0401C006EB
Driver	c:\windows\system32\drivers\saffireaudio.sys (3.5.6.11675, 40.84 KB (41,824 bytes), 10/31/2011 10:27 PM)
	
Name	NVIDIA High Definition Audio
Manufacturer	NVIDIA
Status	Error
PNP Device ID	HDAUDIO\FUNC_01&VEN_10DE&DEV_0012&SUBSYS_10DE0101&REV_1001\5&2147B7AA&0&0001
Driver	c:\windows\system32\drivers\nvhda64v.sys (1.2.24.0, 170.10 KB (174,184 bytes), 10/25/2011 9:46 AM)
	
Name	Saffire MIDI
Manufacturer	Focusrite A.E.
Status	OK
PNP Device ID	SAFFIRE\MIDIIN\DICEPARENTPREFIX&MI00130E0401C006EB
Driver	c:\windows\system32\drivers\saffiremidi.sys (3.5.6.11675, 49.97 KB (51,168 bytes), 10/31/2011 10:27 PM)
	
Name	Saffire MIDI
Manufacturer	Focusrite A.E.
Status	OK
PNP Device ID	SAFFIRE\MIDIOUT\DICEPARENTPREFIX&MO00130E0401C006EB
Driver	c:\windows\system32\drivers\saffiremidi.sys (3.5.6.11675, 49.97 KB (51,168 bytes), 10/31/2011 10:27 PM)
	
Name	NVIDIA High Definition Audio
Manufacturer	NVIDIA
Status	Error
PNP Device ID	HDAUDIO\FUNC_01&VEN_10DE&DEV_0012&SUBSYS_10DE0101&REV_1001\5&2147B7AA&0&0101
Driver	c:\windows\system32\drivers\nvhda64v.sys (1.2.24.0, 170.10 KB (174,184 bytes), 10/25/2011 9:46 AM)
	
Name	NVIDIA High Definition Audio
Manufacturer	NVIDIA
Status	Error
PNP Device ID	HDAUDIO\FUNC_01&VEN_10DE&DEV_0012&SUBSYS_10DE0101&REV_1001\5&2147B7AA&0&0201
Driver	c:\windows\system32\drivers\nvhda64v.sys (1.2.24.0, 170.10 KB (174,184 bytes), 10/25/2011 9:46 AM)

I hypothesize that all three being enabled and running is causing conflicts with the Saffire card.

Nevermind, I see they are all disabled... I do see

1394 OHCI Compliant Host Controller (Legacy)	PCI\VEN_1106&DEV_3044&SUBSYS_81FE1043&REV_C0\4&F7B076E&0&5040	This device is disabled.

which is basically what is causing your crash, so you may want to enable this device.

 

[kylendm]

Yes I have the Microsoft and HD Audio disabled because they cause conflicts with my Saffire Interface. I just enabled the other 1394. I hope this might help with stability.

 

[writhziden]

Yes I have the Microsoft and HD Audio disabled because they cause conflicts with my Saffire Interface. I just enabled the other 1394. I hope this might help with stability.

Yeah, I just saw they were there and then saw the errors associated with them. It was not until I checked your hardware problem devices that I saw them disabled and noticed the Legacy driver disabled. I did some research and saw that other people had the same crash as you if the Legacy driver was out of date, so I figured having it disabled is probably a lot worse than having it out of date.

This also gives you an idea that if you continue to have 1394 OHCI crashes, you may want to update the Legacy 1394 OHCI driver. Best wishes that enabling it does the trick, though.

 

[kylendm]

Alright I updated the driver and enabled it. No more BSODs in game but I had my computer on idle, came back after an hour, moved the mouse just a little and it froze. I got a dump for it.

 

[writhziden]

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


Loading Dump File [E:\BSODDmpFiles\Kylendm\Feb 10th Minidump kylendm\021012-51807-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03257000 PsLoadedModuleList = 0xfffff800`0349c670
Debug session time: Fri Feb 10 14:56:33.462 2012 (GMT-7)
System Uptime: 0 days 0:00:15.679
Loading Kernel Symbols
.................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8005f6f8f8, 0, 0}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8005f6f8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031686f0 fffff800`03519c59 : fffffa80`05f6f8d0 fffffa80`03a74040 00000000`0000000f 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03168c10 fffff800`033f9f57 : fffffa80`05f6f8d0 fffff800`034742b8 fffffa80`03a74040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03168c40 fffff800`033615d5 : fffff800`034d5ae0 00000000`00000001 fffffa80`049f8820 fffffa80`03a74040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03168c80 fffff800`032de001 : fffff880`00ddbe00 fffff800`033615b0 fffffa80`03a74000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03168cb0 fffff800`0356efee : 00000000`00000000 fffffa80`03a74040 00000000`00000080 fffffa80`03973890 : nt!ExpWorkerThread+0x111
fffff880`03168d40 fffff800`032c55e6 : fffff880`03088180 fffffa80`03a74040 fffff880`03093040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03168d80 00000000`00000000 : fffff880`03169000 fffff880`03163000 fffff880`03b1d690 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

Back to http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

This looks like either the memory, CPU, motherboard, or PSU. What RAM do you currently have in the system? Can you remove your old RAM and only run the new modules?
If you swap any memory components, follow these steps for ESD safety:

1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.

 

[kylendm]

I can plug the new RAM in, I hope that's all it is. The PSU is pretty new and 80 plus. I'll throw the new RAM in and let you know. I wish there was a way to really test it because sometimes the freezing won't come for days other times it can happy twice in an hour.

Also thanks for helping me with all this, you've been a huge help so far!

 

[writhziden]

I too hope it is just the old RAM that is at fault. Keep us posted as to whether stability improves.

 

[kylendm]

I haven't switched the RAM yet but I got another BSOD that I don't think had to do with the RAM. Seems to be the same file size as the other BSOD that had to do with the 1394 being disabled.

I was playing Civilization V by the way just to narrow it down a little.

 

[writhziden]

There definitely seems to be some conflict with your sound devices. Can any of the devices be disabled through the BIOS?

 

[kylendm]

Not sure, I'll check.

 

[kylendm]

Alright I disabled my onboard 1394 and my onboard audio in BIOS.

 

[writhziden]

Sounds good. Post back if you have similar crashes. Hopefully this will help narrow the problem down to something more tangible, or better yet, it will eliminate the crashes altogether.

 

[kylendm]

Alright was going strong and then it just froze. Here is your complimentary minidump .

I was just finishing up a website I was doing and went to cancel my browser just a note. Guessing this one has to do with my hardware. I'll install the other RAM.

 

[writhziden]

Download and install CPUZ and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs.

Also, go into your BIOS and post all RAM and CPU Voltages and all RAM settings (timings, frequency, etc.)

 

[kylendm]

Well everything is set to auto in my BIOS and I didn't get much info out of it but here's what I did get.

CPU frequency 2800MHz
DRAM frequency 1333MHz

And these were all set to auto but I'm getting the standard is what I'm using which is this:
NB Voltage 1.10V
HT Voltage 1.20V
RAM Voltage 1.50V
CPU VDDA Voltage 2.50v
DRAM CAS 9-9-9-24

 

[writhziden]

Bump the NB Voltage to 1.20 V. Manually set the timing to 9-9-9-24 and command rate to 2T. See if the system runs more stable.

Thanks to Dave76 for help learning RAM Stability


What are the results of the RAM setting changes?

 

[kylendm]

Eh I still have a few crashes and freeze ups. Not as frequent though.