Is this a virus issue or something else?

[joddle]

I am running an Acer Aspire 7720 under W7 unlimate. and recently had a virus problem which I think I have cleared using the Kaspersky rescue and Avira resue system disks.

 

The PC appears to be running fine with no sign of the the scareware which had infected the machine earlier. However when I run either a malwarebytes or antivirus scan it blues screens towards the end of the scan. If I run in safe more it does not blue screen and malwarebytes found some pup items whic it deleted but when I revert to normal mode it blue screen again just at the end of the malwarebytes scan.

 

I ran the Avira rescue system under ubantu and if found two infecitons which it removed. however the system still blue screens when I run Malwarebytes in normal mode.

 

The message I get in safe mode on the crash is as follows but the first file (the minidump) I can find but the second I can't seem to locate anywhere! but not sure what to do with the files anyway!!!

 

Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7600.2.0.0.256.1

Locale ID: 2057

 

Additional information about the problem:

BCCode: 7a

BCP1: C023B924

BCP2: C0000185

BCP3: 13788BE0

BCP4: 8EE49000

OS Version: 6_1_7600

Service Pack: 0_0

Product: 256_1

 

Files that help describe the problem:

C:\Windows\Minidump\042614-58593-01.dmp

C:\Users\Bob\AppData\Local\Temp\WER-67564-0.sysdata.xml

[Starbuck]

Hi joddle,

 

The obvious thing to do would be to have a look at the minidump file and see what the cause was.

Ok, M$ don't make it easy to read these reports.

If you want to take a look at the file, download BlueScreenView to your desktop.

Very easy to install ..... at the end of the install, let it open the program.

It will find the minidump files for you and show them in the top screen.

Double click on the one you want to view and a report will open.

[joddle]

Hi joddle,

 

The obvious thing to do would be to have a look at the minidump file and see what the cause was.

Ok, M$ don't make it easy to read these reports.

If you want to take a look at the file, download BlueScreenView to your desktop.

Very easy to install ..... at the end of the install, let it open the program.

It will find the minidump files for you and show them in the top screen.

Double click on the one you want to view and a report will open.

 

Thanks but it does not mean much to me - does it to enyone else?

 

I Assume the first part is the bit which is saying what is wrong

042614-58593-01.dmp 26/04/2014 14:50:50 KERNEL_DATA_INPAGE_ERROR 0x0000007a 0xc023b924 0xc0000185 0x13788be0 0x8ee49000 ntoskrnl.exe ntoskrnl.exe+d1294 32-bit ntoskrnl.exe+d1294 ntoskrnl.exe+9aaed ntoskrnl.exe+ac316 ntoskrnl.exe+60a85

 

ntoskrnl.exe ntoskrnl.exe+9aaed 0x82c1f000 0x83020000 0x00401000 0x5147d367 19/03/2013 04:54:31

halmacpi.dll 0x83020000 0x83057000 0x00037000 0x4a5bbf07 14/07/2009 01:11:03

kdcom.dll 0x80bac000 0x80bb4000 0x00008000 0x4a5bdaaa 14/07/2009 03:08:58

mcupdate_GenuineIntel.dll 0x89003000 0x8907b000 0x00078000 0x4a5bda21 14/07/2009 03:06:41

PSHED.dll 0x8907b000 0x8908c000 0x00011000 0x4a5bdad0 14/07/2009 03:09:36

BOOTVID.dll 0x8908c000 0x89094000 0x00008000 0x4a5bd9a2 14/07/2009 03:04:34

CLFS.SYS 0x89094000 0x890d6000 0x00042000 0x4a5bbf0e 14/07/2009 01:11:10

CI.dll 0x890d6000 0x89181000 0x000ab000 0x4a5bdac8 14/07/2009 03:09:28

piokkmbp.sys 0x89181000 0x8918e300 0x0000d300 0x4a9ee5b5 02/09/2009 23:37:57

