Solved Multiple BSOD Windows 7 Pro 64

erickva · May 25, 2011

Hi Guys,

I've been having BSOD on my new system bought 2 weeks ago. It is driving me crazy and I cannot figure out what is happening. Many random and different BSODs. If anyone can please help me.

Windows 7 Pro 64, 8gb ram, SSD 64gb, AMD x6 1100T

All drivers are updated to the lastest version.

It normally happens when the computer is idle and I am not here, only twice, including the last time I was working on the computer.

Thanks,
Erick

erickva · May 25, 2011

Hi,

I had 2 new BSODs since last post, the last one is DRIVER_IRQL_NOT_LESS_OR_EQUAL.
I appreciate any help.

Thank you

Dave76 · May 27, 2011

The debugger mentions STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory

You ran windows memory diagnostic with no errors, it's not a good memory test.

Run memtest86+ with all your RAM cards installed.
This tutorial will explain it:RAM - Test with Memtest86+

This needs to run for a full 7 passes, each test is important, best to run the test overnight.
If you get any errors you can stop the test.

D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80003177d5f, Address of the instruction which caused the bugcheck
Arg3: fffff8800a08d090, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
 
EXCEPTION_CODE: (NTSTATUS) [COLOR=black]0xc0000005 [/COLOR]- The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
nt!IoRemoveIoCompletion+9f
fffff800`03177d5f 8b4b10          mov     ecx,dword ptr [rbx+10h]
CONTEXT:  fffff8800a08d090 -- (.cxr 0xfffff8800a08d090)
rax=0000000000000000 rbx=0000000000000001 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000001 rdi=0000000000000000
rip=fffff80003177d5f rsp=fffff8800a08da70 rbp=fffff8800a08dca0
 r8=fffffa8008b8e0e8  r9=0000000000000000 r10=ffffffffffffffdf
r11=fffff880030a4100 r12=0000000000000000 r13=fffff8800a08db68
r14=000000000326ec98 r15=0000000074c02450
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
nt!IoRemoveIoCompletion+0x9f:
fffff800`03177d5f 8b4b10          mov     ecx,dword ptr [rbx+10h] ds:002b:00000000`00000011=????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff8000314bf75 to fffff80003177d5f
STACK_TEXT:  
fffff880`0a08da70 fffff800`0314bf75 : fffff880`00000000 fffff880`0a08db68 fffff880`0a08db60 00000000`0043b801 : nt!IoRemoveIoCompletion+0x9f
fffff880`0a08db00 fffff800`02e8ef93 : fffffa80`08c88060 00000000`0326ec68 fffff880`0a08dbc8 fffff800`032b4716 : nt!NtRemoveIoCompletion+0x145
fffff880`0a08dbb0 00000000`74c02e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0326ec48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74c02e09
 
FOLLOWUP_IP: 
nt!IoRemoveIoCompletion+9f
fffff800`03177d5f 8b4b10          mov     ecx,dword ptr [rbx+10h]
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!IoRemoveIoCompletion+9f
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b
STACK_COMMAND:  .cxr 0xfffff8800a08d090 ; kb
FAILURE_BUCKET_ID:  X64_0x3B_nt!IoRemoveIoCompletion+9f
BUCKET_ID:  X64_[COLOR=red]0x3B[/COLOR]_nt!IoRemoveIoCompletion+9f
Followup: MachineOwner
---------

This is an outdated driver from Gigabyte EasyTune6.
Uninstall this program it is known to cause crashes with win7.

Code:

 GVTDrv64 GVTDrv64.sys Tue Sep 05 15:10:02 2006

STOP 0x000000C2: BAD_POOL_CALLER
Usual causes: Device driver, ?Memory

Code:

Event[8826]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2011-05-18T12:17:40.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: TradingStation
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: [COLOR=red]0x000000c2 [/COLOR](0x0000000000000007, 0x0000000000001097, 0x0000000000000000, 0xfffffa80066d3130). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 051811-10639-01.

STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel

Code:

Event[10905]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2011-05-16T19:52:51.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: TradingStation
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001a (0x0000000000000403, 0xfffff68000043ff8, 0x96b0000029cce867, 0xfffff68000043fe8). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id

erickva · May 31, 2011

Few more BSODs

Hi Dave,

Thanks so much for the help.
Easy Tune 6 is now removed but I still have BSODs.

Also run a 12 hours 8 pass memory test and everything is fine with them.

I am sending the new attachments.

Thank you,
Erick

erickva · May 31, 2011

Hi,

After I sent this message I enabled Driver Verifier, as per instructions in another post and restarted computer.
As soon as I enter my password to login it crashed straight away.

