Question blue screen of death help windows 7

May 17, 2021
9
0
10
0
I am running Windows 7 had no problems until recently. i have tried to turn back the system to an eariler date but still has the probeml. I have changed out the ram and stll have the problem. recently now when it reboots after the crash the network card is not loading the proxy corre ctly it never did this i used to be able to remote to it from my phone and get the os back up but now the network card is doing this it requires me to physically be there

well here is the code i get can anyone tell me more as to what will solve this problem

thanks

nick

Bluescreen help. I get the error code BCC0de 124 00000000 86e39024 b2000000 1040080f how do i fix this i have removed and replaced

this is what i get in the dump file
halmacpi.dll halmacpi.dll+ef3f 0x82c06000 0x82c3d000 0x00037000 0x4a5bbf07 7/13/2009 4:11:03 PM
ntkrnlpa.exe ntkrnlpa.exe+cf204 0x82c3d000 0x8304e000 0x00411000 0x550a2c44 3/18/2015 6:54:12 PM
kdcom.dll 0x80b9c000 0x80ba4000 0x00008000 0x4a5bdaaa 7/13/2009 6:08:58 PM
mcupdate_GenuineIntel.dll 0x83212000 0x8328a000 0x00078000 0x4a5bda21 7/13/2009 6:06:41 PM
PSHED.dll 0x8328a000 0x8329b000 0x00011000 0x4a5bdad0 7/13/2009 6:09:36 PM
BOOTVID.dll 0x8329b000 0x832a3000 0x00008000 0x4a5bd9a2 7/13/2009 6:04:34 PM
CLFS.SYS 0x832a3000 0x832e5000 0x00042000 0x4a5bbf0e 7/13/2009 4:11:10 PM
CI.dll 0x832e5000 0x83390000 0x000ab000 0x4a5bdac8 7/13/2009 6:09:28 PM
Wdf01000.sys 0x88e2f000 0x88ea0000 0x00071000 0x4a5bbf28 7/13/2009 4:11:36 PM
WDFLDR.SYS 0x88ea0000 0x88eae000 0x0000e000 0x4a5bbf1d 7/13/2009 4:11:25 PM
ACPI.sys 0x88eae000 0x88ef6000 0x00048000 0x4a5bbf0f 7/13/2009 4:11:11 PM
WMILIB.SYS 0x88ef6000 0x88eff000 0x00009000 0x4a5bbf1a 7/13/2009 4:11:22 PM
msisadrv.sys 0x88eff000 0x88f07000 0x00008000 0x4a5bbf0d 7/13/2009 4:11:09 PM
pci.sys 0x88f07000 0x88f31000 0x0002a000 0x4a5bbf14 7/13/2009 4:11:16 PM
vdrvroot.sys 0x88f31000 0x88f3c000 0x0000b000 0x4a5bc74b 7/13/2009 4:46:19 PM
partmgr.sys 0x88f3c000 0x88f4d000 0x00011000 0x4a5bbf27 7/13/2009 4:11:35 PM
volmgr.sys 0x88f4d000 0x88f5d000 0x00010000 0x4a5bbf1d 7/13/2009 4:11:25 PM
volmgrx.sys 0x88f5d000 0x88fa8000 0x0004b000 0x4a5bbf2d 7/13/2009 4:11:41 PM
intelide.sys 0x88fa8000 0x88faf000 0x00007000 0x4a5bbf17 7/13/2009 4:11:19 PM
PCIIDEX.SYS 0x88faf000 0x88fbd000 0x0000e000 0x4a5bbf13 7/13/2009 4:11:15 PM
mountmgr.sys 0x88fbd000 0x88fd3000 0x00016000 0x4a5bbf1f 7/13/2009 4:11:27 PM
iaStorV.sys 0x89011000 0x890ec000 0x000db000 0x49dcd6e2 4/8/2009 9:54:58 AM
atapi.sys 0x890ec000 0x890f5000 0x00009000 0x4a5bbf13 7/13/2009 4:11:15 PM
ataport.SYS 0x890f5000 0x89118000 0x00023000 0x4a5bbf16 7/13/2009 4:11:18 PM
Si3114r5.sys 0x89118000 0x8914e000 0x00036000 0x492663f8 11/21/2008 12:32:08 AM
SCSIPORT.SYS 0x8914e000 0x89174000 0x00026000 0x4a5bc733 7/13/2009 4:45:55 PM
amdxata.sys 0x89174000 0x8917d000 0x00009000 0x4a12f30f 5/19/2009 10:57:35 AM
SI3114R.sys 0x8917d000 0x89196400 0x00019400 0x461bc191 4/10/2007 9:55:45 AM
fltmgr.sys 0x89197000 0x891cb000 0x00034000 0x4a5bbf11 7/13/2009 4:11:13 PM
fileinfo.sys 0x891cb000 0x891dc000 0x00011000 0x4a5bc18f 7/13/2009 4:21:51 PM
SiWinAcc.sys 0x891dc000 0x891de880 0x00002880 0x41868cbb 11/1/2004 12:21:31 PM
Ntfs.sys 0x8921f000 0x8934e000 0x0012f000 0x4a5bbf45 7/13/2009 4:12:05 PM
msrpc.sys 0x8934e000 0x89379000 0x0002b000 0x00000000
ksecdd.sys 0x89379000 0x8938c000 0x00013000 0x4a5bbf3c 7/13/2009 4:11:56 PM
cng.sys 0x8938c000 0x893e9000 0x0005d000 0x4a5bc427 7/13/2009 4:32:55 PM
pcw.sys 0x893e9000 0x893f7000 0x0000e000 0x4a5bbf0e 7/13/2009 4:11:10 PM
Fs_Rec.sys 0x893f7000 0x89400000 0x00009000 0x00000000
ndis.sys 0x89421000 0x894d8000 0x000b7000 0x4a5bbf58 7/13/2009 4:12:24 PM
NETIO.SYS 0x894d8000 0x89516000 0x0003e000 0x4a5bbf63 7/13/2009 4:12:35 PM
ksecpkg.sys 0x89516000 0x8953b000 0x00025000 0x4a5bc468 7/13/2009 4:34:00 PM
tcpip.sys 0x8962e000 0x89777000 0x00149000 0x4a5bbf8e 7/13/2009 4:13:18 PM
fwpkclnt.sys 0x89777000 0x897a8000 0x00031000 0x4a5bbf43 7/13/2009 4:12:03 PM
vmstorfl.sys 0x897a8000 0x897b1000 0x00009000 0x00000000
volsnap.sys 0x897b1000 0x897f0000 0x0003f000 0x4a5bbf26 7/13/2009 4:11:34 PM
spldr.sys 0x897f0000 0x897f8000 0x00008000 0x4a084ebb 5/11/2009 9:13:47 AM
rdyboost.sys 0x89600000 0x8962d000 0x0002d000 0x4a5bc19a 7/13/2009 4:22:02 PM
SiRemFil.sys 0x897f8000 0x897f9580 0x00001580 0x45b7e904 1/24/2007 4:17:24 PM
mup.sys 0x8953b000 0x8954b000 0x00010000 0x4a5bbfc6 7/13/2009 4:14:14 PM
hwpolicy.sys 0x8954b000 0x89553000 0x00008000 0x4a5bbf05 7/13/2009 4:11:01 PM
fvevol.sys 0x89553000 0x89585000 0x00032000 0x4abd7b55 9/25/2009 7:24:21 PM
disk.sys 0x89585000 0x89596000 0x00011000 0x4a5bbf20 7/13/2009 4:11:28 PM
CLASSPNP.SYS 0x89596000 0x895bb000 0x00025000 0x4a5bbf18 7/13/2009 4:11:20 PM
null.sys 0x895bb000 0x895c2000 0x00007000 0x00000000
Beep.SYS 0x895f4000 0x895fb000 0x00007000 0x4a5bc6fc 7/13/2009 4:45:00 PM
vga.sys 0x89400000 0x8940c000 0x0000c000 0x4a5bc27e 7/13/2009 4:25:50 PM
VIDEOPRT.SYS 0x891df000 0x89200000 0x00021000 0x4a5bc27d 7/13/2009 4:25:49 PM
watchdog.sys 0x8940c000 0x89419000 0x0000d000 0x4a5bc21a 7/13/2009 4:24:10 PM
RDPCDD.sys 0x89419000 0x89421000 0x00008000 0x4a5bcae4 7/13/2009 5:01:40 PM
rdpencdd.sys 0x89200000 0x89208000 0x00008000 0x4a5bcae3 7/13/2009 5:01:39 PM
rdprefmp.sys 0x89208000 0x89210000 0x00008000 0x4a5bcae5 7/13/2009 5:01:41 PM
Msfs.SYS 0x89210000 0x8921b000 0x0000b000 0x4a5bbf1e 7/13/2009 4:11:26 PM
Npfs.SYS 0x89000000 0x8900e000 0x0000e000 0x4a5bbf23 7/13/2009 4:11:31 PM
tdx.sys 0x88fd3000 0x88fea000 0x00017000 0x4a5bbf4a 7/13/2009 4:12:10 PM
TDI.SYS 0x88fea000 0x88ff5000 0x0000b000 0x4a5bbf4c 7/13/2009 4:12:12 PM
afd.sys 0x83390000 0x833ea000 0x0005a000 0x4a5bbf62 7/13/2009 4:12:34 PM
netbt.sys 0x8dc31000 0x8dc63000 0x00032000 0x4a5bbf52 7/13/2009 4:12:18 PM
wfplwf.sys 0x8dc63000 0x8dc6a000 0x00007000 0x4a5bc90f 7/13/2009 4:53:51 PM
pacer.sys 0x8dc6a000 0x8dc89000 0x0001f000 0x4a5bc916 7/13/2009 4:53:58 PM
netbios.sys 0x8dc89000 0x8dc97000 0x0000e000 0x4a5bc912 7/13/2009 4:53:54 PM
wanarp.sys 0x8dcb1000 0x8dcc4000 0x00013000 0x4a5bc956 7/13/2009 4:55:02 PM
termdd.sys 0x8dcc4000 0x8dcd4000 0x00010000 0x4a5bcadf 7/13/2009 5:01:35 PM
rdbss.sys 0x8dcd4000 0x8dd15000 0x00041000 0x4a5bbfd2 7/13/2009 4:14:26 PM
nsiproxy.sys 0x8dd15000 0x8dd1f000 0x0000a000 0x4a5bbf48 7/13/2009 4:12:08 PM
mssmbios.sys 0x8dd1f000 0x8dd29000 0x0000a000 0x4a5bc0fd 7/13/2009 4:19:25 PM
discache.sys 0x8dd29000 0x8dd35000 0x0000c000 0x4a5bc214 7/13/2009 4:24:04 PM
csc.sys 0x8dd35000 0x8dd99000 0x00064000 0x4a5bbffc 7/13/2009 4:15:08 PM
dfsc.sys 0x8dd99000 0x8ddb1000 0x00018000 0x4a5bbfc8 7/13/2009 4:14:16 PM
blbdrive.sys 0x8ddb1000 0x8ddbf000 0x0000e000 0x4a5bc1d8 7/13/2009 4:23:04 PM
tunnel.sys 0x8ddbf000 0x8dde0000 0x00021000 0x4a5bc91b 7/13/2009 4:54:03 PM
intelppm.sys 0x8dde0000 0x8ddf2000 0x00012000 0x4a5bbf07 7/13/2009 4:11:03 PM
nvlddmkm.sys 0x8e816000 0x8f2ac000 0x00a96000 0x54cc17ac 1/30/2015 4:45:48 PM
dxgkrnl.sys 0x8f2ac000 0x8f363000 0x000b7000 0x4a5bc297 7/13/2009 4:26:15 PM
dxgmms1.sys 0x8f363000 0x8f39c000 0x00039000 0x4a5bc265 7/13/2009 4:25:25 PM
HDAudBus.sys 0x8f39c000 0x8f3bb000 0x0001f000 0x4a5bc85f 7/13/2009 4:50:55 PM
usbuhci.sys 0x8f3bb000 0x8f3c6000 0x0000b000 0x4a5bc86e 7/13/2009 4:51:10 PM
USBPORT.SYS 0x92205000 0x92250000 0x0004b000 0x4a5bc871 7/13/2009 4:51:13 PM
usbehci.sys 0x92250000 0x9225f000 0x0000f000 0x4a5bc872 7/13/2009 4:51:14 PM
1394ohci.sys 0x9225f000 0x9228b000 0x0002c000 0x4a5bc89f 7/13/2009 4:51:59 PM
cxfalcon_32.sys 0x922a8000 0x922c0580 0x00018580 0x4a68e9cf 7/23/2009 3:53:03 PM
ks.sys 0x922c1000 0x922f5000 0x00034000 0x4a5bc709 7/13/2009 4:45:13 PM
e100b325.sys 0x922f5000 0x9231bc00 0x00026c00 0x473de72c 11/16/2007 11:53:32 AM
parport.sys 0x9231c000 0x92334000 0x00018000 0x4a5bc71e 7/13/2009 4:45:34 PM
CompositeBus.sys 0x92334000 0x92341000 0x0000d000 0x4a5bc716 7/13/2009 4:45:26 PM
AgileVpn.sys 0x92341000 0x92353000 0x00012000 0x4a5bc954 7/13/2009 4:55:00 PM
rasl2tp.sys 0x92353000 0x9236b000 0x00018000 0x4a5bc939 7/13/2009 4:54:33 PM
ndistapi.sys 0x9236b000 0x92376000 0x0000b000 0x4a5bc930 7/13/2009 4:54:24 PM
ndiswan.sys 0x92376000 0x92398000 0x00022000 0x4a5bc93a 7/13/2009 4:54:34 PM
raspppoe.sys 0x92398000 0x923b0000 0x00018000 0x4a5bc94d 7/13/2009 4:54:53 PM
raspptp.sys 0x923b0000 0x923c7000 0x00017000 0x4a5bc947 7/13/2009 4:54:47 PM
rassstp.sys 0x923c7000 0x923de000 0x00017000 0x4a5bc951 7/13/2009 4:54:57 PM
rdpbus.sys 0x923de000 0x923e8000 0x0000a000 0x4a5bcb20 7/13/2009 5:02:40 PM
kbdclass.sys 0x923e8000 0x923f5000 0x0000d000 0x4a5bbf13 7/13/2009 4:11:15 PM
mouclass.sys 0x8f3c6000 0x8f3d3000 0x0000d000 0x4a5bbf13 7/13/2009 4:11:15 PM
swenum.sys 0x923f5000 0x923f6380 0x00001380 0x4a5bc704 7/13/2009 4:45:08 PM
umbus.sys 0x8f3d3000 0x8f3e1000 0x0000e000 0x4a5bc88a 7/13/2009 4:51:38 PM
usbhub.sys 0x92a1b000 0x92a5f000 0x00044000 0x4a5bc8a6 7/13/2009 4:52:06 PM
RTKVHDA.sys 0x92e07000 0x930a37c0 0x0029c7c0 0x4a7803dd 8/4/2009 2:48:13 AM
portcls.sys 0x930a4000 0x930d3000 0x0002f000 0x4a5bc864 7/13/2009 4:51:00 PM
drmk.sys 0x930d3000 0x930ec000 0x00019000 0x4a5bd2f5 7/13/2009 5:36:05 PM
NDProxy.SYS 0x930ec000 0x930fd000 0x00011000 0x4a5bc933 7/13/2009 4:54:27 PM
win32k.sys 0x94a90000 0x94ce8000 0x00258000 0x00000000
Dxapi.sys 0x930fd000 0x93107000 0x0000a000 0x4a5bc265 7/13/2009 4:25:25 PM
crashdmp.sys 0x93107000 0x93114000 0x0000d000 0x4a5bc72e 7/13/2009 4:45:50 PM
dump_dumpata.sys 0x93114000 0x9311f000 0x0000b000 0x4a5bbf14 7/13/2009 4:11:16 PM
dump_atapi.sys 0x9311f000 0x93128000 0x00009000 0x4a5bbf13 7/13/2009 4:11:15 PM
dump_dumpfve.sys 0x93128000 0x93139000 0x00011000 0x4a5bbf6f 7/13/2009 4:12:47 PM
hidusb.sys 0x93139000 0x93144000 0x0000b000 0x4a5bc868 7/13/2009 4:51:04 PM
HIDCLASS.SYS 0x93144000 0x93157000 0x00013000 0x4a5bc865 7/13/2009 4:51:01 PM
HIDPARSE.SYS 0x93157000 0x9315d480 0x00006480 0x4a5bc863 7/13/2009 4:50:59 PM
USBD.SYS 0x9315e000 0x9315f700 0x00001700 0x4a5bc869 7/13/2009 4:51:05 PM
kbdhid.sys 0x93160000 0x9316c000 0x0000c000 0x4a5bc705 7/13/2009 4:45:09 PM
usbprint.sys 0x9316c000 0x93177000 0x0000b000 0x4a5bce82 7/13/2009 5:17:06 PM
monitor.sys 0x93177000 0x93182000 0x0000b000 0x4a5bc286 7/13/2009 4:25:58 PM
mouhid.sys 0x93182000 0x9318d000 0x0000b000 0x4a5bc704 7/13/2009 4:45:08 PM
USBSTOR.SYS 0x9318d000 0x931a4000 0x00017000 0x4a5bc877 7/13/2009 4:51:19 PM
TSDDD.dll 0x94d00000 0x94d09000 0x00009000 0x00000000
cdd.dll 0x94d30000 0x94d4e000 0x0001e000 0x00000000
luafv.sys 0x931a4000 0x931bf000 0x0001b000 0x4a5bc020 7/13/2009 4:15:44 PM
WudfPf.sys 0x931bf000 0x931d9000 0x0001a000 0x4a5bc835 7/13/2009 4:50:13 PM
lltdio.sys 0x931d9000 0x931e9000 0x00010000 0x4a5bc8ee 7/13/2009 4:53:18 PM
rspndr.sys 0x931e9000 0x931fc000 0x00013000 0x4a5bc8f0 7/13/2009 4:53:20 PM
HTTP.sys 0x92a5f000 0x92ae4000 0x00085000 0x4a5bbf75 7/13/2009 4:12:53 PM
bowser.sys 0x92ae4000 0x92afd000 0x00019000 0x4a5bbfcd 7/13/2009 4:14:21 PM
mpsdrv.sys 0x92afd000 0x92b0f000 0x00012000 0x4a5bc8d4 7/13/2009 4:52:52 PM
mrxsmb.sys 0x92b0f000 0x92b32000 0x00023000 0x4b88ca72 2/27/2010 12:32:02 AM
mrxsmb10.sys 0x92b32000 0x92b6d000 0x0003b000 0x4b88ca85 2/27/2010 12:32:21 AM
mrxsmb20.sys 0x92b6d000 0x92b88000 0x0001b000 0x4b88ca7b 2/27/2010 12:32:11 AM
parvdm.sys 0x92e00000 0x92e07000 0x00007000 0x00000000
peauth.sys 0x9e603000 0x9e69a000 0x00097000 0x4a5bd2e0 7/13/2009 5:35:44 PM
secdrv.SYS 0x9e69a000 0x9e6a4000 0x0000a000 0x45080528 9/13/2006 6:18:32 AM
srvnet.sys 0x9e6a4000 0x9e6c5000 0x00021000 0x4c20242d 6/21/2010 7:47:09 PM
tcpipreg.sys 0x9e6c5000 0x9e6d2000 0x0000d000 0x4a5bc926 7/13/2009 4:54:14 PM
srv2.sys 0x9e6d2000 0x9e721000 0x0004f000 0x4c202437 6/21/2010 7:47:19 PM
srv.sys 0x9e721000 0x9e772000 0x00051000 0x4c202444 6/21/2010 7:47:32 PM
WUDFRd.sys 0x9e772000 0x9e792480 0x00020480 0x4a5bc854 7/13/2009 4:50:44 PM
rdpdr.sys 0x9e793000 0x9e7b8000 0x00025000 0x4a5bcb30 7/13/2009 5:02:56 PM
tdtcp.sys 0x9e7b8000 0x9e7c2000 0x0000a000 0x4a5bcae1 7/13/2009 5:01:37 PM
tssecsrv.sys 0x9e7c2000 0x9e7cf000 0x0000d000 0x4a5bcaee 7/13/2009 5:01:50 PM
RDPWD.SYS 0x9e7cf000 0x9e800000 0x00031000 0x4a5bcaee 7/13/2009 5:01:50 PM
fastfat.SYS 0x92b88000 0x92bb2000 0x0002a000 0x4a5bbfb9 7/13/2009 4:14:01 PM
 
