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: Multiple BSODs


04 Jul 2010   #1

windows 7 x64
 
 
Multiple BSODs

I just put together a new computer and i have been getting a few BSOD, some when watching youtube, some when changing video details in games. Some which happens when i click something. I can play games with no problems.

Specs:
Gigabyte GA-P55A-UD3
1TB Samsung Spinpoint F3 HD103SJ
Intel Core i5 750, 2.66GHz
Corsair 4GB (2x2GB) Value Select DDR3 1333MHz
PowerColor Radeon HD5850 PCS+ 1GB
Creative Sound Blaster X-Fi Titanium Fatal1ty Pro
Noctua NH-U9B SE2
Corsair VX 550W 80+
Windows 7 Home Premium 64-bit OEM

My System SpecsSystem Spec
.

04 Jul 2010   #2

Microsoft Window 7 Professional 32 bit
 
 

Please upload your minidump so that someone can help u:
http://www.sevenforums.com/crash-loc...d-problem.html
My System SpecsSystem Spec
04 Jul 2010   #3

windows 7 x64
 
 

Sorry, i just edited it and added to my first post.
My System SpecsSystem Spec
.


04 Jul 2010   #4

Microsoft Window 7 Professional 32 bit
 
 

Quote:
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Usual causes: Device driver
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
STOP 0x0000001A: MEMORY_MANAGEMENT

Usual causes: Device driver, memory, kernel
Memory corruption was blamed in some dmp file. please download third party called memtestx86, burn it to CD using iso recorder: http://isorecorder.alexfeinman.com/W7.htm and let it run for at least 7 passes.

USBport.sys was blamed in one of the dmp file. I will give you generic tip to solve that. Please go to device manager, under usb list, uninstall every devices, then restart your machine.

Finally, run SFC system files check: SFC /SCANNOW Command - System File Checker

Code:
BugCheck D1, {568e1c8, 2, 0, fffff88004820f70}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_ProcessScatterGatherList+494 )

Followup: MachineOwner
---------
BugCheck A, {1d000be7530, 2, 1, fffff80002efca5f}

Probably caused by : win32k.sys ( win32k!memset+b0 )

Followup: MachineOwner
---------
BugCheck A, {8500000000, 2, 1, fffff80002f14fa2}

Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )

Followup: MachineOwner
---------
BugCheck 1A, {5003, fffff70001080000, 12df, 585015}

Probably caused by : win32k.sys ( win32k!memmove+d2 )

Followup: MachineOwner
---------
BugCheck A, {137000c22e38, 2, 1, fffff80002ea8274}

Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+1ca )

Followup: MachineOwner
---------
BugCheck A, {14c0008560f0, 2, 1, fffff80002efca5f}

Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )

Followup: MachineOwner
---------
Regard,

Tuan
My System SpecsSystem Spec
04 Jul 2010   #5

windows 7 x64
 
 

Running MTx86 now

Did a SFC test and I had no errors.
My System SpecsSystem Spec
04 Jul 2010   #6

windows 7 x64
 
 

Memtest86+ v4.10
Intel Core i5/i7 2665 Mhz
L1 Cache: 32K 88828 MB/s
L2 Cache: 256K 35063 MB/s
L3 Cache: 8192K 26126 MB/s
Memory : 4092M 11843 MB/s
Chipset : Core IMC (ECC : Disabled) / BCLK : 133 MHz
Settings : RAM : 666MHz (DDR3-1332) / CAS : 9-9-9-24 /Dual Channel
____________________________________________________________________

[Walltime_1:23:39] [Cached_4092m] [RsvdMem_8k] [MemMap_e820] [Cache_on] [ECC_off] [Test_Std] [Pass_2] [Error_3] [ECC Errs_0]
____________________________________________________________________

Tst - Pass - Failing Address - Good - Bad - Err-Bits - Count
____________________________________________________________________
7 - 1 - 0007deafd60 2014.6MB - 04c60d41 - 04c61d41 - 00001000 - 1
7 - 1 - 0007ea0fd60 2026.0MB - 060c6c94 - 060c7c94 - 00001000 - 2
2 - 2 - 0005f29fd20 1522.6MB - 00000000 - 00001000 - 00001000 - 3

Stopped the test at this point, guess i need to get new memory?

Thanks in advance!
My System SpecsSystem Spec
04 Jul 2010   #7

windows 7 x64
 
 

