Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSoD Volgrx.sys

18 Feb 2014   #1
raixik

W7 Home Premium 32bit
 
 
BSoD Volgrx.sys

Hey

I just started getting BSods on my Dell Vostro 3500, OS w7 home premium 32bit. Attached SF diagnostic tools zip.

Regards


My System SpecsSystem Spec
.
18 Feb 2014   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Welcome to the forum.

Post screenshot(s) of your Hard Drive(s) using Crystal Disk Info Software: CrystalDiskInfo - Software - Crystal Dew World

Run a Hard Drive test: http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html


Run Disk Check on your Hard Drive(s): Disk Check

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Usra\Downloads\SF_18-02-2014\021814-8502-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 x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0x82e0b000 PsLoadedModuleList = 0x82f544d0
Debug session time: Tue Feb 18 16:39:50.292 2014 (UTC + 6:00)
System Uptime: 0 days 2:33:04.557
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {c0457b80, c00000c0, 3d83b860, 8af70000}

GetPointerFromAddress: unable to read from 82f74834
Probably caused by : memory_corruption

Followup: memory_corruption
---------


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


Loading Dump File [C:\Users\Usra\Downloads\SF_18-02-2014\021814-9438-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 x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0x82e03000 PsLoadedModuleList = 0x82f4c4d0
Debug session time: Tue Feb 18 14:05:12.904 2014 (UTC + 6:00)
System Uptime: 1 days 1:49:13.556
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
............................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {c05b9218, c000000e, 2180be0, b7243000}

Probably caused by : memory_corruption ( nt!MiWaitForInPageComplete+302 )

Followup: MachineOwner
---------
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
Quote:
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
information   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Do this test overnight, before going to bed.
My System SpecsSystem Spec
20 Feb 2014   #3
raixik

W7 Home Premium 32bit
 
 

Thank you for the quick reply. Attached CrystalDisk screen.
SeaTools: Short DST - pass; Long generic - pass; Short generic - pass; SMART - pass
Neither Kaspersky nor ESET found anything and according to CHKDSK the disk is clean ( no errors ).
Memetest yet to run
My System SpecsSystem Spec
.

20 Feb 2014   #4
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Thanks. Keep us updated.
My System SpecsSystem Spec
25 Feb 2014   #5
raixik

W7 Home Premium 32bit
 
 

Did a clean reinstall to windows, still bsods. Will run memtest tonight but woulod appreciate if someone checked the dump files if anything changed.
My System SpecsSystem Spec
25 Feb 2014   #6
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Code:
Model	KINGSTON SVP200S37A120G ATA Device
I see that you have an SSD, is the firmware for it up to date?

If not, you should update it.

Also remove AVG and Glary Utilities for testing purpose.

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Use Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

Good and Free system security combination.

Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Usra\Downloads\SF_25-02-2014\SF_25-02-2014\022514-12012-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
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02a51000 PsLoadedModuleList = 0xfffff800`02c946d0
Debug session time: Tue Feb 25 14:00:47.382 2014 (UTC + 6:00)
System Uptime: 0 days 0:01:12.084
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8004e48b30, fffffa8004e48e10, fffff80002dcb7b0}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe

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

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8004e48b30, Terminating object
Arg3: fffffa8004e48e10, Process image file name
Arg4: fffff80002dcb7b0, Explanatory message (ascii)

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

----- ETW minidump data unavailable-----

PROCESS_OBJECT: fffffa8004e48b30

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0xF4_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`065700e8 fffff800`02e54ab2 : 00000000`000000f4 00000000`00000003 fffffa80`04e48b30 fffffa80`04e48e10 : nt!KeBugCheckEx
fffff880`065700f0 fffff800`02dffabb : ffffffff`ffffffff fffffa80`04f7d060 fffffa80`04e48b30 fffffa80`04e48b30 : nt!PspCatchCriticalBreak+0x92
fffff880`06570130 fffff800`02d7f674 : ffffffff`ffffffff 00000000`00000001 fffffa80`04e48b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`06570180 fffff800`02ac5e53 : fffffa80`04e48b30 fffff800`c0000005 fffffa80`04f7d060 00000000`026204c0 : nt!NtTerminateProcess+0xf4
fffff880`06570200 fffff800`02ac2410 : fffff800`02b1182f fffff880`06570b78 fffff880`065708d0 fffff880`06570c20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`06570398 fffff800`02b1182f : fffff880`06570b78 fffff880`065708d0 fffff880`06570c20 00000000`02621d00 : nt!KiServiceLinkage
fffff880`065703a0 fffff800`02ac6242 : fffff880`06570b78 00000000`00050a34 fffff880`06570c20 00000000`026217d8 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`06570a40 fffff800`02ac4dba : 00000000`00000001 00000000`02620a78 00000000`02627001 00000000`00050a34 : nt!KiExceptionDispatch+0xc2
fffff880`06570c20 00000000`76e68e5d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`02620a80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e68e5d


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_c0000005_IMAGE_wininit.exe

BUCKET_ID:  X64_0xF4_c0000005_IMAGE_wininit.exe

Followup: MachineOwner
---------
My System SpecsSystem Spec
Reply

 BSoD Volgrx.sys




Thread Tools Search this Thread
Search this Thread:

Advanced Search



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 21:24.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App