Another BSOD topic..

[HolyBumble]

I usually run my Dell Inspiron 1525 laptop with Windows 7 Home Premium (32-bit) but in the last month I was told that running x64 was a better option. I formatted my hard drive (about a month ago) and installed an MSDN version of Windows 7 Pro x64. The first few days were fine but I soon started getting some BSOD. I can't recall ever getting them with my 32 install. I've googled a bit and nothing has seemed to fix it. It usually occurs when playing games, ripping/burning dvds or logging in to windows. Sometimes it will happen while simply browsing the web though.

I've uploaded the minidumps here if you are interested in looking at them. I also have a crash summary, generated by BlueScreenView, here.

If you need my system info, I've pasted it below.

Hidden: show

OS Name Microsoft Windows 7 Professional
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name R2D2
System Manufacturer Dell Inc.
System Model Inspiron 1525
System Type x64-based PC
Processor Intel(R) Core(TM)2 Duo CPU T6400 @ 2.00GHz, 2000 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Dell Inc. A08, 1/7/2008
SMBIOS Version 2.4
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "6.1.7601.17514"
User Name R2D2\Micah
Time Zone AUS Eastern Standard Time
Installed Physical Memory (RAM) 2.00 GB
Total Physical Memory 1.99 GB
Available Physical Memory 359 MB
Total Virtual Memory 3.98 GB
Available Virtual Memory 1.77 GB
Page File Space 1.99 GB
Page File C:\pagefile.sys

If anything else is needed, I'll happily provide it

[Dinwiddie]

Were you having problems when still running the 32bit OS ?

I don't have debugging tools to read the mini dump, but the blue screen error makes reference to potential memory issues, MEMORY_MANAGEMENT seems obvious, IRQL_NOT_LESS_OR_EQUAL is often RAM, but can be many things.
The Bad Pool Header could also relate to corrupt driver install among other things, but I'll bet on too little RAM if you weren't having problems before installing 64bit.

A 64bit OS is good/better, but not with only 2GB RAM. 64bit uses more RAM than 32bit. I don't know how much more, but
my 64bit system idles with 1.25+ GB RAM in use. I've got 1.85GB in use atm with only a few browsers open
(I do have Firefox set to cache to RAM as an SSD tweak, which ups it a tiny bit).
Have a look at Task Manager - Performance and see how much RAM is in use on your machine.

Have you run mem test to verify there are no memory errors ?

[-Slayer-]

I don't have debugging tools to read the mini dump,

Dinwiddie does this help, just ran the mini dumps in whocrashed.

Crash Dump Analysis

Hidden: show

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 29/07/2012 3:21:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072912-29484-01.dmp
This was probably caused by the following module: shareduserdata.sys (SharedUserData+0x0)
Bugcheck code: 0x1A (0x3452, 0x7FEFDE00000, 0xFFFFF70001081F38, 0xB560000000000000)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: shareduserdata.sys .
Google query: shareduserdata.sys MEMORY_MANAGEMENT




On Sun 22/07/2012 12:24:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072212-28969-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x19 (0x3, 0xFFFFFA8001820F20, 0x0, 0x0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 19/07/2012 10:18:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071912-38875-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x4CB3)
Bugcheck code: 0xA (0xFFFFFA8026A22048, 0x2, 0x1, 0xFFFFF80002B50366)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 which cannot be identified at this time.


On Thu 19/07/2012 9:33:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071912-41075-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41284, 0x335B001, 0x216F, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 18/07/2012 10:11:46 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071812-44148-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFFA802686C0F8, 0x2, 0x1, 0xFFFFF80002B88366)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

5 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

shareduserdata.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Grab this to look at the dump files it's quite good.
http://www.resplendence.com/whocrashed/

Free to download.
http://www.resplendence.com/download/wh ... dSetup.exe

[Dinwiddie]

Dinwiddie does this help

Yep - Possibly bad driver install, yes ?
Or a simple - "Your system configuration may be incorrect."
The comment "shareduserdata.sys " is still ambiguous. Relating to an unidentified driver ?
Maybe if HolyB troubleshoots from Clean Boot a software with conflicting driver can be found.
http://support.microsoft.com/kb/929135

Thanks for the links mate - Now I can be professional eh ! (been lazy about this for too long ).

HolyB still needs more RAM, but....

[HolyBumble]

Thanks Dinwiddie and -Slayer-! So it could either be a hardware of software issue? I downloaded installed all of the drivers direct from the Dell website when I installed Windows, but I'll run Driver Genius to see if that can update anything (I have a DG Pro key, I just have to find it..). I have run memtest86 and it completed successfully with no issues.

Is 2GB of ram really bad for 64? I've seen numerous times computers in stores running 64 bit with only 2gb of ram..

[Dinwiddie]

From the report it's not a hardware issue, driver or software.
Drivers can be corrupted on install. It's a matter of identifying which one stuffed up.

Is 2GB of ram really bad for 64? I've seen numerous times computers in stores running 64 bit with only 2gb of ram..

Not BAD (only sad ) , but look at the figures in my first post, or your own in Task Manager and see how much RAM you will have left for tasks and games. Of course how much RAM you need depends on the games you play, and how many tasks you run.
Basically - 64bit is no advantage with 2GB RAM, so you're probably better off with 32bit and free up some RAM.

Driver Genius - eh! No, better just getting them direct from Dell or, or hardware mfg, or if it's a driver for a software you use then from the publishers of that software. ie - Tages DRM has 64bit driver updates that can be used with games like The Witcher which was released with a 32bit version of Tages.

Note: I'm a compulsive editor, so in case you missed it - check the comment and link for Clean Boot in my previous post.

[v4moose]

who told you win64 would be better for your laptop?

at two gbs of ram it would be making sfa difference. shoulda stuck with plain ol 32bit.

Id recommend turning off every graphical bell and whistle win 7 has, to try and minimize the resources it consumes.

if its stable for normal usage after an hour, open up 50 firefox windows and see if it BSODS. if it does you know its a lack of ram issue.

[Dinwiddie]

Id recommend turning off every graphical bell and whistle win 7 has, to try and minimize the resources it consumes.

Yeah! I didn't mention that the 1.25+ GB at idle is with AERO off. Go 4GB RAM (minimum with 64bit, or 32bit Win7.

[steve_rogers42]

sounds like somethings loading up memory and causing it to crash, or power profile states causing it to crash...

Is it doing anything in particular when it crashes, or just when you leave it and come back to it?

[HolyBumble]

Thanks for all the replies guys! After a big of googling I think I'll just re-format my laptop and install Windows 7 x32 bit. Apparently you don't get as many BSOD while using that (and to my horrible memory, I don't recall ever getting one while running that).

[Dinwiddie]

Apparently you don't get as many BSOD while using that

Not with only 2GB RAM you don't. Win7 64bit has no inherent BSOD problem.