BSOD when computer is idle or watching movies [moved from XP]

techno king · 05-26-2009, 05:34 AM

I have a ASUS F3F on Windows Xp Home SP3.When i watch movies or leave the computer idle it will go BSOD in just 10-20 minutes.
I have the memory.dmp files but i dont know how to upload them.(i dont really want to upload the files because they are 500mb and i am on a isolated island and on a stric allowence of 3gb)
please email me or reply.

From me
Kelvin

**justpassingby** · 05-26-2009, 06:08 AM

Hi Kelvin and welcome to TSF !

What's the exact model of the Asus F3F laptop ? (something like AP010H for instance)

What's the size of a single .dmp file in the minidump folder ? If a single file is 500MB then right-click my computer => properties => advanced => settings under startup and recovery => under Write debugging information change the setting to small memory dump. Next time the system hangs you'll get a smaller .dmp file (less than 100k). Zip the latest 10 .dmp files and attach them to your next post using the manage attachment button (click on post reply or on go advanced).

If you always get the same message on the BSOD then write it down and post it here.

Go to start => run and type eventvwr.msc. If there are any errors under application or system then double-click the event, click once on the third button on the right then right-click paste the information here.

If the BSOD always happens after a given time it could be an overheating problem. Enter the BIOS at startup and find the hardware monitor screen, report your temps and fan speeds. Is the base of the laptop hot to the touch ? Turn the laptop off and blow some compressed air through the side vent.

I'll move this thread to the laptop support section. I removed you email address since leaving it on an open forum will get you tons of spam in no time.

**CCT** · 05-26-2009, 06:12 AM

With laptops, one of the key issues is air-vent cleanliness.

Are the bottom vents clear of dust?

**justpassingby** · 05-26-2009, 06:26 AM

yep, compressed air does wonders (10$ at your local computer shop)

techno king · 05-26-2009, 06:48 AM

thx for the suggestions i have a AP106D. i have opened the back and have put a cooler under it so it forces air into the mobo. it cant be overheating im sure becuz watching movies is kinda being idle.
P.S the fan screems at me.

**justpassingby** · 05-26-2009, 07:03 AM

Watching movies uses the GPU (video chipset) quite intensively, it used to make my GF's laptop restart. If the fan makes noise it may have caught a dust bunny, cooling the motherboard won't help much if the CPU is overheating, blow some air through it.

Any error messages in the event viewer ? what's the message on the BSOD ? Can you zip and attach your minidump files once you've set the setting to small memory dump ?

techno king · 05-26-2009, 07:32 AM

ill post the dmp files tomarrow and i will clean the heatsink. i have to go to sleep thanks for your support.

techno king · 05-26-2009, 07:36 AM

i Manage to get this.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x1d8fe718, 0x00000002, 0x00000000, 0x804f449e). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

ill boot the computer in normole mode.

techno king · 05-26-2009, 07:38 AM

about the sleeping now. im not going to sleep i thought it was 9.30 my time

techno king · 05-26-2009, 08:19 AM

my comp temps.
Idle Firefox with 11 tabs
HDD0: 31 30
Temp1: 72 72
Core0: 42 60
Core1: 43 60
are these okay?

o Yeah last week i had friends over and we managed to watch 5 eposods family guy without freezing eventurly i went to sleep

**justpassingby** · 05-26-2009, 10:50 AM

c:\windows\memory.dmp is still a full kernel dump, too big to attach it here. Set the setting under startup and recovery to small memory dump (see post #2 here), the files will be saved in c:\windows\minidump\minixxxxxx-xx.dmp.

Where did you get the temps from ? If you used some third party program like speedfan then please enter the BIOS at startup and report the temps from there. Software readings within Windows can be wrong if the program doesn't know the sensors layout (we don't know what temp1 is).

0x0000000A is an IRQL_NOT_LESS_OR_EQUAL error but we need the .dmp file to say more :
You receive a "Stop 0x0000000A" error message in Windows XP

techno king · 05-27-2009, 04:36 AM