Wdf01000.sys 0x8918f000 0x89210000 0x00081000 0x5010ac41 26/07/2012 04:32:33

WDFLDR.SYS 0x89210000 0x8921e000 0x0000e000 0x5010ad36 26/07/2012 04:36:38

ACPI.sys 0x8921e000 0x89266000 0x00048000 0x4a5bbf0f 14/07/2009 01:11:11

WMILIB.SYS 0x89266000 0x8926f000 0x00009000 0x4a5bbf1a 14/07/2009 01:11:22

msisadrv.sys 0x8926f000 0x89277000 0x00008000 0x4a5bbf0d 14/07/2009 01:11:09

pci.sys 0x89277000 0x892a1000 0x0002a000 0x4a5bbf14 14/07/2009 01:11:16

vdrvroot.sys 0x892a1000 0x892ac000 0x0000b000 0x4a5bc74b 14/07/2009 01:46:19

partmgr.sys 0x892ac000 0x892bd000 0x00011000 0x4f641a99 17/03/2012 07:01:13

compbatt.sys 0x892bd000 0x892c5000 0x00008000 0x4a5bc0f6 14/07/2009 01:19:18

BATTC.SYS 0x892c5000 0x892d0000 0x0000b000 0x4a5bc0f3 14/07/2009 01:19:15

volmgr.sys 0x892d0000 0x892e0000 0x00010000 0x4a5bbf1d 14/07/2009 01:11:25

volmgrx.sys 0x892e0000 0x8932b000 0x0004b000 0x4a5bbf2d 14/07/2009 01:11:41

intelide.sys 0x8932b000 0x89332000 0x00007000 0x4a5bbf17 14/07/2009 01:11:19

PCIIDEX.SYS 0x89332000 0x89340000 0x0000e000 0x4a5bbf13 14/07/2009 01:11:15

mountmgr.sys 0x89340000 0x89356000 0x00016000 0x4a5bbf1f 14/07/2009 01:11:27

atapi.sys 0x89356000 0x8935f000 0x00009000 0x4a5bbf13 14/07/2009 01:11:15

ataport.SYS 0x8935f000 0x89382000 0x00023000 0x4a5bbf16 14/07/2009 01:11:18

msahci.sys 0x89382000 0x8938c000 0x0000a000 0x4a5bc72e 14/07/2009 01:45:50

amdxata.sys 0x8938c000 0x89395000 0x00009000 0x4ba3a3f5 19/03/2010 18:19:01

fltmgr.sys 0x89395000 0x893c9000 0x00034000 0x4a5bbf11 14/07/2009 01:11:13

fileinfo.sys 0x893c9000 0x893da000 0x00011000 0x4a5bc18f 14/07/2009 01:21:51

Ntfs.sys 0x89438000 0x89567000 0x0012f000 0x5167f2a5 12/04/2013 13:40:21

msrpc.sys 0x89567000 0x89592000 0x0002b000 0x4a5bbf3f 14/07/2009 01:11:59

ksecdd.sys 0x89592000 0x895a5000 0x00013000 0x4fc97bae 02/06/2012 04:34:22

cng.sys 0x895a5000 0x89602000 0x0005d000 0x4fc980d8 02/06/2012 04:56:24

pcw.sys 0x89602000 0x89610000 0x0000e000 0x4a5bbf0e 14/07/2009 01:11:10

Fs_Rec.sys 0x89610000 0x89619000 0x00009000 0x4f4eecfd 01/03/2012 05:29:01

ndis.sys 0x89619000 0x896d0000 0x000b7000 0x4a5bbf58 14/07/2009 01:12:24

NETIO.SYS 0x896d0000 0x8970e000 0x0003e000 0x4a5bbf63 14/07/2009 01:12:35

ksecpkg.sys 0x8970e000 0x89733000 0x00025000 0x4fc9810e 02/06/2012 04:57:18

