Unexpected shutdown.

Win7 pro SP1

I had a blue-screen shutdown yesterday and the following startup gave
a message:
***********
C:\Windows\Minidump\093014-44023-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
**********
Does this mean there's a missing file, or a virus?
Peter

Peter Jason used his keyboard to write :
Win7 pro SP1

I had a blue-screen shutdown yesterday and the following startup gave
a message:
***********
C:\Windows\Minidump\093014-44023-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
**********
Does this mean there's a missing file, or a virus?
Peter

What you posted means nothing other than there is a dump file to read
and that will hopefully tell you why it crashed.

On 29 Sep 2014, Peter Jason wrote in
alt.windows7.general:

Win7 pro SP1

I had a blue-screen shutdown yesterday and the following startup gave
a message:
***********
C:\Windows\Minidump\093014-44023-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
**********
Does this mean there's a missing file, or a virus?

No, it doesn't.

Peter Jason wrote:
On Mon, 29 Sep 2014 19:49:00 -0400, Seth
wrote:

Peter Jason used his keyboard to write :
Win7 pro SP1

I had a blue-screen shutdown yesterday and the following startup gave
a message:
***********
C:\Windows\Minidump\093014-44023-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
**********
Does this mean there's a missing file, or a virus?
Peter
What you posted means nothing other than there is a dump file to read
and that will hopefully tell you why it crashed.

Searching
C:\Windows\Minidump\093014-44023-01.dmp
returned:
093014-44023-01.dmp
which won't open

I searched for this:
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
which returned..

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\K ernel_0_0_cab_1786e752\WER-69748-0.sysdata.xml

And in IE11 this gave:
******
?xml version="1.0" encoding="UNICODE"?

-SYSTEMINFO
massive snip
/SYSTEMINFO

Try BlueScreenView. Open the .dmp.

http://www.nirsoft.net/utils/blue_screen_view.html

Paul

On Mon, 29 Sep 2014 20:41:48 -0400, Paul wrote:

Peter Jason wrote:
On Mon, 29 Sep 2014 19:49:00 -0400, Seth
wrote:

Peter Jason used his keyboard to write :
Win7 pro SP1

I had a blue-screen shutdown yesterday and the following startup gave
a message:
***********
C:\Windows\Minidump\093014-44023-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
**********
Does this mean there's a missing file, or a virus?
Peter
What you posted means nothing other than there is a dump file to read
and that will hopefully tell you why it crashed.

Searching
C:\Windows\Minidump\093014-44023-01.dmp
returned:
093014-44023-01.dmp
which won't open

I searched for this:
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
which returned..

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\K ernel_0_0_cab_1786e752\WER-69748-0.sysdata.xml

And in IE11 this gave:
******
?xml version="1.0" encoding="UNICODE"?

-SYSTEMINFO
massive snip
/SYSTEMINFO

Try BlueScreenView. Open the .dmp.

http://www.nirsoft.net/utils/blue_screen_view.html

Paul

Many thanks Paul,
I downloaded this program, and it gave.....

