Diablo® III

BSOD when i play D3

im having problems with the damn blue screen there are the txt dumo files from bluescreenview. Any heko would be appreciate. ty

==================================================
Dump File : 070612-9828-01.dmp
Crash Time : 7/6/2012 6:36:44 PM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`08be23f0
Parameter 3 : fffffa80`08be26d0
Parameter 4 : fffff800`03781510
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070612-9828-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 289,936
==================================================

==================================================
Dump File : 070612-11187-01.dmp
Crash Time : 7/6/2012 5:39:12 PM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`08157060
Parameter 3 : fffffa80`08157340
Parameter 4 : fffff800`0379b510
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070612-11187-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 290,768
==================================================
Reply Quote
I would run a memory testing app like memtest86+ this could very well be bad memory.

http://www.memtest.org/
Reply Quote
Support Forum Agent
Posts: 32,861
Pikaboo

I'd check that the system's RAM is working properly by using Memtest86 Plus.

You can find the download and instructions here: http://www.memtest.org/

For the most accurate results, I'd leave the test running overnight.

Even if no errors are found with the test, there is still a good chance that there is an issue with the RAM. The best way to test this is to remove some RAM and just leave one stick at a time, then try the game. If you get the error again, remove the stick of RAM that is currently in there and insert another. This is basically a process of elimination to determine which sticks might be causing the issue.
________________________________________________
Support Information Administrator
If you can't find a solution to your issue, feel free to contact a Support Representative directly for further assistance. Their contact information can be found at the following link: http://us.blizzard.com/en-us/company/about/contact.html

I'm available on the forums Monday through Friday from 11AM to 8PM Pacific Time
Reply Quote
Thank you for ur fast response no errors where detect it, so i started to play BF3 and no crash ill try with D3 and see wat happens :)

Thank you very much.
Reply Quote
Thank you for ur fast response no errors where detect it, so i started to play BF3 and no crash ill try with D3 and see wat happens :)

Thank you very much.
you should let the test run for a minimum of 10 passes and thats a bare minimum. i normally set a test to start before i leave work and then check it in the morning.
Reply Quote
OK now, it happened again with both memorys :/, i downloaed the whocrash here is the analysis:

System Information (local)
--------------------------------------------------------------------------------

computer name: JOSHUA-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 4258476032 total
VM: 2147352576, free: 1952350208

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 7/10/2012 8:10:40 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8005B90B30, 0xFFFFFA8005B90E10, 0xFFFFF80003783510)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown CRITICAL_OBJECT_TERMINATION

On Tue 7/10/2012 7:29:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071012-10906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8008BCE760, 0xFFFFFA8008BCEA40, 0xFFFFF800037CB510)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Tue 7/10/2012 8:58:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071012-9921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009004060, 0xFFFFFA8009004340, 0xFFFFF800037CA510)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Fri 7/6/2012 11:36:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070612-9828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8008BE23F0, 0xFFFFFA8008BE26D0, 0xFFFFF80003781510)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Fri 7/6/2012 10:38:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070612-11187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8008157060, 0xFFFFFA8008157340, 0xFFFFF8000379B510)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

5 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

unknown

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

-----------------------------------------------------------------------------------------------------------

Here is the diskcheck stuff:

- EventData

Checking file system on C: The type of the file system is NTFS. Volume label is Windows. One of your disks needs to be checked for consistency. You may cancel the disk check, but it is strongly recommended that you continue. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 3)... 146432 file records processed. File verification completed. 115 large file records processed. 0 bad file records processed. 0 EA records processed. 60 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)... Unable to locate the file name attribute of index entry restore.0.etl of index $I30 with parent 0xc7ea in file 0x16a9f. Deleting index entry restore.0.etl in index $I30 of file 51178. The multi-sector header signature for VCN 0x0 of index $I30 in file 0x1db6b is incorrect. 60 00 00 00 02 00 00 00 64 0a 00 00 00 00 17 00 `.......d....... ea c7 00 00 00 00 73 06 00 00 e4 0d 00 00 00 00 ......s......... Correcting error in index $I30 for file 121707. The index bitmap $I30 in file 0x1db6b is incorrect. Correcting error in index $I30 for file 121707. The down pointer of current index entry with length 0x18 is invalid. 00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................ ff ff ff ff ff ff ff ff 15 b9 aa 8a 93 54 cd 01 .............T.. 15 b9 aa 8a 93 54 cd 01 3b df aa 8a 93 54 cd 01 .....T..;....T.. Sorting index $I30 in file 121707. 193036 index entries processed. Index verification completed. CHKDSK is scanning unindexed files for reconnect to their original directory. There is no NTFS file name attribute in file 0x16a9f. Correcting minor file name errors in file 92831. Recovering orphaned file SYSTEM~1 (121707) into directory file 68084. Recovering orphaned file SystemRestore (121707) into directory file 68084. Recovering orphaned file VOLSNA~1 (121708) into directory file 121707. Recovering orphaned file VolSnapPreCopyOnWriteSettings (121708) into directory file 121707. Recovering orphaned file RESTOR~3.ETL (121709) into directory file 51178. Recovering orphaned file restore.0.etl (121709) into directory file 51178. Recovering orphaned file NEW-DE~1 (121710) into directory file 121707. Recovering orphaned file New-default (121710) into directory file 121707. Recovering orphaned file New-SAM (121711) into directory file 121707. Recovering orphaned file NEW-SE~1 (121712) into directory file 121707. Recovering orphaned file New-SECURITY (121712) into directory file 121707. Recovering orphaned file NEW-SO~1 (121713) into directory file 121707. Recovering orphaned file New-software (121713) into directory file 121707. Recovering orphaned file NEW-SY~1 (121714) into directory file 121707. Recovering orphaned file New-system (121714) into directory file 121707. Recovering orphaned file NEW-SC~1.DAT (121715) into directory file 121707. Recovering orphaned file New-schema.dat (121715) into directory file 121707. 11 unindexed files scanned. Recovering orphaned file NEW-CO~1 (121716) into directory file 121707. Recovering orphaned file New-COMPONENTS (121716) into directory file 121707. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)... 146432 file SDs/SIDs processed. Cleaning up 11 unused index entries from index $SII of file 0x9. Cleaning up 11 unused index entries from index $SDH of file 0x9. Cleaning up 11 unused security descriptors. Security descriptor verification completed. 23303 data files processed. CHKDSK is verifying Usn Journal... The USN Journal entry at offset 0x1027b000 and length 0x98c4d88 crosses the page boundary. Repairing Usn Journal file record segment. 33802520 USN bytes processed. Usn Journal verification completed. Correcting errors in the Volume Bitmap. Windows has made corrections to the file system. 976656383 KB total disk space. 114979288 KB in 100462 files. 59532 KB in 23304 indexes. 0 KB in bad sectors. 276215 KB in use by the system. 65536 KB occupied by the log file. 861341348 KB available on disk. 4096 bytes in each allocation unit. 244164095 total allocation units on disk. 215335337 allocation units available on disk. Internal Info: 00 3c 02 00 82 e3 01 00 cd 82 03 00 00 00 00 00 .<.............. eb 00 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 ....<........... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Windows has finished checking your disk. Please wait while your computer restarts.

-----------------------------------------------------------------------------------------------------------
I hope u can help me. Ty.
Reply Quote
I already test it with 10 tests like the other guy said there where no errors found...............

Could be something else?

maybe i should get some ram from another computer and see /
Edited by Pikaboo#1179 on 7/10/2012 3:56 PM PDT
Reply Quote

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)
Submit Cancel

Reported!

[Close]