tcpip.sys 0x89837000 0x89981000 0x0014a000 0x50e6424b 04/01/2013 04:45:31

fwpkclnt.sys 0x89981000 0x899b2000 0x00031000 0x50e64206 04/01/2013 04:44:22

vmstorfl.sys 0x899b2000 0x899ba380 0x00008380 0x4a5bc32c 14/07/2009 01:28:44

volsnap.sys 0x899bb000 0x899fa000 0x0003f000 0x4a5bbf26 14/07/2009 01:11:34

spldr.sys 0x899fa000 0x89a02000 0x00008000 0x4a084ebb 11/05/2009 18:13:47

rdyboost.sys 0x89a02000 0x89a2f000 0x0002d000 0x4a5bc19a 14/07/2009 01:22:02

mup.sys 0x89a2f000 0x89a3f000 0x00010000 0x4a5bbfc6 14/07/2009 01:14:14

hwpolicy.sys 0x89a3f000 0x89a47000 0x00008000 0x4a5bbf05 14/07/2009 01:11:01

fvevol.sys 0x89a47000 0x89a79000 0x00032000 0x51009fc1 24/01/2013 04:43:13

disk.sys 0x89a79000 0x89a8a000 0x00011000 0x4a5bbf20 14/07/2009 01:11:28

CLASSPNP.SYS 0x89a8a000 0x89aaf000 0x00025000 0x4a5bbf18 14/07/2009 01:11:20

cdrom.sys 0x89ae2000 0x89b01000 0x0001f000 0x4a5bbf1c 14/07/2009 01:11:24

aswSnx.SYS 0x89b01000 0x89b9b000 0x0009a000 0x4f56a5e5 07/03/2012 02:03:49

ImmunetProtect.sys 0x89b9b000 0x89ba5980 0x0000a980 0x52f16e55 05/02/2014 00:48:53

ImmunetSelfProtect.sys 0x89ba6000 0x89bac780 0x00006780 0x52f16ea8 05/02/2014 00:50:16

Null.SYS 0x89bad000 0x89bb4000 0x00007000 0x4a5bbf10 14/07/2009 01:11:12

Beep.SYS 0x89bb4000 0x89bbb000 0x00007000 0x4a5bc6fc 14/07/2009 01:45:00

vga.sys 0x89bbb000 0x89bc7000 0x0000c000 0x4a5bc27e 14/07/2009 01:25:50

VIDEOPRT.SYS 0x89bc7000 0x89be8000 0x00021000 0x4a5bc27d 14/07/2009 01:25:49

watchdog.sys 0x89be8000 0x89bf5000 0x0000d000 0x4a5bc21a 14/07/2009 01:24:10

RDPCDD.sys 0x89bf5000 0x89bfd000 0x00008000 0x4a5bcae4 14/07/2009 02:01:40

rdpencdd.sys 0x89800000 0x89808000 0x00008000 0x4a5bcae3 14/07/2009 02:01:39

rdprefmp.sys 0x89808000 0x89810000 0x00008000 0x4a5bcae5 14/07/2009 02:01:41

Msfs.SYS 0x89810000 0x8981b000 0x0000b000 0x4a5bbf1e 14/07/2009 01:11:26

Npfs.SYS 0x8981b000 0x89829000 0x0000e000 0x4a5bbf23 14/07/2009 01:11:31

tdx.sys 0x89733000 0x8974a000 0x00017000 0x4a5bbf4a 14/07/2009 01:12:10

TDI.SYS 0x89829000 0x89834000 0x0000b000 0x4a5bbf4c 14/07/2009 01:12:12

afd.sys 0x8974a000 0x897a4000 0x0005a000 0x4db4ddf9 25/04/2011 04:35:37

netbt.sys 0x897a4000 0x897d6000 0x00032000 0x4a5bbf52 14/07/2009 01:12:18

