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: random BSOD HELP PLEASE

09 Dec 2010   #1

windows 7 Ultimate x64

ok i randomly get BSODs when i play games or leave my pc untouched for sometime
ive reinstalled all my drivers and reinstalled windows can some please help

Is Windows 7 . . .
- x86 (32-bit) or x64 ? 64bit
- the original installed OS on the system? yes
- an OEM or full retail version? Full retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)?1week-2years
- What is the age of OS installation (have you re-installed the OS?) 12 hours

My System SpecsSystem Spec
09 Dec 2010   #2

Windows 7 Ultimate 32 bit

Both of your dumps indicate memory corruption and neither point to a specific cause.
Error code BE, ATTEMPTED_WRITE_TO_READONLY_MEMORY. Usual causes: Device driver, Memory.

Error code 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control.
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a0e000 PsLoadedModuleList = 0xfffff800`02c4be50
Debug session time: Thu Dec  9 00:58:55.941 2010 (GMT-5)
System Uptime: 0 days 0:16:45.987
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck BE, {fffff8800186fafc, 1282a9121, fffff8800641b620, b}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4244e )

Followup: MachineOwner

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

An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arg1: fffff8800186fafc, Virtual address for the attempted write.
Arg2: 00000001282a9121, PTE contents.
Arg3: fffff8800641b620, (reserved)
Arg4: 000000000000000b, (reserved)

Debugging Details:






TRAP_FRAME:  fffff8800641b620 -- (.trap 0xfffff8800641b620)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800186fa70 rbx=0000000000000000 rcx=fffff8800186fad0
rdx=fffff8a00186f980 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880012b3933 rsp=fffff8800641b7b0 rbp=fffff8800641ba80
 r8=0000000000000000  r9=0000000000000001 r10=fffff8800641b840
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffff880`012b3933 f001b08c000000  lock add dword ptr [rax+8Ch],esi ds:fffff880`0186fafc=483d7510
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002afedb2 to fffff80002a7ff00

fffff880`0641b4b8 fffff800`02afedb2 : 00000000`000000be fffff880`0186fafc 00000001`282a9121 fffff880`0641b620 : nt!KeBugCheckEx
fffff880`0641b4c0 fffff800`02a7dfee : 00000000`00000001 00000000`00000000 fffff8a0`01871c00 fffff980`03fe5630 : nt! ?? ::FNODOBFM::`string'+0x4244e
fffff880`0641b620 fffff880`012b3933 : 00000000`00000000 fffff880`0641ba80 00000000`00000001 fffffa80`03a7c010 : nt!KiPageFault+0x16e
fffff880`0641b7b0 fffff880`01304bbd : fffffa80`03a7c010 fffffa80`04a49180 00000000`00000001 0000000f`ffffff00 : Ntfs!NtfsFlushVolume+0x213
fffff880`0641b8e0 fffff880`013055f0 : fffffa80`03a7c010 fffffa80`04055910 fffffa80`04bab510 00000000`00000000 : Ntfs!NtfsCommonFlushBuffers+0x459
fffff880`0641b9c0 fffff880`0104323f : fffffa80`04055cb0 fffffa80`04055910 fffffa80`03a7c010 fffff880`0641b9e8 : Ntfs!NtfsFsdFlushBuffers+0x104
fffff880`0641ba30 fffff880`010416df : fffffa80`04947950 00000000`00000000 fffffa80`04947900 fffffa80`04055910 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0641bac0 fffff800`02d93929 : 00000000`00000002 fffffa80`04bab510 00000000`00000000 fffffa80`04055910 : fltmgr!FltpDispatch+0xcf
fffff880`0641bb20 fffff800`02d218ad : fffffa80`04055910 fffffa80`044bf870 fffffa80`04bab510 fffff880`02f63180 : nt!IopSynchronousServiceTail+0xf9
fffff880`0641bb90 fffff800`02a7f153 : fffffa80`044bf870 00000000`ffcd2270 fffffa80`04947950 fffffa80`04bab510 : nt!NtFlushBuffersFile+0x171
fffff880`0641bc20 00000000`76d2036a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0287f7c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d2036a


nt! ?? ::FNODOBFM::`string'+4244e
fffff800`02afedb2 cc              int     3


SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4244e

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  ntkrnlmp.exe


FAILURE_BUCKET_ID:  X64_0xBE_nt!_??_::FNODOBFM::_string_+4244e

BUCKET_ID:  X64_0xBE_nt!_??_::FNODOBFM::_string_+4244e

Followup: MachineOwner

Debug session time: Thu Dec  9 13:21:03.799 2010 (GMT-5)
System Uptime: 0 days 0:14:05.845
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
0: kd> !Analyze
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffff80000003, fffff88003fdb365, fffff88004bf5608, fffff88004bf4e70}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption

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

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
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff88003fdb365, The address that the exception occurred at
Arg3: fffff88004bf5608, Exception Record Address
Arg4: fffff88004bf4e70, Context Record Address

Debugging Details:

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

fffff880`03fdb365 cc              int     3

