Lots of BSOD in the past week

[Irene2011]

Hi guys, first post here, so hello to everyone.

My husband's computer has been behaving erratically for about 10 days or so. It will crash with different BSOD's at random.

Details of the behavior:
- The computer shuts itself down anytime: It can be idle doing nothing for hours, you may be working with it, running programs or not, after it just restarted or after about 12 hours or more.
- The BSOD messages so far have been: "BAD_POOL_HEADER" (mainly on the first few days, haven't seen that one in a while), "SYSTEM_SERVICE_EXCEPTION", a few days ago and twice yesterday, and "IRQL_NOT_LESS_OR_EQUAL" a good few times. Today, for the first time, when running the BSOD Dump & System File Collection app, we had a "MEMORY_MANAGEMENT" one.
-I used "Speccy" to monitor the temperatures and there's no sign of overheating for CPU or motherboard. The graphic card is at around 80 C, but i've read that's quite OK.
- There has been no major new software installed (I think my husband had installed quicktime a couple of days before), windows has been updated, and there have been NO hardware changes at all. There is no hardware connected to the computer except for the USB wireless adaptor for the Mouse and keyboard (see below).
- Technical details: Computer is a Packard Bell Onetwo L A6524 UK.
AMD Athion II X2 220 dual-core processor
23" multimedia Touch monitor Full HD 1080
4GB DDR3 Memory
1 TB HD
DVD Super Multidrive
NVDIA GeForce 9200 graphics
Software: Windows 7 Home Premium 64 bit

The computer is fairly new (3 months old or so), OEM, we haven't done anything hardware-wise, windows updates are ran frequently, and no major software changes done. About three days before the first BSOD there was a power cut here. I unplugged it after the power cut, and only restarted it a good while after power came back.

What I've done so far:
- Ran chkdsk and sfc/scannow, both came clean. (May 31st)
- Removed Avast (and installed MSE) and updated the nVidia drivers (SMU, storage, graphics and ethernet) (also May 31st)
-After that the computer ran normally for about 12 hours, until it crashed again when i re-enabled the power management settings. It crashed at the time it was scheduled to shut down the monitor. It BSOD a couple of times, i disabled power management and crashed again, it was an "IRQL" BSOD, the culprit was "usbport.sys".
- After that it started crashing during POST. It just wouldn't start, once it managed to beep once and then it made a long, continuous beep.
- Then I moved the wireless adaptor to a different usb port and it started normally. After it restarted, I disabled "USB selective suspend setting". No usbport.sys crashes since then. (June 2nd).
-Worked fine for a while, then it crashed again: "BAD_POOL_HEADER", restarted normally for a few minutes, but it froze (wouldn't respond to keyboard, mouse or touchscreen) and the bottom of the screen was "flickering" (like an old VCR having tracking issues). Turned it off, on again, restarted without issues (June 3rd)
- Worked fine for nearly 24 hours, crashed again yesterday while watching a youtube video in fullscreen (we had been watching videos for a while, without any problems).
- Since then, it's crashed a couple of times. Last time was the "MEMORY MANAGEMENT" one I mentioned above.
- Ran Dump & System File Collection in safe mode. Then restarted and ran System Health Report in normal mode.
- Saw something about the mouse in the SHR, checked the drivers, found 2 mice (?), disabled one, checked for updates, it said the drivers were up to date.

I'm attaching SHE report, Dump & System File Collection report, and the whole minidump zipped folder in case you want to take a look at it.

Thanks for any input you might provide. I can find my way around a PC, but please bear in mind I haven't used Windows in a couple of years, so please anything you need me doing, explain it to me as if i were 5 years old, cause it takes me a long while to find my way around W7

 

[Maguscreed]

Crashes seem to have been plaguing this machine in various forms for some times looking over the information.
Unfortunately I'm unable to pin down any one cause and the minidumps are all over the place.

I do notice that the usb system driver has caused several of the crashes. I would recommend unplugging any usb devices in the short term to see if that helps clear up the issue.

That being said.

There's 2 things I would like you to try for the moment.


The first is a simple windows core file check, this is easy to do and only takes a few minutes.
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

The second is not very difficult either but will take some time (it's best to allow it to run overnight) and that is to check the physical memory for problems
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Needless to say you have a massive number of minidumps here to go over, and I would like to try these two relatively easy on both of us options before I start digging through 15+ minidumps looking for a common problem causer.


I'm attaching one of the minidumps just for future reference.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 000000006f6d7455, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88003b30f6f, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eaf0e0
 000000006f6d7455 

CURRENT_IRQL:  2

FAULTING_IP: 
USBPORT!USBPORT_ReleaseEpListLock+17
fffff880`03b30f6f 8b13            mov     edx,dword ptr [rbx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002f1bb30 -- (.trap 0xfffff88002f1bb30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880009f2f00 rbx=0000000000000000 rcx=fffffa8004c48a28
rdx=fffffa8004c48a10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003b30f6f rsp=fffff88002f1bcc8 rbp=fffffa8004c48a10
 r8=000000004f444648  r9=0000000000000000 r10=00000000ffffffff
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
USBPORT!USBPORT_ReleaseEpListLock+0x17:
fffff880`03b30f6f 8b13            mov     edx,dword ptr [rbx] ds:81a0:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c76c69 to fffff80002c77700

STACK_TEXT:  
fffff880`02f1b9e8 fffff800`02c76c69 : 00000000`0000000a 00000000`6f6d7455 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f1b9f0 fffff800`02c758e0 : 00000000`001312d0 00000000`6f6d7455 fffffa80`04f00ea8 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f1bb30 fffff880`03b30f6f : fffff800`02c82c0c fffff880`009e8180 fffffa80`04c48050 fffffa80`04c49178 : nt!KiPageFault+0x260
fffff880`02f1bcc8 fffffa80`04eff880 : fffff880`009e8180 00000000`400000c3 0000002a`8de0e451 00000000`00000010 : USBPORT!USBPORT_ReleaseEpListLock+0x17
fffff880`02f1bcf8 fffff880`009e8180 : 00000000`400000c3 0000002a`8de0e451 00000000`00000010 00000000`00000283 : 0xfffffa80`04eff880
fffff880`02f1bd00 00000000`400000c3 : 0000002a`8de0e451 00000000`00000010 00000000`00000283 fffff880`02f1bd38 : 0xfffff880`009e8180
fffff880`02f1bd08 0000002a`8de0e451 : 00000000`00000010 00000000`00000283 fffff880`02f1bd38 00000000`00000018 : 0x400000c3
fffff880`02f1bd10 00000000`00000010 : 00000000`00000283 fffff880`02f1bd38 00000000`00000018 fffff880`02f1bd40 : 0x2a`8de0e451
fffff880`02f1bd18 00000000`00000283 : fffff880`02f1bd38 00000000`00000018 fffff880`02f1bd40 fffff880`009ecec0 : 0x10
fffff880`02f1bd20 fffff880`02f1bd38 : 00000000`00000018 fffff880`02f1bd40 fffff880`009ecec0 fffffa80`036c9040 : 0x283
fffff880`02f1bd28 00000000`00000018 : fffff880`02f1bd40 fffff880`009ecec0 fffffa80`036c9040 00000000`00000000 : 0xfffff880`02f1bd38
fffff880`02f1bd30 fffff880`02f1bd40 : fffff880`009ecec0 fffffa80`036c9040 00000000`00000000 00000000`00000000 : 0x18
fffff880`02f1bd38 fffff880`009ecec0 : fffffa80`036c9040 00000000`00000000 00000000`00000000 fffffa80`04f8e760 : 0xfffff880`02f1bd40
fffff880`02f1bd40 fffffa80`036c9040 : 00000000`00000000 00000000`00000000 fffffa80`04f8e760 fffff880`009f2f40 : 0xfffff880`009ecec0
fffff880`02f1bd48 00000000`00000000 : 00000000`00000000 fffffa80`04f8e760 fffff880`009f2f40 00000000`00000000 : 0xfffffa80`036c9040


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBPORT!USBPORT_ReleaseEpListLock+17
fffff880`03b30f6f 8b13            mov     edx,dword ptr [rbx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  USBPORT!USBPORT_ReleaseEpListLock+17

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc07

FAILURE_BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_ReleaseEpListLock+17

BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_ReleaseEpListLock+17

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

1: kd> lm t n
start             end                 module name
fffff800`00bc1000 fffff800`00bcb000   kdcom    kdcom.dll    Sat Feb 05 06:21:45 2011 (4D4D40D9)
fffff800`02c07000 fffff800`031e3000   nt       ntkrnlmp.exe Fri Apr 08 23:14:44 2011 (4D9FDD34)
fffff800`031e3000 fffff800`0322c000   hal      hal.dll      Mon Jul 13 20:27:36 2009 (4A5BDF08)
fffff880`00c04000 fffff880`00c11000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 20:29:09 2009 (4A5BDF65)
fffff880`00c11000 fffff880`00c25000   PSHED    PSHED.dll    Mon Jul 13 20:32:23 2009 (4A5BE027)
fffff880`00c25000 fffff880`00c83000   CLFS     CLFS.SYS     Mon Jul 13 18:19:57 2009 (4A5BC11D)
fffff880`00c83000 fffff880`00d43000   CI       CI.dll       Mon Jul 13 20:32:13 2009 (4A5BE01D)
fffff880`00d43000 fffff880`00de7000   Wdf01000 Wdf01000.sys Mon Jul 13 18:22:07 2009 (4A5BC19F)
fffff880`00de7000 fffff880`00df6000   WDFLDR   WDFLDR.SYS   Mon Jul 13 18:19:54 2009 (4A5BC11A)
fffff880`00e00000 fffff880`00e11000   blbdrive blbdrive.sys Mon Jul 13 18:35:59 2009 (4A5BC4DF)
fffff880`00e1b000 fffff880`00e72000   ACPI     ACPI.sys     Mon Jul 13 18:19:34 2009 (4A5BC106)
fffff880`00e72000 fffff880`00e7b000   WMILIB   WMILIB.SYS   Mon Jul 13 18:19:51 2009 (4A5BC117)
fffff880`00e7b000 fffff880`00e85000   msisadrv msisadrv.sys Mon Jul 13 18:19:26 2009 (4A5BC0FE)
fffff880`00e85000 fffff880`00eb8000   pci      pci.sys      Mon Jul 13 18:19:51 2009 (4A5BC117)
fffff880`00eb8000 fffff880`00ec5000   vdrvroot vdrvroot.sys Mon Jul 13 19:01:31 2009 (4A5BCADB)
fffff880`00ec5000 fffff880`00eda000   partmgr  partmgr.sys  Mon Jul 13 18:19:58 2009 (4A5BC11E)
fffff880`00eda000 fffff880`00eef000   volmgr   volmgr.sys   Mon Jul 13 18:19:57 2009 (4A5BC11D)
fffff880`00eef000 fffff880`00f4b000   volmgrx  volmgrx.sys  Mon Jul 13 18:20:33 2009 (4A5BC141)
fffff880`00f4b000 fffff880`00f52000   pciide   pciide.sys   Mon Jul 13 18:19:49 2009 (4A5BC115)
fffff880`00f52000 fffff880`00f62000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 18:19:48 2009 (4A5BC114)
fffff880`00f62000 fffff880`00f7c000   mountmgr mountmgr.sys Mon Jul 13 18:19:54 2009 (4A5BC11A)
fffff880`00f7c000 fffff880`00f85000   atapi    atapi.sys    Mon Jul 13 18:19:47 2009 (4A5BC113)
fffff880`00f85000 fffff880`00faf000   ataport  ataport.SYS  Mon Jul 13 18:19:52 2009 (4A5BC118)
fffff880`00faf000 fffff880`00fee000   nvstor64 nvstor64.sys Fri Apr 09 04:22:41 2010 (4BBEF1E1)
fffff880`00fee000 fffff880`00ffb000   TDI      TDI.SYS      Mon Jul 13 18:21:18 2009 (4A5BC16E)
fffff880`01000000 fffff880`0104a000   fwpkclnt fwpkclnt.sys Mon Jul 13 18:21:08 2009 (4A5BC164)
fffff880`0104a000 fffff880`01053000   rdprefmp rdprefmp.sys Mon Jul 13 19:16:35 2009 (4A5BCE63)
fffff880`0105c000 fffff880`010be000   storport storport.sys Tue May 11 23:14:15 2010 (4BEA2B17)
fffff880`010be000 fffff880`010c9000   amdxata  amdxata.sys  Fri Mar 19 11:18:18 2010 (4BA3A3CA)
fffff880`010c9000 fffff880`01115000   fltmgr   fltmgr.sys   Mon Jul 13 18:19:59 2009 (4A5BC11F)
fffff880`01115000 fffff880`01129000   fileinfo fileinfo.sys Mon Jul 13 18:34:25 2009 (4A5BC481)
fffff880`01129000 fffff880`01135040   PxHlpa64 PxHlpa64.sys Tue Oct 20 13:08:42 2009 (4ADDFCAA)
fffff880`01136000 fffff880`01194000   msrpc    msrpc.sys    Mon Jul 13 18:21:32 2009 (4A5BC17C)
fffff880`01194000 fffff880`011bf000   ksecpkg  ksecpkg.sys  Fri Dec 11 00:03:32 2009 (4B21E0B4)
fffff880`011bf000 fffff880`011ca000   Msfs     Msfs.SYS     Mon Jul 13 18:19:47 2009 (4A5BC113)
fffff880`011ca000 fffff880`011db000   Npfs     Npfs.SYS     Mon Jul 13 18:19:48 2009 (4A5BC114)
fffff880`011db000 fffff880`011f9000   tdx      tdx.sys      Mon Jul 13 18:21:15 2009 (4A5BC16B)
fffff880`01200000 fffff880`01225000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 18:38:51 2009 (4A5BC58B)
fffff880`01226000 fffff880`013c8000   Ntfs     Ntfs.sys     Tue May 11 22:25:59 2010 (4BEA1FC7)
fffff880`013c8000 fffff880`013e2000   ksecdd   ksecdd.sys   Mon Jul 13 18:20:54 2009 (4A5BC156)
fffff880`013e2000 fffff880`013f2000   watchdog watchdog.sys Mon Jul 13 18:37:35 2009 (4A5BC53F)
fffff880`013f2000 fffff880`013fb000   rdpencdd rdpencdd.sys Mon Jul 13 19:16:34 2009 (4A5BCE62)
fffff880`01400000 fffff880`01460000   NETIO    NETIO.SYS    Thu Apr 08 21:43:59 2010 (4BBE946F)
fffff880`01460000 fffff880`0146e000   vga      vga.sys      Mon Jul 13 18:38:47 2009 (4A5BC587)
fffff880`01472000 fffff880`014e5000   cng      cng.sys      Mon Jul 13 18:49:40 2009 (4A5BC814)
fffff880`014e5000 fffff880`014f6000   pcw      pcw.sys      Mon Jul 13 18:19:27 2009 (4A5BC0FF)
fffff880`014f6000 fffff880`01500000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 18:19:45 2009 (4A5BC111)
fffff880`01500000 fffff880`015f2000   ndis     ndis.sys     Mon Jul 13 18:21:40 2009 (4A5BC184)
fffff880`015f2000 fffff880`015fb000   RDPCDD   RDPCDD.sys   Mon Jul 13 19:16:34 2009 (4A5BCE62)
fffff880`01600000 fffff880`017fd000   tcpip    tcpip.sys    Sun Jun 13 22:39:04 2010 (4C15A458)
fffff880`01800000 fffff880`01867000   srv2     srv2.sys     Tue Feb 22 23:15:59 2011 (4D64980F)
fffff880`0186a000 fffff880`01894000   cdrom    cdrom.sys    Mon Jul 13 18:19:54 2009 (4A5BC11A)
fffff880`01894000 fffff880`018c5000   MpFilter MpFilter.sys Tue Sep 14 19:19:28 2010 (4C901110)
fffff880`018c5000 fffff880`018ce000   Null     Null.SYS     Mon Jul 13 18:19:37 2009 (4A5BC109)
fffff880`018cf000 fffff880`0191b000   volsnap  volsnap.sys  Mon Jul 13 18:20:08 2009 (4A5BC128)
fffff880`0191b000 fffff880`01923000   spldr    spldr.sys    Mon May 11 11:56:27 2009 (4A0858BB)
fffff880`01923000 fffff880`0195d000   rdyboost rdyboost.sys Fri Jun 18 23:25:06 2010 (4C1C46A2)
fffff880`0195d000 fffff880`0196f000   mup      mup.sys      Mon Jul 13 18:23:45 2009 (4A5BC201)
fffff880`0196f000 fffff880`01978000   hwpolicy hwpolicy.sys Mon Jul 13 18:19:22 2009 (4A5BC0FA)
fffff880`01978000 fffff880`019b2000   fvevol   fvevol.sys   Fri Sep 25 21:34:26 2009 (4ABD7DB2)
fffff880`019b2000 fffff880`019c8000   disk     disk.sys     Mon Jul 13 18:19:57 2009 (4A5BC11D)
fffff880`019c8000 fffff880`019f8000   CLASSPNP CLASSPNP.SYS Mon Jul 13 18:19:58 2009 (4A5BC11E)
fffff880`019f8000 fffff880`019ff000   Beep     Beep.SYS     Mon Jul 13 19:00:13 2009 (4A5BCA8D)
fffff880`02c00000 fffff880`02c14000   termdd   termdd.sys   Mon Jul 13 19:16:36 2009 (4A5BCE64)
fffff880`02c14000 fffff880`02c65000   rdbss    rdbss.sys    Mon Jul 13 18:24:09 2009 (4A5BC219)
fffff880`02c65000 fffff880`02c71000   nsiproxy nsiproxy.sys Mon Jul 13 18:21:02 2009 (4A5BC15E)
fffff880`02c71000 fffff880`02c7c000   mssmbios mssmbios.sys Mon Jul 13 18:31:10 2009 (4A5BC3BE)
fffff880`02c7c000 fffff880`02c8b000   discache discache.sys Mon Jul 13 18:37:18 2009 (4A5BC52E)
fffff880`02c8b000 fffff880`02ca9000   dfsc     dfsc.sys     Mon Jul 13 18:23:44 2009 (4A5BC200)
fffff880`02cb2000 fffff880`02d3c000   afd      afd.sys      Mon Jul 13 18:21:40 2009 (4A5BC184)
fffff880`02d3c000 fffff880`02d81000   netbt    netbt.sys    Mon Jul 13 18:21:28 2009 (4A5BC178)
fffff880`02d81000 fffff880`02d8a000   wfplwf   wfplwf.sys   Mon Jul 13 19:09:26 2009 (4A5BCCB6)
fffff880`02d8a000 fffff880`02db0000   pacer    pacer.sys    Mon Jul 13 19:09:41 2009 (4A5BCCC5)
fffff880`02db0000 fffff880`02dc6000   vwififlt vwififlt.sys Mon Jul 13 19:07:22 2009 (4A5BCC3A)
fffff880`02dc6000 fffff880`02dd5000   netbios  netbios.sys  Mon Jul 13 19:09:26 2009 (4A5BCCB6)
fffff880`02dd5000 fffff880`02df0000   wanarp   wanarp.sys   Mon Jul 13 19:10:21 2009 (4A5BCCED)
fffff880`03a00000 fffff880`03a53a80   nvmf6264 nvmf6264.sys Thu Mar 04 19:04:39 2010 (4B9058A7)
fffff880`03aad000 fffff880`03ad3000   tunnel   tunnel.sys   Mon Jul 13 19:09:37 2009 (4A5BCCC1)
fffff880`03ad3000 fffff880`03ae8000   amdppm   amdppm.sys   Mon Jul 13 18:19:25 2009 (4A5BC0FD)
fffff880`03b06000 fffff880`03b15000   mouclass mouclass.sys Mon Jul 13 18:19:50 2009 (4A5BC116)
fffff880`03b15000 fffff880`03b20000   nvsmu    nvsmu.sys    Mon Mar 22 20:29:19 2010 (4BA8196F)
fffff880`03b20000 fffff880`03b2b000   usbohci  usbohci.sys  Mon Jul 13 19:06:30 2009 (4A5BCC06)
fffff880`03b2b000 fffff880`03b81000   USBPORT  USBPORT.SYS  Mon Jul 13 19:06:31 2009 (4A5BCC07)
fffff880`03b81000 fffff880`03b92000   usbehci  usbehci.sys  Fri Oct 23 23:27:33 2009 (4AE28235)
fffff880`03b92000 fffff880`03bb6000   HDAudBus HDAudBus.sys Mon Jul 13 19:06:13 2009 (4A5BCBF5)
fffff880`03e00000 fffff880`03e46000   dxgmms1  dxgmms1.sys  Tue Jan 25 22:22:12 2011 (4D3FA174)
fffff880`03e46000 fffff880`03e4f000   wmiacpi  wmiacpi.sys  Mon Jul 13 18:31:02 2009 (4A5BC3B6)
fffff880`03e4f000 fffff880`03e5f000   CompositeBus CompositeBus.sys Mon Jul 13 19:00:33 2009 (4A5BCAA1)
fffff880`03e5f000 fffff880`03e75000   AgileVpn AgileVpn.sys Mon Jul 13 19:10:24 2009 (4A5BCCF0)
fffff880`03e75000 fffff880`03e99000   rasl2tp  rasl2tp.sys  Mon Jul 13 19:10:11 2009 (4A5BCCE3)
fffff880`03e99000 fffff880`03ea5000   ndistapi ndistapi.sys Mon Jul 13 19:10:00 2009 (4A5BCCD8)
fffff880`03ea5000 fffff880`03ed4000   ndiswan  ndiswan.sys  Mon Jul 13 19:10:11 2009 (4A5BCCE3)
fffff880`03ed4000 fffff880`03eef000   raspppoe raspppoe.sys Mon Jul 13 19:10:17 2009 (4A5BCCE9)
fffff880`03eef000 fffff880`03ef0480   swenum   swenum.sys   Mon Jul 13 19:00:18 2009 (4A5BCA92)
fffff880`03efd000 fffff880`03ff1000   dxgkrnl  dxgkrnl.sys  Tue Jan 25 22:22:56 2011 (4D3FA1A0)
fffff880`03ff1000 fffff880`04000000   kbdclass kbdclass.sys Mon Jul 13 18:19:50 2009 (4A5BC116)
fffff880`04200000 fffff880`04215000   lltdio   lltdio.sys   Mon Jul 13 19:08:50 2009 (4A5BCC92)
fffff880`04215000 fffff880`04268000   nwifi    nwifi.sys    Mon Jul 13 19:07:23 2009 (4A5BCC3B)
fffff880`04268000 fffff880`0427b000   ndisuio  ndisuio.sys  Mon Jul 13 19:09:25 2009 (4A5BCCB5)
fffff880`0427f000 fffff880`042d9000   usbhub   usbhub.sys   Fri Oct 23 23:28:24 2009 (4AE28268)
fffff880`042d9000 fffff880`042ee000   NDProxy  NDProxy.SYS  Mon Jul 13 19:10:05 2009 (4A5BCCDD)
fffff880`042ee000 fffff880`043b1000   RTL8192su RTL8192su.sys Thu Nov 25 00:13:42 2010 (4CEDFE96)
fffff880`043b1000 fffff880`043d4000   luafv    luafv.sys    Mon Jul 13 18:26:13 2009 (4A5BC295)
fffff880`043d4000 fffff880`043df000   Sftvollh Sftvollh.sys Fri Apr 23 14:20:08 2010 (4BD1F2E8)
fffff880`043df000 fffff880`04400000   WudfPf   WudfPf.sys   Mon Jul 13 19:05:37 2009 (4A5BCBD1)
fffff880`04800000 fffff880`0482d200   usbvideo usbvideo.sys Wed Mar 03 22:40:57 2010 (4B8F39D9)
fffff880`0482e000 fffff880`04848c00   usbaudio usbaudio.sys Mon Jul 13 19:06:31 2009 (4A5BCC07)
fffff880`04849000 fffff880`04857000   monitor  monitor.sys  Mon Jul 13 18:38:52 2009 (4A5BC58C)
fffff880`04857000 fffff880`04a7f780   RTKVHD64 RTKVHD64.sys Tue Feb 09 09:28:17 2010 (4B717F11)
fffff880`04a80000 fffff880`04abd000   portcls  portcls.sys  Mon Jul 13 19:06:27 2009 (4A5BCC03)
fffff880`04abd000 fffff880`04adf000   drmk     drmk.sys     Mon Jul 13 20:01:25 2009 (4A5BD8E5)
fffff880`04adf000 fffff880`04aed000   MBfilt64 MBfilt64.sys Thu Jul 30 22:40:32 2009 (4A7267B0)
fffff880`04aed000 fffff880`04af2200   ksthunk  ksthunk.sys  Mon Jul 13 19:00:19 2009 (4A5BCA93)
fffff880`04af3000 fffff880`04b01000   crashdmp crashdmp.sys Mon Jul 13 19:01:01 2009 (4A5BCABD)
fffff880`04b01000 fffff880`04b0b000   dump_diskdump dump_diskdump.sys Fri Apr 22 13:11:55 2011 (4DB1C4EB)
fffff880`04b0b000 fffff880`04b4a000   dump_nvstor64 dump_nvstor64.sys Fri Apr 09 04:22:41 2010 (4BBEF1E1)
fffff880`04b4a000 fffff880`04b5d000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 18:21:51 2009 (4A5BC18F)
fffff880`04b5d000 fffff880`04b6b000   hidusb   hidusb.sys   Mon Jul 13 19:06:22 2009 (4A5BCBFE)
fffff880`04b6b000 fffff880`04b84000   HIDCLASS HIDCLASS.SYS Mon Jul 13 19:06:21 2009 (4A5BCBFD)
fffff880`04b84000 fffff880`04b8c080   HIDPARSE HIDPARSE.SYS Mon Jul 13 19:06:17 2009 (4A5BCBF9)
fffff880`04b8d000 fffff880`04b8ef00   USBD     USBD.SYS     Mon Jul 13 19:06:23 2009 (4A5BCBFF)
fffff880`04b8f000 fffff880`04b9c000   mouhid   mouhid.sys   Mon Jul 13 19:00:20 2009 (4A5BCA94)
fffff880`04b9c000 fffff880`04bb9000   usbccgp  usbccgp.sys  Mon Jul 13 19:06:45 2009 (4A5BCC15)
fffff880`04bb9000 fffff880`04bc7000   kbdhid   kbdhid.sys   Mon Jul 13 19:00:20 2009 (4A5BCA94)
fffff880`04bc7000 fffff880`04bd4000   vwifibus vwifibus.sys Mon Jul 13 19:07:21 2009 (4A5BCC39)
fffff880`04bd4000 fffff880`04bef000   USBSTOR  USBSTOR.SYS  Tue May 11 23:21:12 2010 (4BEA2CB8)
fffff880`04bef000 fffff880`04bfb000   Dxapi    Dxapi.sys    Mon Jul 13 18:38:28 2009 (4A5BC574)
fffff880`09400000 fffff880`0942d000   mrxsmb   mrxsmb.sys   Tue Feb 22 23:15:23 2011 (4D6497EB)
fffff880`0942d000 fffff880`0947b000   mrxsmb10 mrxsmb10.sys Tue Feb 22 23:15:14 2011 (4D6497E2)
fffff880`0947b000 fffff880`0949e000   mrxsmb20 mrxsmb20.sys Tue Feb 22 23:15:13 2011 (4D6497E1)
fffff880`094e1000 fffff880`095a9000   HTTP     HTTP.sys     Mon Jul 13 18:22:16 2009 (4A5BC1A8)
fffff880`095a9000 fffff880`095c7000   bowser   bowser.sys   Tue Feb 22 23:15:06 2011 (4D6497DA)
fffff880`095c7000 fffff880`095df000   mpsdrv   mpsdrv.sys   Mon Jul 13 19:08:25 2009 (4A5BCC79)
fffff880`09602000 fffff880`096a8000   peauth   peauth.sys   Mon Jul 13 20:01:19 2009 (4A5BD8DF)
fffff880`096a8000 fffff880`096b3000   secdrv   secdrv.SYS   Wed Sep 13 08:18:38 2006 (4508052E)
fffff880`096b3000 fffff880`0976a000   Sftfslh  Sftfslh.sys  Fri Apr 23 14:20:30 2010 (4BD1F2FE)
fffff880`0976a000 fffff880`097b7000   Sftplaylh Sftplaylh.sys Fri Apr 23 14:20:28 2010 (4BD1F2FC)
fffff880`097b7000 fffff880`097e4000   srvnet   srvnet.sys   Tue Feb 22 23:15:49 2011 (4D649805)
fffff880`097e4000 fffff880`097f6000   tcpipreg tcpipreg.sys Mon Jul 13 19:09:49 2009 (4A5BCCCD)
fffff880`09e21000 fffff880`09eb6000   srv      srv.sys      Tue Feb 22 23:16:24 2011 (4D649828)
fffff880`09eb6000 fffff880`09ec1000   Sftredirlh Sftredirlh.sys Fri Apr 23 14:20:39 2010 (4BD1F307)
fffff880`09ec1000 fffff880`09ed1000   MpNWMon  MpNWMon.sys  Tue Sep 14 19:19:30 2010 (4C901112)
fffff880`09ed1000 fffff880`09ee6000   NisDrvWFP NisDrvWFP.sys Tue Sep 14 19:20:25 2010 (4C901149)
fffff880`09ee6000 fffff880`09f17000   WUDFRd   WUDFRd.sys   Mon Jul 13 19:06:06 2009 (4A5BCBEE)
fffff880`09f88000 fffff880`09fbe000   fastfat  fastfat.SYS  Mon Jul 13 18:23:28 2009 (4A5BC1F0)
fffff880`0fe00000 fffff880`0fe21000   raspptp  raspptp.sys  Mon Jul 13 19:10:18 2009 (4A5BCCEA)
fffff880`0fe21000 fffff880`0fe3b000   rassstp  rassstp.sys  Mon Jul 13 19:10:25 2009 (4A5BCCF1)
fffff880`0fe3b000 fffff880`0fe7e000   ks       ks.sys       Wed Mar 03 22:32:25 2010 (4B8F37D9)
fffff880`0fe7e000 fffff880`0fe90000   umbus    umbus.sys    Mon Jul 13 19:06:56 2009 (4A5BCC20)
fffff880`0fe90000 fffff880`0fea8000   rspndr   rspndr.sys   Mon Jul 13 19:08:50 2009 (4A5BCC92)
fffff880`0febe000 fffff880`10be7700   nvlddmkm nvlddmkm.sys Tue Mar 16 02:57:48 2010 (4B9F39FC)
fffff880`10be8000 fffff880`10be9180   nvBridge nvBridge.kmd Tue Mar 16 02:26:37 2010 (4B9F32AD)
fffff960`00000000 fffff960`00312000   win32k   win32k.sys   unavailable (00000000)
fffff960`005b0000 fffff960`005ba000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff960`00760000 fffff960`00787000   cdd      cdd.dll      unavailable (00000000)

Unloaded modules:
fffff880`09f17000 fffff880`09f88000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00071000
fffff880`01800000 fffff880`0180e000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`0180e000 fffff880`01818000   dump_storpor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000A000
fffff880`01818000 fffff880`01857000   dump_nvstor6
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0003F000
fffff880`01857000 fffff880`0186a000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000
fffff880`03ae8000 fffff880`03b06000   i8042prt.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0001E000

 

[Irene2011]

Thanks Maguscreed!

Just ran sfc / scannow, and came clear: "Windows Resource Protection did not find any integrity violations".

Going to run Memtest later tonight.

About the USB: We currently don't have (and haven't had since the problems began) anything plugged in any of the usb's except for the wireless adaptor (and we need that for keyboard and mouse, even if we went for wired mouse/keyboard, the ones we have are all USB). There was a huge difference after I moved the wireless adaptor to a different USB port a couple of days ago. At least it stopped the computer from hanging during POST, and having all sorts of startup issues.

We had another BSOD, before running sfc. This one said "an attempt was made to execute to non-executable memory". No dump was created. The computer restarted without any issues after that.

Thanks for taking the trouble to go over all this data. I know it's a massive lot and even I realize that it's pretty much all over the place and doesn't have a clear pattern. That's why we're getting quite confused and annoyed.

Thanks again!

 

[Maguscreed]

Yeah, let's go ahead and wait for the memtest to run overnight. That still seems like the right thing to do here.

 

[Irene2011]

Hi again,

Ran memtest during the night. 9 passes were completed and no errors found.

The computer has been stable for the last 18 hours or so (I think the last BSOD was the one i mentioned in the post above). But i'm pretty sure it's going to at some point :sarc:

What's next?

 

[Maguscreed]

Alright well since memory is ruled out I need a more specific crash dump.
The 15+ attached in your original post almost all blame different components and whittling it down is just too time consuming.
Hopefully driver verifier will produce a dump that actually points to the offending driver.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[Irene2011]

Hi again,

Between the time of my last post and yesterday evening the computer was absolutely fine. No crashes, no BSOD, all worked seamlessly, Whether using it normally or being idle, it worked. So i held off on running Driver verifier.

Late last night, it crashed again, quite out of the blue (no pun intended). It crashed twice, my husband turned it on again this morning, and it was working fine but, since it had crashed again, I ran DV.
Upon first rebooting after enabling it, nothing happened for a few minutes (not sure how long), but at some point the computer froze, not even responding to ctrl+alt+del. So i turned it off, back on, and after a while i got another BSOD. It was an "IRQL" one, and had a hell of a time turning the computer back on again after that, since it started hanging during POST (not beeping, not doing anything really). After a good few attempts, it started again. I disabled verifier, copied the dumps (i'm attaching last night one and the one after enabling verifier). The file ending in 20030-01 is from last night, the 20482-01 one is post Driver Verifier.

Thank you!

 

[Maguscreed]

That's normal actually driver verifier is supposed to crash problem drivers. I'll have a look and post back in a bit here, it's a hectic day for me so give me a little time

 

[Maguscreed]

okay I am having a really hard time tracking down specific information on your system.
Is there a part number you can give for it?
I think we're looking at a chipset driver issue here, I know the chipset is nvidia, but I don't know exactly which one and I am having a hard time getting specific information from packard bell with the information I already have.
A part code should look something like this
PW.U4402.004

Sorry we seem to be just spinning our wheels but these OneTwo's are basically laptops that have been turned on their side, so I really need to be specific with the drivers or we could make things worse.

 

[Irene2011]

Hi Maguscreed,
Thanks for the quick reply. Just to make something clear: I did expect Driver Verifier to make the computer BSOD, it did worry me a bit when after crashing it just wouldn't start at all.
It keeps BSOD'ing even after i disabled it, btw.

Where do i get the chipset part code from?

 

[Maguscreed]

If there is a part number for the item I would assume it to be on the back of the panel ...

actually scratch that I'm starting to wonder if this is a thermal profile issue after familiarizing myself a bit more with the model series.
Can you navigate through this
Support Download
and find the bios update for you model?

 

[Irene2011]

Managed to turn the computer on (briefly) and tried to find something that looked like what you mentioned but couldn't find it (was probably looking in the wrong place).
I ran Speccy and saved all the info it tells, so maybe there's something in there you might find helpful.

I was just replying all this here and I saw your reply
I'll upload the speccy text file anyway (because you might find what you're looking for before I do) and in the meantime, i'll check the link you gave me and see if i can find the right one .

BTW, last restart didn't last long. Computer worked fine for about 30 minutes, it even loaded the screensaver fine, and then it became all "lines" (not sure how to explain, all horizontal lines somehow formed by the image that was being showed, but all scrambled)

Will get back to you as soon as I find what you need at the PB site
Thank you!

 

[Maguscreed]

This is not something I normally suggest, but I think it's about time to contact packard bell.
What you are describing is sounding more and more like either a heat or hardware problem.
That's not something I can help you fix here.

This most recent crash sounds like a corruption of the graphics video memory.
Nothing I have tracked in the dumps points directly to any software issue.
I'm going to have another dump file reader come and have a look at your stuff as well, but it's seeming more and more like the machine is either suffering a heat issue or some kind of hardware failure.

 

[zigzag3143]

Your chrash causes are all over the map as Maguscreed said. USB,video driver, etc.

SInce they are I am thinking one of two causes

1-hardware. see here
Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html




2-malware. Download malwarebytes and run in safe mode.


I also notive your avast which of itself can cause BSOD's on certain systems. REmove and replace to test with Microsoft Security Essentials

http://files.avast.com/files/eng/aswclear5.exe

Virus, Spyware & Malware Protection | Microsoft Security Essentials

I would also remove utorrent for a different torrent client.

 

[Irene2011]

For what it may be worth, I'm pretty sure the model is PW.U5R, and that's pretty much all i could get from the back panel. The BIOS is P01-A1, and the date is a month older than the one in the PB site. There's no mention I can find anywhere of the other BIOS stated in the PB site for that model (the one that says "Updates system fan curve") nor do I know whether there should be one.

Just out of curiosity, about heat issues: Am I assuming right in thinking that the 3 temps that matter are CPU, motherboard and graphics? I'm asking because those are the 3 i've been monitoring throughout all this, and they've been pretty stable --as I said in my first post, the Graphics temp seemed a bit too high and the reading from Speccy I posted here is at idle and 2 minutes after starting the computer (74 Celsius), but what I read was that Graphic cards can handle higher temps (mine never seems to go over 50 though).
Also, I did have some heat issues a couple of years ago, and the pattern was pretty much the same as you get when a car overheats: If you start it from cold, it'll do OK for a while, it crashes when on for some time, and if you restart it right away it will not last long cause it hasn't had time to cool down. This was not the pattern the crashes presented in this case (although off the top of my head i'm thinking that an intermittently failing cooling fan could cause this?).
Which brings me to the next question: How many fans is a OneTwo supposed to have? Speccy only sees the CPU one, it made me curious (I have a Mac myself which, to me, is the same kind of thing, and it has 3: CPU, HD and Optical Drive).

About the corruption of the graphics video memory: Is it something that can also come and go? When it happened today, my husband said "oh yes, i had that yesterday when trying to see something in MySpace". He had mentioned it, but I had thought it was more like the screen freezing, he took a picture and it was just like happened today. The computer restarted normally after it happened to him.
Found an app called GPU-Z

http://www.techpowerup.com/gpuz/

. Do you think it's worth downloading it to check ours? Safe? Useful?

Thanks a lot for your help! I'm sorry if i'm being a nuisance, I just want to have all the information possible if we have to take it back to PB (which seems like the most likely scenario), and also I always liked knowing all I could about computer issues in order to know what to do best in each case. That seemed a much easier task in the good old XP days, lol.

 

[Irene2011]

Hi zigzag,

Took me so long to write my latest post that i couldn't see yours

It's nearly 4 AM here, so I just took a quick look at the stop 0x124 article and will look more into it in the morning.
At first glance:
1) Cooling issues, there's a few questions i have in the post above this one
2) Overclocking: Not that we have done it, could it have come overclocked when we bought it and how do we know?
3) BIOS updating: Also, in the post above I put what I found (or my reply to what Maguscreed found). Not sure whether or not to update?
4) Stress tests: memtest86 ran 9 passes and found nothing. I ran chkdsk about a week ago, and came clean too (without the /r, can run it with it if you think it's necessary)

Also, Avast was uninstalled also about a week ago, did you find evidence of it in a recent dump? In theory the uninstall wasn't much trouble and we didn't get any message saying there were components left behind, but I'll check. Using MSE now.
utorrent: Can it cause trouble even when it's not running? The computer crashed many times with only the standard startup programs running (utorrent not one of them).

Time for bed, I'll give the article a long read tomorrow, and start by running malwarebytes and chkdsk/r unless you think the previous chkdsk was enough. Thank you!!

 

[Irene2011]

Update: Ran chkdsk again, and it came clear. Ran malwarebytes and it came clean (the computer actually BSOD'd while running it, but it was already over halfway through scanning the non system partition)
Since updating the NVIDIA drivers hadn't changed much a couple of days ago, we just went for a full format and re-install. I was intending to go for a "vanilla" install, but apparently we can't because the PB recovery disks make the full install with all of PB's software included, and you're never prompted for an option not to.

After installing for a couple of hours without any hassle at all, the computer BSOD'd again an hour or so into Windows.

It's going back to the shop tomorrow.

 

[simon106]

Irene,

I have the exact same PC as you bought from PC world

Computer is a Packard Bell Onetwo L A6524 UK.
AMD Athion II X2 220 dual-core processor
23" multimedia Touch monitor Full HD 1080
4GB DDR3 Memory
1 TB HD
DVD Super Multidrive
NVDIA GeForce 9200 graphics
Software: Windows 7 Home Premium 64 bit

Bought it in December last year so is still in warranty! I've had no issues with this PC until this morning

Woke up this morning went to use PC which to be fair has been powered on for a couple of days (not unusual for me) Moved mouse to wake it up from sleep mode and got a BSOD, after rebooting the machine doesnt even show the BIOS screen just keeps rebooting itself, powered off for a few minutes to cool down but still doesnt start, tried all the usual unplug all USB's etc but hasnt helped!!

From all your above posts does sound like a overheating issue!! Hoping after leaving mine to cool all day it boots up else its going straight back to the shop!! I have lots of data on mine which needs to be backed would temporary removing the HDD void any warranty?

Did you get yours machine replaced in the end?

Thanks

Simon

 

[simon106]

NOTE# No new software or hardware installed on my PC for weeks!! But noticed lots of new Windows Updates 2 days ago!

 

[Irene2011]

Hi Simon: Sorry to hear about your computer.
We eventually took it back to PC World, they sent it to repair, it took a bit over 2 weeks. Got it back on June 30th and on July 8th it started with BSODs again!!!!
We took it back on Sunday, and my husband got a call from them on Tuesday, in which they offered to replace it with a brand new one. My hubbty asked if he could get a different computer even if he had to pay the difference, at which point the technician pretty much admitted that it would probably be a good idea cause it looks like the whole touchscreen thing is not fully invented and causing a great deal of conflicts.
My hubby then went to the shop, paid the difference and got himself a Mac

BTW they never told us what the problem was or what they did the first time to "solve" it.
Hope you get yours sorted without so much hassle. I wouldn't remove the HDD just in case, as i think that might void the warranty.