093014-44023-01.dmp 29-Sep-14 5:22:25 PM
KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005
fffff800`039b26ca 00000000`00000000 00000000`0000004e
Msfs.SYS Msfs.SYS+2d96e50 Mailslot driver Microsoft®
Windows® Operating System Microsoft Corporation 6.1.7600.16385
(win7_rtm.090713-1255) x64 ntoskrnl.exe+75bc0
C:\Windows\Minidump\093014-44023-01.dmp 12 15 7601 301,425
30-Sep-14 8:42:15 AM



In the lower details pane two lines are in pink and these a

Msfs.SYS Msfs.SYS+2d96e50 fffff880`01a8d000
fffff8aa`01a98000 0x0000002a0000b000 0x4a5bc113 14-Jul-09
9:19:47 AM Microsoft® Windows® Operating System Mailslot driver
6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation
C:\Windows\system32\drivers\Msfs.SYS

ntoskrnl.exe ntoskrnl.exe+c0738 fffff800`03658000
fffff800`03c3d000 0x005e5000 0x531590fb 04-Mar-14
6:38:19 PM Microsoft® Windows® Operating System NT Kernel &
System 6.1.7601.18409 (win7sp1_gdr.140303-2144) Microsoft
Corporation C:\Windows\system32\ntoskrnl.exe

there are many other lines that I can post if needed.

Peter

On Tue, 30 Sep 2014 10:52:49 +1000 "Peter Jason" wrote in
article

On Mon, 29 Sep 2014 20:41:48 -0400, Paul wrote:

Peter Jason wrote:
On Mon, 29 Sep 2014 19:49:00 -0400, Seth
wrote:

Peter Jason used his keyboard to write :
Win7 pro SP1

I had a blue-screen shutdown yesterday and the following startup gave
a message:
***********
C:\Windows\Minidump\093014-44023-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
**********
Does this mean there's a missing file, or a virus?
Peter
What you posted means nothing other than there is a dump file to read
and that will hopefully tell you why it crashed.

Searching
C:\Windows\Minidump\093014-44023-01.dmp
returned:
093014-44023-01.dmp
which won't open

I searched for this:
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
which returned..

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\K ernel_0_0_cab_1786e752\WER-69748-0.sysdata.xml

And in IE11 this gave:
******
?xml version="1.0" encoding="UNICODE"?

-SYSTEMINFO
massive snip
/SYSTEMINFO

Try BlueScreenView. Open the .dmp.

http://www.nirsoft.net/utils/blue_screen_view.html

Paul

Many thanks Paul,
I downloaded this program, and it gave.....


Msfs.SYS Msfs.SYS+2d96e50 fffff880`01a8d000
fffff8aa`01a98000 0x0000002a0000b000 0x4a5bc113 14-Jul-09

I'd guess that Msfs is the file system. Something blew up.
It might be a transient fault caused by a memory failure or a cpu hiccup.
In the bad old days, PC's had far less memory than they do now, by two
orders of magnitude. Unfortunately, unlike "real" computers, PC's don't
have error-correcting memory so are subject to the occasional cosmic ray
hit or an error caused when the chip sustrate emits a charged particle
due to radioactive decay - rare, but it happens. Such errors are totally
random. If it's not reproducible, I'd ignore it.

Jason wrote:
On Tue, 30 Sep 2014 10:52:49 +1000 "Peter Jason" wrote in
article
On Mon, 29 Sep 2014 20:41:48 -0400, Paul wrote:

Peter Jason wrote:
On Mon, 29 Sep 2014 19:49:00 -0400, Seth
wrote:

Peter Jason used his keyboard to write :
Win7 pro SP1

I had a blue-screen shutdown yesterday and the following startup gave
a message:
***********
C:\Windows\Minidump\093014-44023-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
**********
Does this mean there's a missing file, or a virus?
Peter
What you posted means nothing other than there is a dump file to read
and that will hopefully tell you why it crashed.
Searching
C:\Windows\Minidump\093014-44023-01.dmp
returned:
093014-44023-01.dmp
which won't open

I searched for this:
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
which returned..

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\K ernel_0_0_cab_1786e752\WER-69748-0.sysdata.xml

And in IE11 this gave:
******
?xml version="1.0" encoding="UNICODE"?

-SYSTEMINFO
massive snip
/SYSTEMINFO
Try BlueScreenView. Open the .dmp.

http://www.nirsoft.net/utils/blue_screen_view.html

Paul
Many thanks Paul,
I downloaded this program, and it gave.....

Msfs.SYS Msfs.SYS+2d96e50 fffff880`01a8d000
fffff8aa`01a98000 0x0000002a0000b000 0x4a5bc113 14-Jul-09

I'd guess that Msfs is the file system. Something blew up.
It might be a transient fault caused by a memory failure or a cpu hiccup.
In the bad old days, PC's had far less memory than they do now, by two
orders of magnitude. Unfortunately, unlike "real" computers, PC's don't
have error-correcting memory so are subject to the occasional cosmic ray
hit or an error caused when the chip sustrate emits a charged particle
due to radioactive decay - rare, but it happens. Such errors are totally
random. If it's not reproducible, I'd ignore it.

I'm not getting any traction on this one.

The mailslot file system, seems to be mentioned in the same sentence
as "named pipes", so it's some kind of interprocess communications.
Maybe we'd need to be Comp.sci grads to say more...

http://msdn.microsoft.com/en-us/libr.../jj124408.aspx

If this happened on my machine, I'd need to collect more symptoms or
"strange coincidences".

If Peter had a memory problem, he'd probably have a long list
of crashes already under his belt.

Memory does fail, but on modern machines, memory errors
due to bus problems should be a lot more infrequent. The
memtest86+ program can be used for a basic memory check,
but I doubt this is going to find a "smoking gun".

http://www.memtest.org

Paul

On Mon, 29 Sep 2014 22:53:24 -0400, Paul wrote:

Jason wrote:
On Tue, 30 Sep 2014 10:52:49 +1000 "Peter Jason" wrote in
article
On Mon, 29 Sep 2014 20:41:48 -0400, Paul wrote:

Peter Jason wrote:
On Mon, 29 Sep 2014 19:49:00 -0400, Seth
wrote:

Peter Jason used his keyboard to write :
Win7 pro SP1

I had a blue-screen shutdown yesterday and the following startup gave
a message:
***********
C:\Windows\Minidump\093014-44023-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
**********
Does this mean there's a missing file, or a virus?
Peter
What you posted means nothing other than there is a dump file to read
and that will hopefully tell you why it crashed.
Searching
C:\Windows\Minidump\093014-44023-01.dmp
returned:
093014-44023-01.dmp
which won't open

I searched for this:
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
which returned..

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\K ernel_0_0_cab_1786e752\WER-69748-0.sysdata.xml

And in IE11 this gave:
******
?xml version="1.0" encoding="UNICODE"?

-SYSTEMINFO
massive snip
/SYSTEMINFO
Try BlueScreenView. Open the .dmp.

http://www.nirsoft.net/utils/blue_screen_view.html

Paul
Many thanks Paul,
I downloaded this program, and it gave.....

Msfs.SYS Msfs.SYS+2d96e50 fffff880`01a8d000
fffff8aa`01a98000 0x0000002a0000b000 0x4a5bc113 14-Jul-09

I'd guess that Msfs is the file system. Something blew up.
It might be a transient fault caused by a memory failure or a cpu hiccup.
In the bad old days, PC's had far less memory than they do now, by two
orders of magnitude. Unfortunately, unlike "real" computers, PC's don't
have error-correcting memory so are subject to the occasional cosmic ray
hit or an error caused when the chip sustrate emits a charged particle
due to radioactive decay - rare, but it happens. Such errors are totally
random. If it's not reproducible, I'd ignore it.

I'm not getting any traction on this one.

The mailslot file system, seems to be mentioned in the same sentence
as "named pipes", so it's some kind of interprocess communications.
Maybe we'd need to be Comp.sci grads to say more...

http://msdn.microsoft.com/en-us/libr.../jj124408.aspx

If this happened on my machine, I'd need to collect more symptoms or
"strange coincidences".

If Peter had a memory problem, he'd probably have a long list
of crashes already under his belt.

Memory does fail, but on modern machines, memory errors
due to bus problems should be a lot more infrequent. The
memtest86+ program can be used for a basic memory check,
but I doubt this is going to find a "smoking gun".

http://www.memtest.org

Paul

I fear it's blue-screening at every shutdown, and the latest error
message on subsequent startup is..

************
Problem signatu
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF8000395E6CA
BCP3: 0000000000000000
BCP4: 000000000000004E
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\093014-89060-01.dmp
C:\Users\Frank\AppData\Local\Temp\WER-198589-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

If the online privacy statement is not available, please read our
privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
****************

On 9/29/2014 7:23 PM, Peter Jason wrote:
Win7 pro SP1

I had a blue-screen shutdown yesterday and the following startup gave
a message:
***********
C:\Windows\Minidump\093014-44023-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
**********
Does this mean there's a missing file, or a virus?
Peter


It does help to know what application(s) were running when the Blue
Screen occurred.

I used to have trouble with some of the lesser common
hardware drivers. (Web Cams, Video TV/capture, scanners, etc.)
and some applications.

Peter Jason wrote:
On Mon, 29 Sep 2014 22:53:24 -0400, Paul wrote:

Jason wrote:
On Tue, 30 Sep 2014 10:52:49 +1000 "Peter Jason" wrote in
article
On Mon, 29 Sep 2014 20:41:48 -0400, Paul wrote:

Peter Jason wrote:
On Mon, 29 Sep 2014 19:49:00 -0400, Seth
wrote:

Peter Jason used his keyboard to write :
Win7 pro SP1

I had a blue-screen shutdown yesterday and the following startup gave
a message:
***********
C:\Windows\Minidump\093014-44023-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
**********
Does this mean there's a missing file, or a virus?
Peter
What you posted means nothing other than there is a dump file to read
and that will hopefully tell you why it crashed.
Searching
C:\Windows\Minidump\093014-44023-01.dmp
returned:
093014-44023-01.dmp
which won't open

I searched for this:
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
which returned..

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\K ernel_0_0_cab_1786e752\WER-69748-0.sysdata.xml

And in IE11 this gave:
******
?xml version="1.0" encoding="UNICODE"?

-SYSTEMINFO
massive snip
/SYSTEMINFO
Try BlueScreenView. Open the .dmp.

http://www.nirsoft.net/utils/blue_screen_view.html

Paul
Many thanks Paul,
I downloaded this program, and it gave.....
Msfs.SYS Msfs.SYS+2d96e50 fffff880`01a8d000
fffff8aa`01a98000 0x0000002a0000b000 0x4a5bc113 14-Jul-09
I'd guess that Msfs is the file system. Something blew up.
It might be a transient fault caused by a memory failure or a cpu hiccup.
In the bad old days, PC's had far less memory than they do now, by two
orders of magnitude. Unfortunately, unlike "real" computers, PC's don't
have error-correcting memory so are subject to the occasional cosmic ray
hit or an error caused when the chip sustrate emits a charged particle
due to radioactive decay - rare, but it happens. Such errors are totally
random. If it's not reproducible, I'd ignore it.
I'm not getting any traction on this one.

The mailslot file system, seems to be mentioned in the same sentence
as "named pipes", so it's some kind of interprocess communications.
Maybe we'd need to be Comp.sci grads to say more...

http://msdn.microsoft.com/en-us/libr.../jj124408.aspx

If this happened on my machine, I'd need to collect more symptoms or
"strange coincidences".

If Peter had a memory problem, he'd probably have a long list
of crashes already under his belt.

Memory does fail, but on modern machines, memory errors
due to bus problems should be a lot more infrequent. The
memtest86+ program can be used for a basic memory check,
but I doubt this is going to find a "smoking gun".

http://www.memtest.org

Paul

I fear it's blue-screening at every shutdown, and the latest error
message on subsequent startup is..

************
Problem signatu
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF8000395E6CA
BCP3: 0000000000000000
BCP4: 000000000000004E
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\093014-89060-01.dmp
C:\Users\Frank\AppData\Local\Temp\WER-198589-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

If the online privacy statement is not available, please read our
privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
****************


My problem is, I'm not finding any associations of that
file (Msfs.SYS), with any particular classes of problems.
The file name does show up in searches, so the file
has been heard of, but there's nothing negative recorded
against it.

What is the last software added to the system, before
the blue screen storm hit your system ?

Paul

"Peter Jason" wrote in message

On Mon, 29 Sep 2014 20:41:48 -0400, Paul wrote:

Peter Jason wrote:
On Mon, 29 Sep 2014 19:49:00 -0400, Seth

wrote:

Peter Jason used his keyboard to write :
Win7 pro SP1

I had a blue-screen shutdown yesterday and the following startup
gave a message:
***********
C:\Windows\Minidump\093014-44023-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
**********
Does this mean there's a missing file, or a virus?
Peter
What you posted means nothing other than there is a dump file to
read and that will hopefully tell you why it crashed.

Searching
C:\Windows\Minidump\093014-44023-01.dmp
returned:
093014-44023-01.dmp
which won't open

I searched for this:
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
which returned..

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\K ernel_0_0_cab_1786e752\WER-69748-0.sysdata.xml

And in IE11 this gave:
******
?xml version="1.0" encoding="UNICODE"?

-SYSTEMINFO
massive snip
/SYSTEMINFO

Try BlueScreenView. Open the .dmp.

http://www.nirsoft.net/utils/blue_screen_view.html

Paul

Many thanks Paul,
I downloaded this program, and it gave.....

093014-44023-01.dmp 29-Sep-14 5:22:25 PM
KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005
fffff800`039b26ca 00000000`00000000 00000000`0000004e
Msfs.SYS Msfs.SYS+2d96e50 Mailslot driver Microsoft®
Windows® Operating System Microsoft Corporation 6.1.7600.16385
(win7_rtm.090713-1255) x64 ntoskrnl.exe+75bc0
C:\Windows\Minidump\093014-44023-01.dmp 12 15 7601 301,425
30-Sep-14 8:42:15 AM