ws2ifsl.sys 0x897d6000 0x897df000 0x00009000 0x4a5bc955 14/07/2009 01:55:01

wfplwf.sys 0x897df000 0x897e6000 0x00007000 0x4a5bc90f 14/07/2009 01:53:51

pacer.sys 0x89400000 0x8941f000 0x0001f000 0x4a5bc916 14/07/2009 01:53:58

netbios.sys 0x8941f000 0x8942d000 0x0000e000 0x4a5bc912 14/07/2009 01:53:54

wanarp.sys 0x897e6000 0x897f9000 0x00013000 0x4a5bc956 14/07/2009 01:55:02

termdd.sys 0x893da000 0x893ea000 0x00010000 0x4a5bcadf 14/07/2009 02:01:35

rdbss.sys 0x93c1d000 0x93c5e000 0x00041000 0x4a5bbfd2 14/07/2009 01:14:26

nsiproxy.sys 0x93c5e000 0x93c68000 0x0000a000 0x4a5bbf48 14/07/2009 01:12:08

mssmbios.sys 0x93c68000 0x93c72000 0x0000a000 0x4a5bc0fd 14/07/2009 01:19:25

discache.sys 0x93c72000 0x93c7e000 0x0000c000 0x4a5bc214 14/07/2009 01:24:04

csc.sys 0x93c7e000 0x93ce2000 0x00064000 0x4a5bbffc 14/07/2009 01:15:08

dfsc.sys 0x93ce2000 0x93cfa000 0x00018000 0x4db78089 27/04/2011 04:33:45

blbdrive.sys 0x93cfa000 0x93d08000 0x0000e000 0x4a5bc1d8 14/07/2009 01:23:04

tunnel.sys 0x93d08000 0x93d29000 0x00021000 0x4a5bc91b 14/07/2009 01:54:03

intelppm.sys 0x93d29000 0x93d3b000 0x00012000 0x4a5bbf07 14/07/2009 01:11:03

igdkmd32.sys 0x94023000 0x9452c000 0x00509000 0x4aba7471 23/09/2009 21:18:09

dxgkrnl.sys 0x9452c000 0x945e3000 0x000b7000 0x4ccf7981 02/11/2010 04:37:53

dxgmms1.sys 0x945e3000 0x9461c000 0x00039000 0x4d4a2259 03/02/2011 05:34:49

usbuhci.sys 0x9461c000 0x94627000 0x0000b000 0x4d8c06a1 25/03/2011 05:06:09

USBPORT.SYS 0x94627000 0x94672000 0x0004b000 0x4d8c06ae 25/03/2011 05:06:22

usbehci.sys 0x94672000 0x94681000 0x0000f000 0x4d8c06a4 25/03/2011 05:06:12

HDAudBus.sys 0x94681000 0x946a0000 0x0001f000 0x4a5bc85f 14/07/2009 01:50:55

b57nd60x.sys 0x946a0000 0x946dc000 0x0003c000 0x49f44256 26/04/2009 13:15:34

netw5v32.sys 0x96030000 0x96443000 0x00413000 0x49cba8fd 26/03/2009 18:10:37

1394ohci.sys 0x96443000 0x9646f000 0x0002c000 0x4a5bc89f 14/07/2009 01:51:59

sdbus.sys 0x9646f000 0x96488000 0x00019000 0x4a5bc0fe 14/07/2009 01:19:26

rimmptsk.sys 0x96488000 0x96497000 0x0000f000 0x45dfd03d 24/02/2007 07:42:21

rimsptsk.sys 0x96497000 0x964ab000 0x00014000 0x45b5bbe3 23/01/2007 09:40:19

rixdptsk.sys 0x964ab000 0x964fc000 0x00051000 0x46012cca 21/03/2007 15:02:02

i8042prt.sys 0x964fc000 0x96514000 0x00018000 0x4a5bbf1b 14/07/2009 01:11:23

