BSOD after fresh install

Dave76 · 06 Mar 2012

It is still possible that your RAM may be indicated in the crashes.

Are you still using the USB wireless adapter?
What other USB devices are you using?
List them all.

You should get a PCI wireless card, those USB adapters can cause issues.

You had three crash dump files.

Code:

BUGCODE_USB_DRIVER (fe)
Usual causes:  USB device driver
This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is using a physical memory address that was not allocated by the USBport driver.
SYMBOL_NAME:  usbohci!OHCI_PollAsyncEndpoint+99
IMAGE_NAME:  usbohci.sys
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbohci!OHCI_PollAsyncEndpoint+99
-----------------------------------------------------------------------------------------------------------------------------------------------
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
Usual causes:  Device driver
This indicates that a pool header is corrupt.
FOLLOWUP_NAME:  Pool_corruption
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+cbb
----------------------------------------------------------------------------------------------------------------------------------------------
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
An attempt was made to execute an illegal instruction.
Usual causes:  System service, Device driver, graphics driver, ?memory
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
SYMBOL_NAME:  atikmdag+3af900
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_atikmdag.sys
MODULE_NAME: hardware

Let's give your CPU a voltage bump.
Is your CPU offset voltage still at 1.356v?
If it is let's bump that up a little, to 1.375v.
This should help with any crashes caused by low idle CPU voltage.

carlocgc · 09 Mar 2012

All RAM has been tested.

I am using wireless adapter again but it was still crashing when i was using a wired connection....

USB devices
Xbox 360 pad
Wifi Dongle
Wired keyboard and mouse

I tested with no pad, dongle and different keyboard and mouse. still crashing

BIOS returned to default a while ago as i was met with "Overclocking failed" warning on startup

I will change them back with the increase and see

Many thanks

carlocgc · 10 Mar 2012

never got chance to change BIOS as a crash on shut down has corrupted C: Drive.

computer tries to check disk for consistency on boot but fails "Due to recently installed service package"? and requests i system restore

boots in safe mode but system restore fails because i haven't checked the disk for errors which i cant do because it fails...

any ideas?

thanks

writhziden · 10 Mar 2012

Use Advanced Boot Options to select Repair Your Computer and get to the System Recovery Options. Then select the command prompt. Do the following:

chkdsk /r c:
chkdsk /r d:
chkdsk /r e:
chkdsk /r f:

.etc until you get the message that the volume could not be opened for direct access. For any drives that do not give the message:
Windows has checked the file system and found no problems
run chkdsk again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.

I realize you may only have one disk show up in Windows explorer, but you may have more than one disk through recovery options. This is because the system creates a hidden boot partition (which will be C: in recovery), you may have a recovery partition for your PC that is hidden (which will be D: in recovery), and you will have your primary Windows partition (which may be E: in recovery). A custom PC will likely have at least C: and D: to scan.

If you are unable to get to the Recovery Environment (RE) using the above steps, you will need a repair disc to reach the RE. You can create a repair disc on any Windows 7 64-bit system; it does not matter whether it is Home Premium, Professional, Ultimate, etc. as long as it is 64-bit. System Repair Disc - Create

carlocgc · 11 Mar 2012

thanks HDD recovered :) still crashing however

carlocgc · 22 Mar 2012

here are recent crashes. any help appreciated

writhziden · 22 Mar 2012

Have you checked if your hard disk is faulty? HD Diagnostic

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\carlogc\Windows_NT6_BSOD_jcgriff2\031612-21450-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c00000 PsLoadedModuleList = 0xfffff800`02e44650
Debug session time: Fri Mar 16 08:32:05.438 2012 (UTC - 6:00)
System Uptime: 0 days 1:03:55.983
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 3fa1001, 0, fffff70001080000}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Allocate+3dd )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 0000000003fa1001
Arg3: 0000000000000000
Arg4: fffff70001080000

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_41284

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002cd3817 to fffff80002c7cd40

STACK_TEXT:  
fffff880`0883b6c8 fffff800`02cd3817 : 00000000`0000001a 00000000`00041284 00000000`03fa1001 00000000`00000000 : nt!KeBugCheckEx
fffff880`0883b6d0 fffff800`02cae200 : fffff700`01080000 00000000`000000f3 fffff880`0883b858 00000000`0425ffff : nt! ?? ::FNODOBFM::`string'+0x4ac3
fffff880`0883b710 fffff800`02c694bf : fffffa80`00000000 00000000`0425ffff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x4e8
fffff880`0883b8d0 fffff800`02c7bfd3 : ffffffff`ffffffff fffff880`0883bbb0 fffff880`0883bc18 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0883b9d0 fffff800`02c78570 : fffff880`0535efd5 00000001`40002e40 fffffa80`08b0f220 fffff8a0`02c9f010 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0883bb68 fffff880`0535efd5 : 00000001`40002e40 fffffa80`08b0f220 fffff8a0`02c9f010 00000000`c0000017 : nt!KiServiceLinkage
fffff880`0883bb70 fffff880`0534a974 : 00000000`00000174 00000000`00300000 fffff8a0`02bee0d0 00000000`000007ff : dxgmms1!VIDMM_PROCESS_HEAP::Allocate+0x3dd
fffff880`0883bc10 fffff880`05344f38 : 00000000`00000000 00000000`00000000 fffffa80`0b9bf000 fffff8a0`02bee0d0 : dxgmms1!VIDMM_GLOBAL::OpenLocalAllocation+0x570
fffff880`0883bcb0 fffff880`0532baa7 : fffff8a0`0b2ca770 fffff8a0`02f45910 fffff880`0883be20 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::OpenOneAllocation+0x268
fffff880`0883bd90 fffff880`042d1469 : 00000000`00000000 fffff880`0883c260 00000000`00000000 fffff8a0`09c7f6a0 : dxgmms1!VidMmOpenAllocation+0xeb
fffff880`0883bde0 fffff880`042ca610 : fffff880`0883c048 fffff8a0`0b69d4e0 fffff880`0883c220 fffff880`0883c220 : dxgkrnl!DXGDEVICE::CreateVidMmAllocations<_DXGK_ALLOCATIONINFO>+0x291
fffff880`0883be70 fffff880`042cc2ef : fffff8a0`083b4000 fffff880`0883c4d0 00000000`00000000 fffff8a0`083b4000 : dxgkrnl!DXGDEVICE::CreateAllocation+0xca8
fffff880`0883c470 fffff880`042d24d5 : 00000000`00009000 00000000`00000001 00000000`00000000 00000000`00000004 : dxgkrnl!DXGDEVICE::CreateStandardAllocation+0x367
fffff880`0883c5d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgkCddEnable+0x3f9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_PROCESS_HEAP::Allocate+3dd
fffff880`0535efd5 493bed          cmp     rbp,r13

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS_HEAP::Allocate+3dd

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x1a_41284_dxgmms1!VIDMM_PROCESS_HEAP::Allocate+3dd