While watching video on youtube i get these BSODs, once the computer just restarted without any errors poping up.
My System SpecsSystem Spec
04 Jul 2010   #8

Windows 7 Ultimate 32 bit
 
 

Quote   Quote: Originally Posted by mahitto View Post
Memtest86+ v4.10
Intel Core i5/i7 2665 Mhz
L1 Cache: 32K 88828 MB/s
L2 Cache: 256K 35063 MB/s
L3 Cache: 8192K 26126 MB/s
Memory : 4092M 11843 MB/s
Chipset : Core IMC (ECC : Disabled) / BCLK : 133 MHz
Settings : RAM : 666MHz (DDR3-1332) / CAS : 9-9-9-24 /Dual Channel
____________________________________________________________________

[Walltime_1:23:39] [Cached_4092m] [RsvdMem_8k] [MemMap_e820] [Cache_on] [ECC_off] [Test_Std] [Pass_2] [Error_3] [ECC Errs_0]
____________________________________________________________________

Tst - Pass - Failing Address - Good - Bad - Err-Bits - Count
____________________________________________________________________
7 - 1 - 0007deafd60 2014.6MB - 04c60d41 - 04c61d41 - 00001000 - 1
7 - 1 - 0007ea0fd60 2026.0MB - 060c6c94 - 060c7c94 - 00001000 - 2
2 - 2 - 0005f29fd20 1522.6MB - 00000000 - 00001000 - 00001000 - 3

Stopped the test at this point, guess i need to get new memory?

Thanks in advance!
At this point, remove all of your RAM sticks but one. Run memtest on that stick for seven passes. If no errors are reported, place that stick in another slot and again run memtest. Repeat until you have tested that stick in each slot. Remove it and test the next stick in the same manner.

What you are doing by this is testing each stick individually to find which stick is bad and you are also testing your RAM slots for a bad slot.

Post your results.
My System SpecsSystem Spec
04 Jul 2010   #9

Windows 7 Ultimate 32 bit
 
 