kbdclass.sys 0x96514000 0x96521000 0x0000d000 0x4a5bbf13 14/07/2009 01:11:15

mouclass.sys 0x96521000 0x9652e000 0x0000d000 0x4a5bbf13 14/07/2009 01:11:15

CmBatt.sys 0x9652e000 0x96531700 0x00003700 0x4a5bc0f6 14/07/2009 01:19:18

wmiacpi.sys 0x96532000 0x9653b000 0x00009000 0x4a5bc0f4 14/07/2009 01:19:16

CompositeBus.sys 0x9653b000 0x96548000 0x0000d000 0x4a5bc716 14/07/2009 01:45:26

serscan.sys 0x96548000 0x96550000 0x00008000 0x4a5bcdf6 14/07/2009 02:14:46

AgileVpn.sys 0x96550000 0x96562000 0x00012000 0x4a5bc954 14/07/2009 01:55:00

rasl2tp.sys 0x96562000 0x9657a000 0x00018000 0x4a5bc939 14/07/2009 01:54:33

ndistapi.sys 0x9657a000 0x96585000 0x0000b000 0x4a5bc930 14/07/2009 01:54:24

ndiswan.sys 0x96585000 0x965a7000 0x00022000 0x4a5bc93a 14/07/2009 01:54:34

raspppoe.sys 0x965a7000 0x965bf000 0x00018000 0x4a5bc94d 14/07/2009 01:54:53

raspptp.sys 0x965bf000 0x965d6000 0x00017000 0x4a5bc947 14/07/2009 01:54:47

rassstp.sys 0x965d6000 0x965ed000 0x00017000 0x4a5bc951 14/07/2009 01:54:57

rdpbus.sys 0x965ed000 0x965f7000 0x0000a000 0x4a5bcb20 14/07/2009 02:02:40

swenum.sys 0x965f7000 0x965f8380 0x00001380 0x4a5bc704 14/07/2009 01:45:08

ks.sys 0x965f9000 0x9662d000 0x00034000 0x4b8f2fc0 04/03/2010 05:57:52

umbus.sys 0x9662d000 0x9663b000 0x0000e000 0x4a5bc88a 14/07/2009 01:51:38

usbhub.sys 0x9663b000 0x9667f000 0x00044000 0x4d8c06c3 25/03/2011 05:06:43

NDProxy.SYS 0x9667f000 0x96690000 0x00011000 0x4a5bc933 14/07/2009 01:54:27

HdAudio.sys 0x96690000 0x966e0000 0x00050000 0x4a5bc892 14/07/2009 01:51:46

portcls.sys 0x966e0000 0x9670f000 0x0002f000 0x4a5bc864 14/07/2009 01:51:00

drmk.sys 0x9670f000 0x96728000 0x00019000 0x4a5bd2f5 14/07/2009 02:36:05

VSTAZL3.SYS 0x96728000 0x96765000 0x0003d000 0x48f68b0b 16/10/2008 02:30:03

VSTDPV3.SYS 0x946dc000 0x947de000 0x00102000 0x48f68b84 16/10/2008 02:32:04

VSTCNXT3.SYS 0x93d3b000 0x93df0000 0x000b5000 0x48f68ad9 16/10/2008 02:29:13

modem.sys 0x96765000 0x96772000 0x0000d000 0x4a5bc96c 14/07/2009 01:55:24

win32k.sys 0x97420000 0x97671000 0x00251000 0x00000000

Dxapi.sys 0x96772000 0x9677c000 0x0000a000 0x4a5bc265 14/07/2009 01:25:25

crashdmp.sys 0x9677c000 0x96789000 0x0000d000 0x4a5bc72e 14/07/2009 01:45:50

dump_dumpata.sys 0x96789000 0x96794000 0x0000b000 0x4a5bbf14 14/07/2009 01:11:16

dump_msahci.sys 0x96794000 0x9679e000 0x0000a000 0x4a5bc72e 14/07/2009 01:45:50

