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: "memory_corruption" BSOD out of nowhere.

22 Mar 2012   #1
gnomefar

Windows 7 Home x64
 
 
"memory_corruption" BSOD out of nowhere.

Hi.

My Asus n53sn laptop have started acting weird.
Ive been having a couple of different BSOD's, but only One made a .dump file.

Some weeks ago i ofen had BSOD. I wrote one of them down:
0x000000f4 (0x0000000000000003, 0xfffffa800bceeb30, 0xfffffa800bceee10, 0xfffff800033e58b0)

Yesterday i got a new one, which made a .dump file.
I opened it with Windbg and it looked like this:


Loading Dump File [C:\Users\Gnomefar\Desktop\032212-30076-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
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03053000 PsLoadedModuleList = 0xfffff800`03297650
Debug session time: Thu Mar 22 10:55:36.429 2012 (UTC + 1:00)
System Uptime: 0 days 0:48:14.335
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa8007078b60, fffff80000b9c3d0}

*** 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 *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8007078b60, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c3d0

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


DRVPOWERSTATE_SUBCODE: 4

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAULTING_MODULE: fffff88000f4f000 pci

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffff880`0355abc0 fffff800`030c56c2 : fffffa80`07078b60 fffffa80`07078b60 00000000`00000000 00000000`0000000c : nt!KiSwapContext+0x7a
fffff880`0355ad00 fffff800`030d6baf : fffffa80`08139c30 fffffa80`08139c30 fffffa80`00000000 fffff880`0183900c : nt!KiCommitThreadWait+0x1d2
fffff880`0355ad90 fffff800`0312b706 : 00000000`00000000 fffffa80`00000000 fffff880`01996800 fffff880`01746200 : nt!KeWaitForSingleObject+0x19f
fffff880`0355ae30 fffff880`0184074d : 00000000`00000100 0000000c`00000003 00000000`00000000 ffffe4cd`40010023 : nt! ?? ::FNODOBFM::`string'+0x13186
fffff880`0355aea0 fffff880`0196c93e : 00000000`c00000bb 00000000`00000008 fffff880`0355b020 00000000`00000000 : tcpip!FlPnpEvent+0x17d
fffff880`0355af10 fffff880`0175bb2f : fffffa80`07fbed58 00000000`00000008 fffffa80`07fbe870 fffffa80`0772a1a0 : tcpip!Fl68PnpEvent+0xe
fffff880`0355af40 fffff880`0175c4b7 : fffffa80`0a240640 00000000`00000008 00000000`00000000 fffffa80`0a240640 : ndis!ndisPnPNotifyBinding+0xbf
fffff880`0355afd0 fffff880`017768f1 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`0c3844c0 : ndis!ndisPnPNotifyAllTransports+0x377
fffff880`0355b140 fffff880`01777c3b : 00000000`00000001 fffffa80`0772a1a0 fffffa80`07213020 fffffa80`0772a050 : ndis!ndisCloseMiniportBindings+0x111
fffff880`0355b250 fffff880`0170ee5a : fffffa80`0772a1a0 fffffa80`0772a1a0 fffffa80`075d25e0 fffff880`03389180 : ndis!ndisPnPRemoveDevice+0x25b
fffff880`0355b3f0 fffff880`0176b5b2 : 00000000`00000000 fffffa80`0772a1a0 fffffa80`075d25e0 00000000`00000002 : ndis!ndisPnPRemoveDeviceEx+0xca
fffff880`0355b450 fffff880`00ea293c : 00000000`00000001 fffffa80`075d2740 fffffa80`07ccab60 00000000`00000000 : ndis! ?? ::LNCPHCLB::`string'+0x7363
fffff880`0355b4f0 fffff880`00e9b2ce : 00000000`00000001 fffff880`0355b600 fffff880`0355b600 fffffa80`07ccab00 : Wdf01000!FxPkgFdo::ProcessRemoveDeviceOverload+0x74
fffff880`0355b520 fffff880`00e99dd6 : fffffa80`09ef7e02 00000000`c00000bb 00000000`00000000 fffffa80`07ccab60 : Wdf01000!FxPkgPnp::_PnpRemoveDevice+0x126
fffff880`0355b590 fffff880`00e69245 : fffffa80`075d25e0 fffffa80`075d25e0 fffffa80`07c35040 fffffa80`07c35040 : Wdf01000!FxPkgPnp:ispatch+0x1b2
fffff880`0355b600 fffff880`00e6914b : 00000000`00000004 fffffa80`075d25e0 00000000`c00000bb fffffa80`07c35040 : Wdf01000!FxDevice:ispatch+0xa9
fffff880`0355b630 fffff800`03339ab9 : fffffa80`07c35040 00000000`c00000bb fffff880`0355b728 fffffa80`075d25e0 : Wdf01000!FxDevice:ispatchWithLock+0x93
fffff880`0355b670 fffff800`034b8161 : fffffa80`0d0617c0 00000000`00000000 fffffa80`07e49230 00000000`00000801 : nt!IopSynchronousCall+0xc5
fffff880`0355b6e0 fffff800`031cb863 : fffff8a0`04988f80 fffff8a0`04988f80 00000000`00000018 00000000`00000000 : nt!IopRemoveDevice+0x101
fffff880`0355b7a0 fffff800`034b7cb4 : fffffa80`07e49230 00000000`00000000 00000000`00000002 00000000`00000000 : nt!PnpRemoveLockedDeviceNode+0x1a3
fffff880`0355b7f0 fffff800`034b7dc0 : 00000000`00000000 fffffa80`0d061700 fffff8a0`0db862d0 fffff800`032cda60 : nt!PnpDeleteLockedDeviceNode+0x44
fffff880`0355b820 fffff800`034b7eb9 : fffffa80`0da25402 fffffa80`0da254a0 00000000`00000001 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`0355b890 fffff800`034b8031 : fffffa80`0da254a0 00000000`00000000 fffffa80`0da254a0 00000000`00000003 : nt!PnpDelayedRemoveWorker+0x79
fffff880`0355b8e0 fffff800`031cba89 : 00000000`00000002 fffffa80`07d0c7e0 00000000`00000001 00000000`00000001 : nt!PnpChainDereferenceComplete+0x131
fffff880`0355b920 fffff800`03549000 : 00000000`00000000 fffffa80`07e49200 fffff8a0`0d83f010 00000000`00000001 : nt!PnpIsChainDereferenced+0xc9
fffff880`0355b9a0 fffff800`0354929c : fffff880`0355bb78 fffffa80`0d095200 fffffa80`07078b00 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0xff0
fffff880`0355bae0 fffff800`0343256e : 00000000`00000000 fffffa80`0d095220 fffff8a0`0dd82010 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`0355bb10 fffff800`030d9471 : fffff800`03338958 fffff8a0`0d83f010 fffff800`0326f2b8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x5aeab
fffff880`0355bb70 fffff800`03369f7a : 00000000`00000000 fffffa80`07078b60 00000000`00000080 fffffa80`06fa1990 : nt!ExpWorkerThread+0x111
fffff880`0355bc00 fffff800`030c09c6 : fffff880`03389180 fffffa80`07078b60 fffff880`033940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0355bc40 00000000`00000000 : fffff880`0355c000 fffff880`03556000 fffff880`0355a430 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff800030d2fb3 - nt!SwapContext_PatchXSave+2
[ 01:21 ]
1 error : !nt (fffff800030d2fb3)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

MEMORY_CORRUPTOR: ONE_BIT

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT

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


My Laptop have some problems with the network-card. Sometimes it can't "find it". (I think there is a loose connection to it), can this have something to do with the crashes?

I have BSOD, but i just cant figure out whats wrong.

- Gnomefar

Ps. im new inhere, so please say if i missed anything or you need more information or anything


My System SpecsSystem Spec
.
22 Mar 2012   #2
raf051888

Windows 7 64-bit
 
 

Did you try running Memtest?
My System SpecsSystem Spec
22 Mar 2012   #3
writhziden

Windows 7 Home Premium 64 Bit
 
 

While the Windbg analysis can be helpful, in most cases it is not. Yours points to memory corruption, but it could be a number of other causes, as well. Please follow the http://www.sevenforums.com/crashes-d...tructions.html to provide us with more information so we can give specific troubleshooting steps.
My System SpecsSystem Spec
.

23 Mar 2012   #4
gnomefar

Windows 7 Home x64
 
 

Yes, i did run a memtest and it found 0 problems.

Ive attached the .dump-file here:
Attachment 203978

Ive attached the system health report and Windows_NT6_BSOD_jcgriff2 files here:
Attachment 203979

I have Windows 7 Home edition x64
I bought this computer last summer, with Windows installed on it.
I have avast! anti-virus

Hope thats enough data ^^

- Gnomefar
My System SpecsSystem Spec
23 Mar 2012   #5
writhziden

Windows 7 Home Premium 64 Bit
 
 

Security Software:
Code:
avastsvc.exe	c:\program files\avast software\avast\avastsvc.exe	1360	8	200	1380	23-03-2012 06:43	6.0.1203.0	41,20 KB (42.184 byte)	25-08-2011 23:26
avastui.exe	c:\program files\avast software\avast\avastui.exe	4296	8	200	1380	23-03-2012 06:44	6.0.1203.0	3,33 MB (3.493.720 byte)	25-08-2011 23:26

Possible out of date drivers:
Code:
btwl2cap	fffff880`0db4f000	fffff880`0db5b000	Fri Apr 03 18:28:45 2009 (49d6a9bd)	00009866		btwl2cap.sys
LHidFilt	fffff880`03bae000	fffff880`03bc1000	Wed Jun 17 10:49:39 2009 (4a391ea3)	00014ede		LHidFilt.Sys
LMouFilt	fffff880`03bc1000	fffff880`03bd5000	Wed Jun 17 10:49:43 2009 (4a391ea7)	0001d7ff		LMouFilt.Sys
LEqdUsb	fffff880`03a9d000	fffff880`03ab4000	Wed Jun 17 10:49:54 2009 (4a391eb2)	00019cc3		LEqdUsb.Sys
LHidEqd	fffff880`03acf000	fffff880`03ad7000	Wed Jun 17 10:49:56 2009 (4a391eb4)	0000f0de		LHidEqd.Sys
ASMMAP64	fffff880`065f5000	fffff880`065fd000	Thu Jul 02 03:13:26 2009 (4a4c7a36)	0000ceab		ASMMAP64.sys
btwl2cap.sys
LHidFilt.Sys
LMouFilt.Sys
LEqdUsb.Sys
LHidEqd.Sys
ASMMAP64.sys


Code:
Loading Dump File [D:\Kingston\BSODDmpFiles\gnomefar\Windows_NT6_BSOD_jcgriff2\032212-30076-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03053000 PsLoadedModuleList = 0xfffff800`03297650
Debug session time: Thu Mar 22 03:55:36.429 2012 (UTC - 6:00)
System Uptime: 0 days 0:48:14.335
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa8007078b60, fffff80000b9c3d0}