In the lower details pane two lines are in pink and these a

Msfs.SYS Msfs.SYS+2d96e50 fffff880`01a8d000
fffff8aa`01a98000 0x0000002a0000b000 0x4a5bc113 14-Jul-09
9:19:47 AM Microsoft® Windows® Operating System Mailslot driver
6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation
C:\Windows\system32\drivers\Msfs.SYS

ntoskrnl.exe ntoskrnl.exe+c0738 fffff800`03658000
fffff800`03c3d000 0x005e5000 0x531590fb 04-Mar-14
6:38:19 PM Microsoft® Windows® Operating System NT Kernel &
System 6.1.7601.18409 (win7sp1_gdr.140303-2144) Microsoft
Corporation C:\Windows\system32\ntoskrnl.exe

there are many other lines that I can post if needed.

Peter

Read this...
http://support2.microsoft.com/kb/275678

--

dadiOH
____________________________

Winters getting colder? Tired of the rat race?
Taxes out of hand? Maybe just ready for a change?
Check it out... http://www.floridaloghouse.net

On Tue, 30 Sep 2014 00:10:36 -0400, Paul wrote:

Peter Jason wrote:
On Mon, 29 Sep 2014 22:53:24 -0400, Paul wrote:

Jason wrote:
On Tue, 30 Sep 2014 10:52:49 +1000 "Peter Jason" wrote in
article
On Mon, 29 Sep 2014 20:41:48 -0400, Paul wrote:

Peter Jason wrote:
On Mon, 29 Sep 2014 19:49:00 -0400, Seth
wrote:

Peter Jason used his keyboard to write :
Win7 pro SP1

I had a blue-screen shutdown yesterday and the following startup gave
a message:
***********
C:\Windows\Minidump\093014-44023-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
**********
Does this mean there's a missing file, or a virus?
Peter
What you posted means nothing other than there is a dump file to read
and that will hopefully tell you why it crashed.
Searching
C:\Windows\Minidump\093014-44023-01.dmp
returned:
093014-44023-01.dmp
which won't open

I searched for this:
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
which returned..

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\K ernel_0_0_cab_1786e752\WER-69748-0.sysdata.xml

And in IE11 this gave:
******
?xml version="1.0" encoding="UNICODE"?

-SYSTEMINFO
massive snip
/SYSTEMINFO
Try BlueScreenView. Open the .dmp.

http://www.nirsoft.net/utils/blue_screen_view.html

Paul
Many thanks Paul,
I downloaded this program, and it gave.....
Msfs.SYS Msfs.SYS+2d96e50 fffff880`01a8d000
fffff8aa`01a98000 0x0000002a0000b000 0x4a5bc113 14-Jul-09
I'd guess that Msfs is the file system. Something blew up.
It might be a transient fault caused by a memory failure or a cpu hiccup.
In the bad old days, PC's had far less memory than they do now, by two
orders of magnitude. Unfortunately, unlike "real" computers, PC's don't
have error-correcting memory so are subject to the occasional cosmic ray
hit or an error caused when the chip sustrate emits a charged particle
due to radioactive decay - rare, but it happens. Such errors are totally
random. If it's not reproducible, I'd ignore it.
I'm not getting any traction on this one.