Last edited by a moderator:

Colif

Win 10 Master
Moderator
i hid results as its just a list of drivers. based on the top 2 I could guess that bccode 124 = whea error. I knew it already

what are specs of the PC?

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

Open Windows File Explore
Navigate to C:\Windows\Minidump
Copy the mini-dump files out onto your Desktop
create a zip file with the files you copied as contents
Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
Then post a link here to the zip file, so we can take a look for you . . .

if it is a whea error, the dumps won't reveal a lot (unless you fortunate) but they will show me a list of drivers running which might help.

WHEA - Windows hardware error architecture
error called by CPU but not necessarily caused by it
can be any hardware (maybe that network card?)
can be caused by overclocking so remove any you have
can be caused by overclocking software
can be caused by heat
 
May 17, 2021
9
0
10
0
i hid results as its just a list of drivers. based on the top 2 I could guess that bccode 124 = whea error. I knew it already

what are specs of the PC?

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

Open Windows File Explore
Navigate to C:\Windows\Minidump
Copy the mini-dump files out onto your Desktop
create a zip file with the files you copied as contents
Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
Then post a link here to the zip file, so we can take a look for you . . .

if it is a whea error, the dumps won't reveal a lot (unless you fortunate) but they will show me a list of drivers running which might help.

WHEA - Windows hardware error architecture
error called by CPU but not necessarily caused by it
can be any hardware (maybe that network card?)
can be caused by overclocking so remove any you have
can be caused by overclocking software
can be caused by heat
----------------------------------------------------------------------------------