BUCKET_ID:  X64_0x1a_41284_dxgmms1!VIDMM_PROCESS_HEAP::Allocate+3dd

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

Crash points to DirectX/Graphics Card problems...

Try re-installing DirectX using the Download: DirectX Redist (June 2010) - Microsoft Download Center - Download Details and see how the system responds.

Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.
1. Download the latest drivers for your display card(s)
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Expand Display adapters
7. Do the following for each adapter (in case you have multiple display cards)
  - Right click the adapter
  - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
8. Restart your computer after uninstalling drivers for all display cards
9. Install the latest driver for the display cards once Windows starts
Alternatively:
1. Login as an adminstrative user
2. Download the latest drivers for your display card(s)
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Expand Display adapters
8. Do the following for each adapter (in case you have multiple display cards)
  - Right click the adapter
  - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  - 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 after uninstalling drivers for all display cards
10. Install the latest driver for the display cards once Windows starts

Hardware check:

Monitor temperatures during the following tests.

Use the following programs to monitor the temperatures.
- Real Temp is a good CPU temperature monitor.
- Speccy - System Information - Free Download will monitor all hardware temperatures.
- HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
- Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
- Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.

carlocgc · 02 Apr 2012

video driver and dx updated stress tests ran no errors.
need to check hd next
any help with these crashes appreciated some new ones this time :s

writhziden · 02 Apr 2012

Still getting memory corruption crashes... Hmmm... I saw that your wireless USB might have been to blame at one point. Let's try something new. Remove the wireless USB network adapter and use wired. Clean up all possible USB problems:

Start with USB Driver - General Fix for Problems to resolve the USB issues. Also, USB ports can sometimes enter a safe power state to protect the system from power surges due to USB devices. To reset the USB ports to a nominal power state:
1. Shut down and turn off the computer.
2. Unplug the computer from the wall or surge protector (then remove the battery if it is a
  laptop).
3. Hold down the power button for 30 seconds. This closes the circuit and ensures all
  power from components is drained to clear the software connections between the BIOS
  and hardware and clear any corruption in the temporary memory.
4. (If it is a laptop, plug the battery back into the laptop and then) Plug the computer back
  into the wall.
5. Turn it on to reinitialize the software connections between the BIOS and hardwarelist]

Also, your latest crashes pointed to hard disk errors again as well as memory. Have you had a chance to run the manufacturer's diagnostic of the hard drive to see if it may be faulty? Run Hitachi's Drive Fitness Test on your hard disk.

carlocgc · 04 Apr 2012

hd diagnostic ran no errors.

tried using wired connection still crashes.

did power reset as you suggest still crashes.

at my wits end with this lol any ideas i still believe its a hardware problem either motherboard or GPU.

GPU isnt on QVL for Mobo think that could be it? also i only have a 550w psu and this card is giant.
i have funds to make changes or get a repair place to have a look. any advice appreciated.

any suggestions for replacing gpu or psu or mobo? or anything at all. i fear ive exhausted all software updating and stress testing

was goin to buy a cheap ass gpu to test with next. if still crashes that will leave Mobo HDD and RAM as potential problems correct?

is this a good idea ?

many thanks

P.S. noticed lowering DRAM voltage to 1.45 brings about alot more USB and memory crashes.
bumped it up to 1.55 now its a bit more stable still crashing though.
dunno if its relevent

P.S.S. all other voltages set to default except RAM. most crashes are resetting BIOS at this point.