dump_dumpfve.sys 0x9679e000 0x967af000 0x00011000 0x4a5bbf6f 14/07/2009 01:12:47

monitor.sys 0x967af000 0x967ba000 0x0000b000 0x4a5bc286 14/07/2009 01:25:58

TSDDD.dll 0x97690000 0x97699000 0x00009000 0x00000000

cdd.dll 0x976c0000 0x976de000 0x0001e000 0x00000000

usbccgp.sys 0x967ba000 0x967d1000 0x00017000 0x4d8c06af 25/03/2011 05:06:23

USBD.SYS 0x967d1000 0x967d2700 0x00001700 0x4d8c069e 25/03/2011 05:06:06

usbvideo.sys 0x967d3000 0x967f6b80 0x00023b80 0x4b8f3158 04/03/2010 06:04:40

ATMFD.DLL 0x976e0000 0x9772d000 0x0004d000 0x00000000

luafv.sys 0x96000000 0x9601b000 0x0001b000 0x4a5bc020 14/07/2009 01:15:44

lltdio.sys 0x9601b000 0x9602b000 0x00010000 0x4a5bc8ee 14/07/2009 01:53:18

nwifi.sys 0x93df0000 0x93e36000 0x00046000 0x4a5bc89f 14/07/2009 01:51:59

ndisuio.sys 0x947de000 0x947ee000 0x00010000 0x4a5bc90f 14/07/2009 01:53:51

rspndr.sys 0x94000000 0x94013000 0x00013000 0x4a5bc8f0 14/07/2009 01:53:20

HTTP.sys 0x93e36000 0x93ebb000 0x00085000 0x4a5bbf75 14/07/2009 01:12:53

bowser.sys 0x93ebb000 0x93ed4000 0x00019000 0x4d649594 23/02/2011 07:05:24

mpsdrv.sys 0x947ee000 0x94800000 0x00012000 0x4a5bc8d4 14/07/2009 01:52:52

mrxsmb.sys 0x93ed4000 0x93ef7000 0x00023000 0x4dc0bd5c 04/05/2011 04:43:40

mrxsmb10.sys 0x93ef7000 0x93f32000 0x0003b000 0x4e17bc3f 09/07/2011 04:26:07

mrxsmb20.sys 0x93f32000 0x93f4d000 0x0001b000 0x4dc0bd63 04/05/2011 04:43:47

ImmunetNetworkMonitor.sys 0x93f65000 0x93f7f000 0x0001a000 0x52f16e4e 05/02/2014 00:48:46

peauth.sys 0xad036000 0xad0cd000 0x00097000 0x4a5bd2e0 14/07/2009 02:35:44

RVIEg01.sys 0xad0cd000 0xad0f42c0 0x000272c0 0x3ad6d205 13/04/2001 12:16:37

secdrv.SYS 0xad0f5000 0xad0ff000 0x0000a000 0x45080528 13/09/2006 15:18:32

srvnet.sys 0xad0ff000 0xad120000 0x00021000 0x4dba2908 29/04/2011 04:57:12

tcpipreg.sys 0xad120000 0xad12d000 0x0000d000 0x4a5bc926 14/07/2009 01:54:14

srv2.sys 0xad12d000 0xad17c000 0x0004f000 0x4dba290f 29/04/2011 04:57:19

srv.sys 0xad17c000 0xad1ce000 0x00052000 0x4dba291b 29/04/2011 04:57:31

mbamswissarmy.sys 0xad1ce000 0xad1d6000 0x00008000 0x4e807679 26/09/2011 14:56:25

Edited April 26, 2014 by joddle

[Starbuck]

Hi joddle,

 

When i check my minidump files using the instructions i gave earlier i get this:

 

http://img.photobucket.com/albums/v708/starbuck50/minid_zps7d79a351.png

 

as you can see, it's a lot easier to read.