ok i got the dump files to a drive link. here is the link of the zip file
here is an updated version as of may 30

https://drive.google.com/file/d/1hQFk1E2zx4wFGHsaATGjtEyNuciZ5qxO/view?usp=sharing
 
Last edited:

Colif

Win 10 Master
Moderator
I have changed out all the ram and still have the problem. removed my network controller and still have the problem. i have been logical in each thing i did only doing 1 at a time to see if it fixed the issue but none have
https://en.wikipedia.org/wiki/Intel_Viiv
So its a laptop? that reduces choices as I don't know how to test a laptop PSU

whea can be any hardware, so could be hdd.
try running crystaldiskinfo - https://crystalmark.info/en/software/crystaldiskinfo/ and check its smart score. Also tell us who made drive.

I don't think this will work on cpu - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool as CPU is probably too old.
 
May 17, 2021
9
0
10
0
https://en.wikipedia.org/wiki/Intel_Viiv
So its a laptop? that reduces choices as I don't know how to test a laptop PSU

whea can be any hardware, so could be hdd.
try running crystaldiskinfo - https://crystalmark.info/en/software/crystaldiskinfo/ and check its smart score. Also tell us who made drive.

I don't think this will work on cpu - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool as CPU is probably too old.

ITs a tower, sold from sams club, it was a media comuter at the time
HP MEDIA CENTER PC m7000
i tried the digansotic tool and yeah its too old to run the tool it says
 