*** 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                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8007078b60, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c3d0

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


DRVPOWERSTATE_SUBCODE:  4

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAULTING_MODULE: fffff88000f4f000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x9F

PROCESS_NAME:  Í

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0355abc0 fffff800`030c56c2 : fffffa80`07078b60 fffffa80`07078b60 00000000`00000000 00000000`0000000c : nt!KiSwapContext+0x7a
fffff880`0355ad00 fffff800`030d6baf : fffffa80`08139c30 fffffa80`08139c30 fffffa80`00000000 fffff880`0183900c : nt!KiCommitThreadWait+0x1d2
fffff880`0355ad90 fffff800`0312b706 : 00000000`00000000 fffffa80`00000000 fffff880`01996800 fffff880`01746200 : nt!KeWaitForSingleObject+0x19f
fffff880`0355ae30 fffff880`0184074d : 00000000`00000100 0000000c`00000003 00000000`00000000 ffffe4cd`40010023 : nt! ?? ::FNODOBFM::`string'+0x13186
fffff880`0355aea0 fffff880`0196c93e : 00000000`c00000bb 00000000`00000008 fffff880`0355b020 00000000`00000000 : tcpip!FlPnpEvent+0x17d
fffff880`0355af10 fffff880`0175bb2f : fffffa80`07fbed58 00000000`00000008 fffffa80`07fbe870 fffffa80`0772a1a0 : tcpip!Fl68PnpEvent+0xe
fffff880`0355af40 fffff880`0175c4b7 : fffffa80`0a240640 00000000`00000008 00000000`00000000 fffffa80`0a240640 : ndis!ndisPnPNotifyBinding+0xbf
fffff880`0355afd0 fffff880`017768f1 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`0c3844c0 : ndis!ndisPnPNotifyAllTransports+0x377
fffff880`0355b140 fffff880`01777c3b : 00000000`00000001 fffffa80`0772a1a0 fffffa80`07213020 fffffa80`0772a050 : ndis!ndisCloseMiniportBindings+0x111
fffff880`0355b250 fffff880`0170ee5a : fffffa80`0772a1a0 fffffa80`0772a1a0 fffffa80`075d25e0 fffff880`03389180 : ndis!ndisPnPRemoveDevice+0x25b
fffff880`0355b3f0 fffff880`0176b5b2 : 00000000`00000000 fffffa80`0772a1a0 fffffa80`075d25e0 00000000`00000002 : ndis!ndisPnPRemoveDeviceEx+0xca
fffff880`0355b450 fffff880`00ea293c : 00000000`00000001 fffffa80`075d2740 fffffa80`07ccab60 00000000`00000000 : ndis! ?? ::LNCPHCLB::`string'+0x7363
fffff880`0355b4f0 fffff880`00e9b2ce : 00000000`00000001 fffff880`0355b600 fffff880`0355b600 fffffa80`07ccab00 : Wdf01000!FxPkgFdo::ProcessRemoveDeviceOverload+0x74
fffff880`0355b520 fffff880`00e99dd6 : fffffa80`09ef7e02 00000000`c00000bb 00000000`00000000 fffffa80`07ccab60 : Wdf01000!FxPkgPnp::_PnpRemoveDevice+0x126
fffff880`0355b590 fffff880`00e69245 : fffffa80`075d25e0 fffffa80`075d25e0 fffffa80`07c35040 fffffa80`07c35040 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff880`0355b600 fffff880`00e6914b : 00000000`00000004 fffffa80`075d25e0 00000000`c00000bb fffffa80`07c35040 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`0355b630 fffff800`03339ab9 : fffffa80`07c35040 00000000`c00000bb fffff880`0355b728 fffffa80`075d25e0 : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff880`0355b670 fffff800`034b8161 : fffffa80`0d0617c0 00000000`00000000 fffffa80`07e49230 00000000`00000801 : nt!IopSynchronousCall+0xc5
fffff880`0355b6e0 fffff800`031cb863 : fffff8a0`04988f80 fffff8a0`04988f80 00000000`00000018 00000000`00000000 : nt!IopRemoveDevice+0x101
fffff880`0355b7a0 fffff800`034b7cb4 : fffffa80`07e49230 00000000`00000000 00000000`00000002 00000000`00000000 : nt!PnpRemoveLockedDeviceNode+0x1a3
fffff880`0355b7f0 fffff800`034b7dc0 : 00000000`00000000 fffffa80`0d061700 fffff8a0`0db862d0 fffff800`032cda60 : nt!PnpDeleteLockedDeviceNode+0x44
fffff880`0355b820 fffff800`034b7eb9 : fffffa80`0da25402 fffffa80`0da254a0 00000000`00000001 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`0355b890 fffff800`034b8031 : fffffa80`0da254a0 00000000`00000000 fffffa80`0da254a0 00000000`00000003 : nt!PnpDelayedRemoveWorker+0x79
fffff880`0355b8e0 fffff800`031cba89 : 00000000`00000002 fffffa80`07d0c7e0 00000000`00000001 00000000`00000001 : nt!PnpChainDereferenceComplete+0x131
fffff880`0355b920 fffff800`03549000 : 00000000`00000000 fffffa80`07e49200 fffff8a0`0d83f010 00000000`00000001 : nt!PnpIsChainDereferenced+0xc9
fffff880`0355b9a0 fffff800`0354929c : fffff880`0355bb78 fffffa80`0d095200 fffffa80`07078b00 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0xff0
fffff880`0355bae0 fffff800`0343256e : 00000000`00000000 fffffa80`0d095220 fffff8a0`0dd82010 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`0355bb10 fffff800`030d9471 : fffff800`03338958 fffff8a0`0d83f010 fffff800`0326f2b8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x5aeab
fffff880`0355bb70 fffff800`03369f7a : 00000000`00000000 fffffa80`07078b60 00000000`00000080 fffffa80`06fa1990 : nt!ExpWorkerThread+0x111
fffff880`0355bc00 fffff800`030c09c6 : fffff880`03389180 fffffa80`07078b60 fffff880`033940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0355bc40 00000000`00000000 : fffff880`0355c000 fffff880`03556000 fffff880`0355a430 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff800030d2fb3 - nt!SwapContext_PatchXSave+2
	[ 01:21 ]
1 error : !nt (fffff800030d2fb3)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------
Do you use your Bluetooth for any network activity? If so, make sure it is up to date.

Also, recommend re-installing the latest network adapter drivers for your network adapters:
My System SpecsSystem Spec
25 Mar 2012   #6
gnomefar

Windows 7 Home x64
 
 

Thank you very much. I did use my Bluetooth right before it crashed, so ive updated it.
My System SpecsSystem Spec
25 Mar 2012   #7
writhziden

Windows 7 Home Premium 64 Bit
 
 

Alright, let us know how the system responds over the next few days. Best of luck!
My System SpecsSystem Spec
Reply

 "memory_corruption" BSOD out of nowhere.




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
bsod copying files from "c" to "d" drive and system lock ups
Hi New installation of windows 7 ultimate 32bit and on trying to copy a 38gb folder from c drive to d drive, pc gives bsod. Lately playing world of tanks is resulting in system lock ups,please can anyone help Frosty
BSOD Help and Support
BSOD every few hours: mostly "STOP: 0x00000F4", "c00021a" & "c0000135"
Hi everyone! Yesterday my HP laptop (Windows 7) started getting BSOD with various types of errors (mostly "STOP: 0x00000F4", "STOP: 0x0000007A", "c00021a" and one "missing %hs, c0000135"). Most of the time it restarts without any issues and works fine right after the BSOD and then an hour or two...
BSOD Help and Support
Need to add "TASKBARS" (MSese for "Launchpads", "Docks" NOT "Toolbars"
My office just upgraded, and I can no longer use Windows XP. On this system, I was able to add a separate taskbar to facilitate quick access to commonly-browsed folder locations on our vast network, and another one expedited the launching of useful programs and lists. Each task on each taskbar...
General Discussion
BSOD "Bad Pool Header" and "Page In Nonpage Area" Runs in Safe Mode
Hi, I am having a problem with my newer computer, I just got this rig a few months ago and never had a problem until last Thursday. It Blue Screened on me while I was installing ARC GIS 10.1. From then on it randomly crashes. (I have previously installed ARC GIS 10 and never had a problem.) I...
BSOD Help and Support
BSOD playing Aion, "REFERENCE BY POINTER" and "IRQL NOT LESS OR EQUAL"
Hello, i've been having this problem for a week now, tried to fix it but no luck what so ever. So i got tired and i am looking for your assistance on this matter. Every time I play Aion online, in about 10-30mins i get a blue screen saying "REFERENCE BY POINTER" or "IRQL NOT LESS OR EQUAL", tried...
BSOD Help and Support
BSOD with "usbhub.sys" and "driver power state failure"
I have been getting the BSOD since a few weeks and found out by trial and error that a USB-hub is causing the problem. Whenever I disconnect the hub before I shut off the computer I do not get the blue screen. Yesterday I also got a BSOD that mentioned driver power state failure. After I had...
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 22:19.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App