All three of these dumps files show the same stop error code of A.
Quote:
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_DUMP2.zip\070510-16770-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e62000 PsLoadedModuleList = 0xfffff800`0309fe50
Debug session time: Sun Jul  4 20:49:16.349 2010 (GMT-4)
System Uptime: 0 days 2:28:35.396
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {194003533d10, 2, 1, fffff80002ef7a5f}

Probably caused by : win32k.sys ( win32k!memset+b0 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000194003533d10, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ef7a5f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310a0e0
 0000194003533d10 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReplenishPageSlist+100
fffff800`02ef7a5f f00fba6b1000    lock bts dword ptr [rbx+10h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  firefox.exe

TRAP_FRAME:  fffff8800aa88020 -- (.trap 0xfffff8800aa88020)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c4c00000 rbx=0000000000000000 rcx=fffff900c4fe6000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960000d3c10 rsp=fffff8800aa881b8 rbp=0000000000000001
 r8=0000000000000028  r9=000000000000a6c8 r10=000000000000007f
r11=0000000000000034 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
win32k!memset+0xb0:
fffff960`000d3c10 480fc311        movnti  qword ptr [rcx],rdx ds:0001:fffff900`c4fe6000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ed1b69 to fffff80002ed2600

STACK_TEXT:  
fffff880`0aa87868 fffff800`02ed1b69 : 00000000`0000000a 00001940`03533d10 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0aa87870 fffff800`02ed07e0 : fffff880`0aa87a10 00001940`03533d00 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0aa879b0 fffff800`02ef7a5f : fffff6fc`80626c90 00001f80`00000000 00000001`0e670002 fffffa80`01616c70 : nt!KiPageFault+0x260
fffff880`0aa87b40 fffff800`02ef7f8f : fffff800`0310c400 00000000`00000070 fffffa80`023c9d00 fffffa80`01e0ed00 : nt!MiReplenishPageSlist+0x100
fffff880`0aa87ba0 fffff800`02ef0197 : 00000000`00000002 fffff880`00000002 fffff880`0578fc00 00000000`00000000 : nt!MiRemoveAnyPage+0x24f
fffff880`0aa87cc0 fffff800`02eeeb82 : 00000000`00000001 fffff900`c4fe6000 fffff880`0aa88020 fffff6fc`80627f30 : nt!MiResolveDemandZeroFault+0x577
fffff880`0aa87db0 fffff800`02eecbd1 : 00000000`000a77d2 00000000`00000084 00000000`00000000 fffff960`0009e761 : nt!MiDispatchFault+0x8c2
fffff880`0aa87ec0 fffff800`02ed06ee : 00000000`00000001 fffff900`c4c00000 00000000`35316800 00000000`00681228 : nt!MmAccessFault+0x8f1
fffff880`0aa88020 fffff960`000d3c10 : fffff960`000c2a12 fffff900`c2014be0 00000000`00000000 fffff960`00206ffc : nt!KiPageFault+0x16e
fffff880`0aa881b8 fffff960`000c2a12 : fffff900`c2014be0 00000000`00000000 fffff960`00206ffc fffff960`000d4215 : win32k!memset+0xb0
fffff880`0aa881c0 fffff960`000c3f2b : 00000000`00000000 fffff880`0aa88360 00000000`00000001 fffff960`000c15e6 : win32k!AllocateObject+0xf2
fffff880`0aa88200 fffff960`0009b4a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SURFMEM::bCreateDIB+0x1fb
fffff880`0aa882f0 fffff960`0009b01e : 00000378`00000780 00000000`00000378 00000000`5b080f4c 00000000`00000780 : win32k!hsurfCreateCompatibleSurface+0x3bc
fffff880`0aa883c0 fffff800`02ed1853 : fffffa80`03ee3b60 fffff880`0aa88520 00000000`00000000 fffff900`c00bf010 : win32k!GreCreateCompatibleBitmap+0x26e
fffff880`0aa884a0 00000000`75482dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0013d0e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75482dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!memset+b0
fffff960`000d3c10 480fc311        movnti  qword ptr [rcx],rdx

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  win32k!memset+b0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bdc4376

FAILURE_BUCKET_ID:  X64_0xA_win32k!memset+b0

BUCKET_ID:  X64_0xA_win32k!memset+b0

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


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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_DUMP2.zip\070510-17238-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e03000 PsLoadedModuleList = 0xfffff800`03040e50
Debug session time: Sun Jul  4 20:53:41.087 2010 (GMT-4)
System Uptime: 0 days 0:03:19.133
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {140007c1cb0, 2, 1, fffff80002e98a5f}

Probably caused by : win32k.sys ( win32k!memset+b0 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000140007c1cb0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e98a5f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ab0e0
 00000140007c1cb0 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReplenishPageSlist+100
fffff800`02e98a5f f00fba6b1000    lock bts dword ptr [rbx+10h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  firefox.exe

TRAP_FRAME:  fffff8800a4a6020 -- (.trap 0xfffff8800a4a6020)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c4e00000 rbx=0000000000000000 rcx=fffff900c5492000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000153c10 rsp=fffff8800a4a61b8 rbp=0000000000000001
 r8=000000000000001c  r9=00000000000029cf r10=000000000000007f
r11=0000000000000034 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po nc
win32k!memset+0xb0:
fffff960`00153c10 480fc311        movnti  qword ptr [rcx],rdx ds:0001:fffff900`c5492000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e72b69 to fffff80002e73600

STACK_TEXT:  
fffff880`0a4a5868 fffff800`02e72b69 : 00000000`0000000a 00000140`007c1cb0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0a4a5870 fffff800`02e717e0 : fffffa80`007c47c0 00000140`007c1ca0 00000000`00000004 00000000`00000003 : nt!KiBugCheckDispatch+0x69
fffff880`0a4a59b0 fffff800`02e98a5f : fffff6fc`806281f8 00000580`00000000 fffff6fb`7e403140 00001f80`00da00e4 : nt!KiPageFault+0x260
fffff880`0a4a5b40 fffff800`02e98f8f : fffff800`030ad400 00000000`0000006e fffffa80`007caca0 fffffa80`007c94a0 : nt!MiReplenishPageSlist+0x100
fffff880`0a4a5ba0 fffff800`02e91197 : 00000000`00000002 fffff880`00000002 fffff880`053a9c00 00000000`00000000 : nt!MiRemoveAnyPage+0x24f
fffff880`0a4a5cc0 fffff800`02e8fb82 : 00000000`00000001 fffff900`c5492000 fffff880`0a4a6020 fffff6fc`8062a490 : nt!MiResolveDemandZeroFault+0x577
fffff880`0a4a5db0 fffff800`02e8dbd1 : 00000000`000a9ff8 fffff880`00daab7b fffff880`0a4a6448 fffff960`002627fb : nt!MiDispatchFault+0x8c2
fffff880`0a4a5ec0 fffff800`02e716ee : 00000000`00000001 fffff900`c4e00000 fffff880`0a4a6200 00000000`00000080 : nt!MmAccessFault+0x8f1
fffff880`0a4a6020 fffff960`00153c10 : fffff960`00142a12 fffff900`c1f13250 00000000`00000000 fffff960`00286ffc : nt!KiPageFault+0x16e
fffff880`0a4a61b8 fffff960`00142a12 : fffff900`c1f13250 00000000`00000000 fffff960`00286ffc fffff960`00154215 : win32k!memset+0xb0
fffff880`0a4a61c0 fffff960`00143f2b : 00000000`00000000 fffff880`0a4a6360 00000000`00000001 fffff960`001415e6 : win32k!AllocateObject+0xf2
fffff880`0a4a6200 fffff960`0011b4a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SURFMEM::bCreateDIB+0x1fb
fffff880`0a4a62f0 fffff960`0011b01e : 000003e3`0000076f 00000000`000003e3 00000000`01080030 00000000`0000076f : win32k!hsurfCreateCompatibleSurface+0x3bc
fffff880`0a4a63c0 fffff800`02e72853 : fffffa80`082a5b60 fffff880`0a4a6520 00000000`00000000 fffff900`c00bf010 : win32k!GreCreateCompatibleBitmap+0x26e
fffff880`0a4a64a0 00000000`74a92dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0012d258 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74a92dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!memset+b0
fffff960`00153c10 480fc311        movnti  qword ptr [rcx],rdx

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  win32k!memset+b0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bdc4376

FAILURE_BUCKET_ID:  X64_0xA_win32k!memset+b0

BUCKET_ID:  X64_0xA_win32k!memset+b0

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


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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_DUMP2.zip\070510-17565-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e0f000 PsLoadedModuleList = 0xfffff800`0304ce50
Debug session time: Sun Jul  4 21:00:06.289 2010 (GMT-4)
System Uptime: 0 days 0:01:44.725
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {12e0015d1ee8, 2, 1, fffff80002ea0274}

Probably caused by : win32k.sys ( win32k!memset+b0 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000012e0015d1ee8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ea0274, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b70e0
 000012e0015d1ee8 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiUnlinkFreeOrZeroedPage+1ca
fffff800`02ea0274 48893cc2        mov     qword ptr [rdx+rax*8],rdi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  firefox.exe

TRAP_FRAME:  fffff8800a4daee0 -- (.trap 0xfffff8800a4daee0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c4400000 rbx=0000000000000000 rcx=fffff900c47ab000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000193c10 rsp=fffff8800a4db078 rbp=0000000000000001
 r8=000000000000001c  r9=0000000000008489 r10=000000000000007f
r11=0000000000000034 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
win32k!memset+0xb0:
fffff960`00193c10 480fc311        movnti  qword ptr [rcx],rdx ds:0001:fffff900`c47ab000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e7eb69 to fffff80002e7f600

STACK_TEXT:  
fffff880`0a4da718 fffff800`02e7eb69 : 00000000`0000000a 000012e0`015d1ee8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0a4da720 fffff800`02e7d7e0 : 00000000`00000000 fffffa80`015d36e0 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0a4da860 fffff800`02ea0274 : fffffa80`015eb6b0 fffff800`02ea4c2e 00000000`00000210 00001f80`00000001 : nt!KiPageFault+0x260
fffff880`0a4da9f0 fffff800`02ea4f18 : fffff880`0a4daac0 00000000`0007467a fffffa80`015d36e0 fffffa80`015f5eb0 : nt!MiUnlinkFreeOrZeroedPage+0x1ca
fffff880`0a4daa60 fffff800`02e9d197 : 00000000`00000002 fffff880`00000002 fffff880`053a2c00 00000000`00000000 : nt!MiRemoveAnyPage+0x1d8
fffff880`0a4dab80 fffff800`02e9bb82 : 00000000`00000001 fffff900`c47ab000 fffff880`0a4daee0 fffff6fc`80623d58 : nt!MiResolveDemandZeroFault+0x577
fffff880`0a4dac70 fffff800`02e99bd1 : 00000000`000b3a71 fffff900`c4533000 00000000`00000000 00000000`0000001c : nt!MiDispatchFault+0x8c2
fffff880`0a4dad80 fffff800`02e7d6ee : 00000000`00000001 fffff900`c4400000 fffff880`0a4db500 fffff900`c0835cb0 : nt!MmAccessFault+0x8f1
fffff880`0a4daee0 fffff960`00193c10 : fffff960`00182a12 fffff900`c297df20 00000000`00000000 fffff960`002c6ffc : nt!KiPageFault+0x16e
fffff880`0a4db078 fffff960`00182a12 : fffff900`c297df20 00000000`00000000 fffff960`002c6ffc fffff960`00194215 : win32k!memset+0xb0
fffff880`0a4db080 fffff960`00183f2b : 00000000`00000000 fffff880`0a4db220 00000000`00000001 fffff960`001815e6 : win32k!AllocateObject+0xf2
fffff880`0a4db0c0 fffff960`0015b4a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SURFMEM::bCreateDIB+0x1fb
fffff880`0a4db1b0 fffff960`0015b01e : 000003dd`000005f1 00000000`000003dd 00000000`01080030 00000000`000005f1 : win32k!hsurfCreateCompatibleSurface+0x3bc
fffff880`0a4db280 fffff800`02e7e853 : fffffa80`0844a9a0 fffff880`0a4db3e0 00000000`00000000 fffff900`c00bf010 : win32k!GreCreateCompatibleBitmap+0x26e
fffff880`0a4db360 00000000`75072dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0016ccb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75072dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!memset+b0
fffff960`00193c10 480fc311        movnti  qword ptr [rcx],rdx

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  win32k!memset+b0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bdc4376

FAILURE_BUCKET_ID:  X64_0xA_win32k!memset+b0

BUCKET_ID:  X64_0xA_win32k!memset+b0

Followup: MachineOwner
---------
These don't give us much specific information. I will dig a little deeper and edit this post. Be back in a few minutes.

I see you are running ESet NOD on your system. For the purposes of troubleshooting, I suggest you uninstall it using this removal tool >Info > Tool I recommend that you install MSE for your antivirus and make sure Windows Firewall is turned on.

Many third party anti-malware programs, especially suites, can cause conflicts and BSOD's on some Win 7 systems. MSE, a Microsoft product, will not cause conflicts. We just need to eliminate ESet as a cause. You can reinstall ESet after you get your system running smoothly although I recommend staying with MSE.

I also find the following outdated drivers on your system:
Quote:
gdrv.sys Thu Mar 12 23:22:29 2009 (49B9D175)
LHidFilt.Sys Wed Jun 17 12:49:39 2009 (4A391EA3)
LUsbFilt.Sys Wed Jun 17 12:49:46 2009 (4A391EAA)
Outdated drivers can be a cause of BSOD's. I suggest you update these drivers to eliminate them as potential conflicts. Go to the manufactures sites and search for updated drivers. Download these and install them.

gdrv.sys - gdrv.sys is a component of Dynamic Energy Saver Advanced. Update this driver or uninstall the software. Personally, I would recommend uninstalling the software and use Windows' built in energy saving program.

LHidFilt.Sys and LUsbFilt.Sys - both of these are Logitech mouse drivers. See if you can update both of these. Downloads
My System SpecsSystem Spec
04 Jul 2010   #10

windows 7 x64
 
 

LHidFilt.Sys and LUsbFilt.Sys are updated succesfully

The energy saver is a part of Easy tune which i haventh installed, so i installed it and removed it. The driver was updated trough that but wasnt deleted after i uninstalled ET again. Dunno if that was the right way to do this but i couldnt find that program anywhere on my computer.

Will remove eset and test the memory sticks one at the time in each slot. Thanks alot, I let you know what happens.
My System SpecsSystem Spec
Reply

 Multiple BSODs




Thread Tools



Similar help and support threads for2: Multiple BSODs
Thread Forum
Multiple BSODS BSOD Help and Support
Multiple BSODs, Random Occurences, Multiple Error Codes BSOD Help and Support
Multiple BSODs, multiple BCCodes, does not happen in safe mode. BSOD Help and Support
Solved Multiple BSODs on new PC BSOD Help and Support
multiple BSODs in a day now :( BSOD Help and Support
Multiple BSODs BSOD Help and Support
Multiple and various BSoDs 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 08:04 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33