BSOD when running memory intensive apps

[cornc5]

Hi, when running memory certain intensive applications like VLC (when watching videos) or uTorrent, I intermitentley get BSOD crashes (screen shot below), which can happen every 10 minutes to several hours apart.

Basic System Info:
Windows 7 x64 Ultimate Service Pack 1
Full Retail Version
Original OS installed on my bootcamp partition
System is about 3 years old
The OS was recently installed (last two weeks or so) on the Hard Drive from an image file/backup of a year old build from a previous hard drive that was physically damaged/dropped but had otherwise been working fine.

Thanks in advance for any help/guidance

 

[staticx57]

If you have time to spare I would test your ram with memtest86. If everything passes then report back but if you start getting errors then test each stick individually to narrow down which is/are bad.

 

[cornc5]

Thanks, I started the memtest early this morning, when I left for work it was about halfway through the second pass with no errors so far, but I let it keep running and will post an update when I get home tonight.

 

[staticx57]

I am going to assume you don't get any errors on your RAM. That is good news as it is most likely software. Are all your drivers updated?

 

[cornc5]

It ran 8 passes and found no errors. As far as I can tell everything is up to date, I've had widows check for new drivers and double check most of the major components with their manufacturer websites. I know there's got to be a conflict somewhere but I don't now how to spot or find it.

 

[cornc5]

I have narrowed this down a little more and it seems to only happen when I am downloading with utorrent, and I was downloading at the times the BSOD happened while I was watching video. I still however have no idea how to resolve the problem.

 

[writhziden]

It is most likely your network adapter driver that is causing the issue. Re-install using the following method...
To fully re-install a driver, use the following steps.

1. Click Start Menu
2. Right Click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Find the device you are trying to uninstall by expanding the appropriate set of devices
6. Right click the device
7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
8. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Install the latest driver for the device.

Alternatively:

1. Login as an adminstrative user.
2. Click Start Menu
3. Click Control Panel
4. Click Hardware and Sound
5. Click Device Manager (the last link under Devices and Printers)
6. Find the device you are trying to uninstall by expanding the appropriate set of devices
7. Right click the device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
10. Install the latest driver for the device.

Update the following drivers or report back if you cannot find an up to date version.

MacHALDriver	fffff880`08ed5000	fffff880`08edc000	Wed Jul 30 13:01:43 2008 (4890ba97)	00009b47		MacHALDriver.sys
KeyAgent	fffff880`08ecd000	fffff880`08ed5000	Wed Aug 27 17:58:23 2008 (48b5ea1f)	00008ec9		KeyAgent.sys

MacHALDriver.sys
KeyAgent.sys

 

[cornc5]

I figured out how to apply all the driver updates apple has for the system, which included new versions of the drivers writhziden recommended, but the next time i started downloading/uploading a torrent I got another blue screen. I've attached the new files and a new performance report. Also, I ran the system file checker and it did not find any errors.

 

[writhziden]

Outdated drivers:

IRFilter	fffff880`039eb000	fffff880`039f7000	Wed Jul 02 13:53:12 2008 (486bdca8)	0000d020		IRFilter.sys
nvmfdx64	fffff880`02c54000	fffff880`02dbf780	Tue Jul 08 03:18:13 2008 (487330d5)	0016dbd4		nvmfdx64.sys
nvsmu		fffff880`02b9e000	fffff880`02ba9000	Tue Jul 22 11:21:00 2008 (488616fc)	00008fd0		nvsmu.sys
GEARAspiWDM	fffff880`02dc0000	fffff880`02dcd000	Mon May 18 06:17:04 2009 (4a1151c0)	000159b4		GEARAspiWDM.sys

IRFilter.sys
nvmfdx64.sys
nvsmu.sys
GEARAspiWDM.sys

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