[joddle]

Ah - so much to learn

 

Now I see - I get this - but what does it mean??? And why no blue screen in safe mode?

 

[ATTACH=CONFIG]1209.vB5-legacyid=2207[/ATTACH]

[Plastic Nev]

Hi Joddle, from everything I have found, the main error code of 0x0000007a points at two different things, for some strange reason it can be associated with either boot up problems, or printer problems.

However the second clue is the "Caused by driver ntoskrnl.exe", which is a vital part of boot up. Why that should be the cause of blue screens at the end of a Malwarebytes scan is a puzzle, however, someone has very kindly posted a video on Youtube showing how to download, and install a microsoft fix.

 

 

Have a look at that, it may answer the problem.

 

If not, the other possible causes for the original 0X0000007a error are printer problems, if a printer is installed, try uninstalling and a reinstall.

 

Nev.

[Dokie]

Here's Micro$$oft definition of safe mode.

http://windows.microsoft.com/en-us/windows/what-is-safe-mode#1TC=windows-7

Now I see - I get this - but what does it mean??? And why no blue screen in safe mode?

[joddle]

Thanks Nev - tried the hotfix but no joy with that - still blue screens - this time I was watching the file progression and it seemed to crash as it was checkng the programme files/Kodak folder - dose that help at all? will try uninstalling printers later tomorrow.

[Plastic Nev]

Yep, that is the next, especially now you say it crashed while on the Kodak files, totally uninstall the printer, I assume a Kodak one, then try again before reinstalling the printer.

If all is OK, but the problem returns after reinstalling the printer, it looks like some sort of conflict between the two. Let us know how you get on please.

 

Oh and to answer the question why does it not BSOD in safe mode is because in safe mode the drivers will not be active for the printer.

 

Nev.

[joddle]

Well I tried uninstalling the kodak printer but nothing changed - it still crashes.

 

I have run a little utility recommended to me to see what the crash is about and the results are posted below - perhaps they will mean something to someone! Where do I look now?

 

On Mon 28/04/2014 08:08:30 GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: win32k.sys (win32k+0x6E076)

Bugcheck code: 0x7A (0xFFFFFFFFC03FEB48, 0xFFFFFFFFC0000185, 0x6FB49880, 0xFFFFFFFFFFAD2174)

Error: KERNEL_DATA_INPAGE_ERROR

file path: C:\Windows\system32\win32k.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Multi-User Win32 Driver

Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

[DSTM]

Hi. Did you actually remove the Printer Drivers?

 

Try this.

 

Open the File menu in the Printers folder and select "Server Properties", then click on the "Drivers tab". You should see your printer listed in this window. Select it so that it's highlighted, then click the "Remove" button down below. This should delete Windows' official record of the driver, which will then cause it to prompt you for a new driver when you plug the printer back in.

 

[joddle]

Hi. Did you actually remove the Printer Drivers?

 

Try this.

 

Open the File menu in the Printers folder and select "Server Properties", then click on the "Drivers tab". You should see your printer listed in this window. Select it so that it's highlighted, then click the "Remove" button down below. This should delete Windows' official record of the driver, which will then cause it to prompt you for a new driver when you plug the printer back in.

 

I used the kodak unistall printer tool which I downloaded from their website. Can't actually see a printers folder - where should I be looking for that? There is not one under the device manager section - but what was there under "other devices" was an unknown device. I tried to uninstall it and it appeared to go but returned next time I rebooted.

Edited April 28, 2014 by joddle

[DSTM]

This should help you. The lower part of the pages tells you where to look and the top how to install drivers.

 

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/print_drivers_install_updatew.mspx?mfr=true

[joddle]

Well I seem to making some progress. I used the Acer update tools and downloaded the W7 drivers and installed them - now it does not blue screen in malwarebytes but it still exits the programme without finishing and now returnes to the desktop....

 

There were no chipset drivers on the Acer web for W7, only for vista - are they the same?

 