I am attaching the crashes again with the new one.

Thanks,
Erick

erickva · May 31, 2011

Hi,

Before I went to bed this night I enabled Drivers Verifier and once again when I woke up it had crashed.

Here are the files, with the Verifier enabled.

Thanks,
Erick

Dave76 · Jun 1, 2011

D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Disable Driver Verifier.

Caused by memory mangement, post the info requested above.

STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
The MEMORY_MANAGEMENT bug check has a value of 0x0000001A. This indicates that a severe memory management error occurred.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[COLOR=red]MEMORY_MANAGEMENT (1a)[/COLOR]
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000411, The subtype of the bugcheck.
Arg2: fffff6fc00018d30
Arg3: 37100000031a6860
Arg4: fffff6fc00018d21
Debugging Details:
------------------
 
BUGCHECK_STR:  0x1a_411
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  wmpnetwk.exe
CURRENT_IRQL:  2
TRAP_FRAME:  fffff8800b487a10 -- (.trap 0xfffff8800b487a10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000266f610
rdx=00000000001f0003 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800031a6fe0 rsp=fffff8800b487ba8 rbp=fffff8800b487ca0
 r8=0000000000000000  r9=0000000000000000 r10=fffff800031a6fe0
r11=fffff80002ee0f78 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!NtCreateEvent:
fffff800`031a6fe0 48895c2408      mov     qword ptr [rsp+8],rbx ss:0018:fffff880`0b487bb0=fffffa80098b6430
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002ebe9ad to fffff80002ee1d00
STACK_TEXT:  
fffff880`0b4876b8 fffff800`02ebe9ad : 00000000`0000001a 00000000`00000411 fffff6fc`00018d30 37100000`031a6860 : nt!KeBugCheckEx
fffff880`0b4876c0 fffff800`02f13071 : 37100000`031a6860 fffff6fc`00018d30 0000007f`fffffff8 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x6061
fffff880`0b487710 fffff800`02eff84f : 00000000`00000000 37a00000`031ba860 fffff880`0b487898 fffff800`03114500 : nt!MiResolveTransitionFault+0x381
fffff880`0b4877a0 fffff800`02eefa2b : 00000000`000000d8 fffffa80`08ebdb30 fffffa80`08ebdb30 fffff800`02f0d890 : nt!MiDispatchFault+0x95f
fffff880`0b4878b0 fffff800`02edfe2e : 00000000`00000008 fffff800`031a6fe0 fffff800`03069300 fffffa80`098b6430 : nt!MmAccessFault+0xe1b
fffff880`0b487a10 fffff800`031a6fe0 : fffff800`02ee0f93 fffffa80`098b6430 00000000`0266f468 fffff880`0b487bc8 : nt!KiPageFault+0x16e
fffff880`0b487ba8 fffff800`02ee0f93 : fffffa80`098b6430 00000000`0266f468 fffff880`0b487bc8 fffffa80`00000000 : nt!NtCreateEvent
fffff880`0b487bb0 00000000`7745179a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0266f5c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7745179a
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+6061
fffff800`02ebe9ad cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+6061
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b
FAILURE_BUCKET_ID:  X64_0x1a_411_VRF_nt!_??_::FNODOBFM::_string_+6061
BUCKET_ID:  X64_0x1a_411_VRF_nt!_??_::FNODOBFM::_string_+6061
Followup: MachineOwner
---------

Are your two SSDs in RAID?

Attach the Perfmon report in your next post.

3. Run a System Health Report -
START | type perfmon /report - a viewer will appear | Click on "File" and "Save As" an HTML file (default file extension)

erickva · Jun 1, 2011

Hi Dave,

I post the CPUZ before, it is in the Files.zip

Do you want me to post again?

Thanks,
Erick

erickva · Jun 1, 2011

Anyway, here they are.
With a whole new lot of BSOD I got today

Verifier is Disabled.

Thanks heaps, Dave!

Dave76 · Jun 1, 2011

Much easier if you post them by this method, then they can be seen in the post, any one else trying to help can see them easily.

For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

erickva · Jun 1, 2011

Here they are:

View attachment 157632

View attachment 157633

View attachment 157634

View attachment 157635

Thanks

Dave76 · Jun 1, 2011

Good information.

Which motherboard version do you have?
Look on the lower left corner of your motherboard.

How do you like the Hybrid EFI?

There are a couple of issues with your RAM settings.
Even if your RAM passes memtest86+, doesn't mean that the RAM or RAM settings are not causing the crashes.

First, the frequency setting.

There is a known issue with AMD CPUs integrated memory controllers having problems running RAM at 1600 MHz and above.
VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's and RAM SPEEDS
Q&A for the topic VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's & RAM....

For testing purposes change the RAM frequency to 1333MHz (666MHz).

Second, when you have more than 4GB RAM, RAM cards 2GB or larger, you will usually need to adjust the settings to get it to run stable.

Have you been checking your temperatures?
Use Core Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

erickva · Jun 1, 2011

Hi Dave,

How do you know I have a Toyota Prius?

I have no idea of what Hybrid EFI is, just had a look Gigabyte website and not sure I can benefit from that as I only have 2 64Gb SSD.

I am not sure about the version, I will check the board as soon as I get home.

Thanks for the help.
Erick

Dave76 · Jun 1, 2011

Hi Erick,

From the CPUZ Mainboard snip, BIOS version FF.

GA-880GA-UD3H (rev. 3.1)

1.Update Hybrid EFI version
2. Support Turbo XHD function

The rev 2.0, 2.1, 2.2, BIOS versions are numbered F1 to F7 and don't mention the Hybrid EFI.

Versions 3.0 and 3.1 BIOS versions are numbered FB, FD, FE, FF.

DualBIOS™ 3TB+ HDD Support (Hybrid EFI Technology)

Hybrid EFI Technology combines the benefits of GIGABYTE's mature BIOS platform including stability and compatibility with 3rd party products with 3TB+ HDD support from EFI technology.
GIGABYTE DualBIOS™ is a patented technology that automatically recovers BIOS data when the main BIOS has crashed or failed. Featuring 2 physical BIOS ROMs integrated onboard, GIGABYTE DualBIOS™ allows quick and seamless recovery from BIOS damage or failure due to viruses or improper BIOS updating. In addition, GIGABYTE DualBIOS™ now supports 3TB+ (terabyte) hard drive booting without the need for partitioning, and enables more data storage on a single hard drive.

GIGABYTE Hybrid EFI Technology

Question 1: When will GIGABYTE introduce an EFI compatible BIOS for their motherboards?
Answer 1: GIGABYTE has already introduced Hybrid EFI Technology that is fully compliant with EFI aware operating systems. This BIOS is shipping now with all GIGABYTE P67 and H67 chipset motherboards, and we have started introducing this BIOS on motherboards using other chipsets with the intention of making is available on all GIGABYTE motherboards.

It's the BIOS version on your Gigabyte motherboard.
After you confirm the motherboard version D/L your motherboard manual from one of the links above, you will need this for reference.

erickva · Jun 2, 2011

Hi Dave,

Board version rev 3.0.

Voltages are:
CPU PLL 2.5
DRAM 1.51
DDR VTT 0.75
NB 1.2
NB/PCIe/PLL 1.8
I hope this is what you want.

Also changed the Memory to 1333Mhz:
View attachment 157676

It is pretty cold here CPU is 25C when Idle, I ran some quick tests with Prime95 and it went up to 42C.
I have also downloaded the board manual, just in case.
Anything else?

Cheers,
Erick

Dave76 · Jun 2, 2011

Change the 'Command Rate' to 2T. This will help stability.

Which slots do you have the RAM cards installed in?
You can count slot 1 as closest to the CPU, should be in slots 1&3.

In the BIOS post the CPU NB VID control voltage, that is the integrated memory controller voltage.
Default is 1.10v, increase it to 1.20v.

Run Prime95 torture test for two hours.
First open Core Temp to monitor CPU temperatures, don't go over 62 °C.
Open Prime95 and stop the test if it is running, in Advanced tab select 'Round off checking', in the Options tab select 'Torture Test...', in the window that opens select 'Blend', after 'Number of torture test threads to run' enter 6, then click OK to start the test.

AMD Phenom II X6 1100

erickva · Jun 4, 2011

Hi Dave,

You are a legend, I have not changed the command rate or run the CPU test yet, nor changed the voltage.
But reducing the memory frequency to 1333mhz stopped the crashes. It's been 3 days now that it is very stable. It used to crash few times a day!

Cheers,
Erick

Dave76 · Jun 4, 2011

That's good news.

If it's stable, your all set.
You might need to do those RAM setting adjustment if you have any more crashes.

Let us know if you have any questions or any more crashes.

Solved Multiple BSOD Windows 7 Pro 64

New member

My Computer

New member

My Computer

Endeavor to Persevere

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Endeavor to Persevere

My Computer

New member

My Computer

New member

My Computer

Endeavor to Persevere

My Computer

New member

My Computer

Endeavor to Persevere

My Computer

New member

My Computer

Endeavor to Persevere

My Computer

New member

My Computer

Endeavor to Persevere

My Computer

New member

My Computer

Endeavor to Persevere

My Computer