http://www.techsupportforum.com/atta...1&d=1243420483
this is the dump files

**jcgriff2** · 06-05-2009, 05:31 AM

Hi -

I ran 29 of the 83 dumps you submitted. I found different bugchecks on some, but most had 0x8e - kernel exception.

All of the dumps indicate the presence of an NT Kernel that cannot be fully identified by the MSDN symbol packages. The most recent dump shows a BSOD on May 25, 2009 and claims to be from an XP SP3 system -

Code:


Debug session time: Mon May 25 02:15:37.265 2009 (GMT-7)
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9d

The NT Kernel (nt) timestamp = 45e53f9d, which translates - Wed Feb 28 00:38:53 2007. XP SP3 RTM should have a Kernel w/ minimum date = April 2008.

The 1st BSOD dump was from an October 2006 BSOD. It shows the same 2007 NT Kernel module as the May 2009 BSOD above, yet this BSOD occurred 5 months before the timestamp found on the NT module and other Microsoft drivers -

Code:




Debug session time:                                Sat Oct 28 15:25:16.250                                2006 (GMT-7)

Debug session time: Sat Oct 28 15:25:16.250 2006 (GMT-7)
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs)  Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
update.sys   Mon Apr 23 03:32:54 2007 (462C8B56)
ntoskrnl.exe Wed Feb 28 01:08:32 2007 (45E54690)
Ntfs.sys     Fri Feb 09 03:10:31 2007 (45CC56A7)
fltMgr.sys   Mon Aug 21 02:14:57 2006 (44E97991)
PxHelp20.sys Tue Jun 06 13:08:29 2006 (4485E0BD)
rdbss.sys    Fri May 05 02:47:55 2006 (445B1F4B)
mrxsmb.sys   Fri May 05 02:41:42 2006 (445B1DD6)
w39n51.sys   Tue Apr 04 03:17:22 2006 (443247B2)
SynTP.sys    Fri Oct 21 14:13:08 2005 (435959E4)
rimmptsk.sys Fri Sep 16 19:01:49 2005 (432B790D)
rimsptsk.sys Tue Sep 13 20:45:23 2005 (43279CD3)
ATKACPI.sys  Thu Feb 17 07:07:46 2005 (4214B342)
HDAudBus.sys Fri Jan 07 17:07:15 2005 (41DF3243)
BTHidMgr.sys Mon Oct 18 22:40:54 2004 (4174A8E6)
ipnat.sys    Wed Sep 29 15:28:36 2004 (415B3714)
vbtenum.sys  Tue Sep 21 03:18:01 2004 (414FFFD9)
btnetdrv.sys Tue Sep 21 03:15:32 2004 (414FFF44)
ATMFD.DLL    Wed Aug 04 00:56:56 2004 (411096C8)
Mup.sys      Tue Aug 03 23:15:20 2004 (41107EF8)
ks.sys       Tue Aug 03 23:15:20 2004 (41107EF8)
netbt.sys    Tue Aug 03 23:14:36 2004 (41107ECC)
i8042prt.sys Tue Aug 03 23:14:36 2004 (41107ECC)
ndiswan.sys  Tue Aug 03 23:14:30 2004 (41107EC6)
NDIS.sys     Tue Aug 03 23:14:27 2004 (41107EC3)
ipsec.sys    Tue Aug 03 23:14:27 2004 (41107EC3)
CLASSPNP.SYS Tue Aug 03 23:14:26 2004 (41107EC2)
raspptp.sys  Tue Aug 03 23:14:26 2004 (41107EC2)
rasl2tp.sys  Tue Aug 03 23:14:21 2004 (41107EBD)
Cdfs.SYS     Tue Aug 03 23:14:09 2004 (41107EB1)
ohci1394.sys Tue Aug 03 23:10:05 2004 (41107DBD)
1394BUS.SYS  Tue Aug 03 23:10:03 2004 (41107DBB)
usbhub.sys   Tue Aug 03 23:08:40 2004 (41107D68)
usbuhci.sys  Tue Aug 03 23:08:34 2004 (41107D62)
USBPORT.SYS  Tue Aug 03 23:08:34 2004 (41107D62)
usbehci.sys  Tue Aug 03 23:08:34 2004 (41107D62)
HIDCLASS.SYS Tue Aug 03 23:08:18 2004 (41107D52)
HIDPARSE.SYS Tue Aug 03 23:08:15 2004 (41107D4F)
TDI.SYS      Tue Aug 03 23:07:47 2004 (41107D33)
mssmbios.sys Tue Aug 03 23:07:47 2004 (41107D33)
pci.sys      Tue Aug 03 23:07:45 2004 (41107D31)
ACPI.sys     Tue Aug 03 23:07:35 2004 (41107D27)
watchdog.sys Tue Aug 03 23:07:32 2004 (41107D24)
vga.sys      Tue Aug 03 23:07:06 2004 (41107D0A)
VIDEOPRT.SYS Tue Aug 03 23:07:04 2004 (41107D08)
sr.sys       Tue Aug 03 23:06:22 2004 (41107CDE)
raspppoe.sys Tue Aug 03 23:05:06 2004 (41107C92)
psched.sys   Tue Aug 03 23:04:16 2004 (41107C60)
msgpc.sys    Tue Aug 03 23:04:11 2004 (41107C5B)
netbios.sys  Tue Aug 03 23:03:19 2004 (41107C27)
ndisuio.sys  Tue Aug 03 23:03:10 2004 (41107C1E)
dxg.sys      Tue Aug 03 23:00:51 2004 (41107B93)
Npfs.SYS     Tue Aug 03 23:00:38 2004 (41107B86)
VolSnap.sys  Tue Aug 03 23:00:14 2004 (41107B6E)
imapi.sys    Tue Aug 03 23:00:12 2004 (41107B6C)
disk.sys     Tue Aug 03 22:59:53 2004 (41107B59)
cdrom.sys    Tue Aug 03 22:59:52 2004 (41107B58)
KSecDD.sys   Tue Aug 03 22:59:45 2004 (41107B51)
atapi.sys    Tue Aug 03 22:59:41 2004 (41107B4D)
PCIIDEX.SYS  Tue Aug 03 22:59:40 2004 (41107B4C)
SCSIPORT.SYS Tue Aug 03 22:59:39 2004 (41107B4B)
redbook.sys  Tue Aug 03 22:59:34 2004 (41107B46)
halmacpi.dll Tue Aug 03 22:59:09 2004 (41107B2D)
termdd.sys   Tue Aug 03 22:58:52 2004 (41107B1C)
swenum.sys   Tue Aug 03 22:58:41 2004 (41107B11)
mouclass.sys Tue Aug 03 22:58:32 2004 (41107B08)
kbdclass.sys Tue Aug 03 22:58:32 2004 (41107B08)
MountMgr.sys Tue Aug 03 22:58:29 2004 (41107B05)