The mailslot file system, seems to be mentioned in the same sentence
as "named pipes", so it's some kind of interprocess communications.
Maybe we'd need to be Comp.sci grads to say more...

http://msdn.microsoft.com/en-us/libr.../jj124408.aspx

If this happened on my machine, I'd need to collect more symptoms or
"strange coincidences".

If Peter had a memory problem, he'd probably have a long list
of crashes already under his belt.

Memory does fail, but on modern machines, memory errors
due to bus problems should be a lot more infrequent. The
memtest86+ program can be used for a basic memory check,
but I doubt this is going to find a "smoking gun".

http://www.memtest.org

Paul

I fear it's blue-screening at every shutdown, and the latest error
message on subsequent startup is..

************
Problem signatu
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF8000395E6CA
BCP3: 0000000000000000
BCP4: 000000000000004E
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\093014-89060-01.dmp
C:\Users\Frank\AppData\Local\Temp\WER-198589-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

If the online privacy statement is not available, please read our
privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
****************


My problem is, I'm not finding any associations of that
file (Msfs.SYS), with any particular classes of problems.
The file name does show up in searches, so the file
has been heard of, but there's nothing negative recorded
against it.

What is the last software added to the system, before
the blue screen storm hit your system ?


Paul

Thanks to all, but I fixed it (tentatively) by removing a Shintaro
USB3.0 PCI-e host card (driver SHUUSB3PCIE)
http://www.mwave.com.au/product/shin...FdaCvQod9SgAVQ
I'd inserted into the motherboard (Gigabyte GA-X58A-UD7) PCIEX16_2
expansion slot. Although this card worked OK, something with it was
causing the problem.
Perhaps I should have inserted it into another slot?
http://download.gigabyte.eu/FileList...d7_v.2.0_e.pdf
Peter