Loading Dump File [D:\Kingston\BSODDmpFiles\cornc5\Windows_NT6_BSOD_jcgriff2\022312-18844-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`01c13000 PsLoadedModuleList = 0xfffff800`01e58670
Debug session time: Thu Feb 23 19:51:46.839 2012 (UTC - 7:00)
System Uptime: 0 days 1:26:47.839
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {28, 2, 0, fffff880017adb2d}

Probably caused by : NETIO.SYS ( NETIO!RtlCopyBufferToMdl+1d )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880017adb2d, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001ec2100
 0000000000000028 

CURRENT_IRQL:  2

FAULTING_IP: 
NETIO!RtlCopyBufferToMdl+1d
fffff880`017adb2d 448b5228        mov     r10d,dword ptr [rdx+28h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880021db7f0 -- (.trap 0xfffff880021db7f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880021dba10 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880017adb2d rsp=fffff880021db980 rbp=fffff880021dbab0
 r8=00000000ffffffbc  r9=0000000000000044 r10=0000000000000000
r11=fffffa80072446c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
NETIO!RtlCopyBufferToMdl+0x1d:
fffff880`017adb2d 448b5228        mov     r10d,dword ptr [rdx+28h] ds:1900:00000000`00000028=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80001c8f1e9 to fffff80001c8fc40

STACK_TEXT:  
fffff880`021db6a8 fffff800`01c8f1e9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`021db6b0 fffff800`01c8de60 : fffffa80`089d1098 00000000`000200ff 00000000`00000202 00000000`00000044 : nt!KiBugCheckDispatch+0x69
fffff880`021db7f0 fffff880`017adb2d : 00000000`0000002e fffff880`0188afec 00000000`0000000a fffffa80`0731cf58 : nt!KiPageFault+0x260
fffff880`021db980 fffff880`01912bac : 00000000`00000000 fffff880`018e1906 00000000`00000001 fffff880`0842c00f : NETIO!RtlCopyBufferToMdl+0x1d
fffff880`021db9e0 fffff880`018deef3 : fffffa80`072446c0 00000000`00000001 fffffa80`07306220 00000000`00000000 : tcpip! ?? ::FNODOBFM::`string'+0x1d5cf
fffff880`021dba50 fffff880`018d1d54 : fffff880`021dbf08 fffffa80`00000029 fffffa80`07306220 00000000`00000001 : tcpip!TcpTcbCarefulDatagram+0x543
fffff880`021dbc00 fffff880`018d067a : fffffa80`0777cf00 fffff880`018c8b34 fffffa80`0775c8e0 00000000`00000000 : tcpip!TcpTcbReceive+0x694
fffff880`021dbdb0 fffff880`018d22ab : fffffa80`09b89940 fffffa80`07795000 00000000`00000000 fffff880`021dc100 : tcpip!TcpMatchReceive+0x1fa
fffff880`021dbf00 fffff880`018c91c7 : fffffa80`0777cf00 fffffa80`076e48cc fffffa80`0000406a 00000000`0000406a : tcpip!TcpPreValidatedReceive+0x36b
fffff880`021dbfd0 fffff880`018c8d3a : 00000000`00000000 fffff880`019e3800 fffff880`021dc190 fffffa80`072eb6f0 : tcpip!IppDeliverListToProtocol+0x97
fffff880`021dc090 fffff880`018c8339 : fffffa80`072eb6f0 fffffa80`072eb6f0 00000000`00000000 fffff880`021dc180 : tcpip!IppProcessDeliverList+0x5a
fffff880`021dc130 fffff880`018c60af : 00000000`00000000 00000000`08985b00 fffff880`019e3800 fffff880`019e3800 : tcpip!IppReceiveHeaderBatch+0x23a
fffff880`021dc210 fffff880`018c56a2 : fffffa80`08981550 00000000`00000000 fffffa80`08985b00 fffff880`00000001 : tcpip!IpFlcReceivePackets+0x64f
fffff880`021dc410 fffff880`0194434a : fffffa80`07486740 00000000`00000014 fffffa80`08985ba0 fffffa80`074bbfc0 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`021dc4f0 fffff800`01c9c618 : fffffa80`07781858 00000000`00000000 fffffa80`06cf1b60 00000000`00000001 : tcpip! ?? ::FNODOBFM::`string'+0x55122
fffff880`021dc540 fffff880`018c5202 : fffff880`018c4a60 00000000`00000000 00000000`00000000 fffffa80`07781801 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`021dc620 fffff880`017680eb : fffffa80`08985460 00000000`00000000 fffffa80`085e21a0 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`021dc690 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!RtlCopyBufferToMdl+1d
fffff880`017adb2d 448b5228        mov     r10d,dword ptr [rdx+28h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  NETIO!RtlCopyBufferToMdl+1d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79381

FAILURE_BUCKET_ID:  X64_0xD1_NETIO!RtlCopyBufferToMdl+1d

BUCKET_ID:  X64_0xD1_NETIO!RtlCopyBufferToMdl+1d

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

Still points to a network device. Appears to be your nVidia Networking Controller Driver (nForce chipset driver) or your nVidia nForce System Management Controller (nVidia nForce chipset driver) which are outdated.

 

[cornc5]

Thanks for all the help writhzide! I've installed the updated drivers, but the BSOD's are still happening, however instead of happening within five minutes of my starting a torrent, they now are happening after about thirty, so maybe part of the problem is fixed but at least some part of the problem is still there. I've attached a new set of dump files and a new performance report, and new thoughts or ideas would be most appreciated.

 

[writhziden]

An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:

a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​

The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

 

[cornc5]

Thanks again writhziden,

I could not start driver verifier in "normal mode", so I ran it in "safe mode with networking" for 12 hours, and everything, including torrents downloading, worked fine without any crashes occurring. I then rebooted into "safe mode - directory services restore mode" and had three crashes and have attached their dump and performance reports to this post.

Thanks again for any help or ideas

 

[writhziden]

Problem devices (probably due to being in Safe Mode, so don't worry about it too much):

J:\	WPDBUSENUMROOT\UMB\2&37C186B&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_APPLE&PROD_SD_CARD_READER&REV_1.00#000000009833&0#	This device is not working properly because Windows cannot load the drivers required for this device.
Link-Layer Topology Discovery Mapper I/O Driver	ROOT\LEGACY_LLTDIO\0000	This device is not present, is not working properly, or does not have all its drivers installed.
Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64	ROOT\NET\0000	This device is disabled.
1 LACIE15GB	WPDBUSENUMROOT\UMB\2&37C186B&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_LACIE&PROD_WHIZKEY&REV_0.00#6381764701F04A&0#	This device is not working properly because Windows cannot load the drivers required for this device.
Link-Layer Topology Discovery Responder	ROOT\LEGACY_RSPNDR\0000	This device is not present, is not working properly, or does not have all its drivers installed.
CHRISTOPHER	WPDBUSENUMROOT\UMB\2&37C186B&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_APPLE&PROD_IPOD&REV_2.70#000A2700230D57DD&0#	This device is not working properly because Windows cannot load the drivers required for this device.
Security Processor Loader Driver	ROOT\LEGACY_SPLDR\0000	This device is not present, is not working properly, or does not have all its drivers installed.
Unknown Device	USB\VID_0000&PID_0000\6&112A0DF4&0&3	43
IDMWFP	ROOT\LEGACY_IDMWFP\0000	This device is not present, is not working properly, or does not have all its drivers installed.

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


Loading Dump File [D:\Kingston\BSODDmpFiles\cornc5\Driver Verify Crash 3 Dump Files\022512-17924-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`01c19000 PsLoadedModuleList = 0xfffff800`01e5e670
Debug session time: Sat Feb 25 20:26:06.107 2012 (UTC - 7:00)
System Uptime: 0 days 0:22:03.091
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {28, 2, 0, fffff88001779b2d}

Probably caused by : NETIO.SYS ( NETIO!RtlCopyBufferToMdl+1d )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001779b2d, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001ec8100
 0000000000000028 

CURRENT_IRQL:  2

FAULTING_IP: 
NETIO!RtlCopyBufferToMdl+1d
fffff880`01779b2d 448b5228        mov     r10d,dword ptr [rdx+28h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880021db7f0 -- (.trap 0xfffff880021db7f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880021dba10 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001779b2d rsp=fffff880021db980 rbp=fffff880021dbab0
 r8=00000000ffffffbc  r9=0000000000000044 r10=0000000000000000
r11=fffffa80077e2160 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
NETIO!RtlCopyBufferToMdl+0x1d:
fffff880`01779b2d 448b5228        mov     r10d,dword ptr [rdx+28h] ds:00000000`00000028=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80001c951e9 to fffff80001c95c40

STACK_TEXT:  
fffff880`021db6a8 fffff800`01c951e9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`021db6b0 fffff800`01c93e60 : fffffa80`0a837098 fffff880`018b0dd2 00000000`00000246 00000000`00000044 : nt!KiBugCheckDispatch+0x69
fffff880`021db7f0 fffff880`01779b2d : 00000000`0000001c fffff880`01867fec 00000000`0000000a fffffa80`0c338ae8 : nt!KiPageFault+0x260
fffff880`021db980 fffff880`018efbac : 00000000`00000000 fffff880`018be906 00000000`00000001 fffff880`0146d00f : NETIO!RtlCopyBufferToMdl+0x1d
fffff880`021db9e0 fffff880`018bbef3 : fffffa80`077e2160 00000000`00000001 fffffa80`0bdf1bf0 00000000`00000000 : tcpip! ?? ::FNODOBFM::`string'+0x1d5cf
fffff880`021dba50 fffff880`018aed54 : fffff880`021dbf08 fffff800`00000029 fffffa80`0bdf1bf0 00000000`00000001 : tcpip!TcpTcbCarefulDatagram+0x543
fffff880`021dbc00 fffff880`018ad67a : fffffa80`07763a50 fffff880`018a5b34 fffffa80`0771a158 00000000`00000000 : tcpip!TcpTcbReceive+0x694
fffff880`021dbdb0 fffff880`018af2ab : fffffa80`093fc940 fffffa80`07759000 00000000`00000000 fffff880`021dc100 : tcpip!TcpMatchReceive+0x1fa
fffff880`021dbf00 fffff880`018a61c7 : fffffa80`07763a50 fffffa80`07760bc4 fffffa80`0000406a 00000000`0000406a : tcpip!TcpPreValidatedReceive+0x36b
fffff880`021dbfd0 fffff880`018a5d3a : 00000000`00000000 fffff880`019c0800 fffff880`021dc190 fffffa80`07d2a440 : tcpip!IppDeliverListToProtocol+0x97
fffff880`021dc090 fffff880`018a5339 : fffffa80`07d2a440 fffffa80`07d2a440 00000000`00000000 fffff880`021dc180 : tcpip!IppProcessDeliverList+0x5a
fffff880`021dc130 fffff880`018a30af : 00000000`00000000 00000000`088d4b00 fffff880`019c0800 fffff880`019c0800 : tcpip!IppReceiveHeaderBatch+0x23a
fffff880`021dc210 fffff880`018a26a2 : fffffa80`088ce330 00000000`00000000 fffffa80`088d4b00 fffff880`00000001 : tcpip!IpFlcReceivePackets+0x64f
fffff880`021dc410 fffff880`0192134a : 00000000`00000001 00000000`00000014 fffffa80`088d4ba0 fffff880`011a7f4f : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`021dc4f0 fffff800`01ca2618 : fffffa80`07740c38 00000000`00000000 fffffa80`06d51680 00000000`00000001 : tcpip! ?? ::FNODOBFM::`string'+0x55122
fffff880`021dc540 fffff880`018a2202 : fffff880`018a1a60 00000000`00000240 fffff8a0`00010900 00000000`00000001 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`021dc620 fffff880`017340eb : fffffa80`088d4010 00000000`00000000 fffffa80`085921a0 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`021dc690 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!RtlCopyBufferToMdl+1d
fffff880`01779b2d 448b5228        mov     r10d,dword ptr [rdx+28h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  NETIO!RtlCopyBufferToMdl+1d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79381

FAILURE_BUCKET_ID:  X64_0xD1_NETIO!RtlCopyBufferToMdl+1d

BUCKET_ID:  X64_0xD1_NETIO!RtlCopyBufferToMdl+1d

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

Driver verified crashes point toward the network adapter being the issue.

Also, if it is crashing on startup in normal mode with Verifier enabled, you should run driver verifier on one non-Microsoft driver at a time to determine which driver is causing the crash at startup.

 

[tjpearson]

Sorry to barge in on this but having exact same problem

Sorry to just barge in on this thread but I too have this exact issue and have done so for months.

Once crash happens get report "Probably caused by : NETIO.SYS"

I've used Vuze instead for the last year with no issue but wanted to go back to Utorrent so have used it this weekend and suffered 4 crashes.

I would love it if this thread solves this issue and please let me know if any of my info would help.

My PC is Acer Aspire desk top Media Centre.

Regards, tj

 

[writhziden]

tjpearson, please start your own thread following the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to get dedicated help. All systems are different, so your crashes may not be due to the exact same causes. Systems have different hardware, software, and drivers, so there are too many factors to assume the solution in this thread will work for you. You are welcome to follow this thread while getting help in your own, of course.

 

[tjpearson]

I'm so sorry

I do apologise, didn't notice the BSOD rule till after post, it makes sense. Sorry again. Regards, tj

 

[writhziden]

cornc5: did you resolve your network adapter crashes and the Verifier crashes on startup?