The dump below is from a BSOD that occurred on December 29, 2006. This date falls between the two dumps cited above. It does show an NT Kernel dated Aug 2004, which is XP SP2 -

Code:


Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible

Debug session time: Fri Dec 29 05:10:17.968 2006 (GMT-7)

nt ntkrpamp.exe Tue Aug 03 22:58:37 2004 (41107B0D)

I don't know how a 2007 NT kernel odule shows up 5 months before it's released. One reason SP2 & SP3 being interchanged like it appears to be is memory trouble or kernel corruption. I can say that the system these dumps came from has experienced BSODs since mid 2006.

I see no other alternative at this time - you need to re-format the hard drive and re-install XP using the XP CD. Otherwise you will not know if the BSODs are being caused by hardware or the corrupted XP OS itself.

I also would suggest that you run memtest86+. Burn a bootable ISO CD

memtest86+ http://www.memtest.org/

Regards. . .

jcgriff2

.

.

Bugcheck Summary

Code:


*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Debug session time: Mon May 25 02:15:37.265 2009 (GMT-7)
System Uptime: 0 days 0:18:55.938
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 1000008E, {c0000005, a9b9cb3a, a77307e8, 0}
Probably caused by : ntoskrnl.exe ( nt+f7998 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Debug session time: Mon May 25 01:37:51.890 2009 (GMT-7)
System Uptime: 0 days 0:15:26.563
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 1000008E, {c0000005, a8ef4b3a, a7ab07e8, 0}
Probably caused by : ntoskrnl.exe ( nt+f7998 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Debug session time: Sat May 23 05:10:08.343 2009 (GMT-7)
System Uptime: 0 days 0:11:41.897
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000008E, {c0000005, a9a3cb3a, aa4877e8, 0}
Probably caused by : ntkrnlpa.exe ( nt+f7998 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Debug session time: Fri May 22 02:04:21.109 2009 (GMT-7)
System Uptime: 0 days 0:33:51.792
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000007E, {c0000005, f8318f00, f88da970, f88da66c}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by : pci.sys ( pci!busintrf_Constructor+6 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Debug session time: Thu May 21 00:21:46.515 2009 (GMT-7)
System Uptime: 0 days 1:28:45.188
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000008E, {c0000005, a9c3cb3a, a789d7e8, 0}
Probably caused by : ntkrnlpa.exe ( nt+f7998 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Debug session time: Wed May 20 18:53:15.984 2009 (GMT-7)
System Uptime: 0 days 0:09:25.556
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 50, {bad0b148, 0, 805b9ec9, 2}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by : ntkrnlpa.exe ( nt+e2ec9 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Debug session time: Tue May 19 01:17:49.968 2009 (GMT-7)
System Uptime: 0 days 0:05:22.652
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000008E, {c0000005, a9c3cb3a, a7fa57e8, 0}
Probably caused by : ntkrnlpa.exe ( nt+f7998 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Debug session time: Tue May 19 01:07:24.468 2009 (GMT-7)
System Uptime: 0 days 0:05:32.164
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000008E, {c0000005, a8c8db3a, f86b27e8, 0}
Probably caused by : ntkrnlpa.exe ( nt+f7998 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Debug session time: Mon May 18 23:29:19.171 2009 (GMT-7)
System Uptime: 0 days 0:05:35.871
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000008E, {c0000005, a9acbb3a, a84017e8, 0}
Probably caused by : ntkrnlpa.exe ( nt+f7998 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Debug session time: Sat May 2 22:28:52.281 2009 (GMT-7)
System Uptime: 0 days 1:32:11.961
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000008E, {c0000005, a95f7b3a, a6bf47e8, 0}
Probably caused by : ntkrnlpa.exe ( nt+f7998 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Debug session time: Fri May 1 03:09:27.859 2009 (GMT-7)
System Uptime: 0 days 0:06:00.542
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000008E, {c0000005, a95ebb3a, a78ad7e8, 0}
Probably caused by : ntkrnlpa.exe ( nt+f7998 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Debug session time: Fri May 1 02:58:05.984 2009 (GMT-7)
System Uptime: 0 days 0:12:18.656
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000008E, {c0000005, a95dab3a, a6a987e8, 0}
Probably caused by : ntkrnlpa.exe ( nt+f7998 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Debug session time: Tue Apr 28 04:51:19.343 2009 (GMT-7)
System Uptime: 0 days 0:05:22.023
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000008E, {c0000005, a95f7b3a, a6b907e8, 0}
Probably caused by : ntkrnlpa.exe ( nt+f7998 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Debug session time: Tue Apr 28 04:40:11.609 2009 (GMT-7)
System Uptime: 0 days 0:05:36.285
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000008E, {c0000005, a95f7b3a, a73927e8, 0}
Probably caused by : ntkrnlpa.exe ( nt+f7998 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Debug session time: Tue Apr 28 04:28:49.750 2009 (GMT-7)
System Uptime: 0 days 0:05:40.445
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000008E, {c0000005, a95f7b3a, a76ed7e8, 0}
Probably caused by : ntkrnlpa.exe ( nt+f7998 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Debug session time: Tue Apr 28 04:17:26.885 2009 (GMT-7)
System Uptime: 0 days 10:36:40.123
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck A, {2cc86018, 2, 0, 804f449e}
Probably caused by : ntkrnlpa.exe ( nt+1d49e )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Debug session time: Sun Apr 19 22:03:37.812 2009 (GMT-7)
System Uptime: 0 days 3:54:43.504
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000008E, {c0000005, a9436b3a, a65687e8, 0}
Probably caused by : ntkrnlpa.exe ( nt+f7998 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Debug session time: Tue Feb 10 10:18:40.959 2009 (GMT-7)
System Uptime: 0 days 1:40:59.803
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck A, {656e657f, 2, 0, 804f449e}
Probably caused by : ntkrnlpa.exe ( nt+1d49e )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Debug session time: Wed Dec 10 01:40:26.000 2008 (GMT-7)
System Uptime: 0 days 5:56:44.672
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
*** WARNING: Unable to verify timestamp for dump_wmimmc.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_wmimmc.sys
BugCheck 1000008E, {c0000005, a5cd25ac, a5dbc4fc, 0}
Probably caused by : dump_wmimmc.sys ( dump_wmimmc+5ac )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Debug session time: Mon Nov 24 02:54:18.656 2008 (GMT-7)
System Uptime: 0 days 2:15:24.338
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 50, {e3109104, 0, bf35ce85, 1}
*** WARNING: Unable to verify timestamp for igxpdx32.DLL
*** ERROR: Module load completed but symbols could not be loaded for igxpdx32.DLL
Probably caused by : igxpdx32.DLL ( igxpdx32+190e85 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Debug session time: Wed Nov 19 04:02:44.500 2008 (GMT-7)
System Uptime: 0 days 10:55:46.173
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck CB, {a5ab9356, a5ab9508, fe6ca610, 1d}
*** WARNING: Unable to verify timestamp for dump_wmimmc.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_wmimmc.sys
Probably caused by : dump_wmimmc.sys ( dump_wmimmc+2356 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Debug session time: Sun Nov 2 01:53:52.859 2008 (GMT-7)
System Uptime: 0 days 0:11:16.557
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 50, {e3561104, 0, bf35eca1, 1}
*** WARNING: Unable to verify timestamp for igxpdx32.DLL
*** ERROR: Module load completed but symbols could not be loaded for igxpdx32.DLL
Probably caused by : igxpdx32.DLL ( igxpdx32+192ca1 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Debug session time: Wed Oct 17 16:41:23.609 2007 (GMT-7)
System Uptime: 0 days 5:12:56.291
*** WARNING: Unable to verify timestamp for ialmdev5.DLL
*** ERROR: Module load completed but symbols could not be loaded for ialmdev5.DLL
BugCheck EA, {fefb3b90, fecc9cc0, 8149b468, 1}
Probably caused by : ialmdev5.DLL ( ialmdev5+1e7d2 )
PROCESS_NAME: explorer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Debug session time: Tue Jun 19 03:03:25.406 2007 (GMT-7)
System Uptime: 0 days 2:35:07.097
BugCheck A, {825cc60c, 2, 0, 80500317}
Probably caused by : memory_corruption ( nt!MiDeleteValidAddress+44 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Debug session time: Sun Feb 18 01:15:51.481 2007 (GMT-7)
System Uptime: 0 days 1:55:16.222
*** WARNING: Unable to verify timestamp for ialmdev5.DLL
*** ERROR: Module load completed but symbols could not be loaded for ialmdev5.DLL
BugCheck EA, {820c66c0, 82025600, 822ff630, 1}
*** WARNING: Unable to verify timestamp for ialmdnt5.dll
*** ERROR: Module load completed but symbols could not be loaded for ialmdnt5.dll
*** WARNING: Unable to verify timestamp for ialmrnt5.dll
*** ERROR: Module load completed but symbols could not be loaded for ialmrnt5.dll
Probably caused by : ialmdev5.DLL ( ialmdev5+1ea79 )
PROCESS_NAME: explorer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Debug session time: Fri Dec 29 05:10:17.968 2006 (GMT-7)
System Uptime: 0 days 0:02:53.668
BugCheck 1000007F, {8, f8703d70, 0, 0}
Probably caused by : CSDriver.sys
PROCESS_NAME: System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Debug session time: Sat Oct 28 15:25:16.250 2006 (GMT-7)
System Uptime: 0 days 1:49:39.878
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck A, {17fe0b0, 2, 0, 8050f9f6}
Probably caused by : ntoskrnl.exe ( nt+389f6 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 
`

+                                SysInternals •                                BSOD Bugchecks •                                MediaFire •                                Belarc •                                MSTechNet •                                MS NTDE/CPR •                                S/U V2 
                               MSDN Err Cds •                                Everest Hm •                                CCleaner •                                                               Memtest86+ •                                TreeSize Pro Trial •                                MS Help & Support •                                PC Wizard •                                KillDisk •                                PC Wizard •                                ImgBurn •                                                               T Mirco RT 
                               Live SysInternals •                                Auslogics Defrag •                                McAfee RT •                                Norton RT •                                Kaspersky RT •                                MS One Care RT•                                AVG8 •                                ESET NOD32 Trial •                                RT

05-26-2009, 05:34 AM	#1 (permalink)
techno king Registered User Join Date: May 2009 Posts: 7 OS: Win XP	BSOD when computer is idle or watching movies [moved from XP] I have a ASUS F3F on Windows Xp Home SP3.When i watch movies or leave the computer idle it will go BSOD in just 10-20 minutes. I have the memory.dmp files but i dont know how to upload them.(i dont really want to upload the files because they are 500mb and i am on a isolated island and on a stric allowence of 3gb) please email me or reply. From me Kelvin Last edited by justpassingby; 05-26-2009 at 05:55 AM. Reason: removed email to prevent spam

05-26-2009, 06:08 AM	#2 (permalink)
justpassingby Moderator, Microsoft Support Join Date: Mar 2007 Location: Belgium Posts: 6,219 OS: XP Home SP3 / Ubuntu My System	Re: BSOD when computer is idle or watching movies Hi Kelvin and welcome to TSF ! What's the exact model of the Asus F3F laptop ? (something like AP010H for instance) What's the size of a single .dmp file in the minidump folder ? If a single file is 500MB then right-click my computer => properties => advanced => settings under startup and recovery => under Write debugging information change the setting to small memory dump. Next time the system hangs you'll get a smaller .dmp file (less than 100k). Zip the latest 10 .dmp files and attach them to your next post using the manage attachment button (click on post reply or on go advanced). If you always get the same message on the BSOD then write it down and post it here. Go to start => run and type eventvwr.msc. If there are any errors under application or system then double-click the event, click once on the third button on the right then right-click paste the information here. If the BSOD always happens after a given time it could be an overheating problem. Enter the BIOS at startup and find the hardware monitor screen, report your temps and fan speeds. Is the base of the laptop hot to the touch ? Turn the laptop off and blow some compressed air through the side vent. I'll move this thread to the laptop support section. I removed you email address since leaving it on an open forum will get you tons of spam in no time. __________________ Malware removal steps. Post your logs there and not here ! Posting system specs

05-26-2009, 06:12 AM	#3 (permalink)
CCT Helper Join Date: Mar 2009 Location: Canada Posts: 1,869 OS: XP SP3, XP Pro SP3, Vista Home Basic SP2	Re: BSOD when computer is idle or watching movies [moved from XP] With laptops, one of the key issues is air-vent cleanliness. Are the bottom vents clear of dust? __________________ ..... caveat utilitor

05-26-2009, 06:26 AM	#4 (permalink)
justpassingby Moderator, Microsoft Support Join Date: Mar 2007 Location: Belgium Posts: 6,219 OS: XP Home SP3 / Ubuntu My System	Re: BSOD when computer is idle or watching movies [moved from XP] yep, compressed air does wonders (10$ at your local computer shop) __________________ Malware removal steps. Post your logs there and not here ! Posting system specs

05-26-2009, 06:48 AM	#5 (permalink)
techno king Registered User Join Date: May 2009 Posts: 7 OS: Win XP	Re: BSOD when computer is idle or watching movies [moved from XP] thx for the suggestions i have a AP106D. i have opened the back and have put a cooler under it so it forces air into the mobo. it cant be overheating im sure becuz watching movies is kinda being idle. P.S the fan screems at me.

05-26-2009, 07:03 AM	#6 (permalink)
justpassingby Moderator, Microsoft Support Join Date: Mar 2007 Location: Belgium Posts: 6,219 OS: XP Home SP3 / Ubuntu My System	Re: BSOD when computer is idle or watching movies [moved from XP] Watching movies uses the GPU (video chipset) quite intensively, it used to make my GF's laptop restart. If the fan makes noise it may have caught a dust bunny, cooling the motherboard won't help much if the CPU is overheating, blow some air through it. Any error messages in the event viewer ? what's the message on the BSOD ? Can you zip and attach your minidump files once you've set the setting to small memory dump ? __________________ Malware removal steps. Post your logs there and not here ! Posting system specs

05-26-2009, 07:32 AM	#7 (permalink)
techno king Registered User Join Date: May 2009 Posts: 7 OS: Win XP	Re: BSOD when computer is idle or watching movies [moved from XP] ill post the dmp files tomarrow and i will clean the heatsink. i have to go to sleep thanks for your support.

05-26-2009, 07:36 AM	#8 (permalink)
techno king Registered User Join Date: May 2009 Posts: 7 OS: Win XP	Re: BSOD when computer is idle or watching movies [moved from XP] i Manage to get this. The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x1d8fe718, 0x00000002, 0x00000000, 0x804f449e). A dump was saved in: C:\WINDOWS\MEMORY.DMP. ill boot the computer in normole mode.

05-26-2009, 07:38 AM	#9 (permalink)
techno king Registered User Join Date: May 2009 Posts: 7 OS: Win XP	Re: BSOD when computer is idle or watching movies [moved from XP] about the sleeping now. im not going to sleep i thought it was 9.30 my time

05-26-2009, 08:19 AM	#10 (permalink)
techno king Registered User Join Date: May 2009 Posts: 7 OS: Win XP	Re: BSOD when computer is idle or watching movies [moved from XP] my comp temps. Idle Firefox with 11 tabs HDD0: 31 30 Temp1: 72 72 Core0: 42 60 Core1: 43 60 are these okay? o Yeah last week i had friends over and we managed to watch 5 eposods family guy without freezing eventurly i went to sleep

05-26-2009, 10:50 AM	#11 (permalink)
justpassingby Moderator, Microsoft Support Join Date: Mar 2007 Location: Belgium Posts: 6,219 OS: XP Home SP3 / Ubuntu My System	Re: BSOD when computer is idle or watching movies [moved from XP] c:\windows\memory.dmp is still a full kernel dump, too big to attach it here. Set the setting under startup and recovery to small memory dump (see post #2 here), the files will be saved in c:\windows\minidump\minixxxxxx-xx.dmp. Where did you get the temps from ? If you used some third party program like speedfan then please enter the BIOS at startup and report the temps from there. Software readings within Windows can be wrong if the program doesn't know the sensors layout (we don't know what temp1 is). 0x0000000A is an IRQL_NOT_LESS_OR_EQUAL error but we need the .dmp file to say more : You receive a "Stop 0x0000000A" error message in Windows XP __________________ Malware removal steps. Post your logs there and not here ! Posting system specs Last edited by justpassingby; 05-26-2009 at 10:52 AM.