Peter Jason wrote:
On Tue, 30 Sep 2014 00:10:36 -0400, Paul wrote:

Peter Jason wrote:
On Mon, 29 Sep 2014 22:53:24 -0400, Paul wrote:

Jason wrote:
On Tue, 30 Sep 2014 10:52:49 +1000 "Peter Jason" wrote in
article
On Mon, 29 Sep 2014 20:41:48 -0400, Paul wrote:

Peter Jason wrote:
On Mon, 29 Sep 2014 19:49:00 -0400, Seth
wrote:

Peter Jason used his keyboard to write :
Win7 pro SP1

I had a blue-screen shutdown yesterday and the following startup gave
a message:
***********
C:\Windows\Minidump\093014-44023-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
**********
Does this mean there's a missing file, or a virus?
Peter
What you posted means nothing other than there is a dump file to read
and that will hopefully tell you why it crashed.
Searching
C:\Windows\Minidump\093014-44023-01.dmp
returned:
093014-44023-01.dmp
which won't open

I searched for this:
C:\Users\Peter\AppData\Local\Temp\WER-69748-0.sysdata.xml
which returned..

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\K ernel_0_0_cab_1786e752\WER-69748-0.sysdata.xml

And in IE11 this gave:
******
?xml version="1.0" encoding="UNICODE"?

-SYSTEMINFO
massive snip
/SYSTEMINFO
Try BlueScreenView. Open the .dmp.

http://www.nirsoft.net/utils/blue_screen_view.html

Paul
Many thanks Paul,
I downloaded this program, and it gave.....
Msfs.SYS Msfs.SYS+2d96e50 fffff880`01a8d000
fffff8aa`01a98000 0x0000002a0000b000 0x4a5bc113 14-Jul-09
I'd guess that Msfs is the file system. Something blew up.
It might be a transient fault caused by a memory failure or a cpu hiccup.
In the bad old days, PC's had far less memory than they do now, by two
orders of magnitude. Unfortunately, unlike "real" computers, PC's don't
have error-correcting memory so are subject to the occasional cosmic ray
hit or an error caused when the chip sustrate emits a charged particle
due to radioactive decay - rare, but it happens. Such errors are totally
random. If it's not reproducible, I'd ignore it.
I'm not getting any traction on this one.

The mailslot file system, seems to be mentioned in the same sentence
as "named pipes", so it's some kind of interprocess communications.
Maybe we'd need to be Comp.sci grads to say more...

http://msdn.microsoft.com/en-us/libr.../jj124408.aspx

If this happened on my machine, I'd need to collect more symptoms or
"strange coincidences".

If Peter had a memory problem, he'd probably have a long list
of crashes already under his belt.

Memory does fail, but on modern machines, memory errors
due to bus problems should be a lot more infrequent. The
memtest86+ program can be used for a basic memory check,
but I doubt this is going to find a "smoking gun".

http://www.memtest.org

Paul
I fear it's blue-screening at every shutdown, and the latest error
message on subsequent startup is..

************
Problem signatu
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF8000395E6CA
BCP3: 0000000000000000
BCP4: 000000000000004E
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\093014-89060-01.dmp
C:\Users\Frank\AppData\Local\Temp\WER-198589-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

If the online privacy statement is not available, please read our
privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
****************

My problem is, I'm not finding any associations of that
file (Msfs.SYS), with any particular classes of problems.
The file name does show up in searches, so the file
has been heard of, but there's nothing negative recorded
against it.

