Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD after playing Minecraft

19 Jan 2012   #1
kylendm

Windows 7 Proffesional 64bit
 
 
BSOD after playing Minecraft

My computer is a Windows 7 64bit Full Retail version.

I can't tell the age of the hardware but it's all not older than a year I would say. My OS install is about 5 months old.

System Info:
CPU - AMD Phenom II X6 1055T
RAM - 8GB Dual Channel DDR3 @ 666mhz (9-9-9-24)
Motherboard - ASUS M4N75TD (AM3)
GPU - 1024MB GeForce GTX 460 (PNY)
Harddrives - 2x Hitachi Sata drives, One 250gb other 1TB

I was playing Minecraft for a bit and then it went to a BSOD. I have the attached files in the zip below. I also notice other games like Grand Theft Auto 4 crashing at random, no BSOD on that though.






My System SpecsSystem Spec
19 Jan 2012   #2
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\kylendm\Windows7_Vista_jcgriff2\010512-20108-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\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`03258000 PsLoadedModuleList = 0xfffff800`0349d670 Debug session time: Thu Jan 5 11:49:12.630 2012 (UTC - 7:00) System Uptime: 0 days 0:00:17.472 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, fffffa8008bfa8f8, 0, 0} Probably caused by : hardware Followup: MachineOwner --------- 0: 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: fffffa8008bfa8f8, 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`0318b6f0 fffff800`0351ac59 : fffffa80`08bfa8d0 fffffa80`06a6cb60 fffff8a0`0000000f 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c fffff880`0318bc10 fffff800`033faf57 : fffffa80`08bfa8d0 fffff800`034752b8 fffffa80`06a6cb60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49 fffff880`0318bc40 fffff800`033625d5 : fffff800`034d6ae0 00000000`00000001 fffffa80`07a02820 fffffa80`06a6cb60 : nt!WheapProcessWorkQueueItem+0x57 fffff880`0318bc80 fffff800`032df001 : fffff880`0108be00 fffff800`033625b0 fffffa80`06a6cb00 fffffa80`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25 fffff880`0318bcb0 fffff800`0356ffee : 00000000`00000000 fffffa80`06a6cb60 00000000`00000080 fffffa80`069ab890 : nt!ExpWorkerThread+0x111 fffff880`0318bd40 fffff800`032c65e6 : fffff880`03088180 fffffa80`06a6cb60 fffff880`03093040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`0318bd80 00000000`00000000 : fffff880`0318c000 fffff880`03186000 fffff880`037fc5e0 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 ---------
  2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\kylendm\Windows7_Vista_jcgriff2\010712-18595-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\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`03258000 PsLoadedModuleList = 0xfffff800`0349d670 Debug session time: Sat Jan 7 11:57:01.999 2012 (UTC - 7:00) System Uptime: 2 days 0:08:06.840 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols Loading unloaded module list ....................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 10D, {8, 57ff3a9ffd8, 3, fffffa8009256a30} 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 --------- 4: 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: 0000057ff3a9ffd8, Reserved. Arg3: 0000000000000003, Reserved. Arg4: fffffa8009256a30, Reserved. Debugging Details: ------------------ BUGCHECK_STR: 0x10D_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: CivilizationV_ CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff88000c053e1 to fffff800032d4c40 STACK_TEXT: fffff880`03045468 fffff880`00c053e1 : 00000000`0000010d 00000000`00000008 0000057f`f3a9ffd8 00000000`00000003 : nt!KeBugCheckEx fffff880`03045470 fffff880`00c0312c : fffffa80`0c560020 0000057f`f3a9ffd8 00000000`00001401 fffffa80`09256a30 : Wdf01000!FxDmaTransactionBase::Initialize+0xf1 fffff880`030454d0 fffff880`068aa36e : fffffa80`0c560020 00000000`00000000 fffff880`068a9980 fffff880`00000001 : Wdf01000!imp_WdfDmaTransactionInitialize+0x278 fffff880`03045570 fffff880`068a1c04 : fffffa80`00000005 fffffa80`09205b90 0000057f`00000006 fffff880`030456a0 : 1394ohci!IsochTx::HandleIsochAttachBuffers+0x3ce fffff880`03045610 fffff880`068a1069 : 0000057f`f8fdf7a8 0000057f`f6dfa818 00000000`00000028 fffffa80`09261930 : 1394ohci!Isoch::HandleIsochAttachBuffers+0x100 fffff880`03045670 fffff880`00c49047 : fffffa80`07020850 fffffa80`09256a30 fffffa80`09256a30 00000000`00000282 : 1394ohci!Isoch::WdfEvtIoInternalDeviceControl+0x121 fffff880`030456e0 fffff880`00c4899f : fffffa80`092057e0 fffffa80`07020850 fffffa80`092057e0 fffffa80`07020902 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x56f fffff880`03045760 fffff880`00c481ab : fffffa80`092057e0 00000000`00000002 00000000`00000000 00000000`00000000 : Wdf01000!FxIoQueue::DispatchEvents+0x4df fffff880`030457d0 fffff880`00c46f1e : 00000000`00000002 fffffa80`092618d0 fffffa80`092057e0 fffffa80`07020978 : Wdf01000!FxIoQueue::QueueRequestFromForward+0x1f7 fffff880`03045830 fffff880`00c47555 : fffff880`009b2102 fffff800`032e0f58 fffffa80`092618d0 00000000`00000433 : Wdf01000!FxIoQueue::ForwardRequestWorker+0x17a fffff880`030458a0 fffff880`00c24cd6 : 00000000`00000002 fffffa80`09256a30 00000000`00000000 fffffa80`09256a30 : Wdf01000!FxIoQueue::ForwardRequest+0x185 fffff880`03045910 fffff880`0689d8c4 : fffffa80`092057e0 0000057f`f8fdf7a8 fffffa80`07020850 fffffa80`09261c80 : Wdf01000!imp_WdfRequestForwardToIoQueue+0x12e fffff880`03045960 fffff880`0689d605 : 0000057f`f8fdf7a8 0000057f`f6d9e728 00000000`00000028 fffffa80`09261c80 : 1394ohci!Dispatch::DispatchIrbRequest+0xa8 fffff880`030459b0 fffff880`00c49047 : fffffa80`07020850 fffffa80`09256a30 fffffa80`09256a30 fffffa80`092618d0 : 1394ohci!Dispatch::WdfEvtIoInternalDeviceControl+0x131 fffff880`03045a20 fffff880`00c4899f : 00000000`00000000 fffffa80`07020850 fffffa80`092618d0 fffffa80`092618d0 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x56f fffff880`03045aa0 fffff880`00c47f98 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`070209a2 : Wdf01000!FxIoQueue::DispatchEvents+0x4df fffff880`03045b10 fffff880`00c4d558 : fffffa80`075a0402 fffffa80`07020850 fffffa80`075a0380 fffffa80`07020850 : Wdf01000!FxIoQueue::QueueRequest+0x2bc fffff880`03045b80 fffff880`00c37245 : fffffa80`07020850 00000000`00000000 00000000`00000000 0000057f`f44732f8 : Wdf01000!FxPkgIo::Dispatch+0x37c fffff880`03045c00 fffff880`00c236d0 : 00000000`00000000 00000000`00000000 0000057f`f44732f8 fffff880`03045cb0 : Wdf01000!FxDevice::Dispatch+0xa9 fffff880`03045c30 fffff880`0689b178 : fffffa80`09256b80 fffffa80`0bb8cd00 fffffa80`0b361550 fffffa80`0b49e7c0 : Wdf01000!imp_WdfRequestSend+0x37c fffff880`03045c80 fffff880`0689b3af : fffffa80`0acf6d60 0000057f`f44732f8 fffffa80`0ce5bda8 fffffa80`07c642f8 : 1394ohci!ChildDevice::DispatchIrbRequest+0x60 fffff880`03045cd0 fffff880`0689a289 : 0000057f`f44732f8 0000057f`f466fbb8 00000000`00000028 fffffa80`0b49e7c0 : 1394ohci!ChildDevice::HandleIrbRequest+0x1db fffff880`03045d10 fffff880`00c49047 : fffffa80`0bb8cd00 fffffa80`09256a30 fffffa80`09256a30 fffff880`009b2180 : 1394ohci!ChildDevice::WdfEvtIoInternalDeviceControl+0x141 fffff880`03045d80 fffff880`00c4899f : 00000000`00000000 fffffa80`0bb8cd00 fffffa80`0b990440 fffffa80`0b990440 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x56f fffff880`03045e00 fffff880`00c47f98 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`0bb8ce52 : Wdf01000!FxIoQueue::DispatchEvents+0x4df fffff880`03045e70 fffff880`00c4d558 : fffffa80`075a0402 fffffa80`0bb8cd00 fffffa80`075a0380 fffffa80`0bb8cd00 : Wdf01000!FxIoQueue::QueueRequest+0x2bc fffff880`03045ee0 fffff880`00c37245 : fffffa80`0bb8cd00 fffffa80`075a0380 fffff880`097e7c00 fffffa80`0be3aa60 : Wdf01000!FxPkgIo::Dispatch+0x37c fffff880`03045f60 fffff880`097e1537 : fffffa80`00000246 fffffa80`075a0380 fffff880`097e7c00 00000000`000007ff : Wdf01000!FxDevice::Dispatch+0xa9 fffff880`03045f90 fffffa80`00000246 : fffffa80`075a0380 fffff880`097e7c00 00000000`000007ff 00000000`00000000 : Saffire+0x27537 fffff880`03045f98 fffffa80`075a0380 : fffff880`097e7c00 00000000`000007ff 00000000`00000000 00000000`00000000 : 0xfffffa80`00000246 fffff880`03045fa0 fffff880`097e7c00 : 00000000`000007ff 00000000`00000000 00000000`00000000 00000000`00000001 : 0xfffffa80`075a0380 fffff880`03045fa8 00000000`000007ff : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : Saffire+0x2dc00 fffff880`03045fb0 00000000`00000000 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`00000000 : 0x7ff STACK_COMMAND: kb FOLLOWUP_IP: 1394ohci!IsochTx::HandleIsochAttachBuffers+3ce fffff880`068aa36e 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 ---------
  3. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\kylendm\Windows7_Vista_jcgriff2\011912-19999-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\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`03267000 PsLoadedModuleList = 0xfffff800`034ac670 Debug session time: Thu Jan 19 09:18:14.160 2012 (UTC - 7:00) System Uptime: 0 days 11:12:12.001 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols Loading unloaded module list ................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffffa88093776d0, 2, 1, fffff800032d9bf3} Probably caused by : ohci1394.sys ( ohci1394!OhciHandleIsochInt+cb ) Followup: MachineOwner --------- 5: 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: fffffa88093776d0, 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: fffff800032d9bf3, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003516100 fffffa88093776d0 CURRENT_IRQL: 2 FAULTING_IP: nt!KeAcquireSpinLockAtDpcLevel+43 fffff800`032d9bf3 f0480fba2900 lock bts qword ptr [rcx],0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff880030b0a10 -- (.trap 0xfffff880030b0a10) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000007fffffff rbx=0000000000000000 rcx=fffffa88093776d0 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800032d9bf3 rsp=fffff880030b0ba0 rbp=fffffa80093774f0 r8=fffff880030b0600 r9=0000000000000000 r10=0000000000000000 r11=fffffa80070e9110 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!KeAcquireSpinLockAtDpcLevel+0x43: fffff800`032d9bf3 f0480fba2900 lock bts qword ptr [rcx],0 ds:a968:fffffa88`093776d0=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800032e31e9 to fffff800032e3c40 STACK_TEXT: fffff880`030b08c8 fffff800`032e31e9 : 00000000`0000000a fffffa88`093776d0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`030b08d0 fffff800`032e1e60 : fffffa80`0aa33300 fffffa80`06d7b010 fffffa80`0b5a7780 fffff880`03088180 : nt!KiBugCheckDispatch+0x69 fffff880`030b0a10 fffff800`032d9bf3 : fffffa80`0b1282b0 fffff880`0897bbbc fffffa80`0b3ecd90 fffffa80`093774f0 : nt!KiPageFault+0x260 fffff880`030b0ba0 fffff880`06a7badb : 00000000`00000000 fffffa80`093774f0 fffff880`0aecd0c8 00000000`00000003 : nt!KeAcquireSpinLockAtDpcLevel+0x43 fffff880`030b0bf0 fffff880`06a7b8e5 : fffffa80`093761a0 fffff880`7ffffff0 fffff880`030b0c00 00000000`00000001 : ohci1394!OhciHandleIsochInt+0xcb fffff880`030b0c80 fffff800`032ef0ac : fffff880`03088180 00000019`00277318 00000019`ad7491b8 00000000`00000018 : ohci1394!OhciIsochDpc+0x5d fffff880`030b0cd0 fffff800`032db96a : fffff880`03088180 fffff880`03093040 00000000`00000000 fffff880`06a7b888 : nt!KiRetireDpcList+0x1bc fffff880`030b0d80 00000000`00000000 : fffff880`030b1000 fffff880`030ab000 fffff880`030b0d40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: ohci1394!OhciHandleIsochInt+cb fffff880`06a7badb 4533d2 xor r10d,r10d SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: ohci1394!OhciHandleIsochInt+cb FOLLOWUP_NAME: MachineOwner MODULE_NAME: ohci1394 IMAGE_NAME: ohci1394.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc15 FAILURE_BUCKET_ID: X64_0xA_ohci1394!OhciHandleIsochInt+cb BUCKET_ID: X64_0xA_ohci1394!OhciHandleIsochInt+cb Followup: MachineOwner ---------
If you are overclocking anything, please stop.
  1. See Stop 0x124 - what it means and what to try for details.
  2. Caused by a driver, possibly Saffire audio, see Audio Interface, Mic Preamplifier, Small-format Consoles, Channel Strips, EQ & Compressor from Focusrite to find drivers for your product and update them. If you need help, let us know.
  3. Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Antivirus Software...
Start with the following steps.
  • To update the Saffire audio drivers, use the following steps

    You may use the following sites as references for finding drivers. We recommend finding the manufacturer of the driver and downloading drivers directly from the manufacturer or software developer. If you have trouble finding a driver or driver manufacturer, let us know and we will do our best to assist you. If you need help, please provide the device name, manufacturer, and the driver .sys file that you are looking for.
    1. Driver Reference is a good site to find the driver .sys files, their descriptions, and the site most likely to contain an update.
    2. Driver Search Methods provides driver manufacturers and links to their homepages.
    3. Audio Interface, Mic Preamplifier, Small-format Consoles, Channel Strips, EQ & Compressor from Focusrite
    There are a few methods for updating drivers.
    1. Installing and updating drivers in 7
    2. Driver Install - Add Hardware Wizard
    3. Driver Install - Device Manager

    To fully re-install a driver, use the following steps.
    1. Click Start Menu
    2. Right Click My Computer/Computer
    3. Click Manage
    4. Click Device Manager from the list on the left
    5. Find the device you are trying to uninstall by expanding the appropriate set of devices
    6. Right click the device
    7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    8. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    9. Restart your computer
    10. Install the latest driver for the device once Windows starts.

    Alternatively:
    1. Login as an adminstrative user.
    2. Click Start Menu
    3. Click Control Panel
    4. Click Hardware and Sound
    5. Click Device Manager (the last link under Devices and Printers)
    6. Find the device you are trying to uninstall by expanding the appropriate set of devices
    7. Right click the device
    8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    10. Restart your computer
    11. Install the latest driver for the device once Windows starts.
  • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  • Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
  • Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after the third run or if the first run comes back with no integrity violations.
Thanks to Dave76 for help understanding possible causes.
My System SpecsSystem Spec
22 Jan 2012   #3
kylendm

Windows 7 Proffesional 64bit
 
 

Alright I tried to rule out the problem since I added new RAM. I pulled it out and it was a bit stabler. Then again my computer just froze. I attached the dump file.
My System SpecsSystem Spec
22 Jan 2012   #4
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\kylendm\Dump as of Jan 21st\012112-19562-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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`03259000 PsLoadedModuleList = 0xfffff800`0349e670
Debug session time: Sat Jan 21 21:24:34.788 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:17.005
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, fffffa80049c38f8, 0, 0}

Probably caused by : hardware

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

4: 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: fffffa80049c38f8, 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`0317d6f0 fffff800`0351bc59 : fffffa80`049c38d0 fffffa80`03a5e040 00000000`0000000e 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0317dc10 fffff800`033fbf57 : fffffa80`049c38d0 fffff800`034762b8 fffffa80`03a5e040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0317dc40 fffff800`033635d5 : fffff800`034d7ae0 00000000`00000001 fffffa80`049dc820 fffffa80`03a5e040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0317dc80 fffff800`032e0001 : fffff880`010fae00 fffff800`033635b0 fffffa80`03a5e000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0317dcb0 fffff800`03570fee : 00000000`00000000 fffffa80`03a5e040 00000000`00000080 fffffa80`039739e0 : nt!ExpWorkerThread+0x111
fffff880`0317dd40 fffff800`032c75e6 : fffff880`03088180 fffffa80`03a5e040 fffff880`03093040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0317dd80 00000000`00000000 : fffff880`0317e000 fffff880`03178000 fffff880`0317d210 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
---------
Another STOP 0x124.

Download and install HWiNFO64 Download to check hardware temperatures by running in Sensor only mode. Before checking temperatures, run with Sensor only mode unchecked, click Save Report, and click browse to save as HTML to a location you will remember. Upload the HTML file to this thread.

Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net and |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card.

Run Hardware - Stress Test With Prime95 to determine any hardware problems.


Are you only running with the old RAM?
My System SpecsSystem Spec
22 Jan 2012   #5
kylendm

Windows 7 Proffesional 64bit
 
 

Thanks for your help so far. Here's the temps on idle. Other than browsing with firefox that is. And yes, now I'm running with just the old RAM.
My System SpecsSystem Spec
22 Jan 2012   #6
writhziden

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by kylendm View Post
Thanks for your help so far. Here's the temps on idle. Other than browsing with firefox that is. And yes, now I'm running with just the old RAM.
That is actually the hardware on your computer that you uploaded. I asked for that so I can check the compatibility of your devices. To check the temps, run HWINFO with sensor-only checked and post your temps during idle and during the tests I linked to.
My System SpecsSystem Spec
22 Jan 2012   #7
writhziden

Windows 7 Home Premium 64 Bit
 
 

Mushkin 991782 (996782) DDR3-1600 2x2GB is not listed as being compatible in the memory list provided by your manufacturer. That does not necessarily mean it is not compatible, just that it was not tested by ASUS.

You could try reducing the frequency to the next lowest and see if it provides more stability. Otherwise, contact Mushkin and ask if the RAM you have is supposed to be compatible with your board/CPU.
My System SpecsSystem Spec
22 Jan 2012   #8
kylendm

Windows 7 Proffesional 64bit
 
 

Weird because I've had that for maybe over a year now with no problems. The HWiNFO64 wont read my CPU temps for some reason.

Both Hard drives run at about 40C.
Graphics Card runs at about 35C on Idle and when running tests it's at about 71C after just a minute.
Motherboard is at about 54C Idle.
My System SpecsSystem Spec
22 Jan 2012   #9
writhziden

Windows 7 Home Premium 64 Bit
 
 

Can you get CPU temps with SpeedFan?
My System SpecsSystem Spec
22 Jan 2012   #10
kylendm

Windows 7 Proffesional 64bit
 
 

It says 41C for CPU and 0C for Core.
My System SpecsSystem Spec
Reply

 BSOD after playing Minecraft




Thread Tools



Similar help and support threads for2: BSOD after playing Minecraft
Thread Forum
BSOD(?) playing Minecraft BSOD Help and Support
BSOD playing Minecraft BSOD Help and Support
BSOD playing MineCraft BSOD Help and Support
playing minecraft and gets bsod!? BSOD Help and Support
BSOD while playing max payne 3 or minecraft BSOD Help and Support
BSOD playing TF2 and Minecraft BSOD Help and Support
BSOD while playing Minecraft BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 12:49 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App