BSOD on New System

[spacelord]

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.

 

[seekermeister]

Here is a way for you to analyze that dump very easily:

http://www.sevenforums.com/crashes-debugging/59619-win7-bsod-help-needed.html

 

[spacelord]

Thanks for the quick reply. Here are the steps I have taken thus far:

1. I ran a scandsk /r as admin from command line. No problems found.
2. I ran TestMem86 overnight. No problems found.
3. I ran the Crash Analyzer. It was unable to find the cause of the problem.
4. I verified all drivers on the system with the Verifier.
5. I checked the core temperature. Doesn't seem unreasonably hot, but I have included a capture in case I'm wrong.

 

[usasma]

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:

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

 

[seekermeister]

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?

 

[spacelord]

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).

 

[zigzag3143]

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?

SM

John uses windb and bluescreenview among others.

WINDB is here http://www.microsoft.com/whdc/DevTools/Debugging/debugstart.mspx

 

[spacelord]

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.

 

[spacelord]

Just had another Blue Screen while logging off a user account. Attaching dump in case anyone wants to help with it.

Thanks.

 

[ickymay]

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 with

*******************************************************************************
* *
* 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 (0x7536385e, 0x2, 0x0, 0xfffffa600a475ca0), with the probable cause listed as ntkrnlmp.exe - the NT Kernel.

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 .............

 

[seekermeister]

Ran it in the Crash Analizer with the same results as before, then ran it in BlueScreenView, and this was the output:

013110-19640-01.dmp 1/31/2010 2:17:28 PM IRQL_GT_ZERO_AT_SYSTEM_SERVICE 0x0000004a 00000000`7732021a 00000000`00000002 00000000`00000000 fffff880`068e1c60 ntoskrnl.exe ntoskrnl.exe+71f00 x64

It's curious that this is a bit different than ickymay's results. I have no idea of which is more accurate, but it might be worth checking this out:

http://www.youtube.com/watch?v=j69K9H87j2s

 

[Capt.Jack Sparrow]

Just had another Blue Screen while logging off a user account. Attaching dump in case anyone wants to help with it.

Thanks.

Did a analysis on your Dump file interestingly the crash occurred with the process GSvr.exe it's a MB Utility DESA (Dynamic Energy Saver Advanced) Go to Gigabyte website and download the Latest version and install them. Since its a MB Utility is involved update your BIOS to the latest Firmware. If your Overclocking please stop it. If your have any Firewall / Antivirus uninstall it see whether that makes any difference.

Debugging Details:

PROCESS_NAME:  GSvr.exe
BUGCHECK_STR:  RAISED_IRQL_FAULT
FAULTING_IP: 
+66e8952f02cddd20
00000000`7732021a ??              ???
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff80002c74469 to fffff80002c74f00
STACK_TEXT:  
fffff880`068e1a98 fffff800`02c74469 : 00000000`0000004a 00000000`7732021a 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`068e1aa0 fffff800`02c743a0 : fffffa80`0597c060 fffff880`068e1c60 00000000`7efad000 fffffa80`00008000 : nt!KiBugCheckDispatch+0x69
fffff880`068e1be0 00000000`7732021a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`01dfe708 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7732021a
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KiSystemServiceExit+245
fffff800`02c743a0 4883ec50        sub     rsp,50h
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  nt!KiSystemServiceExit+245
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
FAILURE_BUCKET_ID:  X64_RAISED_IRQL_FAULT_GSvr.exe_nt!KiSystemServiceExit+245
BUCKET_ID:  X64_RAISED_IRQL_FAULT_GSvr.exe_nt!KiSystemServiceExit+245
Followup: MachineOwner

Hope this helps,
Captain

 

[spacelord]

Okay, getting a few different answers here...

I started with the Captain's advice, since it was rather simple.

I just uninstalled that Dynamic Energy Saver program. I wasn't entirely keen on it anyway, but it came on my MB disk when I built it, so...

I also turned off Prevx, the only malware monitoring I had.

I'm not overclocking. I'll look into flashing the BIOS.

 

[spacelord]

BIOS flashed successfully to newest version.

 

[Capt.Jack Sparrow]

BIOS flashed successfully to newest version.

Ok Good .. Now let it run see whether you having any crashes. Post us back if case of any issues.

Good Luck,
Captain

 

[spacelord]

Also, just to really get things down to the basics, I uninstalled my Nvidia drivers and let Windows 7 install its driver for my GPU. I have heard around that the latest Nvidia drivers are not terribly stable. *shrug*

I'm going to do a bit of gaming and see what happens here.

Thanks again for everyone's help!

 

[seekermeister]

Most often, I advise people to install the Nvidia driver, rather than the native one. With your comment, I just checked with Nvidia, and they released a newer version than I have installed, so I can't vouch for it.

 

[spacelord]

Most often, I advise people to install the Nvidia driver, rather than the native one. With your comment, I just checked with Nvidia, and they released a newer version than I have installed, so I can't vouch for it.

I know what you mean. I have always used Nvidia drivers before. But if things work, they work. I just played Fallout 3 for two hours without problem on the native driver, on the same graphics settings as before. If I run into any problems, then I'll try the second newest driver from Nvidia. Otherwise I'll just keep using my system as is.

I'll keep the forum posted on the status, that way if things get fixed then perhaps the info can help others.

 

[seekermeister]

It is possible that you may have some problems with the native driver outside of game use. If that happens, go back to Nvidia and find an older driver in their archive. At the moment, I'm using 195.62 without any issues.

 

[spacelord]

Arrgh. Just when I thought I was going to make it through a whole day without a BSOD.

I was reading a webpage and downloading a game from Windows Live when the blue screen and reboot occurred. I have attached the dump.

You know, I used Windows 2000/Linux before this and never had a system crash in 9 years...bleh.

Anyway, thanks for the help guys.
--------------------------------------------------
EDIT:
Nevermind. I just figured out that it was caused from Mass Effect installer hanging. So no need to check it out. BTW, I am unable to install Mass Effect. I click past the EULA and then the program closes. I have seen a lot of people with this problem online, but no one seems to have a solution to it. My friend has exact same operating system, but had no problems with it. *shrug*