What is the last software added to the system, before
the blue screen storm hit your system ?


Paul

Thanks to all, but I fixed it (tentatively) by removing a Shintaro
USB3.0 PCI-e host card (driver SHUUSB3PCIE)
http://www.mwave.com.au/product/shin...FdaCvQod9SgAVQ
I'd inserted into the motherboard (Gigabyte GA-X58A-UD7) PCIEX16_2
expansion slot. Although this card worked OK, something with it was
causing the problem.
Perhaps I should have inserted it into another slot?
http://download.gigabyte.eu/FileList...d7_v.2.0_e.pdf
Peter

Seems to be made by this company. Uses a 4 port USB3 chip
for the PCI Express bus. I cannot tell what brand of
chip it is. And they won't say.

http://www.heisei.com.tw/products/me...ess-host-card/

You would need to track down a better driver for it. Since you're
on Windows 7, the company that makes the *chip* might be a potential
source of a driver. Heisei appears to be clueless.

I don't have a ready list of companies that make four port
chips. It might be NEC/Renesas, it might be Asmedia (an Asus company).
There might be others with four port chips by now.

The only chip that had a rocky start, was Etron branded
chips. But I don't know if they make four port chips. I think
eventually there was a stable Etron driver.

In terms of slots, you have two x1 slots, and that is
where I'd put the thing. It really shouldn't make a
difference if the card is routed through the PCI Express
switch chip. Some video card slots in the past, did not
accept non-video cards, and that was some kind of BIOS
issue. A BIOS issue that could be fixed by a BIOS update
in some cases (the developers knew what was wrong).

Paul

Paul
I fear it's blue-screening at every shutdown, and the latest error
message on subsequent startup is..

************
Problem signatu
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF8000395E6CA
BCP3: 0000000000000000
BCP4: 000000000000004E
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\093014-89060-01.dmp
C:\Users\Frank\AppData\Local\Temp\WER-198589-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

If the online privacy statement is not available, please read our
privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
****************

My problem is, I'm not finding any associations of that
file (Msfs.SYS), with any particular classes of problems.
The file name does show up in searches, so the file
has been heard of, but there's nothing negative recorded
against it.

What is the last software added to the system, before
the blue screen storm hit your system ?


Paul

Thanks to all, but I fixed it (tentatively) by removing a Shintaro
USB3.0 PCI-e host card (driver SHUUSB3PCIE)
http://www.mwave.com.au/product/shin...FdaCvQod9SgAVQ
I'd inserted into the motherboard (Gigabyte GA-X58A-UD7) PCIEX16_2
expansion slot. Although this card worked OK, something with it was
causing the problem.
Perhaps I should have inserted it into another slot?
http://download.gigabyte.eu/FileList...d7_v.2.0_e.pdf
Peter

Seems to be made by this company. Uses a 4 port USB3 chip
for the PCI Express bus. I cannot tell what brand of
chip it is. And they won't say.

http://www.heisei.com.tw/products/me...ess-host-card/

You would need to track down a better driver for it. Since you're
on Windows 7, the company that makes the *chip* might be a potential
source of a driver. Heisei appears to be clueless.

I don't have a ready list of companies that make four port
chips. It might be NEC/Renesas, it might be Asmedia (an Asus company).
There might be others with four port chips by now.

The only chip that had a rocky start, was Etron branded
chips. But I don't know if they make four port chips. I think
eventually there was a stable Etron driver.

In terms of slots, you have two x1 slots, and that is
where I'd put the thing. It really shouldn't make a
difference if the card is routed through the PCI Express
switch chip. Some video card slots in the past, did not
accept non-video cards, and that was some kind of BIOS
issue. A BIOS issue that could be fixed by a BIOS update
in some cases (the developers knew what was wrong).

Paul

Thanks, I am using the two X1 slots already, one for a TV tuner
(Hauppauge WinTV-HVR-2200 (8940)) and one for a 4-port USB3.0 made by
Sunix? with a Renesas controller uPD720201, that works fine.

I wanted to use the other 2-port USB3 card but it didn't work in the
X8 or x16 slots.

I was careful to upgrade all the hardware drivers but the blue screen
developed anyway. I'll be happy with just one 4-port USB3 card.

PS: The problem did not occur when I used my SSD with Win8.1pro,
using all the common hardware. It blue-screend with Win7 only.

Peter