Help me please..BSOD problem again..

[tressele]

Hello..can please somebody take a look at my dump file..i didn't know the exact problem of my eepc..i hope forummers here can help me solving my problem..

sorry for my bad english..

 

[zigzag3143]

Hello..can please somebody take a look at my dump file..i didn't know the exact problem of my eepc..i hope forummers here can help me solving my problem..

sorry for my bad english..

This one was caused by your synatpics touchpad driver. I would download and install a fresh copy

Ken

Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun May 30 11:35:16.951 2010 (GMT-4)
System Uptime: 0 days 0:44:46.748
BugCheck D1, {f6cd2e0, 7, 0, 8b223756}
*** WARNING: Unable to verify timestamp for SynTP.sys
*** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
Probably caused by :Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun May 30 11:35:16.951 2010 (GMT-4)
System Uptime: 0 days 0:44:46.748
BugCheck D1, {f6cd2e0, 7, 0, 8b223756}
*** WARNING: Unable to verify timestamp for SynTP.sys
*** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
Probably caused by : SynTP.sys ( SynTP+3756 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System ( SynTP+3756 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System

 

[tressele]

but if i'm not mistaken, i downloaded it from asus website..so what is the best way to solve it? which source should i re-download that driver? or just reinstall it again using the same installer?

 

[zigzag3143]

but if i'm not mistaken, i downloaded it from asus website..so what is the best way to solve it? which source should i re-download that driver? or just reinstall it again using the same installer?

I would go to synaptic for the latest driver.

 

[tressele]

ok..i'll give a try first..thanks for your help..

 

[tressele]

I tried to re-install my touchpad driver from original source..but unluckily this BSOD happened again. I'm not sure whether this is the same error again. So would somebody please take a look at my minidump file and help me counter this problem?

 

[usasma]

From thread located here: http://www.sevenforums.com/crashes-debugging/89163-bsod-keep-occured-please-help.html

BSOD keep occured..please help..
Hello all friends..

I had posted a thread regarding same issues and follow the suggestion given.
I tried to re-install my touchpad driver from original source..but unluckily this BSOD happened again. I'm not sure whether this is the same error again but it happened everyday. So would somebody please take a look at my minidump file and help me counter this problem?

Attached Files

Minidump.rar (113.3 KB, 0 views)

My response will follow shortly...

 

[usasma]

5 memory dumps from 30 May 2010 to 03 Jun 2010 (5 days)
4 different STOP errors, blaming at least 3 different causes

This may be indicative of a hardware problem - but it's too soon to tell.

But, there are also some indications that Driver Verifier might give us some more info here. So please run it according to these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Summary of the BSOD's:

Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Wed Jun  2 19:41:01.590 2010 (GMT-4)
System Uptime: 0 days 0:06:11.277
BugCheck A, {28, 2, 1, 8184c0e9}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+1ed )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Wed Jun  2 07:40:44.666 2010 (GMT-4)
System Uptime: 0 days 1:15:46.353
BugCheck A, {c080ba9c, 0, 0, 818bb435}
Probably caused by : memory_corruption ( nt!MiUpdateWsle+1ab )
BUGCHECK_STR:  0xA
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun  1 12:02:17.314 2010 (GMT-4)
System Uptime: 0 days 2:40:23.001
BUGCHECK_STR:  0x50
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun  1 09:21:39.769 2010 (GMT-4)
System Uptime: 0 days 1:11:16.581
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun May 30 11:35:16.951 2010 (GMT-4)
System Uptime: 0 days 0:44:46.748
BugCheck D1, {f6cd2e0, 7, 0, 8b223756}
*** WARNING: Unable to verify timestamp for SynTP.sys
*** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
Probably caused by : SynTP.sys ( SynTP+3756 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System

 

[tressele]

Ok..i had done setting the verifier..now waiting the windows to crash..but from the procedure above stated that i have to continue using the system normally after crash,so how many time should i let the system crash before posting the memory dump file? And how to know what is the cause of the crash that should i do repeatedly?

I am very sorry because i was not really good in this..

 

[usasma]

Use the system normally for about 36 hours (an estimate on my part) - or until you get a crash.
Upload the memory dump so we can analyze it.
If it shows a Driver Verifier enabled crash, then you can turn the Driver Verifier off.
If you do not get a crash within 36 hours, turn off Driver Verifier anyway - and let us know.

 

[tressele]

hello..
sorry for late reply...this is the dump file that i got after activating the verifier..please advice me..tq..

 

[usasma]

Don't forget to turn Driver Verifier off.

This blames your Intel graphics drivers and the DX drivers
In short, it's either the driver - or it's a physical problem with the video card.

But, there's an instance of ACPI.sys in the stack text just before the crash occurred.
Asus systems/mobo's have some issues with ACPI.sys at times - what is the exact make and model of your Asus product?

Also, please check Device Manager for any devices that aren't functioning properly. Let us know what you find.

I would uninstall your video drivers and then download a fresh copy from the Intel website ( http://downloadcenter.intel.com ) and install it.

Summary of the BSOD:

Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Wed Jun  9 07:41:22.686 2010 (GMT-4)
System Uptime: 0 days 0:00:11.374
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BUGCHECK_STR:  0xc9_c
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System

 

[tressele]

ok i will try to reinstall my video driver just as your advice to..

I am using Asus EEPC 1005P netbook..

As far as i concern..seems like i can't find any malfunctioning drivers after checking them in the Device Manager.

i will proceed with the video driver first and see whether it works or not..

TQ again USASMA..

 

[tressele]

i think i am unlucky guy..BSOD happened again just now..this is the dump file..
please help....

 

[usasma]

Sometimes there's more than one problem. Or, if it's a hardware issue, it'll take a while to reach that conclusion.

This one blames your Avira Anti-Vir.

Please do the following:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Avira Anti-Vir from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Avira Anti-Vir using this free tool: Avira Solutions - Knowledge Base Problem Details
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

Then we wait to see if there's another BSOD (which may mean that there is a hardware problem).

Summary of the BSOD:

Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Thu Jun 10 08:56:52.726 2010 (GMT-4)
System Uptime: 0 days 0:02:25.538
*** WARNING: Unable to verify timestamp for avgntflt.sys
*** ERROR: Module load completed but symbols could not be loaded for avgntflt.sys
BUGCHECK_STR:  0x8E
PROCESS_NAME:  sched.exe

 

[tressele]

ok..this is the latest dump file that happened after all your instructions above followed..wondering what was wrong with my netbook...sigh..

 

[zigzag3143]

ok..this is the latest dump file that happened after all your instructions above followed..wondering what was wrong with my netbook...sigh..

This one still points to memory corruption. I would retest using memtestx86, burn it to cd, and run it for at least 7 passes.


Ken

Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Thu Jun 10 22:44:25.407 2010 (GMT-4)
System Uptime: 0 days 3:01:32.219
BugCheck A, {14, 2, 0, 818e95f1}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+5 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe

 

[tressele]

please lead me the way..i didn't know what is memtestx86 precisely..besides,i'm using netbook..so there is no dvd drives..can i use my pendrive and make it bootable?

 

[tressele]

hye..i figured out how to do the memtest86 and after done it for 9 pass,there is no error showed in the result..

 

[Jonathan_King]

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

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


Loading Dump File [C:\Users\Jonathan\Desktop\New folder (2)\061110-20826-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 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x81855000 PsLoadedModuleList = 0x8199d810
Debug session time: Thu Jun 10 22:44:25.407 2010 (GMT-4)
System Uptime: 0 days 3:01:32.219
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {14, 2, 0, 818e95f1}

Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+5 )

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

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

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 819bd718
Unable to read MiSystemVaType memory at 8199d160
 00000014 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiFindNodeOrParent+5
818e95f1 f7401400ffffff  test    dword ptr [eax+14h],0FFFFFF00h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  a198a694 -- (.trap 0xffffffffa198a694)
ErrCode = 00000000
eax=00000000 ebx=83d98030 ecx=00000000 edx=00000000 esi=83d98030 edi=807eb120
eip=818e95f1 esp=a198a708 ebp=a198a708 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!MiFindNodeOrParent+0x5:
818e95f1 f7401400ffffff  test    dword ptr [eax+14h],0FFFFFF00h ds:0023:00000014=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 818e95f1 to 8189b82b

STACK_TEXT:  
a198a694 818e95f1 badb0d00 00000000 a198a6b4 nt!KiTrap0E+0x2cf
a198a708 818eb04c a198a71c a198a734 818f061e nt!MiFindNodeOrParent+0x5
a198a714 818f061e 00000000 83d98008 83d98078 nt!MiLocateAddressInTree+0x11
a198a734 818e1843 83d98008 00000000 00000000 nt!MiGetSharedProtos+0x5d
a198a754 8188d19a aba04c90 8305431c 83054324 nt!MiComputeStartingOffset+0x61
a198a798 8188d562 83f46e50 83f46000 a198a83c nt!MiIdentifyPfn+0x29e
a198a7c0 81a7144a 00f46060 b8a1733f a198a850 nt!MmQueryPfnList+0xa6
a198a808 81a91e21 00000001 b8a173bf 00000000 nt!PfpPfnPrioRequest+0xde
a198a888 81a8a865 00000000 00000001 a198acd0 nt!PfQuerySuperfetchInformation+0xea
a198ad00 81a8b4cc 0000004f 00000000 00000000 nt!ExpQuerySystemInformation+0x24ce
a198ad1c 8189844a 0000004f 012def50 00000014 nt!NtQuerySystemInformation+0x76
a198ad1c 773864f4 0000004f 012def50 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
012dce10 00000000 00000000 00000000 00000000 0x773864f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiFindNodeOrParent+5
818e95f1 f7401400ffffff  test    dword ptr [eax+14h],0FFFFFF00h

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiFindNodeOrParent+5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cacf

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiFindNodeOrParent+5

BUCKET_ID:  0xA_nt!MiFindNodeOrParent+5

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

1: kd> lmsmn
start    end        module name
81fb2000 81ffa000   ACPI     ACPI.sys    
8a02a000 8a084000   afd      afd.sys     
8af25000 8af37000   AgileVpn AgileVpn.sys
862e0000 862e9000   amdxata  amdxata.sys 
8a026000 8a027080   AsUpIO   AsUpIO.sys  
8629c000 862a5000   atapi    atapi.sys   
862a5000 862c8000   ataport  ataport.SYS 
8ac65000 8ad92000   athr     athr.sys    
8aed2000 8af0b000   av73370o av73370o.SYS
81e00000 81e0b000   BATTC    BATTC.SYS   
86987000 8698e000   Beep     Beep.SYS    
8a018000 8a026000   blbdrive blbdrive.sys
81ebd000 81ec5000   BOOTVID  BOOTVID.dll 
a20af000 a20c8000   bowser   bowser.sys  
a45e3000 a45f0000   BthEnum  BthEnum.sys 
a2000000 a201b000   bthpan   bthpan.sys  
a2184000 a21e8000   bthport  bthport.sys 
a45ad000 a45bf000   BTHUSB   BTHUSB.sys  
a45a3000 a45ac180   btusbflt btusbflt.sys
8c7d0000 8c7ee000   cdd      cdd.dll     
8beef000 8bf0e000   cdrom    cdrom.sys   
81f07000 81fb2000   CI       CI.dll      
86909000 8692e000   CLASSPNP CLASSPNP.SYS
81ec5000 81f07000   CLFS     CLFS.SYS    
8af0b000 8af0e700   CmBatt   CmBatt.sys  
86598000 865f5000   cng      cng.sys     
861f6000 861fe000   compbatt compbatt.sys
8af18000 8af25000   CompositeBus CompositeBus.sys
8bf0e000 8bf1b000   crashdmp crashdmp.sys
8a188000 8a1ec000   csc      csc.sys     
8a000000 8a018000   dfsc     dfsc.sys    
8a17c000 8a188000   discache discache.sys
868f8000 86909000   disk     disk.sys    
8bed6000 8beef000   drmk     drmk.sys    
8bf1b000 8bf26000   dump_dumpata dump_dumpata.sys
8bf30000 8bf41000   dump_dumpfve dump_dumpfve.sys
8bf26000 8bf30000   dump_msahci dump_msahci.sys
8bf41000 8bf4b000   Dxapi    Dxapi.sys   
8a721000 8a7d8000   dxgkrnl  dxgkrnl.sys 
8ac0d000 8ac46000   dxgmms1  dxgmms1.sys 
8d430000 8d4f0000   eamonm   eamonm.sys  
8698e000 869ad000   ehdrv    ehdrv.sys   
a216b000 a2184000   epfwwfpr epfwwfpr.sys
a4579000 a45a3000   fastfat  fastfat.SYS 
8631d000 8632e000   fileinfo fileinfo.sys
862e9000 8631d000   fltmgr   fltmgr.sys  
8640e000 86417000   Fs_Rec   Fs_Rec.sys  
868c6000 868f8000   fvevol   fvevol.sys  
867b0000 867e1000   fwpkclnt fwpkclnt.sys
8181e000 81855000   hal      halmacpi.dll
8ac46000 8ac65000   HDAudBus HDAudBus.sys
8be57000 8bea7000   HdAudio  HdAudio.sys 
a202a000 a20af000   HTTP     HTTP.sys    
868be000 868c6000   hwpolicy hwpolicy.sys
8ae67000 8ae7f000   i8042prt i8042prt.sys
8a219000 8a721000   igdkmd32 igdkmd32.sys
8a1ec000 8a1fe000   intelppm intelppm.sys
8ae7f000 8ae8c000   kbdclass kbdclass.sys
81714000 8171c000   kdcom    kdcom.dll   
8adb7000 8adeb000   ks       ks.sys      
86585000 86598000   ksecdd   ksecdd.sys  
86642000 86667000   ksecpkg  ksecpkg.sys 
8ad9c000 8adac000   L1C62x86 L1C62x86.sys
8d50a000 8d51a000   lltdio   lltdio.sys  
8bf91000 8bfac000   luafv    luafv.sys   
81e34000 81eac000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll
8bf4b000 8bf56000   monitor  monitor.sys 
8aec5000 8aed2000   mouclass mouclass.sys
86286000 8629c000   mountmgr mountmgr.sys
a20c8000 a20da000   mpsdrv   mpsdrv.sys  
a20da000 a20fd000   mrxsmb   mrxsmb.sys  
a20fd000 a2138000   mrxsmb10 mrxsmb10.sys
a2138000 a2153000   mrxsmb20 mrxsmb20.sys
862c8000 862d2000   msahci   msahci.sys  
86800000 8680b000   Msfs     Msfs.SYS    
861d2000 861da000   msisadrv msisadrv.sys
8655a000 86585000   msrpc    msrpc.sys   
8a172000 8a17c000   mssmbios mssmbios.sys
868ae000 868be000   mup      mup.sys     
8632e000 863e5000   ndis     ndis.sys    
8af4f000 8af5a000   ndistapi ndistapi.sys
8d560000 8d570000   ndisuio  ndisuio.sys 
8af5a000 8af7c000   ndiswan  ndiswan.sys 
8be46000 8be57000   NDProxy  NDProxy.SYS 
8a0f6000 8a104000   netbios  netbios.sys 
8a084000 8a0b6000   netbt    netbt.sys   
86604000 86642000   NETIO    NETIO.SYS   
8680b000 86819000   Npfs     Npfs.SYS    
8a168000 8a172000   nsiproxy nsiproxy.sys
81855000 81c65000   nt       ntkrpamp.exe
8642b000 8655a000   Ntfs     Ntfs.sys    
86980000 86987000   Null     Null.SYS    
8d51a000 8d560000   nwifi    nwifi.sys   
8a0c6000 8a0e5000   pacer    pacer.sys   
861e5000 861f6000   partmgr  partmgr.sys 
86000000 8602a000   pci      pci.sys     
862d2000 862e0000   PCIIDEX  PCIIDEX.SYS 
86400000 8640e000   pcw      pcw.sys     
a440a000 a44a1000   peauth   peauth.sys  
8bea7000 8bed6000   portcls  portcls.sys 
81eac000 81ebd000   PSHED    PSHED.dll   
8af37000 8af4f000   rasl2tp  rasl2tp.sys 
8af7c000 8af94000   raspppoe raspppoe.sys
8af94000 8afab000   raspptp  raspptp.sys 
8afab000 8afc2000   rassstp  rassstp.sys 
8a127000 8a168000   rdbss    rdbss.sys   
8afc2000 8afcc000   rdpbus   rdpbus.sys  
869e7000 869ef000   RDPCDD   RDPCDD.sys  
869ef000 869f7000   rdpencdd rdpencdd.sys
869f7000 869ff000   rdprefmp rdprefmp.sys
86881000 868ae000   rdyboost rdyboost.sys
a45bf000 a45e3000   rfcomm   rfcomm.sys  
8d570000 8d583000   rspndr   rspndr.sys  
861ac000 861d2000   SCSIPORT SCSIPORT.SYS
a44a1000 a44ab000   secdrv   secdrv.SYS  
86879000 86881000   spldr    spldr.sys   
860b0000 861a3000   sptd     sptd.sys    
a4528000 a4579000   srv      srv.sys     
a44d9000 a4528000   srv2     srv2.sys    
a44ab000 a44cc000   srvnet   srvnet.sys  
8afcc000 8afcd380   swenum   swenum.sys  
8ae8c000 8aec2380   SynTP    SynTP.sys   
86667000 867b0000   tcpip    tcpip.sys   
a44cc000 a44d9000   tcpipreg tcpipreg.sys
86961000 8696c000   TDI      TDI.SYS     
86819000 86830000   tdx      tdx.sys     
8a117000 8a127000   termdd   termdd.sys  
8c7a0000 8c7a9000   TSDDD    TSDDD.dll   
86200000 86221000   tunnel   tunnel.sys  
8afce000 8afdc000   umbus    umbus.sys   
8bf56000 8bf6d000   usbccgp  usbccgp.sys 
8aec3000 8aec4700   USBD     USBD.SYS    
8ae58000 8ae67000   usbehci  usbehci.sys 
8be02000 8be46000   usbhub   usbhub.sys  
8ae0d000 8ae58000   USBPORT  USBPORT.SYS 
8adac000 8adb7000   usbuhci  usbuhci.sys 
8bf6d000 8bf90b00   usbvideo usbvideo.sys
861da000 861e5000   vdrvroot vdrvroot.sys
869ad000 869b9000   vga      vga.sys     
869b9000 869da000   VIDEOPRT VIDEOPRT.SYS
867e1000 867ea000   vmstorfl vmstorfl.sys
81e0b000 81e1b000   volmgr   volmgr.sys  
8623b000 86286000   volmgrx  volmgrx.sys 
8683a000 86879000   volsnap  volsnap.sys 
8ad92000 8ad9c000   vwifibus vwifibus.sys
8a0e5000 8a0f6000   vwififlt vwififlt.sys
8a104000 8a117000   wanarp   wanarp.sys  
869da000 869e7000   watchdog watchdog.sys
86031000 860a2000   Wdf01000 Wdf01000.sys
860a2000 860b0000   WDFLDR   WDFLDR.SYS  
8a0bf000 8a0c6000   wfplwf   wfplwf.sys  
8c540000 8c78a000   win32k   win32k.sys  
8af0f000 8af18000   wmiacpi  wmiacpi.sys 
861a3000 861ac000   WMILIB   WMILIB.SYS  
8a0b6000 8a0bf000   ws2ifsl  ws2ifsl.sys 
8d4f0000 8d50a000   WudfPf   WudfPf.sys  

Unloaded modules:
a2153000 a216b000   parport.sys
8692e000 8693b000   crashdmp.sys
8693b000 86946000   dump_pciidex
86946000 86950000   dump_msahci.
86950000 86961000   dump_dumpfve
86961000 86980000   cdrom.sys

I suspect that is what was causing the issues.