EXCEPTION_RECORD:  fffff88004bf5608 -- (.exr 0xfffff88004bf5608)
ExceptionAddress: fffff88003fdb365 (dxgmms1!VIDMM_GLOBAL::FindResourcesForOneAllocation+0x0000000000000249)
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 1
   Parameter[0]: 0000000000000000

CONTEXT:  fffff88004bf4e70 -- (.cxr 0xfffff88004bf4e70)
rax=fffff8a009073840 rbx=fffff8a00908ae50 rcx=fffff88004bf58a8
rdx=0000000000000000 rsi=00000000c0000001 rdi=fffffa8006188004
rip=fffff88003fdb365 rsp=fffff88004bf5848 rbp=fffff88003fce550
 r8=0000000000000001  r9=0000000000000000 r10=fffff8a00917e000
r11=0000000000000006 r12=0000000000000000 r13=0000000000000000
r14=fffffa8003eee110 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202
fffff880`03fdb365 cc              int     3
Resetting default scope






ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_PARAMETER1:  0000000000000000

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88003fdb365

fffff880`04bf5848 00000000`00000000 : fffff880`03fd827c 00000000`00000016 00000000`00000000 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::FindResourcesForOneAllocation+0x249

CHKIMG_EXTENSION: !chkimg -lo 50 -db !dxgmms1
6 errors : !dxgmms1 (fffff88003fdb344-fffff88003fdbf54)
fffff88003fdb340  d0  00  00  00 *68  8d  8c  24  c8  00  00  00  48  8b  40  08 ....h..$....H.@.
fffff88003fdb350  48  89  4c  24 *60  48  8d  4c  24  60  48  89  4c  24  38  89 H.L$`H.L$`H.L$8.
fffff88003fdb360  54  24  30  45 *ab  cc  48  8b  d3  48  8b  cf  48  89  6c  24 T$0E..H..H..H.l$
fffff88003fdbec0  a8  00  00  00 *6c  8b  94  24  c0  00  00  00  45  33  ff  48 ....l..$....E3.H
fffff88003fdbf40  f1  fe  ff  bf *20  01  1e  c0  83  78  08  00  74  30  4d  85 .... ....x..t0M.
fffff88003fdbf50  d2  74  18  49 *ab  44  24  10  44  8b  c3  49  8b  ca  8b  90 .t.I.D$.D..I....

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption



STACK_COMMAND:  .cxr 0xfffff88004bf4e70 ; kb



Followup: memory_corruption
I suspect this is a driver issue. Outdated drivers can cause memory corruption and BSOD's. You have two outdated drivers and both of these are known to cause problems with Win 7 systems. One is an XP driver, really obsolete. Uninstall the software these drivers are associated with.
gdrv.sys Thu Mar 12 23:22:29 2009 - uninstall Gigabyte's Easy Saver program, as it is known to cause BSODs.

GVTDrv64.sys Tue Sep 05 03:10:02 2006 - Gigabyte EasyTune6 driver (known issues w/Win7) GIGABYTE - Support & Downloads - Utility - Motherboard.
Uninstall Easy Saver and Easy Tune, reboot and run your system. Let's see if you get anymore BSOD's. If you do, upload the dumps. Post back and let us know how your system is doing.
My System SpecsSystem Spec


Thread Tools

Similar help and support threads
Thread Forum
Random BSOD problems in the past 2 days. Random errors at random times
Three days ago my water cooling failed (got up to 77C while gaming is when I noticed the problem as my CPU should not go over 62C). I decided to install an aftermarket heatsink instead of a new water cooling system ,and add a few more fans just to make sure my whole motherboard was getting plenty...
BSOD Help and Support
BSOD at seemingly random times, memory dump blaming random drivers
I've been plagued by odd problems since making this custom build about a month ago, but the latest is the increasing frequency of BSODs. They never occur at load (gaming with high end specs), but often occur at shutdown (forcing a restart before I can then actually shut down). I normally boot into...
BSOD Help and Support
Random BSOD at random moments on Toshiba L500 laptop; graphics card?
My GF has had a Toshiba L500 laptop for 4 years now. It's a great model and it worked well...till now. It started about two weeks ago, with 1 blue screen every 1-2 days. I haven't reinstalled her windows for about a year, so i figured that was the problem. Four days ago it started blue...
BSOD Help and Support
Random BSOD with random error code at random moment
Hello Ok now i'm out of solution so i come here hoping that someone could help me I always had bsod hapening randomly but not like the this week I got 2 bsod/day when i'm playing, when i'm staring at my monitor or even when i'm sleeping with random error code like 0x1e, 0x24, 0x3b, 0x4a or 0xa...
BSOD Help and Support
BSOD doing random things (Google Chrome, minecraft, random times)
I have finally had it up to here with the BSODs, so I really need help. I ran a windows memtest and it detected no errors. I just finished updating to SP1 with pretty much most updates too. The BSODs I get the most are: Driver IRQL not less or Equal System Service Exception and these two I...
BSOD Help and Support

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 17:32.
Twitter Facebook Google+