Also looked at previous post but as I had deleted the printer there are now no options to uninstall

[joddle]

Ahh a bit too soon - tried relaoding malwarebyes new version - it ran for a while then crashed the PC - when it trie to restart I had a black screen with reported it could not find boot and PX1 and other PX something errors and Broadcom error - never seen that before - after forcing shutdown the machine booted up again fine. Have now uninstalled malwarebytes.

[Dokie]

Ahh a bit too soon - tried relaoding malwarebyes new version - it ran for a while then crashed the PC - when it trie to restart I had a black screen with reported it could not find boot and PX1 and other PX something errors and Broadcom error - never seen that before - after forcing shutdown the machine booted up again fine. Have now uninstalled malwarebytes.

 

Hello joddle! Very strange that malwarebytes is crashing your machine. I don't know if this will help, but you could give it a try . It's new software from Malwarebytes and it's called Chameleon. Malwarebytes has a lot of new software.

https://www.malwarebytes.org/chameleon/

https://www.malwarebytes.org/downloads/#beta

[joddle]

Have tried that - it loads fine but when it runs it crashes themain programme after some time.

Also these crashes sometimes cause the machine to do a dskchk - not always but sometimes..

[DSTM]

I am starting to think the Hard Drive is on the way out.

Looks to me Windows is having issues reading some segments on the Hard Drive and crashing.

I would be backing up your data as a safety measure.

[joddle]

That had crossed my mind too - trouble is its not my PC but one a friend has given to me to try and fix - his IT knowledge is even worse than my own!!!

Putting in a new HDD is no issue for me but I dont have all his installation disks - or even the licence code for the OS which at sometime has been upgraded from Vista to W7 ultimate. Time for a chat with him methinks.....

[joddle]

I am now thinking of what I need for a complete rebuild on a new HDD - (not too scary as I have just done the same for 4 of my own PCs from XP to W7). Once I have located the W7 install disks and COA etc things should be pretty straightforward - but on the Acer site they only list 4 drivers in the W7 section for this PC (Acer aspire 7720) - so what do I use for the rest of the drivers - once the OS is loaded - the Vista ones? I can't seem to find any info on that aspect of a rebuild at all. I assume the reserved partition on the current machine is for Vista as that is what it was shipped with.

[DSTM]

Hi again. Download free "Speccy" and expand "Operating system" will give you the product key this system is using at the moment.

Write that down.

Next I would find all the drivers and download them to a flash drive in case you have an issue getting on the net, and install them straight off the flash drive.

 

http://www.piriform.com/speccy/download

 

Near 3am here and someone else will assist you finding all the correct drivers, I am sure.

 

HTH

[Plastic Nev]

Hi, Further to good advice and idea's from DSTM so far, in most cases where only Vista drivers are available, they should work. The two operating systems are actually very close any way. A good clue is that it was originally Vista, and then the upgrade was installed, and no doubt everything worked OK yet the drivers would all have been original.

 

However, before we go right down the road of new drives and reinstalling everything, lets have a look at the operating system itself as one thing we should try is the system file checker.

Do you know how to run sfc /scannow as administrator, in elevated mode?

If so try it, if not we can explain.

 

Nev.

[joddle]

Very bUsy day today so may not get around to these operations for a day or two yet - wil post results when I do - meanwhile thanks to you all for your input.

[DSTM]

I agree 100%. What that is worth?? Not much my friend, but very good observation on your part. I agree 100% Time to test the HD and maybe the RAM.Memtest86

You can do a sfc /scannow. it won't hurt one thing. Good luck. hope you find a solution.

http://support.microsoft.com/kb/929833

 

 

PS This reply won't last long!!

Your post won't last long because you are passing judgement on another member's post, and I am insulted.

[joddle]

OK - I did run sfc/ scannow as administrator in elevated mode and it ran OK but reported nothing wrong. -