Hello, I have just built a new system a week or two ago and have been getting several BSODs. Mostly this happens when playing Fallout 3, but also has happened while playing Minecraft, and while using Open Office Writer.
This is my first post here. I have filled out the system info on the profile part.
Any help is greatly appreciated, and let me know if I need to provide any other info.
Here is a way for you to analyze that dump very easily:
https://www.sevenforums.com/crashes-d...lp-needed.html
Thanks for the quick reply. Here are the steps I have taken thus far:
- I ran a scandsk /r as admin from command line. No problems found.
- I ran TestMem86 overnight. No problems found.
- I ran the Crash Analyzer. It was unable to find the cause of the problem.
- I verified all drivers on the system with the Verifier.
- I checked the core temperature. Doesn't seem unreasonably hot, but I have included a capture in case I'm wrong.
One of the errors is in Video Memory Management (STOP 0x10E: BSOD Index) Also, the error next to it also has memory as a cause (STOP 0x109: BSOD Index) as does another one (STOP 0xBE: BSOD Index). Of the rest of the errors, there's a lot of memory issues and issues with your video. Please try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Also, please update this older driver to the latest Win7 version: jraid.sys Mon Nov 03 21:20:09 2008
It's a component of your JMicron RAID controller.
Here's a summary of the BSOD's:
Code:Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Tue Jan 26 16:13:00.064 2010 (GMT-5) System Uptime: 0 days 7:45:54.718 BugCheck 3B, {c0000005, fffff88003bc1507, fffff880054cdbf0, 0} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: Fallout3.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Wed Jan 27 02:18:51.824 2010 (GMT-5) System Uptime: 0 days 9:07:41.478 BugCheck 50, {fffff88009106010, 0, fffff88003b87cee, 2} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Thu Jan 28 03:26:44.362 2010 (GMT-5) System Uptime: 0 days 19:24:54.892 BugCheck 10E, {1f, fffff8a00a9fe5f0, 0, 326f84} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Thu Jan 28 23:51:47.347 2010 (GMT-5) System Uptime: 0 days 11:40:00.002 BugCheck 109, {a3a039d89767a899, 0, 3cee2079b59f222a, 101} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Fri Jan 29 11:41:58.347 2010 (GMT-5) System Uptime: 0 days 2:34:14.002 BugCheck A, {fffffa0000a987a0, 2, 0, fffff80002c8a055} Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+1d5 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Fri Jan 29 22:55:40.647 2010 (GMT-5) System Uptime: 0 days 10:19:39.176 BugCheck 50, {fffffa804d70746c, 0, fffff88003b58944, 5} Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCheckGPUTimeout+0 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Fri Jan 29 23:09:07.586 2010 (GMT-5) System Uptime: 0 days 0:12:27.240 BugCheck BE, {fffff9600012d2e0, 24a000010a5ba021, fffff880083717c0, b} Probably caused by : win32k.sys ( win32k!HMFreeObject+6c ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: java.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sat Jan 30 01:07:50.503 2010 (GMT-5) System Uptime: 0 days 0:41:55.157 BugCheck 50, {fffffa0003d3f6e8, 0, fffff8800ff94a9c, 7} *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+e1a9c ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: Fallout3.exe
I'm curious. Like spacelord, when I ran his dumps, the Crash Analizer of DaRT couldn't find the problem. What analyzer are you using?
Okay, I ran the Furmark. Benchmarked around 3600. During stress test I let it run for about 5 minutes. The temperature got up to 75c and then leveled off. (I didn't turn on the "Xtreme burning mode," however).
During all of this my computer seemed to run in stride, and I encountered no errors. Not sure if there was something else you wanted me to do with it.
I am also now installing the driver update. I haven't yet had any BSOD since my first posting here, but then again I haven't had a chance to play any games.
The system seems fine for listening to music, surfing the web, email, etc. And I haven't had any more restarts with OpenOffice yet (had only one).
Last edited by spacelord; 31 Jan 2010 at 11:58. Reason: Added info.
SM
John uses windb and bluescreenview among others.
WINDB is here http://www.microsoft.com/whdc/DevToo...ebugstart.mspx
The only error I have noticed in the Event Viewer currently is:
Log Name: System
Source: Microsoft-Windows-Wininit
Date: 1/31/2010 10:52:53 AM
Event ID: 11
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: Toby-PC
Description:
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206F6DEA-D3C5-4D10-BC72-989F03C8B84B}" />
<EventID>11</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2010-01-31T16:52:53.405385400Z" />
<EventRecordID>7236</EventRecordID>
<Correlation />
<Execution ProcessID="452" ThreadID="468" />
<Channel>System</Channel>
<Computer>Toby-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="StringCount">0</Data>
<Data Name="String">
</Data>
</EventData>
</Event>
I'm not really sure what this is, how to correct it, or if it is related to the problem at hand.
Just had another Blue Screen while logging off a user account. Attaching dump in case anyone wants to help with it.
Thanks.
windows debugger came up with0x4a (0x7536385e, 0x2, 0x0, 0xfffffa600a475ca0), with the probable cause listed as ntkrnlmp.exe - the NT Kernel.*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4A, {7732021a, 2, 0, fffff880068e1c60}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
Followup: MachineOwner
---------
0x4a = IRQL_GT_ZERO_AT_SYSTEM_SERVICE = a driver (called by system) but i doubt ntkrnlmp.exe was the actual cause here ......
I reckon running driver verifier might be a good idea here but I am not prepared to guide you through it as I am not familiar enough with it's use .............
Quote