May 17, 2021
9
0
10
0
try running prime 95 on cpu - https://www.mersenne.org/download/
Prime 95 how to Guide: http://www.playtool.com/pages/prime95/prime95.html
it will test cpu and ram.

I just assumed from the name. I wonder what PSU it has. if its old that could be cause too..

really, anything can be. its an old pc, parts start to wear out.

try checking hdd out
dont the dump files tell anything? im getting confused what to run you gave me quite a few links. which one will tell me what the problem is?
 

Colif

Win 10 Master
Moderator
Sorry, my friend hasn't replied to this thread yet, he could be busy. I can't read the dumps myself until he posts a conversion for me.
I don't expect to see much in them as WHEA errors almost always look the same in the dumps. But it will show drivers and one of those might offer a clue. If you really lucky the dump will point at a driver, but that is rare.

It is why I am testing hardware while I wait for friend to post :)

WHEA errors can be any hardware so since I am not sure which, I am offering tests to reduce the field of possible causes.
 

gardenman

Distinguished
Moderator
Hi, I looked at the most recent 6 out of the 65 dumps that you posted. I ran the dump files through the debugger and got the following information: https://jsfiddle.net/gqweadyL/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.
File information:053021-40187-01.dmp (May 30 2021 - 12:25:26)
Bugcheck:WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:GenuineIntel (Process: System)
Uptime:0 Day(s), 3 Hour(s), 24 Min(s), and 33 Sec(s)

