Sign in with
Sign up | Sign in
Your question

New Mesh PC BSOD problem

Last response: in Windows 7
Share
April 20, 2010 4:19:11 PM

Hi there !

My neighbours bought a brand new pc from mesh

http://www.meshcomputers.com/Default...UCT&KEY=792937

I hooked it up for them and did what i usually do for anyone i help with a new pc run windows update get av/firewall on etc.

PC runs fine for the rest of the evening but upon reboot in the morning it crashes 4 or 5 times with a bsod on bootup twice before making the desktop and 2 or 3 times once desktop had loaded and internet or program was used.

I spoke to mesh tech support who advised to format and reinstall operating system. This was done and pc again was fine for rest of the evening before crashing with bsod multiple times as the day before.

Most of the bsod seem to be either PFN_LIST_CORRUPT or DRIVER_IRQ_NOT_EQUAL

Who crashed it ? report is below

----------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 4/20/2010 2:28:53 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xD1 (0xFFFFF80000ACF052, 0x2, 0x8, 0xFFFFF80000ACF052)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\042010-23010-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 4/20/2010 2:25:16 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x9DC00, 0x3, 0x9DE00)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\042010-22822-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 4/20/2010 2:21:29 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x95B26, 0x0, 0x95C26)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\042010-22479-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 4/20/2010 6:41:00 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x403, 0xFFFFF6800007B6F0, 0x9930000099FDB825, 0xFFFFF6FC004CFED8)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\042010-16910-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 4/20/2010 6:38:05 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x9C744, 0x2, 0x9B543)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\042010-17300-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 4/20/2010 6:35:51 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x9D864, 0x0, 0x9D964)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\042010-17596-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 4/20/2010 6:32:29 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF88000A60B23, 0x0, 0xFFFFFFFFFFFFFF00)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\042010-17581-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

More about : mesh bsod problem

a b \ Driver
a b $ Windows 7
April 20, 2010 4:27:34 PM

If it's a new computer, return it.
New computers are supposed to work.

The more you do to fix the problem, the more likely the vendor will say it is your fault.

FYI - http://en.wikipedia.org/wiki/Ntoskrnl.exe
m
0
l
May 6, 2010 7:12:10 AM

I had a similar problem.

The problem is that Windbg doesnt always return the correct answers as a corrupt driver may return unusual results.

I take it that it worked ok out of the box but started having problems when you started installing software and drivers?

If so then my advice would be to do a clean install, make sure it is working ok before doing any Windows updates or loading anything onto the PC.

Then start loading everything up in the following order, do a burn in test before each modification (by Mod I mean driver install, software install, hardware install). At least hopefully you will find the culprit if after the last mod the PC starts playing up.
-----

1) Do the windows updates

then

Download and install

1) the latest BIOS for your PCs motherboard
2) the latest drivers for your PCs motherboard (e.g. HDD, LAN, onboard Sound etc)
3) the latest graphics drivers
4) the latest sound drivers

then start adding your peripherals and install the latest software and drivers for each one at a time.

Rgds

Phil

p.s. My problem was the graphics drives and a motherboard driver
m
0
l
Related resources
May 7, 2010 10:06:08 PM

If possible please uplaod the dmp files and I will run them.
I can get the driver details from there.
m
0
l
a b $ Windows 7
May 9, 2010 1:16:18 AM

Nazda69,

Have you attempted to boot from safemode and reverse any updates (perhaps it was a botched driver update) ?

Also, Microsoft does have an official Windows 7 Support Forum located here http://tinyurl.com/9fhdl5 . It is supported by product specialists as well as engineers and support teams. You may want to also check the threads available there for additional assistance and guidance.

Jessica
Microsoft Windows Client Team
m
0
l
!