I Keep getting BSOD on my Windows 7 Starter netbook

Have you tried system restore?

Please upload your minidump files:
https://www.sevenforums.com/crash-loc...d-problem.html

if you don't see any files in minidump folder, follow this instruction to enable system to create minidump files:

Windows 7:
Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that "Automatically restart" is unchecked
Under the Write Debugging Information header select "Small memory dump (64 kB)" in the dropdown box
Ensure that the Small Dump Directory is listed as "%systemroot%\Minidump" (without the quotes)
Click OK twice to exit the dialogs, then reboot for the changes to take effect.

Let us know if you need help
Tuan

Please upload your dump files; don't link to them - https://www.sevenforums.com/tutorials...en-forums.html

We will be glad to review them and offer help.

Thanks for uploading the dump file. You have a stop error code of 44.

STOP 0x00000044: MULTIPLE_IRP_COMPLETE_REQUESTS

Usual causes: Device driver(s)

The dmp file indicates that pctgntdi.sys is the probable cause.

Code:

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


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

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x81c50000 PsLoadedModuleList = 0x81d98810
Debug session time: Sun Jun 27 21:35:21.664 2010 (GMT-4)
System Uptime: 0 days 0:12:48.464
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
..........
0: kd> !analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 44, {83fb69b0, eae, 0, 0}

Probably caused by : pctgntdi.sys ( pctgntdi+c465 )

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

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

MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed.  This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened.  Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it.  The
first actually works, and the second fails.  Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second.  However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: 83fb69b0, Address of the IRP
Arg2: 00000eae
Arg3: 00000000
Arg4: 00000000

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


IRP_ADDRESS:  83fb69b0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x44

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 8b7a2465 to 81cb8ebd

STACK_TEXT:  
89447964 8b7a2465 844a2b93 844a2a48 00000000 nt!IopfCompleteRequest+0x4b0
WARNING: Stack unwind information not available. Following frames may be wrong.
8944797c 81cb8b33 8579c930 844a2a48 843715b8 pctgntdi+0xc465
894479c4 8b77a8c7 873d82c0 842965f0 80000804 nt!IopfCompleteRequest+0x128
894479e0 8884845b 004a2a88 00000000 842965f0 tdx!TdxConnectConnectionTlRequestComplete+0x185
89447a3c 88841cb1 842965f0 00000000 89447ad0 tcpip!TcpCreateAndConnectTcbComplete+0x5b8
89447a4c 8885b119 842965f0 00000000 89447bb0 tcpip!TcpSynchronizeTcbDelivery+0x28
89447ad0 8886b5dc 8551b008 842965f0 89447af8 tcpip!TcpTcbCarefulDatagram+0x484
89447b3c 8886b8fc 8551b008 842965f0 01447bb0 tcpip!TcpTcbReceive+0x228
89447ba4 8885aab0 854f14e0 845b8480 00000000 tcpip!TcpMatchReceive+0x237
89447bf4 8885a812 8551b008 845b8480 0000571b tcpip!TcpPreValidatedReceive+0x293
89447c10 888601d3 8551b008 845b8480 89447c4c tcpip!TcpReceive+0x2d
89447c20 8889248e 89447c34 c000023e 00000000 tcpip!TcpNlClientReceiveDatagrams+0x12
89447c4c 88892251 888f1f88 89447ca0 c000023e tcpip!IppDeliverListToProtocol+0x49
89447c6c 88891f26 888f1d98 00000006 89447ca0 tcpip!IppProcessDeliverList+0x2a
89447cc4 8884d872 888f1d98 00000006 8551cd18 tcpip!IppReceiveHeaderBatch+0x1f2
89447cec 81e707fd 854e2d88 008f1d98 83e76020 tcpip!IppLoopbackTransmit+0x52
89447d00 81cbdf3b 8551cd18 00000000 83e76020 nt!IopProcessWorkItem+0x23
89447d50 81e5e6bb 00000001 a804499e 00000000 nt!ExpWorkerThread+0x10d
89447d90 81d100f9 81cbde2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
pctgntdi+c465
8b7a2465 ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  pctgntdi+c465

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: pctgntdi

IMAGE_NAME:  pctgntdi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b6b12fb

FAILURE_BUCKET_ID:  0x44_pctgntdi+c465

BUCKET_ID:  0x44_pctgntdi+c465

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

You also have some outdated drivers running. Win7 does not like older drivers and they can cause conflicts.

amdxata.sys Tue May 19 13:57:35 2009 (4A12F30F)
iaStor.sys Thu Jun 04 21:42:33 2009 (4A287809)
ssmdrv.sys Tue May 05 06:05:18 2009 (4A000F5E)
tmactmon.sys Wed Jul 01 08:16:47 2009 (4A4B53AF)
tmcomm.sys Wed Jul 01 08:16:40 2009 (4A4B53A8)
tmevtmgr.sys Wed Jul 01 08:16:41 2009 (4A4B53A9)

What anti-virus program are you running?

pctgntdi.sys is a PC Tools Generic TDI Driver. Since this driver is listed as a probable cause, I recommend that you uninstall PCTools. Go to the PCTools website and download their uninstall tool.

Next I recommend that you update the drivers above.

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Post back with your results.

You may have to refresh your page since I edited the post above.

Third party tools are not necessary with Win 7. This OS is totally different than XP and very different from Vista. Win 7 is very efficient at managing itself. There are no programs out there that increase the performance of Win 7. At best, these programs do nothing and at worst, they can actually degrade your system and slow it down.

I agree with you about uninstalling Trend Micro Security. I suggest you go to their website and download their uninstall tool. I suggest that for an AV program, you install MSE while we are troubleshooting.

Unless your BSOD occurred prior to your installing PC Tools, that driver is still loading. You will need to use the removal tool if that is the case. Let me know on this.