File information:053021-39875-01.dmp (May 30 2021 - 18:03:19)
Bugcheck:WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:GenuineIntel (Process: System)
Uptime:0 Day(s), 5 Hour(s), 35 Min(s), and 00 Sec(s)

File information:053021-39218-01.dmp (May 30 2021 - 21:21:09)
Bugcheck:WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:GenuineIntel (Process: System)
Uptime:0 Day(s), 1 Hour(s), 48 Min(s), and 36 Sec(s)

File information:053021-39062-01.dmp (May 30 2021 - 08:53:46)
Bugcheck:WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:GenuineIntel (Process: System)
Uptime:0 Day(s), 16 Hour(s), 46 Min(s), and 04 Sec(s)

File information:053021-38093-01.dmp (May 30 2021 - 18:11:24)
Bugcheck:WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:GenuineIntel (Process: System)
Uptime:0 Day(s), 0 Hour(s), 04 Min(s), and 18 Sec(s)

File information:053021-39062-02.dmp (May 30 2021 - 19:29:40)
Bugcheck:WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:GenuineIntel (Process: System)
Uptime:0 Day(s), 1 Hour(s), 16 Min(s), and 56 Sec(s)
System: HP Pavilion 061
BIOS: 3.15 (06/23/2006)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 10 Master
Moderator
65 dumps...

