Tech Support banner
Status
Not open for further replies.
1 - 20 of 39 Posts

·
Registered
Joined
·
18 Posts
Discussion Starter · #1 ·
· OS - Windows 7
· x86 (32-bit) or x64 ? - x64
· What was original installed OS on system - Windows 7
· Is the OS an OEM version or full retail version? - Full retail version
· Age of system(Hardware)? - 2 years
· Age of OS installation? Have you re-installed the OS? - 2 years, no re-install

· CPU: Intel Core i5-2500k
· Video Card: Asus HD 6570
· MotherBoard: Gigabyte Z68AP-D3
· Power Supply - Corsair Cx 600w

· System Manufacturer : Home built
 

Attachments

·
Administrator, Team Manager, Gaming, Team Manager,
Joined
·
54,105 Posts
The latest is dated Aug 20?

From the last 6 all are 1A memory management errors

Testing the ram is a logical starting place.
D/L Memtest+ > How to perform a MemTest86+ Test | Tech Support Forum

Code:
Debug session time: Tue Aug 20 12:51:06.900 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\082013-9110-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:21:57.117
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
BugCheck 1A, {41790, fffffa8005cd1020, ffff, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001A]MEMORY_MANAGEMENT (1a)[/url]
Bugcheck code 0000001A
Arguments: 
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8005cd1020
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  taskhost.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084
MaxSpeed:     3300
CurrentSpeed: 3309
BiosVersion = FB
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Aug 19 21:21:49.795 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\081913-9001-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 1:19:18.638
Probably caused by : win32k.sys ( win32k!SURFACE::Map+175 )
BugCheck 1A, {41790, fffffa8005ee3cc0, ffff, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001A]MEMORY_MANAGEMENT (1a)[/url]
Bugcheck code 0000001A
Arguments: 
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8005ee3cc0
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::Map+175
MaxSpeed:     3300
CurrentSpeed: 3309
BiosVersion = FB
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Aug 19 20:02:03.269 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\081913-9874-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 1:55:33.487
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
BugCheck 1A, {41790, fffffa8005fb6fe0, ffff, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001A]MEMORY_MANAGEMENT (1a)[/url]
Bugcheck code 0000001A
Arguments: 
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8005fb6fe0
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  taskhost.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084
MaxSpeed:     3300
CurrentSpeed: 3309
BiosVersion = FB
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Aug 19 18:05:57.699 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\081913-9500-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 2:32:08.542
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
BugCheck 1A, {41790, fffffa8005c54fa0, ffff, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001A]MEMORY_MANAGEMENT (1a)[/url]
Bugcheck code 0000001A
Arguments: 
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8005c54fa0
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084
MaxSpeed:     3300
CurrentSpeed: 3309
BiosVersion = FB
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Aug 19 15:32:53.231 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\081913-9672-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 3:11:45.449
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
BugCheck 1A, {41790, fffffa8005c2f5f0, ffff, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001A]MEMORY_MANAGEMENT (1a)[/url]
Bugcheck code 0000001A
Arguments: 
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8005c2f5f0
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084
MaxSpeed:     3300
CurrentSpeed: 3309
BiosVersion = FB
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Aug 19 12:20:13.496 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\081913-8814-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 1:46:07.714
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
BugCheck 1A, {41790, fffffa8005edb5c0, ffff, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001A]MEMORY_MANAGEMENT (1a)[/url]
Bugcheck code 0000001A
Arguments: 
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8005edb5c0
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  des2svr.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084
MaxSpeed:     3300
CurrentSpeed: 3309
BiosVersion = FB
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
 

·
Registered
Joined
·
67 Posts
If you haven't re-installed your OS over 2 years, i suggest to do that. Anyaway, when was the last time your system worked fine? if you remember maybe you should do a recovery to the latest date your system worked.
 

·
Administrator, Team Manager, Gaming, Team Manager,
Joined
·
54,105 Posts
That's good, it's what verifier is suppose to do flush out a bad driver.

Looks like it's the Gigabyte Easy Saver - mobo power utility driver gdrv.sys
If it were me I would uninstall it.
GIGABYTE - Motherboard - Socket 1155 - GA-Z68AP-D3 (rev. 1.0)

Turn verifier off running it safe mode defeats the purpose :)

Code:
Debug session time: Sun Sep 15 18:01:01.373 2013 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\091513-12916-01.dmp]
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
System Uptime: 0 days 0:00:20.606
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1809 )
BugCheck C4, {f6, e0, fffffa8009831680, fffff8800976e809}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000C4]DRIVER_VERIFIER_DETECTED_VIOLATION (c4)[/url]
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments: 
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000000e0, Handle value being referenced.
Arg3: fffffa8009831680, Address of the current process.
Arg4: fffff8800976e809, Address inside the driver that is performing the incorrect reference.
BUGCHECK_STR:  0xc4_f6
PROCESS_NAME:  RPMMgr.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_gdrv+1809
MaxSpeed:     3300
CurrentSpeed: 3309
BiosVersion = FB
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
 

·
Registered
Joined
·
18 Posts
Discussion Starter · #15 ·
I'm not sure if verifier was on or off, the last time I used it was when it started causing the BSOD and I had to return to the restore point. Is there a way to check?
 

Attachments

·
Registered
Joined
·
18 Posts
Discussion Starter · #17 ·
Verifier caused it to crash again, but while I was in safe mode getting the dump file I got another BSOD. I had the file from the verifier dump, but when I went back to try and get the most recent dump file I got another BSOD. I realized that it was happening every time I tried to access my C drive. Here is the dump file that the verifier caused, I wasn't able to get the other ones.
 

Attachments

·
Administrator, Team Manager, Gaming, Team Manager,
Joined
·
54,105 Posts
gdrv.sys is still the cause, it along with RPMMgr.exe(GIGABYTE Smart Recovery System Tray) are both named.

What programs from the Gigabyte disk do you have installed?

Code:
BugCheck C4, {f6, 13c, fffffa8009924970, fffff88008fb0809}

*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1809 )

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

0: kd> !analyze -v; !sysinfo cpuspeed; !sysinfo SMBIOS; lmtsmn; q
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 000000000000013c, Handle value being referenced.
Arg3: fffffa8009924970, Address of the current process.
Arg4: fffff88008fb0809, Address inside the driver that is performing the incorrect reference.

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


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  RPMMgr.exe

CURRENT_IRQL:  0
 
1 - 20 of 39 Posts
Status
Not open for further replies.
Top