Vista BSODs - help to troubleshoot

H

hazychris

New Member
Hi,

if anyone knowledgable would be able to help, I'd really appreciate some help!

I have a Dell Dimension 9200 (seemed like a good idea at the time) running Vista Home premium. I'm getting regular BSOD, and I'm at a loss how to find out the cause. Attached are 3 of the most recent minidumps, with extensions of .txt added to allow uploads.

BTW run memtest for 16 hours and no issues.

Thanks in advance for any help you can offer.

Cheers,
Chris
 

Attachments

  • Mini111908-01.dmp.txt
    136.4 KB · Views: 88
  • Mini112008-01.dmp.txt
    136.4 KB · Views: 74
  • Mini112008-02.dmp.txt
    136.4 KB · Views: 78
Last edited:

My Computer

System One

Hi Chris and welcome to Vista Forums :party:

Sorry, but those mini dumps don't make any sense to me. The information that we need is actually on the BSOD itself, specifically the STOP code which, in the example shown below, is 0x000000E2. This code, together with the other information given on the BSOD, can go a long way to helping us assist you with your problem, or at least point you in the right direction.
attachment.php

Image taken from P935 of Windows Vista Inside Out Deluxe Edition.
 

Attachments

  • Capture.JPG
    Capture.JPG
    90.2 KB · Views: 840

My Computer

System One

  • Manufacturer/Model
    Dwarf Dwf/11/2012 r09/2013
    CPU
    Intel Core-i5-3570K 4-core @ 3.4GHz (Ivy Bridge) (OC 4.2GHz)
    Motherboard
    ASRock Z77 Extreme4-M
    Memory
    4 x 4GB DDR3-1600 Corsair Vengeance CMZ8GX3M2A1600C9B (16GB)
    Graphics Card(s)
    MSI GeForce GTX770 Gaming OC 2GB
    Sound Card
    Realtek High Definition on board solution (ALC 898)
    Monitor(s) Displays
    ViewSonic VA1912w Widescreen
    Screen Resolution
    1440x900
    Hard Drives
    OCZ Agility 3 120GB SATA III x2 (RAID 0)
    Samsung HD501LJ 500GB SATA II x2
    Hitachi HDS721010CLA332 1TB SATA II
    Iomega 1.5TB Ext USB 2.0
    WD 2.0TB Ext USB 3.0
    PSU
    XFX Pro Series 850W Semi-Modular
    Case
    Gigabyte IF233
    Cooling
    1 x 120mm Front Inlet 1 x 120mm Rear Exhaust
    Keyboard
    Microsoft Comfort Curve Keyboard 3000 (USB)
    Mouse
    Microsoft Comfort Mouse 3000 for Business (USB)
    Internet Speed
    NetGear DG834Gv3 ADSL Modem/Router (Ethernet) ~4.0 Mb/s (O2)
    Other Info
    Optical Drive: HL-DT-ST BD-RE BH10LS30 SATA Bluray
    Lexmark S305 Printer/Scanner/Copier (USB)
    WEI Score: 8.1/8.1/8.5/8.5/8.25
    Asus Eee PC 1011PX Netbook (Windows 7 x86 Starter)
Dwarf said:
Hi Chris and welcome to Vista Forums :party:

Sorry, but those mini dumps don't make any sense to me. The information that we need is actually on the BSOD itself, specifically the STOP code which, in the example shown below, is 0x000000E2. This code, together with the other information given on the BSOD, can go a long way to helping us assist you with your problem, or at least point you in the right direction.
Click to expand...

Hi Dwarf, thanks for replying.

I've run the minidump.dmp through the debugger and it comes out with the equivalent stop code of oxoooooo8e, highlighted in red / bold below:

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Chris\Desktop\Mini111908-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;C:\Windows\Symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Kernel base = 0x8243a000 PsLoadedModuleList = 0x82551c70
Debug session time: Wed Nov 19 19:13:17.546 2008 (GMT+0)
System Uptime: 0 days 0:56:19.333
Loading Kernel Symbols
............................................................................................................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 8261b6ef, b27837cc, 0}
Probably caused by : memory_corruption ( nt!MiRelocateImageAgain+38 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8261b6ef, The address that the exception occurred at
Arg3: b27837cc, Trap Frame
Arg4: 00000000
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!MiRelocateImageAgain+38
8261b6ef f00fba2800 lock bts dword ptr [eax],0
TRAP_FRAME: b27837cc -- (.trap 0xffffffffb27837cc)
ErrCode = 00000002
eax=0cce3c4c ebx=0cce3c4c ecx=86824c60 edx=54ec0003 esi=8758b008 edi=86824c60
eip=8261b6ef esp=b2783840 ebp=b2783854 iopl=0 nv up ei ng nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010296
nt!MiRelocateImageAgain+0x38:
8261b6ef f00fba2800 lock bts dword ptr [eax],0 ds:0023:0cce3c4c=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: FlashUtil10a.ex
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8267f1c6 to 8261b6ef
STACK_TEXT:
b2783854 8267f1c6 8758b008 00000000 00000000 nt!MiRelocateImageAgain+0x38
b2783968 826832d8 b27839bc 0000000d b2783a0c nt!MmCreateSection+0x51d
b27839dc 825fc452 b2783a4c 0000000d b2783a0c nt!NtCreateSection+0x177
b2783a54 825fc0b1 b2783b0c ab6f25b8 b2783a90 nt!PfSnGetSectionObject+0x1a4
b2783ae8 825fc72c 00783b0c 00000001 00000000 nt!PfSnPrefetchSections+0x1d3
b2783c64 826058b6 b25ad000 b2783c94 b2783ca0 nt!PfSnPrefetchScenario+0x13a
b2783cf8 8260551b 8263ba8b 86011468 b2783d50 nt!PfSnBeginAppLaunch+0x382
b2783d08 8263a34c 93f04e61 00000000 00000000 nt!PfProcessCreateNotification+0x65
b2783d50 82468a2e 00000000 777d9a78 00000001 nt!PspUserThreadStartup+0x116
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiRelocateImageAgain+38
8261b6ef f00fba2800 lock bts dword ptr [eax],0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiRelocateImageAgain+38
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7fa
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x8E_nt!MiRelocateImageAgain+38
BUCKET_ID: 0x8E_nt!MiRelocateImageAgain+38
Followup: MachineOwner
---------
​
Does this help to move the dicussion on?

Cheers,
Chris
 

My Computer

System One

You must log in or register to reply here.
Back
Top