those 5 are all the same

0x124_GenuineIntel_VRF_PROCESSOR_BUS_STACKPTR_ERROR
A bus error is trying to access memory that can't possibly be there. You've used an address that's meaningless to the system, or the wrong kind of address for that operation. However, on a bus error it usually means that you are trying to access memory that does not exist (e. g. you try to access an address at 12G but you only have 8G memory) or if you exceed the limit of usable memory.

Software instructs the CPU to read or write a specific physical memory address. Accordingly, the CPU sets this physical address on its address bus and requests all other hardware connected to the CPU to respond with the results, if they answer for this specific address. If no other hardware responds, the CPU raises an exception, stating that the requested physical address is unrecognized by the whole computer system. Note that this only covers physical memory addresses.
https://en.wikipedia.org/wiki/Bus_error

ptr = pointer, its used by CPU to know what process to run next.

it sounds like it is a ram error or the controller on cpu itself unless you changed any drivers recently?

Just identifying unknown drivers
SI3114R.sys = Sil 3114 SATARAID driver for Windows 98, ME,
e100b325.sys - intel pro network drivers
Si3114r5.sys - Sil 3114 SoftRAID 5 driver for Windows 2000/XP/2003
cxfalcon_32 - Conexant Falcon Driver

i assume you haven't changed any recently

its rare for WHEA errors to be drivers
 
May 17, 2021
9
0
10
0
so i istalled windows 10 on a new tower and alll seems to be working .. only problem I am having now is for my sataraid5 when i open the program i get an error " could not acquire application lock click to exit" someone said you need to run as adminiistrattor? but whatand how do i do it so it will always run that program as adminin?
 

Colif

Win 10 Master
Moderator
May 17, 2021
9
0
10
0
SO I have changed the ownership to reflect my user account but when i reboot i still get the same account lock error. Is there someting else i can do to get around this?

thanks

nick
 

ASK THE COMMUNITY